Support Manual User Testing

[bbertucc]

What problem is the feature trying to solve?

Equalify has no way of inputting user-test data.

Desired Solution

I think this would involve building a chrome extension for my web accessibility platform, Equalify. Equalify creates reports of issues and accessibility pros can use it for free to visualize trends in issues they find.

Everything is always open for discussion, but from my experience with Equalify, the Chrome extension would probably need to do two things:

1. Add an “Add to Equalify” left click menu option when using inspector that will send the selected code, website url, tag(s), “status”, and message to Equalify.
2. Add a quick key for screen reader users to do the same. Screen reader users won’t be using inspector. The code of the active element would be sent to Equalify, in addition to the other info (tags, message, website url, status).

Alternatives

There are no alternatives.

Technical Details

• We have an existing list of messages, tags, and statuses. Users will often select from existing info via an autocomplete, but they can also create their own messages or tags (status options are fixed).
• We have API endpoints in Eqalify that you can use to post material. A user would have to log in to the extension to use it (authentication is handled by oAUth).
• We’ll also need to send the page’s source code to Equalify, so we can eventually train ML to find patterns and build rules to perform better automated tests. …I’m still trying to figure out how we’re storing this data and handling it when the source code changes..
• Users who rely on assistive devices should be incorporated into every aspect of the development process (planning + coding + launch)