10 guidelines to improve your web accessibility | Aerolab

  1. Do not depend on color
  2. Do not block zoom
  3. Rediscover the alt attribute
  4. Add subtitles and captions to your videos
  5. Semantics = accessibility
  6. Use the right mark-up
  7. Use roles when necessary
  8. On hiding elements
  9. Follow web accessibility standards
  10. Audit and review
10 guidelines to improve your web accessibility | Aerolab

Tagged with

Related links

Try text scaling support in Chrome Canary - Josh Tumath

There’s a new meta tag on the block. This time it’s for allowing system-level text sizing to apply to your website.

Tagged with

Developing an alt text button for images on my website | James’ Coffee Blog

I like the idea of adding this to personal websites:

Mastodon shows an “Alt” button in the bottom right of images that have associated alt text. This button, when clicked, shows the alt text the author has written for the image.

Tagged with

Tagged with

80 / 20 accessibility · marcus.io

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.

Tagged with

The Web Accessibility Cookbook

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.

Tagged with

Related posts

Style your underlines

Make your links beautiful and accessible.

Performative performance

When it comes to sustainable web design, the hard work is invisible.

The intersectionality of web performance

Business, sustainability, and inclusivity.

Assumption

Separate your concerns.

Overloading buttons

Can you have too much semantics?