Tiny Accessibility Statement

I’m having a bit of a thing at the moment with MVPs (Minimum Viable Products). By that I mean finding the smallest version of an idea and getting a version of it finished. Then it can be tested, played with, jiggled around, and iterated on.

A popular way to document a web site’s level of accessibility is an ACR (Accessibility Conformance Report). This is usually done in the VPAT (Voluntary Product Accessibility Template) format. At the start of the report is usually a section on “Evaluation Methods Used” and “Accessibility support baseline” (which browsers and assisstive technology are supported, were tested against).

Another popular document is the Accessibility Statement. Here’s an example at the Web Accessibility Initiative. This usually includes “Measures to support accessibility” and “Compatibility with browsers and assistive technology”.

A little bit ACR, a little AS

As you might have noticed, there’s a bit of a crossover. I was wondering about this testing and support bit of these two documents specifically, and if there’s an MVP of that we could do.

So I pulled together a quick sketch of a TAS: a Tiny Accessibility Statement. And because I’m a developer I added some Shields.io badges. The TAS is also available as a gist.

Tiny Accessibility Statement

We are committed to ensuring digital accessibility for people with disabilities. We are continually improving the user experience for everyone, and applying the relevant accessibility standards

We did these checks to make our UI more accessible

• Design reviews using the WCAG POUR framework
• Added jest-axe to our unit tests
• Added cypress-axe to our end-to-end test
• Ran the DevTools version of Deque's aXe
• Used Microsoft's Accessibility Insights to do a manual assessment
• Included accessibility in our Pull Request code reviews

We tested with these browsers and assistive technology pairings

• NVDA on Chrome on Windows
• VoiceOver on Safari on MacOS
• VoiceOver on Safari on iOS
• TalkBack on Chrome on Android

We meet WCAG 2.1

• At Level A
• At Level AA

---

Show these for the ticked ones:

• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 
• 

What next?

I’m still working on the name. I want it to be another animal noise to pair well with the QAC (Quick Accessibility Checks) 🙈.

And it feels too long still. I think the next version will be something like:

• Added jest-axe to our unit tests
• Added cypress-axe to our end-to-end test
• Ran the DevTools version of Deque’s aXe
• Included accessibility in our Pull Request code reviews

and

We tested with these browsers and assistive technology pairings

• NVDA on Chrome on Windows
• VoiceOver on Safari on MacOS