Test, improve, and maintain

Define the scope

Inventory pages, documents, media, templates, third-party services, and important tasks. Record the target WCAG version and level and any additional legal or contractual requirements.

Include error states, authentication, mobile layouts, and complete processes. A successful homepage check does not establish that the site’s services are accessible.

Combine testing methods

• Automated checks: identify detectable structural and contrast issues.
• Keyboard testing: check access, sequence, visible focus, dialogs, and escape paths.
• Visual review: test contrast, zoom, reflow, text spacing, and motion.
• Screen reader testing: examine names, structure, state changes, and task completion.
• Content review: judge whether descriptions, captions, instructions, and errors are meaningful.
• User evaluation: involve disabled participants in realistic tasks.

Official guidance: Evaluating web accessibility

Record findings clearly

For each issue, record where it occurs, the affected task, the expected and actual behavior, reproduction steps, relevant criterion, user impact, owner, and verification result. Use screenshots or recordings as supplements to understandable written steps.

Prioritize barriers that prevent essential tasks while continuing to track all applicable failures. A priority ranking is not a conformance score.

Fix causes and retest

Repair shared components and templates when a problem repeats. Verify the specific fix, then recheck the full task for side effects. Document remaining limitations accurately.

Automated overlays or accessibility widgets do not replace accessible source content, usable interactions, and verified remediation.

Evaluate vendors and purchases

Request a current Accessibility Conformance Report, often based on a VPAT template, and review the product version, scope, test methods, and stated limitations. Ask vendors to demonstrate your essential tasks.

Use practical acceptance criteria, remediation responsibilities, and verification. A vendor report is evidence to assess, not a guarantee that a product works for your audience.

Create an ongoing program

• Assign accountable content, product, facilities, and procurement owners.
• Train authors and maintain accessible templates and components.
• Check new content and releases before publication.
• Provide a practical way to request access support and report barriers.
• Review third-party changes and repeat representative tests.
• Maintain an honest accessibility statement and improvement record.