Their rules of engagement:
- Document a11y requirements via an org benchmark
- Every requirement must have a testable basis
- The web accessibility “check” = program building block
- Every “check” has an owner
- Ownership is distributed
10-stage process for integrating accessibility into enterprise:
- Establish a benchmark, e.g. WCAG 2
- Break down the requirements of web accessibility. Establish accessibility checks
- Determine which checks are machine-detectable vs hand-review
- Identify the roles & responsibilities of each discipline within the site production chain
- Map ownership of checks to production disciplines: nice matrix where for each WCAG checkpoint they assigned roles; e.g. 1.3.2 – dev, qa, ia
- Make room for accessibility information in project documentation, discipline deliverables and project artifacts.
- Creating scripts for automated testing
- Hand review
- Train delivery teams (by discipline): AT&T created their own style guide where every design element was fleshed out and documented (a11y included)
- Train QA to test for all machine-detecible and hand-review errors.
AT&T made sure to do role-based training & work. Also they made sure to divide the accessibility work between teams such that there’s no overlap; e.g. the QA team doesn’t check for the validity of alt text, that’s not their job, content writers do that.
One last important conclusion:
This is a project-based process so they do this with every new project; it is not an organization-wide process;