Check components for basic usability testing

[bengolder]

Inclusivity Score: basic usability check

Summary

For the components listed below, find out if code for america has tested their usability and whether there were any findings.

Details

• it may be useful to contact researchers or others who have conducted usability testing on GCF, SHIBA, or GYR.
• Mark components as untested if they haven't gone through usability testing.
• The database and form are one approach I thought might make this easier to document. Let me know if you have any feedback about how documentation or tracking could be easier.
• Reveal: Basic usability score #277

Components

This is a preliminary list. Please feel free to add, remove, or give feedback about the inclusion of any components in this list.

• Accordion
• Auto-formatted Input
• Document upload button
• Follow up question
• Reveal
• Buttons
• Checkboxes
• Data table
• Date select
• Pagination
• Progress Indicator
• Progress step bar
• Radio buttons
• Searchbar
• Select
• Steps
• Summary table
• Tab bar
• Text input
• Textarea
• Vertical steps

Acceptance

This task is complete when all of the listed components have a documented result for the specific Inclusivity Score control.
You can document the result here using this form.

[bengolder]

We should probably organize this into a list of components per app, so we can ask researchers who conducted usability testing on those apps whether they saw any issues with those components.

[bengolder]

I reviewed the research repositories & airtables that have documentation:
gcf research airtable
gcf product mapping

Learnings:

• there was only one component-specific finding in there, and it was that some clients interpret the "steps" as buttons and try to call the county using the big phone emoji in the steps.
• Most of the other findings indicate a lot of potential fixes and issues that are more about flow, language and new service features. These collectively seem more valuable to the clients than improvements to component usability.

[bengolder]

This is blocked and waiting on further input from qualitative research