Accessibility is simply good user experience

Source page: https://www.feelcreated.com/insights/accessibility-is-simply-good-user-experience/

Structured JSON: https://www.feelcreated.com/insights/accessibility-is-simply-good-user-experience/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-09-28

Retrieval summary

What: The article discusses how accessibility in website projects often starts with compliance but evolves into a broader focus on user experience and people.

Who

Organisation: Feel Created

Relevant for

Problems solved

Article

Type: Insight article

Primary topic: Accessibility as an essential part of good website user experience, from initial planning through to ongoing content and improvement

Intent: The article discusses how accessibility in website projects often starts with compliance but evolves into a broader focus on user experience and people.

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: Independent accessibility audits that include people with lived experience of using assistive technologies often identify issues that development teams and automated tools alone would never discover.

Evidence type: page_content

Evidence strength: medium

Source section: experience-still-matters

Item 2

Claim: Accessibility encourages teams to find solutions that preserve organisational identity while making websites easier for more people to use.

Evidence type: page_content

Evidence strength: medium

Source section: accessibility-becomes-part-of-everyday-decision-making

Item 3

Claim: The most valuable accessibility conversations revolve around whether users can find, understand, and complete tasks.

Evidence type: page_content

Evidence strength: medium

Source section: compliance-is-an-important-benchmark-but-not-the-destination

Item 4

Claim: It's rarely a question of changing the brand; more often, we introduce a complementary set of interface colours.

Evidence type: page_content

Evidence strength: medium

Source section: accessibility-becomes-part-of-everyday-decision-making

Item 5

Claim: Accessibility often works best when it encourages better decisions rather than forcing unnecessary compromise.

Evidence type: page_content

Evidence strength: medium

Source section: accessibility-becomes-part-of-everyday-decision-making

Item 6

Claim: WCAG provides an internationally recognised framework for making digital services more accessible.

Evidence type: page_content

Evidence strength: medium

Source section: compliance-is-an-important-benchmark-but-not-the-destination

Item 7

Claim: Accessibility becomes less about development and more about day-to-day publishing after launch.

Evidence type: page_content

Evidence strength: medium

Source section: accessibility-doesnt-finish-when-the-website-launches

Item 8

Claim: Automated reports are excellent at finding technical issues but do not give the full picture.

Evidence type: page_content

Evidence strength: medium

Source section: experience-still-matters

Services

Accessibility audits & reviews

Relationship: primary

Url: /services/accessibility-audits-reviews/

Digital strategy & UX planning

Relationship: supporting

Url: /services/digital-strategy-ux-planning/

UX design & user experience

Relationship: supporting

Url: /services/ux-design-user-experience/

Information architecture

Relationship: supporting

Url: /services/information-architecture/

Sections

Compliance is an important benchmark, but not the destination

Items

Content

Item 1

Text: When organisations first discover they have accessibility responsibilities, the natural response is to ask what needs to be done. That’s entirely understandable. The Web Content Accessibility Guidelines provide an internationally recognised framework for making digital services more accessible, giving organisations a shared standard against which websites can be designed, developed and assessed. Those standards matter. Without them, accessibility would become subjective and inconsistent. WCAG provides clarity, raises expectations across the industry and helps organisations understand where barriers may exist. Every guideline exists because it addresses a genuine problem that prevents somebody from accessing information or completing a task successfully. At the same time, we’ve found that the most valuable accessibility conversations rarely revolve around the wording of a particular success criterion. Instead, they revolve around much simpler questions. The standards remain an important reference throughout the project, but they gradually become the framework supporting those conversations rather than replacing them. That’s an important distinction because organisations sometimes assume accessibility is primarily about satisfying a standard, when in reality the standard exists to support a better experience. One practical lesson we’ve found is that accessibility is almost always easier to address when it’s considered early. Once visual designs have been approved, content written and functionality developed, accessibility improvements can sometimes feel like compromises. Earlier in the process, those same discussions simply become part of good design. That doesn’t necessarily make accessibility cheaper, but it often makes it far less disruptive. Colours can be refined before they become embedded throughout an interface. Navigation can evolve while user journeys are still being mapped. Content structures can be improved before hundreds of pages have been created. Perhaps the best advice we can offer organisations starting a new website project is not to ask when accessibility testing should begin, but when accessibility thinking should begin. In our experience, the answer is almost always the same: as early as possible.

Accessibility becomes part of everyday decision making

Content

Item 1

Text: One reason accessibility can feel daunting is that people often imagine it as a specialist activity that happens separately from the rest of a website project. In practice, it rarely works like that. Accessibility tends to appear wherever important decisions are made. It influences information architecture, branding, content design, interaction design, development, testing and editorial processes. Sometimes those conversations are significant, but more often they emerge through dozens of relatively small decisions that collectively shape the finished website. A good example is something as simple as a button. A client may naturally choose white text on a red button because it feels familiar and complements the brand. Depending on the colours involved, that combination may not provide sufficient contrast for many users. Black text may perform considerably better, even though it initially feels less intuitive visually. It’s easy to see how conversations like this could create the impression that accessibility means changing an established brand. In reality, that is very rarely the discussion we’re having. Organisations may have years of brand recognition behind them, reflected across printed literature, signage, advertising and other materials that aren’t realistically going to change because of a website project. In our experience, it’s rarely a question of changing the brand. More often, we introduce a complementary set of interface colours or avoid using particular colours where contrast is especially important, such as buttons, alerts or navigation. The organisation keeps its visual identity, but the website becomes easier for more people to use. We’ve found accessibility often works best when it encourages better decisions rather than forcing unnecessary compromise. It rarely asks organisations to abandon what makes their brand recognisable. More often, it encourages teams to think differently about how that brand is applied within a digital interface. That’s an important distinction because accessibility is sometimes perceived as the discipline that tells projects what they can’t do. Our experience has generally been the opposite. The conversation is usually about finding another way to achieve the same objective, one that preserves the organisation's identity while making the website easier for more people to use. Perhaps that’s one of the most valuable things accessibility brings to a project. Rather than acting as a barrier, it encourages teams to step back, understand the challenge and find a solution that supports both the organisation and the people who use the website. Those solutions are often more considered than the original approach, not because accessibility demanded compromise, but because it encouraged better design. The same pattern repeats throughout a project. A bespoke navigation may look impressive until somebody tries to use it with a keyboard. Downloadable PDFs raise questions about how accessible they’ll remain once they’re opened outside the website. The discussion then moves to videos, captions, transcripts and other ways to make the same information available. None of these decisions fundamentally changes what the website is trying to achieve. If anything, they usually strengthen it by encouraging teams to think more carefully about how information is presented and how people interact with it. That’s one reason we’ve gradually stopped seeing accessibility as something that sits alongside user experience. It increasingly feels like a way to achieve good user experience.

Experience still matters

Content

Item 1

Text: Accessibility is often associated with automated testing and rightly so. Modern accessibility tools have become an essential part of website development, identifying many technical issues quickly and consistently. Missing alternative text, heading hierarchy, HTML structure and numerous WCAG checks can all be identified far more efficiently than through manual review alone. Those tools are incredibly valuable, but they are only part of the picture. One of the more surprising things we’ve found over the years is that some of the most important accessibility conversations begin where automated testing ends. Automated reports are excellent at finding technical issues, but they don’t give you the full picture. A page may support keyboard navigation while still feeling awkward to use. A heading structure may be technically correct even though the content is difficult to understand. That’s where judgement becomes just as important as the technical requirements. That’s one reason independent accessibility audits can be so valuable. Where budgets allow, a thorough audit, particularly one that includes people with lived experience of using assistive technologies, often identifies issues that development teams and automated tools alone would never discover. That additional perspective can be invaluable because accessibility is ultimately experienced by people rather than software. At the same time, we also recognise that not every organisation can commission comprehensive external audits for every project. Accessibility shouldn’t be achievable only for organisations with the largest budgets. Professional judgement, regular review and a genuine commitment to continual improvement remain just as important, particularly where resources are more limited. We’ve found that accessibility exists on a spectrum. Some organisations have the budget to commission comprehensive external audits, undertake user testing and revisit interfaces several times before launch. Others simply don’t have those resources, despite having the same desire to improve accessibility. That doesn’t mean accessibility becomes less important. It means organisations need to make thoughtful decisions about where their efforts will have the greatest impact, combining automated testing, judgement and continual improvement in a way that is proportionate to their circumstances.

Accessibility doesn’t finish when the website launches

Content

Item 1

Text: After launch, accessibility becomes less about development and more about day-to-day publishing. Developers and designers establish the technical foundations, but every new page, document and video can either strengthen or weaken the website’s accessibility. Editors still need to write alternative text, structure content carefully, prepare accessible documents and provide captions or transcripts where they’re needed. Those responsibilities often surprise organisations because they’re not really website development tasks. They’re editorial and organisational responsibilities. We’ve seen technically excellent websites gradually become less accessible over time, not because the platform was poorly built, but because accessibility hadn’t become part of the organisation’s day-to-day content processes. Equally, we’ve worked with organisations where accessibility became part of editorial culture, with content teams understanding their role and continually improving the website long after launch. Accessibility follows much the same pattern as performance, security and content quality. Strong technical foundations matter, but maintaining standards depends on the decisions people continue making every day.

Good accessibility requires judgement

Content

Item 1

Text: One aspect of accessibility that often receives less attention is informed judgement. It would be easy to think that every accessibility decision has a simple right or wrong answer, but real projects are rarely that straightforward. Organisations have existing brands, complex systems, limited budgets and years of accumulated content. Improving accessibility often means understanding how to make meaningful progress within those realities rather than pretending they don’t exist. The principle of disproportionate burden reflects that reality. It’s sometimes misunderstood as a way of avoiding accessibility responsibilities, but that’s not its purpose. Organisations may need to prioritise improvements where resources are limited, while still addressing barriers that prevent people from accessing information or completing essential tasks. The principle recognises that budgets, competing priorities and large amounts of legacy content all influence how quickly improvements can be made. What matters is continuing to make meaningful progress. We’ve worked with organisations that have brought together multiple legacy websites into a single modern platform. Building the new website to current accessibility standards was only one part of the project. Hundreds of historic PDF documents also required attention, many of which had been created years before modern accessibility standards were widely understood. Updating every document before launch simply wasn’t realistic. Ignoring the issue wasn’t acceptable either. Instead, the organisations acknowledged the work that remained, published clear accessibility statements, prioritised documents according to need and continued to improve the library over time as resources allowed. That’s why we’ve never seen accessibility as something that’s finished on launch day or measured by a single pass or fail result. What matters is continuing to remove barriers, being honest about what still needs attention and improving the experience over time.

Accessibility is ultimately about people

Content

Item 1

Text: Perhaps that’s why our own perspective on accessibility has changed over the years. The more projects we’ve delivered, the less we’ve thought about accessibility as a separate technical discipline and the more we’ve seen it as another way of understanding people. Better semantic HTML helps screen readers while creating a clearer structure for search engines and AI systems. Clear navigation makes websites easier to move around, whether someone is using a keyboard or a mouse. Logical heading structures help assistive technologies interpret a page, but they’re just as useful for someone quickly scanning the content before a meeting. None of those improvements exists because of AI, search engines or compliance. They exist because they help people use websites more successfully. The wider technical benefits follow naturally from that. Accessibility will quite rightly continue to be shaped by legislation, standards and compliance. Those things are important because they establish a common expectation and help organisations deliver more inclusive digital services. They should never be dismissed or treated as optional. The projects that leave the strongest impression on us, however, are rarely the ones that simply achieve compliance. They’re the ones where accessibility quietly changes the way people think about the website they are building. Perhaps that’s one of the less obvious benefits; that’s why we’ve gradually stopped thinking about accessibility as something separate from good user experience. It doesn’t ask organisations to stop being themselves or to compromise the purpose of their website. More often, it asks them to understand their users a little better and to make more thoughtful decisions about how the website supports them. Compliance will always remain an important benchmark and for many organisations it is rightly a legal responsibility. The opportunity is not to stop seeing accessibility as an obligation, but to stop letting it remain only an obligation. When accessibility becomes part of how a website is planned, designed, developed, and managed, it usually leaves the website stronger than it would otherwise be. In the end, the real value of accessibility isn’t found in compliance alone. It’s found in websites that are easier to understand, easier to navigate and easier for more people to use.

User Experience and Accessibility: A Complete Guide

Content

Item 1

Text: Understand how user research, journeys, information architecture, accessible design and usability testing work together to... 12 minutes read Read the guide

What Is User Experience (UX)?

Content

Item 1

Text: Learn what user experience means, how UX research and testing work, and why reducing unnecessary... 18 minutes read Read the guide

Website Accessibility Explained

Content

Item 1

Text: Learn what website accessibility means, how WCAG 2.2 applies, how accessibility is tested and how... 13 minutes read Read the guide

User Journeys Explained

Content

Item 1

Text: A great user journey makes every interaction feel effortless. Learn what user journeys are, why... 15 minutes read Read the guide

Entities

Web Content Accessibility Guidelines (WCAG)

UK accessibility legislation

Disproportionate burden

Assistive technologies

Editorial culture

User experience

Colour contrast

Brand identity

Legacy content

Accessibility

WCAG

Concept relationships

Item 1

Subject: Accessibility

Predicate: is often introduced through

Object: legislation or procurement

Item 2

Subject: Independent audits

Predicate: identify issues that

Object: automated tools miss

Item 3

Subject: Accessibility

Predicate: depends on

Object: day-to-day publishing decisions

Item 4

Subject: Accessibility

Predicate: is a way to achieve

Object: good user experience

Item 5

Subject: WCAG

Predicate: provides

Object: an internationally recognised framework

Item 6

Subject: Accessibility

Predicate: influences

Object: information architecture

Item 7

Subject: Compliance

Predicate: is a benchmark, not

Object: the destination

Item 8

Subject: Accessibility

Predicate: influences

Object: interaction design

Item 9

Subject: Automated testing

Predicate: is part of

Object: accessibility

Item 10

Subject: Accessibility

Predicate: requires

Object: informed judgement

Implementation patterns

Item 1

Pattern: Integrate accessibility into design process

Description: Encourage teams to step back and find solutions that support both the organisation and users, leading to more considered design.

Benefit: Produces websites that are easier for more people to use while preserving organisational identity

Item 2

Pattern: Complementary interface colours

Description: Introduce a set of interface colours that complement the brand, avoiding colours with poor contrast for critical elements like buttons and alerts.

Benefit: Maintains brand recognition while improving accessibility.

Item 3

Pattern: Early accessibility integration

Description: Address accessibility during initial design and planning phases, before visual designs are approved and content is written.

Benefit: Makes accessibility improvements less disruptive and more natural.

Item 4

Pattern: Combine automated and manual accessibility testing

Description: Use automated tools for technical checks and manual review for usability and judgement.

Benefit: Identifies both technical issues and user experience problems

Item 5

Pattern: Legacy website consolidation

Description: Bringing multiple legacy websites into a single modern platform, including remediation of historic PDFs

Benefit: Improves overall accessibility and reduces fragmentation

Item 6

Pattern: Post-launch accessibility maintenance

Description: Editors write alt text, structure content, prepare accessible documents, and provide captions/transcripts

Benefit: Maintains accessibility standards over time

Item 7

Pattern: Integrating accessibility into project phases

Description: Accessibility becomes woven into design, content, development, testing, and governance.

Benefit: Improves overall website quality and user experience

Item 8

Pattern: Editorial culture integration

Description: Content teams understand their role and continually improve accessibility

Benefit: Long-term accessibility improvement

Practical guidance

Item 1

Guidance: Consider commissioning independent accessibility audits, especially those involving people with lived experience of assistive technologies, where budgets allow.

Importance: medium

Item 2

Guidance: For organisations with limited resources, maintain professional judgement, regular review and a genuine commitment to continual improvement.

Importance: medium

Item 3

Guidance: Use automated testing tools to identify technical issues efficiently, but supplement with manual review and user testing.

Importance: high

Item 4

Guidance: Combine automated testing, judgement, and continual improvement proportionately to circumstances

Importance: high

Item 5

Guidance: Prioritise improvements where resources are limited while addressing barriers to essential tasks

Importance: medium

Item 6

Guidance: Consider accessibility as early as possible in a website project, not just when testing begins.

Importance: high

Item 7

Guidance: Integrate accessibility into everyday decision making across design, content, and development.

Importance: medium

Item 8

Guidance: Introduce complementary interface colours to maintain brand identity while improving contrast.

Importance: medium

Risk areas

Item 1

Risk: Accessibility improvements can feel like compromises if addressed after designs are approved.

Impact: May lead to disruption and resistance to changes.

Item 2

Risk: Accessibility perceived as a specialist activity separate from the rest of the project.

Impact: May lead to accessibility being overlooked in key decisions.

Item 3

Risk: Over-reliance on automated testing may miss usability issues that affect real users

Impact: Websites may pass technical checks but still be difficult to use for people with disabilities

Item 4

Risk: Misunderstanding disproportionate burden as an excuse to avoid accessibility

Impact: Organisations may neglect essential accessibility improvements

Item 5

Risk: Accessibility declines post-launch if not integrated into content processes

Impact: Websites become less accessible over time, undermining initial technical standards

Item 6

Risk: Colour combinations may not provide sufficient contrast for many users.

Impact: Reduced usability and accessibility for users with visual impairments.

Item 7

Risk: Accessibility may be seen as a barrier rather than an opportunity

Impact: Teams may avoid accessibility considerations, leading to less inclusive websites

Item 8

Risk: Limited budgets and legacy content slow accessibility progress

Impact: Meaningful progress may be delayed, affecting user access

Common misconceptions

Item 1

Misconception: Accessibility is a specialist activity that happens separately from the rest of a website project.

Clarification: In practice, accessibility appears wherever important decisions are made.

Item 2

Misconception: Disproportionate burden is a way to avoid accessibility responsibilities

Clarification: It recognises resource constraints but still requires addressing barriers and making meaningful progress

Item 3

Misconception: Every accessibility decision has a simple right or wrong answer

Clarification: Real projects involve existing brands, complex systems, and limited budgets, requiring judgement

Item 4

Misconception: Accessibility is primarily about satisfying a standard

Clarification: The standard exists to support a better experience for users

Item 5

Misconception: Accessibility means changing an established brand.

Clarification: It rarely involves changing the brand; more often, complementary interface colours are introduced.

Item 6

Misconception: Accessibility tells projects what they can't do.

Clarification: It often encourages better decisions and finding another way to achieve goals.

Item 7

Misconception: Accessibility is only about automated testing

Clarification: Automated testing is valuable but only part of the picture; human judgement and lived experience are essential

Item 8

Misconception: Accessibility requires compromise

Clarification: Accessibility often encourages better design and more considered solutions

Technical context

Automated testing: Modern accessibility tools identify technical issues such as missing alternative text, heading hierarchy, HTML structure and WCAG checks.

Manual review: Human judgement is needed to assess usability issues that automated tools cannot detect, such as awkward keyboard navigation or unclear content.

Reasoning paths

Item 1

User problem: Accessibility is often perceived as a specialist activity separate from the rest of a website project

Why this article is relevant: This page explains the topic and gives practical points to consider.

Evidence refs

Relevant sections

Item 2

User problem: Technically excellent websites become less accessible over time due to lack of process integration

Why this article is relevant: This page explains the topic and gives practical points to consider.

Evidence refs

Relevant sections

Item 3

User problem: Accessibility improvements can feel like compromises when addressed late in a project

Why this article is relevant: This page explains the topic and gives practical points to consider.

Evidence refs

Relevant sections

Item 4

User problem: Organisations first encounter accessibility through legislation or procurement

Why this article is relevant: This page explains the topic and gives practical points to consider.

Evidence refs

Relevant sections

Content profile

Content type: Insight article

Primary topic: Accessibility as an essential part of good website user experience, from initial planning through to ongoing content and improvement

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.