Accessibility audits that produce a fix list, not a score.
We assess digital products, documents, services, and physical experiences against WCAG 2.2, AODA, and the Accessible Canada Act — then hand your team a prioritised, developer-readable remediation backlog with retest built in.
What we audit.
- Web & apps
WCAG 2.2 A / AA conformance audits
Manual testing with screen readers (NVDA, JAWS, VoiceOver), keyboard-only navigation, magnification and reflow, colour and contrast, forms and error handling, plus automated scanning to catch the repeatable issues.
- Documents
Document & PDF accessibility
Tagging, reading order, alternative text, table structure, and remediation of reports, forms, and slide decks — with author training so the next document starts accessible.
- Compliance
AODA & Accessible Canada Act reviews
Obligations mapping, multi-year accessibility plans, feedback processes, statutory reporting support, and evidence packages for compliance filings.
- Procurement
Accessible procurement
RFP language, vendor conformance claim review (VPAT / ACR), and acceptance criteria so accessibility is contractual rather than aspirational.
- Service
Programs, events & spaces
Registration and intake journeys, event and venue accessibility, communications practice, and accommodation processes reviewed end to end.
How an audit runs.
- Week 1
Scope and sample
We agree the page and journey sample with you — key tasks, templates, and high-traffic content — and confirm the conformance target and testing environment.
- Weeks 2–3
Test
Manual assistive-technology testing against each applicable success criterion, supported by automated scans. Where possible, sessions include testers with lived experience of disability.
- Week 4
Report and backlog
Findings by criterion with severity, user impact, code-level location, and a suggested fix — delivered as a report plus an issue list your developers can import.
- After
Remediation support and retest
Office hours while your team fixes, then a verification pass and a conformance statement covering what was tested and what was not.
So you need fewer audits over time.
- Accessibility training for designers, developers, content authors, and procurement staff.
- Design system and component reviews, so fixes land once and apply everywhere.
- Acceptance criteria and QA checklists embedded in your existing delivery process.
- An internal champion program with quarterly clinics and a standing review channel.
Our own accessibility
This site is built to meet WCAG 2.2 level AA. If you hit a barrier here, or need any resource in a different format, email cometmoves@gmail.com and we will provide it and fix the source.
The barriers we find most often.
Nine in ten audits surface some version of this list. Knowing it in advance is usually enough to fix half of it before we arrive.
Keyboard traps and hidden focus
Custom menus, modals, and carousels that a mouse can operate and a keyboard cannot escape, or where the focus indicator is invisible.
Forms without programmatic labels
Placeholder text used instead of a label, error messages conveyed only by colour, and required fields announced to nobody.
Untagged PDFs
Reports published as scans or untagged exports — often the most important documents on the site, and the least readable to assistive technology.
Meaningless alternative text
"image1.png", decorative images announced at length, and charts whose data exists nowhere but the picture.
Contrast in the brand palette
Light grey body text, and a brand colour used for buttons that fails against white — usually inherited from a style guide nobody re-tested.
Video without captions
Auto-generated captions left unedited, no transcripts, and no audio description where the visual carries the meaning.
An audit you can hand straight to a developer.
- Findings mapped to the specific WCAG 2.2 success criterion, with level and severity.
- Plain-language description of the user impact — who is blocked and from what.
- The exact page, component, and code location, with a screenshot or recording.
- A recommended fix, and where a design system change would resolve it everywhere at once.
- A prioritised backlog in CSV or issue-tracker format, ordered by impact and effort.
- A conformance statement covering scope, method, tools, and what was not tested.
Tell us what you are trying to change.
Most engagements begin with a 30-minute scoping call. Bring the problem, the timeline, and whatever evidence you already have — we will tell you honestly whether we are the right partner, and what a realistic scope looks like.
- Fixed-fee scopes with deliverables agreed in writing before work starts.
- Not-for-profit and community rates, plus pro bono capacity each year.
- Bilingual delivery (English and French) and fully accessible materials.
- Every engagement leaves behind tools your team can use without us.