AODA Compliance Testing | WCAG-Based Accessibility Testing | TechnoAccess

Website Accessibility Testing

AODA Compliance Testing

AODA compliance testing evaluates digital accessibility through a combination of automated scanning, manual review, keyboard testing, assistive-technology checks, evidence collection and remediation guidance. A scanner alone cannot establish a complete accessibility picture.

Request an Accessibility Consultation Explore Accessibility Services

What is AODA compliance testing?

AODA compliance testing is a structured accessibility evaluation used to identify barriers that may prevent people from accessing or using website content and functionality. Effective testing considers both automated findings and issues that require human review.

The testing scope can include representative pages, navigation, forms, interactive components, documents, media, authentication flows and other important user journeys.

AODA compliance testing framework

1. Define the scopeIdentify the organization, website, templates, applications, pages and critical workflows to be evaluated.

2. Identify applicable requirementsReview the applicable AODA and Information and Communications requirements and establish the relevant accessibility criteria.

3. Map WCAG criteriaMap relevant website components and user journeys to the applicable WCAG success criteria.

4. Perform automated testingUse automated tools to identify detectable issues such as missing names, structural problems, contrast concerns and other machine-detectable failures.

5. Perform manual testingReview keyboard access, focus behaviour, headings, forms, links, error handling, dynamic content and other areas that automation may not reliably assess.

6. Document evidenceRecord affected pages or components, issue descriptions, relevant criteria, user impact and supporting evidence.

7. Prioritize remediationOrganize findings by impact, severity, frequency, user journey and implementation effort.

8. Retest fixesVerify that corrected issues have been resolved and that remediation has not introduced new accessibility barriers.

WCAG and AODA compliance

Ontario's regulation references WCAG 2.0 Level AA for applicable internet websites and web content. WCAG organizes accessibility around four principles: perceivable, operable, understandable and robust.

WCAG 2.1 and WCAG 2.2 provide newer accessibility guidance and may be useful as additional best-practice targets. Organizations should distinguish between the legal requirements applicable to their situation and broader accessibility best practices.

What does AODA compliance testing cover?

Page structure and semantic HTML
Headings, landmarks and navigation
Keyboard accessibility and visible focus
Forms, labels, instructions and error messages
Links, buttons and interactive controls
Images, alternative text and non-text content
Colour contrast and visual presentation
Responsive and mobile accessibility considerations
Dynamic content and status messages
Tables, PDFs and other digital content where included in scope
Representative user journeys and critical workflows

Why automated testing is not enough

Automated accessibility tools are valuable for detecting repeatable, machine-testable conditions, but many accessibility barriers require human judgement. Keyboard interaction, logical focus order, meaningful link purpose, form usability, error recovery and the quality of alternative text are examples that can require manual evaluation.

A stronger accessibility program therefore combines automated checks with manual testing and, where appropriate, testing with assistive technologies and representative users.

What should an accessibility test report include?

Testing scope and URLs or workflows reviewed
Testing methodology and tools used
Manual testing coverage
Accessibility findings and affected components
Relevant WCAG criteria or requirements
User impact and issue severity
Evidence or reproduction details
Recommended remediation
Retest status and outstanding issues

Compliance is an ongoing process

Accessibility can regress when websites change. New templates, content, plugins, third-party components, forms or application functionality can introduce new barriers. For that reason, accessibility testing works best as part of an ongoing design, development, content and quality-assurance process rather than as a single one-time scan.

Frequently Asked Questions

Does WCAG 2.2 automatically replace AODA requirements?

No. The supplied page content identifies WCAG 2.0 requirements in the AODA context. WCAG 2.1 or 2.2 can be considered as additional accessibility best-practice targets, but the applicable legal requirements should be assessed against the relevant regulation.

Can AODA compliance testing be performed before a website launches?

Yes. Testing during design and development can identify accessibility barriers before they reach production and can reduce the cost of remediation later.

Can automated tools provide a complete accessibility audit?

No. Automated tools can identify many detectable conditions, but a complete evaluation may also require manual testing and review of real user interactions and workflows.

What is the difference between testing and an accessibility audit?

Testing is the evaluation process used to identify accessibility issues. An audit generally packages the scope, methodology, findings, evidence, prioritization and recommendations into a formal assessment or report.

Need AODA compliance testing?

Discuss your website, web application, testing scope and reporting requirements with TechnoAccess.

Contact TechnoAccess