Making websites and documents accessible
Review the tasks visitors need to complete, improve website and document accessibility, and build manual checks into your publishing process.

A visitor needs to read your services, complete an enquiry or open a document. Accessibility work should start with those tasks, including the pages and files someone passes through to finish them.
Choose a few important journeys and test the complete process. Include a downloaded form, a booking service or a payment page if your website sends people there. Keep a record of the barriers, their effect and who will fix them.
Know which requirements apply
Ontario’s website accessibility guidance explains the AODA requirement for designated public sector organizations and businesses or non-profits with 50 or more employees. The covered public websites and web content must meet WCAG 2.0 Level AA, with exceptions for live captions and prerecorded audio description. Check the guidance’s scope, including the content publication dates and who controls the website.
That employee threshold concerns the specific website requirement. It doesn’t remove other accessibility duties, such as responding to requests for accessible information. Organizations in other jurisdictions or federally regulated sectors need to check their applicable rules separately.
For new work, specify a clear technical target in the project agreement. W3C’s WCAG overview explains versions 2.0, 2.1 and 2.2 and recommends using the latest version. WCAG 2.2 AA is a useful current target; distinguish it from the version named in a particular law.
Test the enquiry journey without a mouse
Use Tab and Shift+Tab to move through links and controls. Confirm that focus is visible, menus can be opened and closed, and nothing traps the keyboard or hides the focused item behind a banner.
Complete an enquiry with missing or incorrect information. Check that fields have useful labels, required information is explained and errors identify what needs fixing. Keep already-entered information where possible. W3C’s forms tutorial covers labels, instructions, validation and notifications.
Include the third-party booking or payment service in this test. Ask its supplier for remediation if it blocks the journey, and provide an accessible contact route while the issue is addressed.
Review reading, navigation and media
Use real heading styles in a meaningful order, descriptive link text and image alternatives that convey the image’s purpose. Check text contrast (WCAG AA asks for at least 4.5:1 for normal-sized text) and make sure instructions don’t depend on colour alone. Write in plain language, with short paragraphs and headings that say what follows.
Enlarge text and try a narrow window. Confirm the text and controls remain usable without clipped content. Review with a screen reader and with people who use assistive technology where you can. W3C’s Easy Checks give you a quick first pass before a fuller evaluation.
For recordings, provide accurate captions for speech and relevant sounds, plus the alternatives needed to communicate visual information. A transcript alone doesn’t address every video requirement. W3C’s media guidance explains captions, transcripts and audio description.
Fix documents at their source
Start in the Word document, spreadsheet or presentation that produces the download. Use headings, sensible reading order, meaningful links, image alternatives and simple tables with identified headers. An image of a printed page doesn’t provide the same access as structured text.
Microsoft’s accessible-PDF guidance recommends checking the source document and preserving accessibility tags when exporting. Review the resulting PDF too: confirm text can be selected, tags and reading order are useful, and links and forms work. The source file can pass its checker while the PDF still has problems.
For frequently updated information, consider an HTML page with an accessible download when a file is needed. Give documents descriptive names and a clear contact route for alternate formats. Make sure someone answers requests that come through it, and keep fixing the documents themselves.
Give ongoing publishing an owner
Prioritize a blocked enquiry or unreadable service document, then work through the remaining findings. Ask developers for manual and automated test evidence for the agreed standard. Automated scans can find some failures; they can’t confirm full conformance.
Add a short review step for new pages, PDFs and videos. Keep templates that preserve headings and labels, train the people updating content, and retest after a component or third-party service changes.
Talk to us if you need help reviewing the accessibility of your website and the documents it publishes.


