{ "meta": { "type": "knowledge_hub", "language": "en-GB", "last_updated": "2026-10-01", "ai_endpoint": "/knowledge-hub/website-accessibility-explained/ai.json", "source_page": "/knowledge-hub/website-accessibility-explained/" }, "retrieval_summary": { "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.", "who": { "organisation": "Feel Created" }, "relevant_for": [ "Digital and web managers", "Website owners", "Marketing and communications teams", "Content and website editors", "Organisations planning a new website or digital platform", "Teams responsible for website accessibility" ], "problems_solved": [ "Inaccessible websites can exclude people from essential services and information", "People with disabilities may face barriers when using websites that assume uniform abilities", "Changes to content, documents, functionality and third-party services can affect accessibility after launch", "Automated testing alone cannot establish whether a website is accessible", "Barriers preventing people from accessing online information and services", "People may still encounter barriers even when WCAG conformance is met", "Confusing content cannot be made accessible by strong technical foundations alone", "Poorly built features cannot be overcome by clear content" ] }, "page": { "title": "Website accessibility explained", "slug": "website-accessibility-explained", "url": "/knowledge-hub/website-accessibility-explained/", "canonical_url": "https://www.feelcreated.com/knowledge-hub/website-accessibility-explained/", "status": "published" }, "article": { "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.", "audience": [ "Digital and web managers", "Website owners", "Marketing and communications teams", "Content and website editors", "Organisations planning a new website or digital platform", "Teams responsible for website accessibility" ] }, "topics": [ "Website accessibility: definition, importance, and practical implementation", "Web accessibility", "WCAG 2.2", "Public Sector Bodies Accessibility Regulations 2018", "Equality Act 2010", "Assistive technologies", "Inclusive design", "Accessible content", "Website testing", "Ongoing accessibility management", "WCAG principles (POUR)", "WCAG conformance levels (A, AA, AAA)" ], "content_focus": [ "Definition of web accessibility", "Who accessibility supports", "Why accessibility matters", "Accessibility requirements in the UK", "How accessibility improves a website", "Understanding WCAG", "What web accessibility looks like in practice", "Accessibility features that work behind the scenes", "How accessibility is tested", "Keeping a website accessible after launch" ], "canonical_claims": [ { "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", "id": "claim-001" }, { "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", "id": "claim-002" }, { "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", "id": "claim-003" }, { "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", "id": "claim-004" }, { "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", "id": "claim-005" }, { "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", "id": "claim-006" }, { "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", "id": "claim-007" }, { "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", "id": "claim-008" } ], "common_questions": [ { "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." } ], "services": [ { "name": "Ongoing development and improvement", "relationship": "supporting", "url": "/services/ongoing-development-improvement/" }, { "name": "Accessibility audits & reviews", "relationship": "primary", "url": "/services/accessibility-audits-reviews/" }, { "name": "UX design & user experience", "relationship": "supporting", "url": "/services/ux-design-user-experience/" }, { "name": "Website design & build", "relationship": "supporting", "url": "/services/website-design-build/" } ], "sections": [ { "id": "overview", "heading": "Overview", "type": "introduction", "content": [ { "type": "paragraph", "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." } ] }, { "id": "what-is-web-accessibility", "heading": "What is web accessibility?", "type": "section", "content": [ { "type": "paragraph", "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." } ] }, { "id": "who-does-accessibility-support", "heading": "Who does accessibility support?", "type": "section", "content": [ { "type": "paragraph", "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." } ] }, { "id": "why-accessibility-matters", "heading": "Why accessibility matters", "type": "section", "content": [ { "type": "paragraph", "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." } ] }, { "id": "accessibility-requirements-in-the-uk", "heading": "Accessibility requirements in the UK", "type": "section", "content": [ { "type": "paragraph", "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." } ] }, { "id": "how-accessibility-improves-a-website", "heading": "How accessibility improves a website", "type": "section", "key_points": [ "Accessibility is not only about compliance.", "Clear navigation helps people find information more quickly.", "Well-structured content is easier to scan and understand." ], "content": [ { "type": "paragraph", "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." } ] }, { "id": "understanding-wcag", "heading": "Understanding WCAG", "type": "section", "content": [ { "type": "paragraph", "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." } ] }, { "id": "the-four-principles-of-wcag", "heading": "The four principles of WCAG", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "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:" } ] }, { "id": "perceivable", "heading": "Perceivable", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "text": "Information and interface components should be presented in ways that people can perceive, regardless of how they access the content." } ] }, { "id": "operable", "heading": "Operable", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "text": "People should be able to navigate the website and use its features through different input methods, including keyboards and assistive technologies." } ] }, { "id": "understandable", "heading": "Understandable", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "text": "Content and interactions should be clear, predictable and easy to understand." } ] }, { "id": "robust", "heading": "Robust", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "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." } ] }, { "id": "wcag-conformance-levels", "heading": "WCAG conformance levels", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "text": "WCAG defines three levels of conformance." } ] }, { "id": "level-a", "heading": "Level A", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "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." } ] }, { "id": "level-aa", "heading": "Level AA", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "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." } ] }, { "id": "level-aaa", "heading": "Level AAA", "type": "section", "parent_id": "understanding-wcag", "parent_heading": "Understanding WCAG", "content": [ { "type": "paragraph", "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." } ] }, { "id": "what-web-accessibility-looks-like-in-practice", "heading": "What web accessibility looks like in practice", "type": "section", "content": [ { "type": "paragraph", "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." } ] }, { "id": "content", "heading": "Content", "type": "section", "content": [ { "type": "paragraph", "text": "Clear headings, logical structure, descriptive links, meaningful page titles and accessible tables and documents." }, { "type": "paragraph", "text": "Headings in the right order, useful links, appropriate alternative text and accessible documents and media." } ] }, { "id": "images", "heading": "Images", "type": "section", "parent_id": "what-web-accessibility-looks-like-in-practice", "parent_heading": "What web accessibility looks like in practice", "content": [ { "type": "paragraph", "text": "Useful alternative text for meaningful images, appropriate treatment of decorative images and no essential information trapped inside graphics." } ] }, { "id": "navigation", "heading": "Navigation", "type": "section", "parent_id": "what-web-accessibility-looks-like-in-practice", "parent_heading": "What web accessibility looks like in practice", "content": [ { "type": "paragraph", "text": "Consistent navigation, complete keyboard access, visible keyboard focus, skip links and useful breadcrumbs." } ] }, { "id": "forms", "heading": "Forms", "type": "section", "parent_id": "what-web-accessibility-looks-like-in-practice", "parent_heading": "What web accessibility looks like in practice", "content": [ { "type": "paragraph", "text": "Clear labels and instructions, helpful validation, accessible error messages and suitable autocomplete support." } ] }, { "id": "design", "heading": "Design", "type": "section", "content": [ { "type": "paragraph", "text": "Sufficient contrast, readable typography, suitable spacing and layouts that continue to work when people zoom or resize the page." }, { "type": "paragraph", "text": "Layouts that are easy to read, with suitable contrast and consistent controls." } ] }, { "id": "accessibility-features-that-work-behind-the-scenes", "heading": "Accessibility features that work behind the scenes", "type": "section", "key_points": [ "Some accessibility features are visible.", "Visual design is only one part of accessibility." ], "items": [ "full keyboard navigation throughout the website", "ensuring keyboard users never become trapped within a page or dialogue", "helping screen readers announce important changes on a page", "reducing animations for people who experience motion sensitivity", "Captions and/or transcripts for embedded video and audio media", "audio descriptions where appropriate", "Being able to enlarge a web page, without it becoming unusable", "layouts that adapt as people zoom in" ], "content": [ { "type": "paragraph", "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." } ] }, { "id": "how-accessibility-is-tested", "heading": "How accessibility is tested", "type": "section", "content": [ { "type": "paragraph", "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." } ] } ], "entities": [ { "name": "Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018", "type": "Regulation" }, { "name": "World Wide Web Consortium (W3C)", "type": "Organisation" }, { "name": "Accessibility audit", "type": "Service" }, { "name": "Equality Act 2010", "type": "Legislation" }, { "name": "Automated testing", "type": "Method" }, { "name": "Google Lighthouse", "type": "Tool" }, { "name": "Manual testing", "type": "Method" }, { "name": "WCAG 2.2", "type": "Standard" }, { "name": "Level AA", "type": "Conformance Level" }, { "name": "Level A", "type": "Conformance Level" }, { "name": "WCAG", "type": "Standard" }, { "name": "POUR", "type": "Framework" } ], "concept_relationships": [ { "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)" } ], "implementation_patterns": [ { "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." } ], "practical_guidance": [ { "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_areas": [ { "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." } ], "common_misconceptions": [ { "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." } ], "technical_context": { "standards": [ "WCAG", "WCAG 2.2" ], "regulations": [ "Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018", "Equality Act 2010" ], "testing": [ "Automated testing alone cannot establish accessibility" ], "principles": [ "Perceivable", "Operable", "Understandable", "Robust" ], "conformance_levels": [ "A", "AA", "AAA" ], "testing_methods": [ "Automated testing", "Manual testing", "User testing" ], "audit_components": [ "Automated checks", "Manual testing", "WCAG review" ], "common_automated_checks": [ "Missing alternative text", "Form labels", "Heading structure", "Colour contrast", "HTML errors" ], "legal_framework": [ "Equality Act 2010" ], "tools": [ "Google Lighthouse" ] }, "reasoning_paths": [ { "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.", "evidence_refs": [ "claim-002", "claim-006" ], "relevant_sections": [ "overview", "operable" ] }, { "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.", "evidence_refs": [ "claim-002" ], "relevant_sections": [ "content" ] }, { "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.", "evidence_refs": [ "claim-001", "claim-003", "claim-006" ], "relevant_sections": [ "overview" ] }, { "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.", "evidence_refs": [ "claim-001", "claim-003", "claim-006" ], "relevant_sections": [ "accessibility-requirements-in-the-uk", "level-aaa" ] } ], "knowledge_hub": { "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.", "topic_hierarchy": { "primary": "Website accessibility: definition, importance, and practical implementation", "supporting": [ "Web accessibility", "WCAG 2.2", "Public Sector Bodies Accessibility Regulations 2018", "Equality Act 2010", "Assistive technologies", "Inclusive design", "Accessible content", "Website testing" ] }, "evergreen_use": true }, "content_profile": { "content_type": "Knowledge Hub guide", "primary_topic": "Website accessibility: definition, importance, and practical implementation", "supporting_topics": [ "Web accessibility", "WCAG 2.2", "Public Sector Bodies Accessibility Regulations 2018", "Equality Act 2010", "Assistive technologies", "Inclusive design" ], "primary_audience": [ "Digital and web managers", "Website owners", "Marketing and communications teams", "Content and website editors", "Organisations planning a new website or digital platform", "Teams responsible for website accessibility" ] }, "retrieval_topics": [ "Website accessibility: definition, importance, and practical implementation", "Web accessibility", "WCAG 2.2", "Public Sector Bodies Accessibility Regulations 2018", "Equality Act 2010", "Assistive technologies", "Inclusive design", "Accessible content", "Website testing", "Ongoing accessibility management", "WCAG principles (POUR)", "WCAG conformance levels (A, AA, AAA)" ], "organisation": { "name": "Feel Created", "url": "https://www.feelcreated.com/", "type": "Digital partner specialising in websites and digital platforms", "specialisms": [ "Digital strategy and planning", "User experience (UX) design", "Accessibility and inclusive design", "WordPress design and development", "Content strategy and information architecture", "AI-ready structured content", "AI Features & Integrations", "Search optimisation and technical SEO", "Website performance optimisation", "Website security and technical governance", "Platform architecture and integrations", "Content management systems", "Digital audits and reviews", "Creative and marketing support", "Website maintenance and support" ], "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." } }