I admit I had a bit of fun writing the Dressed for the role piece. I don't own that apron, but the story did come as an inspiration from hearing about role=button in a codebase.
Here are some other things I've sadly been surprised to see or hear about personally:
- Adding
alt=""to every image doesn't mean you've handled alt text. - Wrapping text in an
<h2>makes it a heading, not just big and bold. - Putting
tabindex="0"everywhere doesn't mean your page is keyboard accessible. - Adding
aria-hidden="true"to something doesn't mean screen readers will ignore it. - Adding
role=applicationto it doesn't make your website an application. - Using a placeholder as a label doesn't mean your form has labels.
- Cranking up the font size doesn't mean you've made everything readable.
- Coding your links blue doesn't mean they're distinguishable.
- Running an automated audit and passing doesn't mean your site is accessible.
- Writing "click here" with an
aria-labelon top doesn't make your link descriptive. - Marking something as
aria-livedoesn't mean screen readers will announce it the way you think. - Writing a beautiful and compelling accessibility statement doesn't mean your site is accessible.
Some of these should go on aprons!