Web accessibility means a website can be perceived, used and understood by everyone, including people with visual, hearing, motor or cognitive disabilities. WCAG (Web Content Accessibility Guidelines) is the international guideline the W3C publishes for that goal; the current version is WCAG 2.2, and most organizations aim for level AA. In this article we cover the basics of the guidelines, a checklist you can act on and how to test your site.
Accessibility is not a plugin you add before launch; it is the result of how a site is designed and built. In our website development projects, we weigh it in every decision, from the color palette to form errors, and the checklist below comes from that work.
What is WCAG, and what principles is it built on?
WCAG is published by the W3C (World Wide Web Consortium), the body behind web standards. The current version, WCAG 2.2, was published in 2023. It consists of testable success criteria grouped under four principles:
- Perceivable: information is presented in a way users can perceive. Images have text alternatives, and videos have captions.
- Operable: the interface works with a keyboard, not just a mouse, and users get enough time.
- Understandable: text is clear, the interface behaves predictably and errors are explained in plain terms.
- Robust: content works correctly across browsers and assistive technologies, including screen readers.
Each success criterion belongs to one of three conformance levels: A, AA and AAA. Level A removes the most critical barriers. AA is the widely accepted target for business websites. AAA is the most demanding level, and some types of content cannot fully meet it.
Who benefits from an accessible website?
People with disabilities come to mind first, and for them accessibility decides whether they can use a site at all. But the benefit reaches much further:
- People with disabilities: blind users on screen readers, deaf users who need captions, people who navigate by keyboard or voice and users who benefit from plain language.
- Older users: vision, hearing and fine motor skills change with age. High-contrast text and generous click targets help everyone.
- Temporary situations: an arm in a cast, blurred vision after an eye exam or a baby in one arm and a phone in the other.
- Situational limits: a phone screen in bright sunlight, or a crowded train where the sound cannot be turned on.
So accessibility is not a favor to a small group; it is part of the site's quality.
What should you check for an accessible website?
These items cover the most common WCAG 2.2 AA requirements, written so any team can check them:
- Text alternatives: every image that carries information has alternative text that describes its meaning. Decorative images use empty alt text so screen readers skip them.
- Captions and transcripts: videos have captions, and audio recordings have a text transcript.
- Color contrast: the contrast ratio between text and background is at least 4.5:1 for normal text and 3:1 for large text. Light gray text on a white background is the most common failure.
- Not relying on color alone: do not mark required fields or errors with red alone; add an icon or text.
- Keyboard access and visible focus: menus, buttons, forms and pop-ups all work with the keyboard alone. The focused element shows a clear outline that is never removed for the sake of design.
- Logical heading structure: each page has one main heading, and subheadings follow in order. Screen reader users move through a page by its headings.
- Form labels and errors: every field has a visible label; faint placeholder text is not a substitute. Error messages say in words which field is wrong and how to fix it.
- Descriptive link text: instead of "click here" or "read more," use link text that says where the link goes.
- Zoom and reflow: content stays intact when text is enlarged to 200 percent, and narrow screens need no horizontal scrolling. Never block users from zooming.
- Motion and reduced motion: auto-advancing carousels can be paused, users who turn on their system's reduce motion setting get a calmer experience and flashing content is avoided.
- Language attribute: the page language is declared with the lang attribute in the HTML. Screen readers use it to pronounce the text correctly.
- Accessible documents: PDFs contain real text rather than scanned images, with tagged headings and reading order. Information everyone needs belongs on the page itself where possible.
How do you test a website for accessibility?
Accessibility testing has three layers, and none of them is enough on its own:
- Automated tools: Lighthouse in Chrome and axe quickly find missing alt text, low contrast and unlabeled fields. But they catch only part of the issues; they cannot judge whether alt text describes the image or whether the focus order makes sense.
- Keyboard test: put the mouse aside and use the page with only Tab, Shift+Tab, Enter, Space and Esc. Can you reach every element, always see where the focus is and get out of a pop-up?
- Screen reader test: try the key flows with NVDA, which is free on Windows, or VoiceOver, which is built into Mac and iPhone: filling in a form, moving through the menu, adding a product to the cart.
A Lighthouse accessibility score of 100 does not mean a site is accessible; it only means the automated checks passed. Real confidence comes from keyboard and screen reader testing.
Where do accessibility and SEO overlap?
Screen readers and search engines read a page in similar ways: neither sees images, and both learn structure from the code. So much of the work done for accessibility also helps search visibility:
- Alt text tells search engines what an image shows, too.
- A clean heading structure makes the topic and sections of a page clear.
- Descriptive link text explains what the target page is about.
- Video transcripts make content readable and searchable.
The same structure also makes life easier for AI answer engines that summarize content. Accessibility does not bring rankings on its own, but like speed, it is part of a good page experience. We cover the speed side in What Are Core Web Vitals?
Does the European Accessibility Act affect your company?
The European Accessibility Act (Directive (EU) 2019/882) has applied since 28 June 2025 to certain products and services offered to consumers in the European Union. E-commerce services are in scope, while microenterprises that provide services are exempt. On the technical side, the reference is the European standard EN 301 549, which builds on WCAG for web content.
If you sell online to consumers in the EU, including from outside it, you should check whether you are in scope. Scope depends on the type of service, the size of the business and the countries you sell to. That is a legal assessment, so we recommend confirming your situation with a legal advisor.
When should you build accessibility in?
The cheapest moment is the first day of design. The color palette is chosen with its contrast ratios, focus styles and error states go into the components from the start and the content team makes alt text part of the publishing routine. Get these right once, and every new page is born accessible.
Fixing a live site later is possible, but it costs more: brand colors may fail contrast checks, custom-built menus may need to be rewritten and hundreds of images may need alt text one by one. Ask whether accessibility is in scope at the quote stage. We cover the other questions to ask before commissioning a website and the factors that shape the cost of a corporate website in separate articles.
The final step is an accessibility statement page. State the standard you aim for, the known gaps, the date of the last review and a way for users to report problems. An honest statement earns more trust than a page that claims perfection.
An accessible website is not just better for people with disabilities; it is better for everyone.
Frequently asked questions
Is WCAG conformance a legal requirement?
It depends on where you operate, who your customers are and what service you offer. If you provide in-scope services such as e-commerce to consumers in the EU, the European Accessibility Act may apply to you. Ask a legal advisor about your specific situation; as a technical target, WCAG 2.2 AA is a sound starting point.
Is an accessibility plugin or toolbar enough?
No. Tools added with a single line of code do not fix missing labels, broken heading structure or menus that will not open with a keyboard. Screen reader users already have their own tools; what they need is correctly built code.
Should we aim for level A, AA or AAA?
For most business and e-commerce websites, the target is AA. Because some content cannot meet AAA, the W3C itself does not recommend requiring it as a general policy for entire sites. You can still apply some AAA criteria to key pages.
Can we make our existing site accessible without rebuilding it?
In most cases, yes. Start by auditing the most used page templates and flows; a fix made in a template carries over to hundreds of pages at once. If brand colors or custom components have deeper problems, they can go into the scope of the next redesign.
Where to start?
Pick your three most used pages: the home page, a product or service page and the contact form. Run the Lighthouse accessibility report on each, then put the mouse aside and use the page with the keyboard only. Group what you find under the checklist above; that list becomes the draft of both your improvement plan and your accessibility statement.
If you would like to review your site's accessibility together, or plan a site with accessibility built in from the start, get in touch.