You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The condition of the ARIA Practices examples
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.
The text was updated successfully, but these errors were encountered:
Some feedback from Twitter:
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:
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.
The text was updated successfully, but these errors were encountered: