Accessible websites for public institutions: where to start
A public website should let people reach the service they need across devices and with assistive technology. That means reviewing the interface alongside its content, documents and application journeys.
Set the scope and target first
WCAG sets testable criteria for web accessibility. Choose the version and conformance level for a project after reviewing the institution's needs, applicable rules and the scope of the work.
WCAG 2 Level AA requires meeting the applicable Level A and AA criteria. Passing a few sample-page checks does not establish conformance for a whole site; assess the pages, documents and user journeys included in the agreed scope.
Four principles, one sentence each
WCAG is organised around four principles: content should be perceivable, the interface operable, information understandable and the code robust enough to work with assistive technologies. Text alternatives for meaningful images and keyboard access to controls are two practical examples.
A keyboard-only walkthrough is a useful starting point, but it covers only part of the work. Check form labels, heading structure, contrast and the information announced by a screen reader as well.
What to check first
Check text contrast, visible keyboard focus and text alternatives for meaningful images. If an announcement appears inside an image, make the same information available as page text.
Form fields need persistent labels; placeholder text is not a substitute. Heading levels should reflect the page structure. For moving content, assess the relevant WCAG criteria in context, including how long it moves and whether users can pause or stop it.
The PDF problem
A PDF made from scanned page images may lack selectable text, tags or a meaningful reading order. OCR can recognise text, but the document structure and reading order still need to be checked.
When the information can also live on a web page, make an HTML version easy to find. If a PDF is needed, test its text layer, tags, headings and reading order with assistive technology.
How to test
Automated scans can quickly flag some measurable issues, but they cannot establish accessibility on their own. A person still needs to judge whether alternative text is useful in context and whether the focus order guides users clearly.
A useful first pass combines automated checks, keyboard navigation and a screen-reader review of key journeys. Where possible, include testing with people who use the service, especially for critical tasks such as an application form.
A process, not a project
Accessibility remains part of publishing after launch. A short checklist for new images, headings, links and documents helps the editorial team keep that work in view as the site changes.