Web Accessibility
Web accessibility in one sentence: Web accessibility is the practice of designing, building and writing websites so that everyone, including people with visual, hearing, motor, speech and cognitive disabilities, can perceive, understand, navigate and interact with them.
The technical benchmark for web accessibility is WCAG (Web Content Accessibility Guidelines). Laws such as the ADA in the US and the European Accessibility Act in the EU make it a legal obligation for many organizations.
What is web accessibility?
Web accessibility removes the barriers that stop people from using a website. A blind visitor relies on a screen reader to announce images and buttons. A visitor with a tremor moves through a page with a keyboard. A visitor with a cognitive disability needs plain language and predictable navigation.
The W3C Web Accessibility Initiative defines it this way: "Web accessibility means that websites, tools, and technologies are designed and developed so that people with disabilities can use them." Read more in W3C's Introduction to Web Accessibility.
Web accessibility is closely linked to user experience. An accessible site is usually easier for everyone to use, whatever device, ability or situation they bring to it.
What should an accessible website include?
Most accessible websites include the following:
- Alt text at the source: describe the purpose of each meaningful image where the image is stored, so the description follows it everywhere.
- Role-based editing: permissions and review workflows that check accessibility before content goes live.
- Reusable components: design systems built from accessible components, so fixes apply across the site.
- Color contrast: text strong enough to read against its background.
- Clear heading structure: a logical H1, H2, H3 order that screen reader users can navigate.
- Labeled forms, links and buttons: every control has a clear name, even out of context.
- Keyboard access: visible focus indicators and skip links, with no keyboard traps.
- Captions, transcripts and audio versions: alternatives for video and long-form content.
- Plain language: text that matches the reading level of your audience.
- Native HTML before WAI-ARIA: standard HTML elements first, adding WAI-ARIA only when HTML cannot express a component.
How does web accessibility work?
People with disabilities use assistive technologies and browser settings to access the web. An accessible site works with all of them:
| Assistive technology | Who uses it | What your site must provide |
|---|---|---|
Screen readers | Blind and low-vision users | Alt text, headings, labels and correct HTML structure |
Screen magnifiers and zoom | Low-vision users | Layouts that reflow at 200% to 400% zoom without losing content |
Keyboard and switch access | Users with motor disabilities | Full keyboard operation, visible focus and logical tab order |
Captions and transcripts | Deaf and hard-of-hearing users | Captions for video and transcripts for audio |
Voice control | Users who cannot use a mouse or keyboard | Visible labels that match each control's accessible name |
Text-to-speech and reading tools | Users with dyslexia or cognitive disabilities | Plain language, clear layout and readable text |
Because these tools read the underlying code and content, accessibility depends on design, development and editorial work together.
What is the difference between web accessibility and WCAG?
Web accessibility is the goal: a website everyone can use. WCAG is the technical standard that defines how to measure whether a site reaches that goal. For the levels and versions, see WCAG.
What are the main types of disability web accessibility addresses?
- Visual: blindness, low vision and color blindness. Helped by alt text, contrast and screen reader support.
- Auditory: deafness and hearing loss. Helped by captions and transcripts.
- Physical and motor: limited movement or dexterity. Helped by keyboard access and large click targets.
- Cognitive and learning: dyslexia, memory and attention differences. Helped by plain language and consistent layouts.
- Speech: difficulty speaking. Helped by alternatives to voice-only input.
- Situational and temporary: a broken arm, bright sunlight or a noisy train. Helped by all of the above.
Industry Insight
According to the WebAIM Million 2026 report, the six most common accessibility errors on home pages are low contrast, missing alt text, missing form labels, empty links, empty buttons and missing document language. Together they account for 96% of detected errors, and most can be prevented at the content and component level.
What are the benefits of web accessibility?
- Bigger audience: inaccessible pages turn away visitors and customers.
- Legal compliance: accessibility laws in the US, EU, UK, Canada and Australia apply to many public-facing websites. See Secure & Compliant.
- Search and AI visibility: headings, alt text and descriptive links help SEO and AI answer engines understand content.
- Better experience for everyone: clear structure, readable text and captions help every visitor.
- Brand trust: an inclusive site shows an organization takes all its users seriously.
How do you make a website accessible?
- Start early: W3C recommends checking accessibility early and throughout a project. Write it into the brief and record a baseline before a redesign.
- Fix it at the source: build accessibility into templates, widgets and content models, not page by page.
- Govern content: use content governance so every new page, image and video is checked before publishing.
- Test with people: combine automated scans with keyboard and screen reader testing, ideally with people with disabilities.
- Treat it as ongoing: each new page, image, video or widget can add a barrier.
How do you meet WCAG?
Yes. Xperience by Kentico builds accessibility into everyday content work, while accessibility itself depends on how each site is designed, built and tested.
- Alt text: alt-text fields on Content Hub assets, with alt text suggested by AIRA for editors to review.
- Governance: role-based permissions and approval workflows let teams check content before it goes live.
- Reusable content and components: reusable content and Page Builder widgets keep accessible patterns consistent across pages and channels.
- Multilingual content: manage accessible content across languages with multilingual content and localization.
QCEIDAH offers "Easy read" and "plain English" versions of key content, modeled as reusable content items with partner Zeroseven. Moose on the Loose added ReadSpeaker text-to-audio with word-by-word highlighting, with partner SilverTech. Read their stories in The 5 Most Accessible Websites of 2026 on Xperience by Kentico.
Who benefits most from web accessibility?
Everyone benefits, but accessibility matters most for organizations that serve the whole public: government, education, healthcare, financial services, ecommerce and nonprofits. It also matters for any brand with older audiences or many visitors on mobile. Everyone benefits, but accessibility matters most for organizations that serve the whole public: government, education, healthcare, financial services, ecommerce and nonprofits. It also matters for any brand with older audiences or many visitors on mobile.
Frequently Asked Questions.
A page template defines the overall structure and layout of a page, while a widget defines an individual, configurable piece of content placed inside that structure. Templates give editors a starting point, such as a landing page layout with predefined sections, while widgets are what actually populate those sections with specific content like a hero banner or a product grid. In practice, a single page template can host many different widgets, and the same widget can appear across many different page templates.