Welcome to the Accessibility Audit Template!

Like many, we are committed to improving accessibility for our users. We made this checklist to scope out ways we can improve accessibility across the Coda platform, from the website to the onboarding flow to the doc surface. Accessibility auditing is a continual process and we wanted to create an easy reference for evaluation. The content in this doc reflects
(© WebAIM)ーjust with more bells and whistles as we are wont to do at Coda!

When you meet accessibility requirements, it means that your website or product...

“...is accessible to people with a diverse range of hearing, movement, sight, and cognitive ability. Thus
the impact of disability is radically changed on the Web because the Web removes barriers
to communication and interaction that many people face in the physical world.” -

Disclaimer:
WebAIM’s recommendations for Web Content Accessibility Guidelines (WCAG) 2 are based on an interpretation of WCAG’s criteria, but simplified and condensed for easier implementation. If you are looking to verify conformance for policy or law, you’ll want to reference official WCAG documentation.


Overview of the framework

Screen Shot 2020-08-14 at 8.44.44 AM.png

In this checklist, you’ll notice information is nested in a structure of principles, guidelines, success criteria, and levels.

are the high level concepts that provide the foundation for web accessibility:
.
are the basic objectives to work toward for accessible content across a wide range of abilities.
Success Criteria
are the specific scenarios to account for to meet requirements and conformance testing.
There are three levels of conformance:
Level A
(lowest),
Level AA
,
Level AAA
(highest). These levels build off of one another, so to pass conformance for Level AA, you must also pass for Level A.

When working with a team

Within the checklists, you’ll notice a few buttons and columns to work with:
Screen Shot 2020-08-14 at 9.06.51 AM.png
The
Claim
button assigns you as the auditor for the recommendation and bumps the row to
for review.
Add Task
will add a row in
for the team to work on. (You’ll want to select who is responsible for making the fix in that table.)
Conformance
is where you can mark what
each item meets: supports, partially supports, does not support, not applicable, or not evaluated.
And who doesn’t love a good old
Notes
column? You can use this to document some of the details as you go through your audit.

Ready to get started?

First, make a copy of this doc!

Copy Doc

Then, head to
for an all-up view of recommendations, or to the nested Level pages to work on conformance incrementally. Remember to check your
along the way!

This checklist is provided as a resource to help implement
(W3C Recommendation 5 June 2018), which is
© 2017-2018
®.
Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.