Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User test expectations? #2

Open
davatron5000 opened this issue Aug 3, 2018 · 0 comments
Open

User test expectations? #2

davatron5000 opened this issue Aug 3, 2018 · 0 comments

Comments

@davatron5000
Copy link
Owner

davatron5000 commented Aug 3, 2018

Some feedback from Twitter:

I really love this idea, but I think there’s an elephant in the room: the Authoring Practices can be very theoretical, in user testing I saw people not get the keyboard strokes they (eg tabs) require and struggle to interact with the content. User testing still matters a lot

Currently a11y Nutrition Cards doesn't offer any code solutions so there's not much we can do at this point, but it makes sense to vet the expectations we're listing out (largely borrowed from the ARIA Practices site).

Based on a quick surf of the ARIA Practices repo issues, it does seem to heavily review patterns. But maybe that's naïve to assume.

I have some friends and corporations (Microsoft Accessibility Teams, Texas School for the Blind, a11yproject, network of a11y professionals, etc) that I can reach out to on:

  1. The condition of the ARIA Practices examples
  2. Initial impressions of what might need to be updated or clarified in a site like this.

My general feeling is that this is an immense amount of effort for user research and testing (or even coordination if we were to distribute this effort). I'm not opposed to it, just cognizant of that fact. I'm also not sure we'd be able to out-research or out-expertise the team of accessibility professionals on the W3C Web Accessibility Initiative.

I'm a fan of user testing assumptions, just don't want to re-invent the wheel and re-hash already hashed out arguments over screenreader verbosity and nuance.

@davatron5000 davatron5000 self-assigned this Aug 3, 2018
@davatron5000 davatron5000 removed their assignment Apr 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant