Accessibility helps people read your content, navigate your site and complete tasks using different devices and assistive technologies. Start with the journeys that matter to your customers, such as finding a service, requesting a quote or managing an account. The ten checks below help you find practical improvements. They are an initial review, not proof that a site meets every accessibility requirement.
1. Complete a task using the keyboard
Set the mouse aside and follow a familiar journey. Use Tab and Shift+Tab to move between interactive controls. Activate links with Enter and buttons with Enter or Space. Check that menus, forms and dialogs can be used without a mouse, and that focus does not become trapped. Record the exact step that fails instead of simply reporting that the page is inaccessible.
2. Keep the current position visible
A visible focus indicator shows which control will respond. Check it against different backgrounds and around fixed headers or banners. A skip link should let keyboard users bypass repeated navigation and should become visible when focused. Follow the W3C’s preliminary checks to review keyboard access and zoom behavior in a consistent way.
3. Organize headings and identify the language
Use real heading levels to express the page structure, rather than bold text alone. Nest subsections logically and avoid choosing a heading level just for its appearance. See the W3C’s heading guidance. The page’s declared language should match its content, including French and English versions, so assistive technology can use the appropriate pronunciation.
4. Describe an image’s purpose
Give informative images an alternative that conveys the useful information in context. An image that acts as a button or link needs its action or destination explained. Pure decoration should use an empty alternative, alt="". Complex charts also need an accessible explanation of their information. The W3C’s image tutorial helps distinguish these cases; avoid filling alternatives with search keywords.
5. Check contrast and instructions
Measure text against its actual background. WCAG’s AA text contrast criterion generally requires 4.5:1, or 3:1 for large text, defined as at least 18 point or 14 point bold, with specified exceptions. Check the full criterion for the content concerned. Use words or another clear indicator alongside color when identifying errors or required actions.
6. Enlarge content and check the layout
Increase browser zoom to 200% as an initial check. Text, controls and important messages should remain readable and usable. Also try a narrow phone display. Look for clipped labels, overlapping panels and content hidden behind fixed elements. Do not disable the visitor’s ability to zoom. These checks do not replace a complete assessment of resizing and reflow.
7. Make forms understandable
Provide persistent, programmatically associated labels for form controls; placeholder text alone is insufficient. Explain required fields and accepted formats before submission. Test a deliberate error in a test environment and check that the message identifies the problem and how to correct it. Preserve valid entries where feasible and provide a clear confirmation when the task succeeds.
8. Use native controls and handle changes carefully
Prefer built-in HTML buttons, links and form controls. Adding an ARIA role does not supply missing keyboard behavior. For custom controls and dynamic messages, involve the developer and test with assistive technology. The W3C’s ARIA guidance explains the responsibility that comes with these attributes. Landmarks organize page regions; live regions communicate certain updates. They serve different purposes.
9. Provide usable media alternatives
Review videos and audio with the W3C’s media accessibility guidance. Provide appropriate captions, transcripts and descriptions of essential visual information according to the content. Check controls with a keyboard. Prefer user-controlled playback, provide a way to pause moving content, and avoid flashing effects. Automatically generated captions need review for accuracy.
10. Track findings and repeat the checks
Record the page, language, device, browser, steps, expected result and observed barrier. Prioritize anything that prevents task completion. Automated tools can assist, but cannot determine accessibility on their own. Combine manual checks, appropriate assistive-technology testing and feedback from people with disabilities. Recheck after changing templates, forms or content, including both language versions.
When to ask for help
If a shared menu, theme component or form needs code changes, Nuagerie’s web development services can help define the work. Contact us with an affected page and reproducible steps. A focused review can establish priorities; a formal conformance assessment requires an agreed scope and a more comprehensive evaluation.
