Accessibility Auditor User Research Study Request
Categories
(User Research :: Consultation, task)
Tracking
(Not tracked)
People
(Reporter: asa, Assigned: alrhee)
Details
Request Description
The current version of the accessibility inspector only involves inspecting individual elements for color contrast. The version we would like to ship in Q2 is a full page auditor that identifies all elements on a page that fail a color contrast check and is the basis for the fuller accessibility auditor we would like to build in the future.
Q: How understandable and usable is this auditor--both for web devs who currently use accessibility tools like Chrome’s accessibility report, and for web devs who are newer to accessibility on the web. Are there things we should change/adjust before adding in more accessibility checks to this template?
Q: We’d like to validate that the direction that we are moving in with our roadmap (integrating the accessibility inspector with the inspector tool so that devs can identify accessibility issues and fix on-the-spot) is the right direction for web developers’ workflows.
Q: How accessible is the tool itself (for users who use screen readers)?
Deadline
The contrast auditor tool we’d like to evaluate will land in Nightly this week (or early next) - it will be the template for future auditors. The easiest time to make changes for us would be before the 2nd week of May.
Priority Level
P1
Priority Level Description
One of our Q2 OKRs is completing this work. There are no other large scale accessibility features this quarter.
Comment 1•7 years ago
|
||
Hi Asa!
For 2019, we are relying on our design team to run usability tests. Is this something Victoria (?) could potentially take on? We are happy to advise of course.
Comment 2•7 years ago
|
||
Update from Alice: Asa told me he would reach out to Victoria
Updated•7 years ago
|
Description
•