[05-Dec-2018 23:24:13 CST6CDT] PHP Fatal error: Uncaught Error: Call to undefined function add_action() in /home/ispeakin/public_html/wp-content/themes/unlimited/inc/customizer.php:3 Stack trace: #0 {main} thrown in /home/ispeakin/public_html/wp-content/themes/unlimited/inc/customizer.php on line 3 The $h!t I Wish I’d Been Told About #A11y – ispeakincode.com Skip to content

The $h!t I Wish I’d Been Told About #A11y

Posted in a11y, and web accessibility

Almost a year ago, I attended JSConf. It was amazing. I left that conference with SO many great takeaways, the biggest and most challenging for me was web accessibility.

For a few days following the event, I kept finding myself thinking more and more about how users that were blind, visually impaired, deaf, motor-impaired and so on would use the thing that I was working on. I was visualizing these people in my head struggling over the the most basic aspects, and suddenly it became real for me. I could see how bad the user experience was and I wanted to fix it ASAP!

But, where should I start? So, I turned to the internets and sought out to find the go to resources for web accessibility.

Step 1.: Audit the site

  1. W3C validate (this will help you fix heading errors, ect)
  2. Navigate the site strictly via tab. Can you tab logically and easily? If not, note where/how/why to fix.
  3. Automated tests. (ATs)
    • I use gulp, so lean towards using gulp-a11y (free)
    • There’s also tenon.io ($$)
    • I like running updated pages through WAVE. It’s not automated, but, I find the info regarding the errors helpful.
  4. Repeat 1-3 until no more errors. Seriously, do not pass ‘GO,’ do not collect $200. Do not move forward until your site passes these tests.

Some of my gotchas that made it to production for a sprint (or few):

  • The first rule of aria… – It seems as though #a11y newbies (me included) get aria-happy, the ATs will help catch errors here. Another good article on aria: HTML5 Accessibility Chops: notes on using ARIA.
  • Just because you have alt tags, doesn’t mean they are good ones. I had issues with alt text being the same as the text below the image. Sometimes it is ‘ok’ to have alt=” “. ATs will point this out too.
  • Out of order headings h1, h2, h4 … but no h3. 🙁

.: Knowing Where To Go For Help/Info

Information

Social

Testing

Frameworks

Transcriptions

Some history behind me writing this post. It took me a year to get to the point where I could say, confidently, I know where to look for good info on this topic.

And, here’s what I’d like to call my “Don’t do what I did” list (a.k.a. – chasing your tail around until you’re dizzy):

  1. The w3c – I love you, but I can’t read these docs without a constant drip IV of caffeine and a shock treatment for every time I fall asleep. (Of course I reference the w3c for accuracy, but NOT for how-to’s.) They, also, have a lot of content via the web accessibility initiative, but again…so much content/reading, yet, so few examples.
  2. MDN – In fairness, it looks like there have been a lot of updates here. When I was originally here, there were pages that were like… (╯°□°)╯︵ ┻━┻) f-this. No one can agree on best practices and until they do, we are not dealing with documentation. But, it’s still a cluster-mess if all you are trying to do is figure out how/where to get started.
  3. Finally – I was like… I just want examples!!! Someone, please, just show me some freaking examples!!! So, I went to see what the frameworks (bootstrap/foundation/ect) did for accessibility. Unfortunately, at the time, I was finding nothing, zero, zilch…However, I did find bootstrap plugins and forked repos that were accessible. I was so frustrated to see that these existed, but they were not being brought back to the main codebase:

Things on #3’s front are changing, as well, for the better and you now see some basic info in the docs. They even point out their color contrast flaws.

So, I was running into all these issues trying to find a good place to start. Eventually, I found Marcy Sutton’s article on how to audit a site for accessibility. YAY!