WCAG 3.0 Guidelines: what’s changing & what website owners need to know

Source page: https://www.feelcreated.com/insights/wcag-3-accessibility-guidelines/

Structured JSON: https://www.feelcreated.com/insights/wcag-3-accessibility-guidelines/ai.json

This page is generated automatically from the same reviewed FC AI data as the JSON version.

Meta

Type: insight_article

Language: en-GB

Last updated: 2026-10-19

Retrieval summary

What: WCAG 3.0 is a proposed update to the Web Content Accessibility Guidelines, published as a working draft by the W3C in September 2026, introducing a new conformance model and broader scope.

Who

Organisation: Feel Created

Relevant for

Problems solved

Article

Type: Insight article

Primary topic: WCAG 3.0 and its implications for website owners and digital teams

Intent: WCAG 3.0 is a proposed update to the Web Content Accessibility Guidelines, published as a working draft by the W3C in September 2026, introducing a new conformance model and broader scope.

Author

Name: Dan Clark

Organisation: Feel Created

Bio: Lead Developer at Feel Created, focusing on the development of high-performance WordPress websites and bespoke digital solutions.

Audience

Topics

Content focus

Canonical claims

Item 1

Claim: WCAG 3.0 aims to cover a wider range of digital experiences including applications, publishing tools, and emerging technologies.

Evidence type: page_content

Evidence strength: high

Source section: what-is-wcag-3-0

Item 2

Claim: The proposed conformance model groups requirements into four categories: physical harm, risk, barrier, and friction.

Evidence type: page_content

Evidence strength: high

Source section: a-different-way-of-assessing-accessibility

Item 3

Claim: The September 2026 draft proposes a single conformance level with reporting tiers instead of A, AA, AAA levels.

Evidence type: page_content

Evidence strength: high

Source section: whats-changed-in-the-september-2026-update

Item 4

Claim: The W3C has specifically recommended meeting WCAG 2.2 requirements as the best way to prepare for WCAG 3.0.

Evidence type: page_content

Evidence strength: medium

Source section: whats-changed-in-the-september-2026-update

Item 5

Claim: WCAG 2.2 AA remains an appropriate benchmark for organisations looking to improve website accessibility.

Evidence type: page_content

Evidence strength: medium

Source section: will-wcag-3-0-replace-wcag-2-2

Item 6

Claim: WCAG 3.0 is a working draft published in September 2026 and is not yet a completed standard.

Evidence type: page_content

Evidence strength: high

Source section: overview

Item 7

Claim: The W3C has confirmed that WCAG 3.0 is still several years away from completion.

Evidence type: page_content

Evidence strength: medium

Source section: will-wcag-3-0-replace-wcag-2-2

Services

Accessibility audits & reviews

Relationship: primary

Url: /services/accessibility-audits-reviews/

Custom WordPress development

Relationship: supporting

Url: /services/custom-wordpress-development/

Website design & build

Relationship: supporting

Url: /services/website-design-build/

Sections

Overview

Content

Item 1

Text: Website accessibility guidelines are being updated, with the World Wide Web Consortium (W3C) publishing a new working draft of WCAG 3.0 in September 2026. The proposed changes go beyond introducing additional accessibility requirements. They also include a different approach to measuring accessibility, with the aim of providing a more detailed picture of how well websites and digital services meet people’s needs. For organisations managing existing websites or planning a redevelopment, it’s good to understand what’s being proposed. However, WCAG 3.0 is still several years away from becoming a completed standard, and many details are still under discussion. So, what’s changing, and what - if anything - should website owners be doing now?

What is WCAG 3.0?

Content

Item 1

Text: The Web Content Accessibility Guidelines (WCAG) provide internationally recognised recommendations for making websites and digital content accessible to people with disabilities. The W3C develops them, and they help designers, developers, and organisations understand how to make digital services easier for everyone to use. WCAG 3.0 is the next major generation of these guidelines. Unlike WCAG 2, which mainly focuses on web content, WCAG 3.0 is intended to cover a wider range of digital experiences, including websites, applications, publishing tools and emerging technologies. It’s also aiming to address a wider range of accessibility needs, including those of people with cognitive and learning disabilities. Although it builds on earlier versions, WCAG 3.0 introduces a different way to organise requirements and assess whether they're met.

What’s changed in the September 2026 update?

Content

Item 1

Text: On 10 September 2026, the W3C published an updated WCAG 3.0 Working Draft alongside a revised document explaining how the proposed guidelines will work. One of the most significant developments concerns the conformance model, which determines how accessibility is assessed and reported. Under WCAG 2.2, organisations generally work towards one of three conformance levels, varying in strictness: A, AA or AAA. The September draft proposes a different approach, using a single conformance level alongside reporting tiers that recognise progress towards meeting the requirements and improvements beyond them. The intention is to provide a more informative way of reporting accessibility than simply identifying whether a particular level has been achieved. However, the W3C is still seeking feedback on this approach, so the final model may well be different.

A different way of assessing accessibility

Content

Item 1

Text: The proposed WCAG 3.0 model groups accessibility requirements according to the potential consequences of not meeting them. These are currently divided into four categories.

Physical harm

Parent id: a-different-way-of-assessing-accessibility

Parent heading: A different way of assessing accessibility

Content

Item 1

Text: Requirements where an accessibility failure could cause immediate physical harm to someone with a disability.

Risk

Parent id: a-different-way-of-assessing-accessibility

Parent heading: A different way of assessing accessibility

Content

Item 1

Text: Requirements where a failure could unnecessarily increase financial, medical, legal, privacy or security risks.

Barrier

Parent id: a-different-way-of-assessing-accessibility

Parent heading: A different way of assessing accessibility

Content

Item 1

Text: Requirements where a failure could prevent someone from completing an activity or progressing through a digital service.

Friction

Parent id: a-different-way-of-assessing-accessibility

Parent heading: A different way of assessing accessibility

Content

Item 1

Text: Requirements where a failure could make an activity more difficult, even if it doesn’t prevent someone from completing it. The proposed reporting system uses these categories to distinguish different levels of progress. For example, the draft’s third reporting tier represents full conformance with all core requirements. Higher tiers would recognise additional accessibility measures and evidence of organisational practices. This could give organisations a more detailed way to communicate accessibility improvements, particularly where substantial work has been completed but further issues remain. It’s important to note that these categories and reporting arrangements are proposals. So they shouldn’t yet be used as an alternative to established WCAG 2.2 conformance assessments.

Why is WCAG 3.0 being developed to replace WCAG 2.2?

Content

Item 1

Text: Websites and digital services have changed considerably since the earlier WCAG standards were introduced.  As with many established standards, keeping pace with new technologies and the ways people use them can be difficult. Requirements that worked well when first introduced may not fully address the accessibility challenges people face today. People now interact with digital content through a wider range of devices, interfaces and technologies. Websites also contain increasingly complex functionality, from interactive applications to personalised services. WCAG 3.0 aims to provide guidance that accommodates these developments while addressing accessibility needs that existing requirements haven’t always covered adequately. The W3C also wants the guidelines to be easier to understand and more flexible across different technologies. Another important consideration is how accessibility is measured. Meeting individual technical requirements is essential, but accessibility also depends on whether people can successfully use a website or digital service. The proposed changes aim to support a more detailed assessment of accessibility outcomes while retaining clear requirements that organisations can test.

Will WCAG 3.0 replace WCAG 2.2?

Content

Item 1

Text: WCAG 3.0 is intended to become a new W3C accessibility standard, but that doesn’t mean WCAG 2.2 will immediately disappear. The W3C has confirmed that WCAG 3.0 is still several years away from completion. It also expects WCAG 2 to remain in use for several years after the new standard is finalised. For UK organisations, it’s particularly important to distinguish between the publication of accessibility guidelines and the legal requirements that apply to their websites. Introducing a new W3C standard doesn’t automatically change those legal obligations. For now, WCAG 2.2 AA remains an appropriate benchmark for organisations looking to improve website accessibility.

What should website owners do now?

Content

Item 1

Text: There’s no need to delay accessibility improvements or begin redesigning websites specifically around the proposed WCAG 3.0 requirements. In fact, you can’t, since nothing is finalised yet. The most useful approach is to keep addressing accessibility through established standards while watching for future developments, or working with someone who’s doing that for you. This can include:

Review your existing website

Parent id: what-should-website-owners-do-now

Parent heading: What should website owners do now?

Content

Item 1

Text: An accessibility audit can identify problems affecting navigation, content, forms and interactive functionality. Automated testing helps, but it won’t catch every accessibility issue. Manual checks, including keyboard navigation and assistive technology testing, are also important.

Work towards WCAG 2.2 AA

Parent id: what-should-website-owners-do-now

Parent heading: What should website owners do now?

Content

Item 1

Text: Working towards WCAG 2.2 AA is a sensible way to improve accessibility now, while also establishing a strong foundation for future standards such as WCAG 3.0.

Include accessibility in website planning

Parent id: what-should-website-owners-do-now

Parent heading: What should website owners do now?

Content

Item 1

Text: Consider accessibility when you’re thinking about requirements, designing interfaces, developing functionality, and preparing content. Addressing problems early is almost always easier than fixing them after a website launches.

Consider ongoing accessibility responsibilities

Parent id: what-should-website-owners-do-now

Parent heading: What should website owners do now?

Content

Item 1

Text: Accessibility isn’t something you can action once and then forget about. Mistakes creep in. New content, functionality and design changes can introduce problems, so regular testing and appropriate editorial guidance remain important.

What does this mean for organisations planning a website redesign?

Content

Item 1

Text: If you’re planning a new website, the development of WCAG 3.0 is another reminder that accessibility needs to be part of the project from the beginning. That doesn’t mean trying to implement requirements that are still being developed. Instead, organisations should concentrate on building accessible websites that meet current standards and can be maintained as requirements change. This includes choosing a content management system that supports accessible content, designing reusable components with accessibility in mind and establishing testing procedures throughout development. Content editors will play a key role in keeping a website accessible after launch too. With this in mind, and while they need to understand the basics, the CMS should make it easier to manage content without needing specialist technical knowledge. Too much flexibility can actually make accessibility harder to maintain. Website builders that offer endless layout options, colour pickers and styling controls can make it easy to introduce problems, even when the original website was built to meet accessibility standards. Providing editors with accessible, pre-designed components and sensible controls helps reduce these risks while still giving them the flexibility to manage their content.

Looking ahead

Content

Item 1

Text: WCAG 3.0 represents an important development in how website accessibility could be assessed and reported. The September 2026 draft provides more detail on the proposed approach, but considerable work remains before it becomes a completed standard. For website owners, the immediate priority is still the same. Building accessible digital services, testing them properly and maintaining accessibility over time will remain important regardless of how future standards develop. At Feel Created, we use WCAG 2.2 AA as our accessibility baseline when designing and developing websites. We also recognise that accessibility needs ongoing attention, particularly as content and functionality change. We’ll continue to follow the development of WCAG 3.0 and what it means for organisations managing websites and digital platforms.

Entities

Web Content Accessibility Guidelines

Feel Created

WCAG 3.0

WCAG 2.2

W3C

Concept relationships

Item 1

Subject: Accessibility audits

Predicate: can identify

Object: problems affecting navigation, content, forms and interactive functionality

Item 2

Subject: WCAG 2.2 AA

Predicate: is recommended as

Object: a practical baseline for accessibility improvements

Item 3

Subject: WCAG 3.0

Predicate: introduces

Object: a different way of assessing accessibility

Item 4

Subject: WCAG 3.0 conformance model

Predicate: includes

Object: reporting tiers

Item 5

Subject: WCAG 3.0 requirements

Predicate: categorised by

Object: consequences

Implementation patterns

Item 1

Pattern: Choose a CMS that supports accessible content

Description: Select a content management system that makes it easier to manage content without specialist technical knowledge.

Benefit: Reduces the risk of introducing accessibility issues during content updates.

Item 2

Pattern: Conformance reporting tiers

Description: Using a single conformance level with reporting tiers that recognise progress and improvements beyond core requirements.

Benefit: Provides a more informative way to report accessibility than simple pass/fail levels.

Item 3

Pattern: Design reusable components with accessibility in mind

Description: Create pre-designed components that are accessible and provide sensible controls for editors.

Benefit: Helps maintain accessibility while giving editors flexibility to manage content.

Item 4

Pattern: Stay informed on WCAG 3.0 updates

Description: Regularly review official WCAG 3.0 drafts and announcements to anticipate changes.

Benefit: Reduces risk of being caught off guard by new requirements.

Item 5

Pattern: Establish testing procedures throughout development

Description: Integrate accessibility testing at each stage of the development process.

Benefit: Identifies and fixes issues early, reducing the cost and effort of remediation.

Item 6

Pattern: Consequence-based requirement grouping

Description: Grouping accessibility requirements by potential consequences: physical harm, risk, barrier, friction.

Benefit: Helps prioritise fixes based on severity of impact on users.

Item 7

Pattern: Integrate accessibility into redesign planning

Description: Include accessibility considerations from the start of a website redesign project.

Benefit: Avoids costly retrofits and ensures compliance with future standards.

Practical guidance

Item 1

Guidance: Include accessibility in website planning from the start, considering requirements, design, development and content.

Importance: high

Item 2

Guidance: Conduct an accessibility audit to identify problems with navigation, content, forms and interactive functionality.

Importance: high

Item 3

Guidance: Consider future accessibility needs when planning website redesigns, but do not replace current standards.

Importance: medium

Item 4

Guidance: When planning a website redesign, consider how WCAG 3.0 may affect accessibility requirements.

Importance: medium

Item 5

Guidance: Understand that WCAG 3.0 is still under development and not yet a compliance requirement.

Importance: high

Item 6

Guidance: Establish ongoing testing and editorial guidance to maintain accessibility over time.

Importance: medium

Item 7

Guidance: Monitor WCAG 3.0 developments, especially the conformance model and reporting tiers.

Importance: medium

Item 8

Guidance: Continue using WCAG 2.2 conformance levels for current accessibility assessments.

Importance: high

Risk areas

Item 1

Risk: Using WCAG 3.0 proposals as an alternative to established WCAG 2.2 conformance assessments

Impact: Non-compliance with current standards and potential legal or accessibility failures

Item 2

Risk: Organisations may assume WCAG 3.0 is already a compliance requirement.

Impact: Premature changes or unnecessary resource allocation.

Item 3

Risk: Website redesigns may not account for future WCAG 3.0 requirements.

Impact: Increased cost and effort to retrofit accessibility later.

Item 4

Risk: Ignoring WCAG 3.0 developments during website redesign planning

Impact: Missed opportunity to align with future accessibility expectations

Item 5

Risk: Assuming WCAG 3.0 is finalised and implementing prematurely

Impact: Wasted effort and potential misalignment with final standard

Item 6

Risk: Implementing WCAG 3.0 requirements before finalisation

Impact: Not possible as nothing is finalised yet; could lead to wasted effort.

Item 7

Risk: Assuming a new W3C standard changes legal obligations

Impact: Legal requirements for UK organisations are not automatically changed.

Item 8

Risk: Too much flexibility in CMS editing controls

Impact: Can introduce accessibility problems even if the original website was built to standards.

Common misconceptions

Item 1

Misconception: WCAG 3.0 is a completed standard that should be used for compliance now.

Clarification: WCAG 3.0 is a working draft; WCAG 2.2 remains the current standard for conformance.

Item 2

Misconception: WCAG 3.0 will immediately replace WCAG 2.2 once finalised.

Clarification: WCAG 2 is expected to remain in use for several years after the new standard is finalised.

Item 3

Misconception: Automated testing is sufficient to ensure accessibility.

Clarification: Manual checks, including keyboard navigation and assistive technology testing, are also important.

Item 4

Misconception: WCAG 3.0 only adds more accessibility requirements.

Clarification: It also introduces a different approach to measuring accessibility with reporting tiers.

Item 5

Misconception: WCAG 3.0 will only apply to web content.

Clarification: It is intended to cover a wider range of digital experiences, including applications and emerging technologies.

Technical context

Conformance model: Proposed single conformance level with reporting tiers

Requirement categories

Publication date: 10 September 2026

Status: Working Draft

Accessibility standards

Testing methods

Cms features

Reasoning paths

Item 1

User problem: Need for a more detailed way to report accessibility improvements beyond simple conformance levels

Evidence refs

Relevant sections

Item 2

User problem: Complex functionality in websites, such as interactive applications and personalised services

Evidence refs

Relevant sections

Item 3

User problem: Existing WCAG requirements may not fully address current accessibility challenges

Evidence refs

Relevant sections

Item 4

User problem: Accessibility can degrade over time with new content and functionality changes.

Evidence refs

Relevant sections

Related links

Item 1

Text: working draft of WCAG 3.0

Url: https://www.w3.org/TR/wcag-3.0/

Source section: overview

Content profile

Content type: Insight article

Primary topic: WCAG 3.0 and its implications for website owners and digital teams

Supporting topics

Primary audience

Retrieval topics

Organisation

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.