{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

@darius I haven't studied this formally but the general sense I've gotten is that "attempt to anticipate all accessibility needs ahead of time" is an anti-pattern.

Most of what I've seen has emphasized, where possible, giving users the flexibility to set their own environments to be accessible, and putting effort to ensure the document or application doesn't break when changing -- and provides enough control points to change it in the first place -- in those ranges, rather than a discrete set of set paths.

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Gadfly (-booq-)

@darius Like this quote from an intro module to the W3C Digital Accessibility Foundations course ( w3.org/WAI/courses/foundations ):
"""
...

In this case, people with different types of “low vision” actually needed opposite things.

Accessibility is all about supporting that flexibility for different user needs.

Another point I want to make here is that the accessibility needs of people who are blind are totally different from what non-screen reader users with low vision need.

So even though they are often categorized together just under “visual disabilities”, they are very different needs.
"""
w3.org/2020/10/TPAC/w3cx-chall

1
2y
Replies