Web Accessiblity

As part of my UI/UX role at my job, I have been asked to assist with the project to make our website accessible to those using a screen reader.

Holy. Buckets.

This is no small task.

I mean, the really simple stuff that can make your site minimally usable? That’s relatively easy as long as you’re writing good code.

Actually trying to USE a website via a screen reader — even with the full use of my non-impaired vision? It’s a nightmare. (A hilarious nightmare if you tell your installed extension ChromeVox to have a female British accent at a slightly sped up speed)

This is kind of a big deal, and it’s really fascinating to read up on it and learn.

You can separate your site into zones (aria-roles) so that those using a screen reader can skip header content and menus and get right to the meat of your website.

You can add better attributes to things like menus and lists and links and buttons to help someone navigate your content.

Alt tags on images are very important — including empty ones when an image is just decoration.

And every form field should have a label with the correct markup so that a screen reader can hit upon a text box and actually tell the user what they’re expected to enter.

Your site should be completely navigable via keyboard.

If you’re interested in learning more, I recommend The Accessibility Project. One of the gentlest and most easily understood introductions to the ways we can make our website usable by more people.

… and yes, this means I’m looking into changing my blog theme again. My site’s not as bad as some, but the default 2014 theme for WordPress is accessible by default.

Now if you’ll excuse me, I’m going to ask the lovely British lady voice to read my short stories to me. =]