AT testing
User-flow and assistive-technology testing
A page can satisfy every success criterion in isolation and still leave a screen reader user unable to finish a checkout. Criteria are evaluated per page; tasks run across them.
Why journeys, not pages
Barriers cluster at the joins. Focus that vanishes when a dialog opens. A validation error announced nowhere. A multi-step form that resets on the way back. A confirmation that renders visually but never reaches the accessibility tree. Each of those can pass a page-level check and still end the task.
What we exercise
We agree the journeys that matter — registering, searching, purchasing, submitting, downloading — and run each end to end with the assistive technologies your users actually have. Where a journey fails, we record where it failed and what the user would experience at that moment.
How it complements an audit
A WCAG audit tells you which criteria are unmet. Journey testing tells you which of your users cannot do the thing they came to do. Reported together, they let you sequence remediation by consequence rather than by count.
Related
Other things we do
NIMAS XML production from print books
Validated NIMAS filesets built from your print PDFs, with alt text authored and the title carried through to NIMAC certification.
PDF/UAAccessible PDF remediation to PDF/UA
Tag trees, reading order, table headers and metadata remediated to PDF/UA (ISO 14289), delivered with a conformance report.
DocumentsRemediation of Word, PowerPoint, Excel and EPUB
The other formats your organisation publishes — brought up to standard so the same content works for every reader.
Send us a title and a deadline
Tell us the format you have and the format you need. We will tell you plainly whether the source converts cleanly, and what it takes.