#WCUS I’m glad that @RianKinney asked that question regarding accessibility and other policies.
It would be so cool if we could treat #a11y as an “everything-is-awesome” moment and not as a must-do.
Problem with that approach was aptly illustrated by Gutenberg being released in an inaccessible state.
I’d like to say I’m surprised we’re apparently still doing this despite $31,000 worth of audit, but I’m not.
Yes, it would be totally awesome if we didn’t have to say “you must” with regard to accessibility, but unfortunately the makers of the web have consistently demonstrated that that is literally the only way anything gets done.
For the first few years of my career as an accessibility practitioner, I worked on a series of projects whose final reports heavily focused on only the positive, including asking testers with disabilities to talk about what they liked, even on seriously inaccessible sites.
That approach wasn’t just partially ineffective, it was one hundred percent ineffective.
Absolutely none of the sites reported on were fixed, or even improved.
Those sites are still broken.
That’s what happens when you spend your time objecting to accessibility must-dos because they’re must-dos instead of realizing that, yes Matt, there really are things that developers and designers have consistently demonstrated they will not do unless you basically force them to do those things.
All of this also goes for privacy and codes of conduct.
Why do we have to keep saying this?