I didn’t know the Washington Post had a design system or that the system has this good section on accessibility.
So my observation is that 80% of the subject of accessibility consists of fairly simple basics that can probably be learnt in 20% of the time available. The remaining 20% are the difficult situations, edge cases, assistive technology support gaps and corners of specialised knowledge, but these are extrapolated to 100% of the subject, giving it a bad, anxiety-inducing and difficult reputation overall.
Manu’s book is available to pre-order now. I’ve had a sneak peek and I highly recommend it!
You’ll learn how to build common patterns written accessibly in HTML, CSS, and JavaScript. You’ll also start to understand how good and bad practices affect people, especially those with disabilities.
Another handy accessibility testing tool that can be used as a bookmarklet.
This is good advice:
Write alternative text as if you’re describing the image to a friend.
This is a really lovely little HTML web component from Jason. It does just one thing—wires up a trigger button to toggle-able content, taking care of all the ARIA for you behind the scenes.
Business, sustainability, and inclusivity.
Separate your concerns.
Can you have too much semantics?
The difference between inclusive design and accessibility.
Aiming for originality and creativity in alt text.