I went through the 128 questions that a11y.quest proposes

Published on

Soooo... I stumbled by chance upon a11y.quest, the free accessibility quiz by Dave Davies, and I went through all of its 128 questions expecting to be humbled from question one. You know, the classic let's find out how much I really don't know. πŸ˜…

Well... I was surprised!

The questions ramp up from easy to medium to hard, and I finished with 90 correct (which works out to about 70% accuracy), with a best streak of 9 in a row. Definitely better than I thought!

My a11y.quest score card showing 71% accuracy, 129 answered questions, 91 correct and a best streak of 9.
My score card, straight from a11y.quest! (And yes, it says 129 answered: the questions are 128, but they loop back around once you reach the end... and I just expected a score recap that never happened πŸ˜†)

On the practical side, I was mostly fine: contrast, keyboard interaction, forms, focus management... the hands-on questions all felt familiar enough (maybe I do know about a thing or two! :D).

But then two things got me, and got me good.

The obscure corners of ARIA

I would have told you I was comfortable with ARIA. Turns out I am comfortable with the same ten attributes everyone uses, and the quiz went waaaay past those. 😱 A little taste of the ones that got me:

  • Did you know that aria-relevant defaults to "additions text"? Meaning that removals from an aria-live region are not announced by default. But did you even know about aria-relevant, because I surely didn't 🀣
  • aria-valuetext is what lets a slider announce a friendly "Quiet" instead of a raw 25 (while aria-valuenow has to stay a number); and, you guessed, aria-valuetext and aria-valuenow were also unknown to me... ahhh πŸ˜…
  • I'll leave it here as it is... aria-atomic 🫠

A lot of these had me going ooooh, aha!, I see and a few oh god xD

The documents side of things

The other place I kept slipping was everything around how accessibility gets evaluated, documented and interpreted: the exact meaning of the conformance terms in a VPAT/ACR, the five steps of WCAG-EM, how ACT rules are structured, what ATAG actually asks of authoring tools, where EN 301 549 fits in Europe...

Acronyms for everyone!

The classic Oprah 'You get a car' meme, with Oprah shouting: 'You get an acronym, you get an acronym, everybody gets an acronym'.
The accessibility standards landscape, as best summarized by the classic Oprah's "You Get a Car" meme.

So, my biggest learning

Knowing how to build accessible UI is not the same as knowing how accessibility gets assessed and reported, and I want to know more about the latter. It is time to actually sit down with the WAI-ARIA spec, the APG patterns and the conformance documents, at least to familiarize more with all these wild acronyms!

If you are curious, you can see my a11y.quest score here and try the test for yourself β€” and if you do, come tell me in the comments which questions got you! :D


Sources and inspiration:
a11y.quest snippet cover
Thumbnail attribution(s):

My a11y.quest score card on a dark background: 71% accuracy, 129 answered, 91 correct, best streak of 9.



More Snippets

A beautiful Katamari-themed wedding

Beautiful pictures of a beautifully Katamari-themed wedding!

44

Unknown at rule @apply... k thx bye!

Are we finally done seeing all those "Unknown at rule @apply"?! Because I surely am!

424