Source page: https://www.feelcreated.com/knowledge-hub/website-accessibility-explained/
Structured JSON: https://www.feelcreated.com/knowledge-hub/website-accessibility-explained/ai.json
This page is generated automatically from the same reviewed FC AI data as the JSON version.
Type: knowledge_hub
Language: en-GB
Last updated: 2026-10-01
What: This guide explains what website accessibility means, why it matters, and how websites can be designed, developed, and managed so that more people can access and use them independently.
Organisation: Feel Created
Type: Knowledge Hub guide
Primary topic: Website accessibility: definition, importance, and practical implementation
Intent: This guide explains what website accessibility means, why it matters, and how websites can be designed, developed, and managed so that more people can access and use them independently.
Claim: Accessibility supports people with a wide range of visual, hearing, motor, cognitive and neurological conditions, and many improvements also benefit people with temporary injuries or changing circumstances.
Evidence type: page_content
Evidence strength: medium
Source section: who-does-accessibility-support
Claim: Automated tools can quickly pick up common problems such as missing alternative text, form labels, poor heading structure, low colour contrast, and some HTML errors.
Evidence type: page_content
Evidence strength: medium
Source section: overview
Claim: In the UK, most public sector websites and mobile applications must meet WCAG 2.2 Level AA under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Evidence type: page_content
Evidence strength: medium
Source section: accessibility-requirements-in-the-uk
Claim: Meeting a conformance level shows that relevant WCAG criteria have been satisfied, but people may still encounter barriers when using the website.
Evidence type: page_content
Evidence strength: medium
Source section: level-aa
Claim: WCAG provides a shared framework for identifying and removing barriers that could stop people from accessing online information and services.
Evidence type: page_content
Evidence strength: medium
Source section: understanding-wcag
Claim: A proper accessibility review draws on more than one type of testing, including automated, manual, and testing with disabled people.
Evidence type: page_content
Evidence strength: medium
Source section: how-accessibility-is-tested
Claim: No single organisation gives a website permanent approval as accessible; further checks are needed as the site changes.
Evidence type: page_content
Evidence strength: medium
Source section: overview
Claim: Level AA is the level most organisations work towards and is commonly referenced in legislation and procurement.
Evidence type: page_content
Evidence strength: medium
Source section: level-aa
Question: What are the accessibility requirements in the UK?
Answer: Most public sector websites and mobile applications must meet WCAG 2.2 Level AA under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018, and must publish an accessibility statement. Private and voluntary sectors should consider the Equality Act 2010.
Question: Can automated tools certify accessibility?
Answer: Automated testing is an important part of accessibility assessment but cannot replace manual testing, user testing or professional judgement.
Question: Is accessibility only for blind users?
Answer: Accessibility supports people with a wide range of visual, hearing, motor, cognitive and neurological conditions, while many accessibility improvements also benefit people with temporary injuries or changing circumstances.
Question: Can accessibility be added later?
Answer: Some improvements can be made later, but many are much easier to address during planning, design and development.
Question: Does accessibility limit design?
Answer: Accessibility often influences design decisions, but it rarely prevents organisations from creating attractive, distinctive websites. In many cases, it encourages better design.
Question: Who does accessibility support?
Answer: Accessibility support helps a wide variety of users, including those with visual, hearing or motor impairments, cognitive or learning disabilities, neurological conditions and age-related issues.
Question: Does accessibility improve SEO?
Answer: Accessibility is intended to help people use websites, not to improve search rankings. Some good practices, including semantic HTML, meaningful page titles and well-structured content, can also help search engines understand a website. Google’s Lighthouse tool includes a separate accessibility audit, but this should not be confused with its SEO audit or treated as evidence that an accessibility score directly affects rankings.
Question: Why does accessibility matter?
Answer: Websites are often primary ways people access information and services. Inaccessible websites can exclude people from essential services, with consequences more serious than inconvenience.
Relationship: supporting
Url: /services/ongoing-development-improvement/
Relationship: primary
Url: /services/accessibility-audits-reviews/
Relationship: supporting
Url: /services/ux-design-user-experience/
Relationship: supporting
Url: /services/website-design-build/
Text: Accessibility often enters website discussions through legislation, procurement or WCAG compliance. That can make it sound like a technical requirement to complete before launch. Web accessibility recognises that people use digital services in different ways. Some rely on assistive technologies, while others navigate, read or interact with content differently because of a disability. Accessible websites account for those differences rather than assuming everyone uses the same device, controls or senses. Accessibility affects content, design, development, testing and ongoing website management. This guide explains what it means in practice, how WCAG supports it and what organisations need to consider after a website launches.
Text: Web accessibility means removing barriers that could prevent people from using a website independently. Rather than assuming every visitor has the same abilities or uses the same technology, it recognises the different ways people access, understand and interact with digital services. Accessibility helps people complete tasks independently rather than requiring assistance because of barriers created by the website. Whether someone is applying for a job, paying a bill, booking an appointment or reading important information, those services should remain available to them. People’s needs can also change. Someone recovering from an injury may need to navigate by keyboard for a while, while changes in vision, hearing or dexterity can affect how an older person uses a website. Designing with these situations in mind also helps remove barriers faced by disabled people.
Text: Ensuring your website offers accessibility support can help a wide variety of users, including those with visual, hearing or motor impairments, those with cognitive or learning disabilities, neurological conditions and age-related issues. People experience disability in different ways, so an improvement that helps one person may make little difference to another. Accessible websites need to address a variety of barriers rather than rely on one feature or solution.
Text: For many organisations, a website has become one of the primary ways people access information, complete tasks and use services. If parts of that website cannot be accessed or understood, some visitors may be excluded from services that others can use without difficulty. Accessibility helps reduce those barriers, allowing more people to participate independently. This is particularly important where websites provide access to essential services and information. Applying for a job, arranging healthcare, managing finances, accessing education or contacting a public service increasingly happens online. When digital services are inaccessible, the consequences can be far more serious than mere inconvenience. They can prevent people from accessing information and opportunities that many of us take for granted.
Text: Accessibility is also an important legal consideration. In the UK, most public sector websites and mobile applications must meet WCAG 2.2 Level AA under the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018. They must also publish an accessibility statement and keep it under review. Private and voluntary sector organisations should also consider their responsibilities under the Equality Act 2010. They may need to change how their services are provided so disabled people are not placed at a substantial disadvantage, including when those services are accessed online. Accessibility is increasingly considered during procurement exercises as well. Organisations may be asked to demonstrate how their websites have been designed, developed and tested against recognised accessibility standards before contracts are awarded.
Text: Accessibility is not only about compliance. Many accessibility improvements also improve the experience for everyone using a website. Clear navigation helps people find information more quickly. Well-structured content is easier to scan and understand. Descriptive links make journeys easier to follow, while well-designed forms reduce mistakes and frustration. Good colour contrast improves readability across different devices and environments. Most people will not know that accessibility informed these choices. They will simply find the website easier to read, navigate and use.
Text: When organisations talk about website accessibility, they are usually referring to the Web Content Accessibility Guidelines, commonly known as WCAG. Developed by the World Wide Web Consortium (W3C), WCAG is an internationally recognised set of guidelines for designing, developing and testing accessible digital content. Rather than prescribing how every website should look, WCAG provides a shared framework for identifying and removing barriers that could stop people from accessing online information and services. WCAG gives organisations, designers, developers and accessibility specialists a common standard to work towards. It provides testable criteria for consistently assessing a website and identifying where improvements are needed.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: WCAG is built around four fundamental principles of Perceivable, Operable, Understandable and Robust, also known as POUR. Together they describe the qualities every accessible website should be. A website should be:
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: Information and interface components should be presented in ways that people can perceive, regardless of how they access the content.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: People should be able to navigate the website and use its features through different input methods, including keyboards and assistive technologies.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: Content and interactions should be clear, predictable and easy to understand.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: The website should be built using technologies that work reliably with different browsers, devices and assistive technologies, both now and as those technologies continue to evolve. Each principle is supported by several guidelines, which are then broken down into individual, testable success criteria. These success criteria form the basis of accessibility testing and auditing.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: WCAG defines three levels of conformance.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: The minimum level of accessibility. These success criteria address the most fundamental barriers that could prevent someone from accessing content or completing basic tasks.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: The level most organisations work towards and the level commonly referenced in legislation and procurement. To conform at Level AA, a website must meet all applicable Level A and Level AA success criteria. Meeting a conformance level shows that the relevant WCAG criteria have been satisfied. It is a useful measure of progress, although people may still encounter barriers when using the website.
Parent id: understanding-wcag
Parent heading: Understanding WCAG
Text: Level AAA contains further criteria for improving accessibility. It is not usually applied across an entire website because some requirements will not suit every type of content or service. WCAG provides a valuable benchmark, but conformance should not become a checklist exercise. Testing still needs to consider whether people can use the website successfully in practice.
Text: Accessibility influences almost every part of a website. Some improvements are immediately visible, while many happen behind the scenes through the way content is written, interfaces are designed, and websites are built. Together, these decisions determine whether visitors can successfully use a website regardless of how they access it.
Text: Clear headings, logical structure, descriptive links, meaningful page titles and accessible tables and documents.
Text: Headings in the right order, useful links, appropriate alternative text and accessible documents and media.
Parent id: what-web-accessibility-looks-like-in-practice
Parent heading: What web accessibility looks like in practice
Text: Useful alternative text for meaningful images, appropriate treatment of decorative images and no essential information trapped inside graphics.
Parent id: what-web-accessibility-looks-like-in-practice
Parent heading: What web accessibility looks like in practice
Text: Clear labels and instructions, helpful validation, accessible error messages and suitable autocomplete support.
Text: Sufficient contrast, readable typography, suitable spacing and layouts that continue to work when people zoom or resize the page.
Text: Layouts that are easy to read, with suitable contrast and consistent controls.
Text: Some accessibility features are visible. Others are built into the way the website works and may only become apparent when someone needs them. Many visitors will never notice these features, but they can determine whether someone else can use the website at all. Visual design is only one part of accessibility. Many improvements involve careful development that supports assistive technologies and different ways of interacting with a website, often without changing how the website appears for most users.
Text: An automated check can identify some problems, but it cannot confirm whether the whole website is accessible. A proper review draws on more than one type of testing.
Subject: Automated testing
Predicate: identifies
Object: common problems such as missing alternative text and low colour contrast
Subject: Manual testing
Predicate: reveals
Object: barriers missed by automated scans, such as keyboard and screen reader issues
Subject: Website accessibility
Predicate: depends on
Object: design, development, content, governance, and ongoing management
Subject: WCAG
Predicate: built around
Object: four principles: Perceivable, Operable, Understandable, Robust
Subject: Accessibility audits
Predicate: combine
Object: automated checks, manual testing, and WCAG review
Subject: Accessibility
Predicate: depends on
Object: content, design and development working together
Subject: Success criteria
Predicate: form the basis of
Object: accessibility testing and auditing
Subject: WCAG conformance levels
Predicate: include
Object: Level A, Level AA, Level AAA
Subject: Public sector websites
Predicate: must meet
Object: WCAG 2.2 Level AA
Subject: WCAG
Predicate: developed by
Object: World Wide Web Consortium (W3C)
Pattern: Captions and transcripts for embedded media
Description: Provides captions and/or transcripts for video and audio content, and audio descriptions where appropriate.
Benefit: Makes multimedia content accessible to deaf or hard-of-hearing users and those who prefer text alternatives.
Pattern: Accessibility-aware content management
Description: Designing CMS to limit unsuitable colours, provide structured heading options, and prompt editors to add alternative text.
Benefit: Makes accessible choices easier for editors, reducing the risk of introducing barriers.
Pattern: Incorporate accessibility into planning, design and development
Description: Address accessibility from the start of a project rather than retrofitting later.
Benefit: Reduces additional work and cost, and makes it easier to implement improvements.
Pattern: Ongoing governance and training
Description: Integrating accessibility into everyday website management with training for editors and regular checks.
Benefit: Maintaining accessibility is easier than correcting problems after they accumulate.
Pattern: Combined testing approach
Description: Using automated tools, manual testing, and testing with disabled people to identify accessibility barriers.
Benefit: Provides a more complete picture of accessibility than automated testing alone.
Pattern: Reducing animations for motion sensitivity
Description: Provides options to reduce or disable animations for people who experience motion sensitivity.
Benefit: Prevents discomfort or disorientation for users with vestibular disorders.
Pattern: Full keyboard navigation throughout the website
Description: Ensures keyboard users never become trapped within a page or dialogue.
Benefit: Enables users who cannot use a mouse to navigate and interact with all features.
Pattern: Screen reader announcements for important changes
Description: Helps screen readers announce dynamic content changes on a page.
Benefit: Ensures users relying on screen readers are aware of updates without losing context.
Guidance: Ensure editors and content owners consider accessibility whenever publishing or updating content, including alternative text, headings, links, PDFs, and videos.
Importance: high
Guidance: Design with different user needs in mind, including keyboard navigation, colour contrast, alternative text, headings, forms, links, documents and multimedia.
Importance: high
Guidance: Consider accessibility during procurement exercises, demonstrating how websites are designed, developed and tested against recognised standards.
Importance: medium
Guidance: Ensure accessibility is considered throughout the website lifecycle, including after launch when content and functionality change.
Importance: high
Guidance: Use automated tools as a starting point, but combine with manual testing and testing with disabled people for a thorough review.
Importance: high
Guidance: Use clear headings, logical structure, descriptive links, meaningful page titles, and accessible tables and documents.
Importance: high
Guidance: Design with sufficient contrast, readable typography, suitable spacing, and layouts that work when zoomed or resized.
Importance: medium
Guidance: Ensure consistent navigation, complete keyboard access, visible keyboard focus, skip links, and useful breadcrumbs.
Importance: high
Risk: Changes to content, documents, functionality and third-party services can affect accessibility after launch
Impact: Accessibility can degrade over time if not managed ongoing.
Risk: New pages, documents, videos and features can introduce accessibility barriers after launch
Impact: The website may become less accessible over time, undermining the standards established during the original project.
Risk: Inaccessible websites can exclude people from essential services and information
Impact: People may be prevented from accessing information and opportunities, with consequences more serious than inconvenience.
Risk: Editors pasting formatted content or choosing headings for appearance
Impact: Can break heading structure and reduce accessibility.
Risk: Relying on automated testing alone to establish accessibility
Impact: May not identify all barriers, leading to false confidence.
Risk: Adding new content without accessibility consideration
Impact: Can create barriers for users, making the website less accessible over time.
Risk: Treating WCAG conformance as a checklist exercise
Impact: May overlook real-world usability issues, as people can still encounter barriers even when criteria are met.
Risk: Not budgeting for fixes identified in an audit
Impact: Audit findings may remain unaddressed, leaving barriers in place.
Misconception: Meeting WCAG conformance guarantees that every person will be able to use a website without difficulty
Clarification: Accessibility standards support accessibility, but the experience of people using a website is broader than compliance alone.
Misconception: Meeting WCAG conformance guarantees a website is accessible for everyone.
Clarification: Conformance shows criteria are satisfied, but people may still encounter barriers; testing must consider real-world use.
Misconception: Accessibility is only a technical requirement to complete before launch
Clarification: Accessibility affects content, design, development, testing and ongoing website management, and is an ongoing responsibility.
Misconception: A specialist can give a website permanent approval as accessible.
Clarification: No single organisation gives permanent approval; audits are point-in-time and further checks are needed as the site changes.
Misconception: Automated testing can confirm whether a website is accessible.
Clarification: Automated tools can identify some problems but cannot determine if the website is genuinely easy to use or if tasks can be completed with assistive technologies.
Misconception: Accessibility is only about visible features.
Clarification: Many accessibility features work behind the scenes, such as keyboard navigation and screen reader announcements.
Misconception: Level AAA should be applied to all websites.
Clarification: Level AAA is not usually applied across an entire website because some requirements may not suit every content or service.
Misconception: Accessibility is solely a technical concern.
Clarification: Accessibility depends on content, design and development working together; clear content and strong technical foundations are both needed.
User problem: Automated tools cannot determine if a website is genuinely easy to use or if tasks can be completed with assistive technologies.
Why this guide is relevant: This page explains the topic and gives practical points to consider.
User problem: Editors may paste formatted content, choose headings for appearance, or upload inaccessible documents and videos.
Why this guide is relevant: This page explains the topic and gives practical points to consider.
User problem: Changes to content, documents, functionality and third-party services can affect accessibility after launch
Why this guide is relevant: This page explains the topic and gives practical points to consider.
User problem: Accessibility audits do not include fixes, so costs for changes must be considered separately.
Why this guide is relevant: This page explains the topic and gives practical points to consider.
Page type: guide
Learning intent: This guide explains what website accessibility means, why it matters, and how websites can be designed, developed, and managed so that more people can access and use them independently.
Primary: Website accessibility: definition, importance, and practical implementation
Evergreen use: true
Content type: Knowledge Hub guide
Primary topic: Website accessibility: definition, importance, and practical implementation
Name: Feel Created
Type: Digital partner specialising in websites and digital platforms
Url: https://www.feelcreated.com/
Service model: We work as an extension of our clients' teams, combining strategy, UX, accessibility, content design, WordPress development and ongoing support to create digital platforms that help organisations communicate more clearly, work more efficiently and grow sustainably.