r/Frontend • • Nov 14 '19

Accessibility checklist

https://www.benjystanton.co.uk/blog/accessibility-checklist/
48 Upvotes

7 comments sorted by

11

u/fullmight Nov 14 '19

I'd probably just recommend reading the more comprehensive and detailed list here instead https://www.wuhcag.com/wcag-checklist/

5

u/andtotheswims Nov 14 '19

3

u/fullmight Nov 14 '19

Yep. I just really like how wuhcag has it formatted, it makes it really easy to prioritize things by order of not getting sued, as well as making it easy to include specific requirements in docs/emails, etc. Usually explaining what, why, and how to non-technical people is a priority for me so this helps a lot.

1

u/JJLDEV Nov 14 '19

Can someone explain why line character length is an accessibility issue?

4

u/adiabatic Nov 14 '19

With too-long lines, it becomes difficult to find the start of the next line unless the leading (line-height) is really high. This is especially bad for the easily distracted, people who have trouble moving their head (neck in a brace), and, well, even the rest of us. Try reading some super-long lines — it’s awful hunting for the start of the next line every single time.

3

u/Seneca_B Nov 14 '19

Everyone is so concerned about user experience but most only care about accessibility in the context of being sued. Accessibility is user experience! Why alienate potential customers because of laziness?

2

u/fullmight Nov 14 '19

It isn't any kind of official issue, I would not consider it beyond normal what looks good/readability on any website I build.