{ "meta": { "type": "knowledge_hub", "language": "en-GB", "last_updated": "2026-10-01", "ai_endpoint": "/knowledge-hub/user-experience-and-accessibility-a-complete-guide/ai.json", "source_page": "/knowledge-hub/user-experience-and-accessibility-a-complete-guide/" }, "retrieval_summary": { "what": "This guide explains how user experience and accessibility work together, covering user needs, research, journeys, information architecture, interface design, accessibility and ongoing testing.", "who": { "organisation": "Feel Created" }, "relevant_for": [ "Digital and web managers", "Marketing and communications teams", "Website owners", "UX and design teams", "Content teams", "Organisations planning or improving a website or digital platform" ], "problems_solved": [ "Visitors may not understand internal organisational structure", "Navigation using internal wording causes confusion", "Related information split across departments", "Visitors needing to know which team owns a service", "People leave pages for various reasons, making analytics figures ambiguous", "Interviews may uncover issues affecting only a small number of people", "User needs change after launch due to service changes, new audiences, and content growth", "Problems are missed when each page or system is assessed separately" ] }, "page": { "title": "User experience and accessibility: a complete guide", "slug": "user-experience-and-accessibility-a-complete-guide", "url": "/knowledge-hub/user-experience-and-accessibility-a-complete-guide/", "canonical_url": "https://www.feelcreated.com/knowledge-hub/user-experience-and-accessibility-a-complete-guide/", "status": "published" }, "article": { "type": "Knowledge Hub guide", "primary_topic": "How user experience and accessibility work together to create websites that are easier for more people to understand, navigate and use.", "intent": "This guide explains how user experience and accessibility work together, covering user needs, research, journeys, information architecture, interface design, accessibility and ongoing testing.", "audience": [ "Digital and web managers", "Marketing and communications teams", "Website owners", "UX and design teams", "Content teams", "Organisations planning or improving a website or digital platform" ] }, "topics": [ "How user experience and accessibility work together to create websites that are easier for more people to understand, navigate and use.", "User experience (UX)", "Accessibility", "User research", "Website navigation", "Information architecture", "User interface (UI) design", "Task completion", "User journey mapping", "Content design", "Analytics interpretation", "Organisational knowledge in research", "Interface design" ], "content_focus": [ "Definition of user experience (UX)", "Relationship between UX and accessibility", "Importance of understanding user needs", "User research process", "Impact of organisational structure on user experience", "Practical guidance for improving website usability and accessibility", "Planning user journeys and information architecture", "Information architecture principles", "Labeling and terminology", "Content design planning" ], "canonical_claims": [ { "claim": "User experience includes whether people can understand what the organisation offers, find useful information, make decisions and complete the task that brought them there.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "understanding-user-experience", "id": "claim-001" }, { "claim": "Accessibility needs to influence planning, design, development and everyday publishing, rather than being left to a technical review near the end of a project.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "accessibility-as-part-of-the-experience", "id": "claim-002" }, { "claim": "Problems arise when navigation uses internal wording, related information is split across departments or visitors need to know which team owns a service.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "understanding-user-experience", "id": "claim-003" }, { "claim": "The Web Content Accessibility Guidelines (WCAG) provide an internationally recognised standard for identifying many common barriers.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "accessibility-as-part-of-the-experience", "id": "claim-004" }, { "claim": "User research examines what users are trying to achieve, what they already know and where the current experience causes difficulty.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "understanding-people-and-their-needs", "id": "claim-005" }, { "claim": "Reviewing the user journey as a whole can reveal problems that are easy to miss when each page or system is assessed separately.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "planning-journeys-through-a-website", "id": "claim-006" }, { "claim": "Research does not replace existing organisational knowledge; it brings another perspective into decisions.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "understanding-people-and-their-needs", "id": "claim-007" }, { "claim": "Adding a top-level menu item for every new service gradually makes the website harder to navigate.", "evidence_type": "page_content", "evidence_strength": "medium", "source_section": "organising-information-and-content", "id": "claim-008" } ], "services": [ { "name": "Website design & digital platform development", "relationship": "supporting", "url": "/services/website-design-digital-platform-development/" }, { "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": "Digital planning & research", "relationship": "supporting", "url": "/services/digital-planning-research/" } ], "sections": [ { "id": "overview", "heading": "Overview", "type": "introduction", "content": [ { "type": "paragraph", "text": "A good website experience depends on a lot of interconnected decisions. Teams need to understand the people using the website, organise information around their needs and provide content and controls that make important tasks manageable. They also need to account for the devices people use, what they already know and any access needs that affect how they use the service. User experience and accessibility bring those decisions together. They influence how people find information, navigate a website, understand their options and get back on track if something goes wrong. This page introduces the main areas within user experience and accessibility, with links to supporting Knowledge Hub guides as they become available." } ] }, { "id": "understanding-user-experience", "heading": "Understanding user experience", "type": "section", "content": [ { "type": "paragraph", "text": "User experience, or UX as it’s usually shortened to, describes someone’s overall experience of using a website. It includes whether people can understand what the organisation offers, find useful information, make decisions and complete the task that brought them there. It also covers what happens when they take a wrong turn, enter information incorrectly or need to change their approach. Visual design contributes to that experience, but it is only one part of it. A website visit will usually involve more than one page. Someone might begin with a search result, compare several services, open a document and continue into a separate booking or payment system. They could then return later from an email or complete the final step over the phone. From the organisation’s point of view, the task may involve various teams, platforms and processes. To the person trying to get what they need, those differences do not matter; it is all one experience. Problems arise when navigation uses internal wording, related information is split across departments or visitors need to know which team owns a service. Good UX reduces that unnecessary confusion. People should be able to find what they need without first having to understand how the organisation is structured behind the scenes. User interface design, or UI design, focuses on the pages, controls and visual elements people interact with. UX looks at how those elements work alongside content, accessibility, technology and the complete task." } ] }, { "id": "user-journeys-explained", "heading": "User Journeys Explained", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "A great user journey makes every interaction feel effortless. Learn what user journeys are, why... 15 minutes read Read the guide" } ] }, { "id": "information-architecture-explained", "heading": "Information Architecture Explained", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "Learn how information architecture organises website content, improves navigation and helps people find the information... 11 minutes read Read the guide" } ] }, { "id": "website-accessibility-explained", "heading": "Website Accessibility Explained", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "Learn what website accessibility means, how WCAG 2.2 applies, how accessibility is tested and how... 13 minutes read Read the guide" } ] }, { "id": "designing-for-different-user-needs", "heading": "Designing for Different User Needs", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "understanding-people-and-their-needs", "heading": "Understanding people and their needs", "type": "section", "content": [ { "type": "paragraph", "text": "People involved in managing a website usually know the organisation well. Visitors may know very little about it. That familiarity can make it easy to assume visitors will understand the same information, follow the route the team expects or use the same words. It can also hide differences in devices, access needs and the circumstances in which someone is trying to complete a task. Learning more about the people using the website helps teams make better decisions about what it needs to contain and how it should work. User research is the process of learning about the people who use a website. It examines what they’re trying to achieve, what they already know and where the current experience causes difficulty. Organisations may already know more about website use than they realise. Analytics can show where people arrive, which pages they visit and where they leave, while search terms, support enquiries and feedback can reveal unfamiliar wording or recurring questions. The figures do not explain everything on their own and they still need to be interpreted. Someone may leave a page because they found the answer, while an interview may uncover a problem that only affects a small number of people. The useful part comes from seeing whether the same issue appears elsewhere. Existing organisational knowledge also matters. Staff understand services, processes, constraints and recurring problems. Research does not replace that expertise. It brings another perspective into the decisions being made. People’s needs do not always stay the same after a website launches. Services change, new audiences appear and content grows. Devices and the situations in which people use the website change too. Research remains useful after launch because changes to services, audiences and content can alter what people need from the website." } ] }, { "id": "how-do-people-use-websites", "heading": "How Do People Use Websites?", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "planning-journeys-through-a-website", "heading": "Planning journeys through a website", "type": "section", "content": [ { "type": "paragraph", "text": "People usually visit a website because they need to answer a question, decide between several options or complete a task. A user journey maps the route someone takes to complete a task or reach an outcome. It considers where they begin, the steps taken, the decisions made, the alternatives available and any obstacles that slow them down or even stop them. Reviewing the journey as a whole can reveal problems that are easy to miss when each page or system is assessed separately. Journey mapping begins by showing what someone currently does to complete a task. It can then highlight where they need information, where they make decisions and where they go in a different direction. Proposed improvements should be kept separate from what is already known, so teams can see which parts still need testing. Some tasks need several stages because people need time and information before deciding what to do. For instance, choosing a course or applying for support may involve comparing options, checking requirements and understanding what happens next. A shorter route is not always better if it removes information people need. Looking at the stages together can show missing information, unclear responsibilities and points where someone is passed between teams or systems without knowing what happens next." } ] }, { "id": "how-do-websites-build-confidence", "heading": "How do websites build confidence?", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "Read the guide to find out more. 8 minutes read Read the guide" } ] }, { "id": "navigation-that-works", "heading": "Navigation That Works", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "navigation-design-explained", "heading": "Navigation Design Explained", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "organising-information-and-content", "heading": "Organising information and content", "type": "section", "content": [ { "type": "paragraph", "text": "Information architecture is the planning behind how information is grouped, labelled and connected across a website. It helps people see what the website contains, understand how subjects relate and find their way between them. Content design works alongside it by deciding what information people need at each point and how it should be presented. Information architecture covers the categories used to group content, the labels applied to them and the relationships between pages. That planning can be seen through navigation, breadcrumbs, internal links, search, filters and page headings. Navigation is one way of presenting the architecture, but it is not the complete system behind it. As a website grows, adding another top-level menu item for every new service or campaign may solve an immediate need, but it gradually makes the website harder to navigate. New information should usually fit within a category people already recognise. If it does not, the categories themselves may no longer make sense. Labels matter as well. Internal service names may be accurate but unfamiliar to visitors. A useful label should use words someone is likely to recognise, while retaining any professional or legal terminology that still needs to be used. Content design considers what information should appear within that system and when. Someone may need to compare options before starting a task, check what’s needed before completing a form and understand what happens after submitting it. Planning information in this way also makes future publishing easier. New pages, guidance and services can be added without repeatedly inventing new sections or changing how the whole website works." } ] }, { "id": "what-is-content-design", "heading": "What is Content Design?", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "designing-usable-interfaces-and-navigation", "heading": "Designing usable interfaces and navigation", "type": "section", "content": [ { "type": "paragraph", "text": "Research, journey planning and information architecture eventually need to become pages and interactions that people can use. The interface should make available actions easy to recognise, show which information matters and explain what will happen next. People also need to know whether an action has worked, what needs correcting and where they are within a process. People bring habits from other websites with them. They expect links to look like links, menus to open in familiar ways and buttons to describe the action they perform. Forms should explain what needs fixing rather than leaving someone to work it out. These familiar patterns reduce the amount people need to learn before they can use a website. They do not prevent an organisation from creating something distinctive. Typography, colour, imagery, layout and interaction can all express its identity without making ordinary actions difficult to recognise. Interface wording should tell people what an action will do. “Check your eligibility” is more useful than “Continue”, while navigation labels should use terms visitors are likely to recognise. The interface also needs to respond as people use it. Buttons and links should show that they have been activated, forms should identify errors and a completed submission should confirm that the information has been received. When an action is unavailable, the reason should be explained rather than leaving an apparently inactive control. Mobile layouts need more than a desktop design squeezed into a smaller space. Controls need room to use comfortably, content should remain in a sensible order and navigation must still be easy to follow. Repeated tasks should behave consistently throughout the website. Controls that perform the same action should look and work the same way, so people do not have to relearn them from one page to the next. Shared layouts also make the interface easier to maintain than a collection of one-off designs." } ] }, { "id": "accessibility-beyond-compliance", "heading": "Accessibility Beyond Compliance", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "accessibility-as-part-of-the-experience", "heading": "Accessibility as part of the experience", "type": "section", "content": [ { "type": "paragraph", "text": "Web accessibility means removing barriers that can stop people from finding, understanding or using a website. It affects written content, navigation, forms, documents, video, audio and interactive features. Accessibility, therefore, needs to influence planning, design, development and everyday publishing, rather than being left to a technical review near the end of a project. People use websites in many different ways. Some navigate with a keyboard instead of a mouse. Others use screen readers, voice control, magnification or adapted browser and device settings. People may zoom substantially, increase text size, reduce animation or change colours to suit their needs. Accessibility problems can appear at any point in a website’s life. An editor might publish vague link text or an inaccessible document. Elsewhere, colour may be carrying information on its own, a control may not work by keyboard or an external booking system may create barriers that the main website does not. An inaccessible PDF, missing heading structure or poorly labelled image can affect a page even when the underlying website has been built well. The Web Content Accessibility Guidelines, usually known as WCAG, provide an internationally recognised standard for identifying many common barriers. They give organisations, suppliers and auditors a shared set of testable requirements. Accessibility is shared work. Content, design and development decisions all affect it, as do later updates and the third-party systems an organisation chooses. Website owners need to make sure it remains part of ongoing website management." } ] }, { "id": "animation-with-purpose", "heading": "Animation With Purpose", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "helping-people-feel-confident", "heading": "Helping people feel confident", "type": "section", "content": [ { "type": "paragraph", "text": "People continually judge whether they understand a website and whether they can rely on what it tells them. Outdated information, unexplained requests, inconsistent wording and unexpected behaviour can all create doubt. A polished design may make a strong first impression, but confidence depends on what happens as someone moves through the website. People gain confidence when the website gives them clear signs that it is accurate, up to date and dependable. The information should explain whether a service applies to them, what they need to do and what will happen next. Any claims made need enough support for the decision someone is trying to make. That can include prices, timescales, policies, qualifications, case studies or named sources. The website does not need to prove everything in the same way, but people should be able to check the information that matters. Forms often have a strong effect on confidence. People need to know why information is being requested and how it will be used. Errors should explain what needs fixing, while a completed submission should confirm what has happened and when the organisation is likely to respond. Basic organisational details matter too. Contact information, named teams and important policies should be easy to find and consistent across the website. Small problems can weaken confidence quickly. A service described differently on several pages, an old date in a document or a button that behaves unexpectedly may make someone question the rest of the experience. People become more confident when the website behaves consistently and gives them the information they need at each stage." } ] }, { "id": "what-is-user-experience-ux", "heading": "What Is User Experience (UX)?", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "Learn what user experience means, how UX research and testing work, and why reducing unnecessary... 18 minutes read Read the guide" } ] }, { "id": "testing-and-improving-the-experience", "heading": "Testing and improving the experience", "type": "section", "content": [ { "type": "paragraph", "text": "The people who planned and commissioned a website already know how it is intended to work. That makes it difficult for them to fairly assess the experience in the same way a first-time visitor would. Testing shows whether people can understand the information, use the controls and complete important tasks. Usability testing focuses on what people do and where they struggle, rather than whether they like the design. Task-based usability testing involves asking people to attempt realistic activities using a prototype or live website. The person leading the session observes what happens rather than teaching the intended route. Completing the task does not necessarily mean it was easy. Someone may have visited several wrong pages before finding the right one or fixed a form error without knowing why it happened. Observing someone as they work through these activities can show where the website made them work harder than it should. Website features are usually easier to test before they go live. Development teams will often have a separate test environment where navigation, page order, wording and interactions can be reviewed while changes are still straightforward to make. Once the website is live, testing can include the real content, devices and systems people rely on. Analytics, form data, feedback and support enquiries can all point towards areas worth investigating. They may show where people arrive, which routes they take and where they leave or run into problems. Those figures still need interpreting. Leaving a page may mean someone found what they needed, while a heavily visited page may be useful or difficult to understand. The value comes from using the evidence to decide what should change, then checking whether the change improved the task. That work should continue as the website develops and new content, features or external systems are added." } ] }, { "id": "reducing-cognitive-load", "heading": "Reducing Cognitive Load", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "usability-testing-explained", "heading": "Usability Testing Explained", "type": "section", "parent_id": "a-website-works-better-when-people-come-first", "parent_heading": "A website works better when people come first", "content": [ { "type": "paragraph", "text": "More information coming soon Coming soon" } ] }, { "id": "a-website-works-better-when-people-come-first", "heading": "A website works better when people come first", "type": "section", "content": [ { "type": "paragraph", "text": "A good website experience begins with understanding the people expected to use it. That understanding should influence how information is organised, how tasks are planned, how interfaces behave and how barriers are removed. Testing then shows where those decisions are working and where the website still needs attention. The strongest websites are not built around internal structures or assumptions. They are planned around what people need to understand, decide and do." } ] } ], "entities": [ { "name": "Web Content Accessibility Guidelines", "type": "Standard" }, { "name": "User interface (UI) design", "type": "Topic" }, { "name": "Information architecture", "type": "Topic" }, { "name": "User experience (UX)", "type": "Topic" }, { "name": "User journey mapping", "type": "Topic" }, { "name": "Interface design", "type": "Topic" }, { "name": "Mobile usability", "type": "Topic" }, { "name": "Content design", "type": "Topic" }, { "name": "Accessibility", "type": "Topic" }, { "name": "User research", "type": "Topic" }, { "name": "Analytics", "type": "Topic" }, { "name": "WCAG", "type": "Standard" } ], "concept_relationships": [ { "subject": "Analytics", "predicate": "can show", "object": "where people arrive, pages visited, and where they leave" }, { "subject": "Information architecture", "predicate": "covers", "object": "grouping, labelling and connecting content" }, { "subject": "User experience (UX)", "predicate": "includes", "object": "understanding what the organisation offers" }, { "subject": "User journey mapping", "predicate": "reveals", "object": "problems in completing tasks" }, { "subject": "User experience (UX)", "predicate": "includes", "object": "finding useful information" }, { "subject": "Information architecture", "predicate": "influences", "object": "navigation usability" }, { "subject": "Content design", "predicate": "works alongside", "object": "information architecture" }, { "subject": "Interface design", "predicate": "requires", "object": "familiar patterns" }, { "subject": "Content design", "predicate": "supports", "object": "future publishing" }, { "subject": "Consistency", "predicate": "improves", "object": "user experience" } ], "implementation_patterns": [ { "pattern": "Information architecture planning", "description": "Planning how information is grouped, labelled and connected across a website, visible through navigation, breadcrumbs, internal links, search, filters and page headings.", "benefit": "Helps people see what the website contains and find their way between subjects" }, { "pattern": "Journey mapping", "description": "Showing what someone currently does to complete a task, highlighting where they need information, make decisions, and go in a different direction.", "benefit": "Reveals problems that are missed when assessing pages or systems separately" }, { "pattern": "Ongoing accessibility management", "description": "Accessibility is considered in every update and third-party system choice, not just at launch.", "benefit": "Reduces the risk of barriers appearing over time." }, { "pattern": "User research", "description": "Process of learning about the people who use a website, examining their goals, existing knowledge and difficulties.", "benefit": "Helps teams make better decisions about website content and functionality." }, { "pattern": "Consistent information presentation", "description": "Contact details, named teams, and policies are easy to find and consistent across the website.", "benefit": "Builds user confidence and trust." }, { "pattern": "Responsive mobile design", "description": "Designing mobile layouts with comfortable control space, sensible content order, and easy navigation.", "benefit": "Usable experience on mobile devices." }, { "pattern": "Clear form design", "description": "Forms explain why information is requested, how it will be used, and confirm submission outcomes.", "benefit": "Improves user confidence and reduces errors." }, { "pattern": "Consistent interaction design", "description": "Controls that perform the same action look and work the same way throughout the website.", "benefit": "Users do not have to relearn interactions from one page to the next." } ], "practical_guidance": [ { "guidance": "Map user journeys to show current behaviour, highlight decision points and identify where improvements are needed, keeping proposed improvements separate from known facts.", "importance": "medium" }, { "guidance": "Conduct user research to understand what users are trying to achieve, what they already know and where the current experience causes difficulty.", "importance": "medium" }, { "guidance": "Organisations should avoid using internal wording in navigation and structure information around user needs rather than internal departments.", "importance": "high" }, { "guidance": "Use analytics, search terms, support enquiries and feedback to identify potential issues, but interpret them with other evidence.", "importance": "medium" }, { "guidance": "Review the whole journey to spot missing information, unclear responsibilities and handoffs between teams or systems.", "importance": "medium" }, { "guidance": "Teams should learn about the people using the website to make better decisions about content and functionality.", "importance": "high" }, { "guidance": "Combine research findings with existing organisational knowledge about services, processes and constraints.", "importance": "medium" }, { "guidance": "Integrate accessibility into all stages of website planning, design, development, and content publishing.", "importance": "high" } ], "risk_areas": [ { "risk": "Accessibility problems can emerge at any point in a website's life, including from third-party systems.", "impact": "Barriers may affect users even if the main website is built well." }, { "risk": "Inaccessible PDFs, missing heading structure, or poorly labelled images can affect a page.", "impact": "Users may be unable to access content despite a well-built website." }, { "risk": "Assessing pages or systems separately without considering the whole journey", "impact": "May miss cross-page or cross-system problems" }, { "risk": "Assuming visitors understand internal organisational structure", "impact": "Visitors may struggle to find what they need, leading to confusion and task failure." }, { "risk": "Misinterpreting analytics figures without qualitative context", "impact": "May lead to incorrect conclusions about user behaviour" }, { "risk": "Removing information from a user journey to shorten it", "impact": "Could remove essential information people need, harming the experience" }, { "risk": "Splitting related information across departments", "impact": "Visitors may have to piece together information, increasing cognitive load and frustration." }, { "risk": "Using internal service names as labels", "impact": "Visitors may not recognise them" } ], "common_misconceptions": [ { "misconception": "Accessibility is only a technical review at the end of a project.", "clarification": "Accessibility needs to influence planning, design, development and everyday publishing." }, { "misconception": "Visual design is the main part of user experience.", "clarification": "Visual design contributes to the experience but is only one part; UX also includes content, accessibility, technology and the complete task." }, { "misconception": "Analytics figures alone explain user behaviour", "clarification": "Figures need interpretation and should be combined with other evidence like interviews and organisational knowledge" }, { "misconception": "Familiar patterns prevent distinctive design", "clarification": "Typography, colour, imagery, layout and interaction can express identity without making actions difficult to recognise." }, { "misconception": "A polished design ensures user confidence.", "clarification": "Confidence depends on what happens as someone moves through the website, not just first impressions." }, { "misconception": "A shorter user journey is always better", "clarification": "A shorter route may remove information people need, so it is not always better" } ], "technical_context": { "accessibility_standards": "WCAG", "assistive_technologies": "screen readers, voice control, magnification, adapted browser and device settings", "accessibility_considerations": "keyboard navigation, colour contrast, heading structure, image labels, forms, documents, video, audio" }, "reasoning_paths": [ { "user_problem": "User needs change after launch due to service changes, new audiences, and content growth", "why_this_guide_is_relevant": "This page explains the topic and gives practical points to consider.", "evidence_refs": [ "claim-003", "claim-004", "claim-008" ], "relevant_sections": [ "overview", "accessibility-as-part-of-the-experience", "information-architecture-explained" ] }, { "user_problem": "People leave pages for various reasons, making analytics figures ambiguous", "why_this_guide_is_relevant": "This page explains the topic and gives practical points to consider.", "evidence_refs": [ "claim-001" ], "relevant_sections": [ "overview", "understanding-user-experience", "information-architecture-explained" ] }, { "user_problem": "Adding top-level menu items for every new service makes navigation harder", "why_this_guide_is_relevant": "This page explains the topic and gives practical points to consider.", "evidence_refs": [ "claim-008", "claim-003" ], "relevant_sections": [ "information-architecture-explained", "navigation-that-works", "navigation-design-explained" ] }, { "user_problem": "Desktop designs squeezed into smaller spaces are not effective for mobile", "why_this_guide_is_relevant": "This page explains the topic and gives practical points to consider.", "evidence_refs": [ "claim-002" ], "relevant_sections": [ "understanding-user-experience", "designing-for-different-user-needs", "navigation-design-explained" ] } ], "knowledge_hub": { "page_type": "guide", "learning_intent": "This guide explains how user experience and accessibility work together, covering user needs, research, journeys, information architecture, interface design, accessibility and ongoing testing.", "topic_hierarchy": { "primary": "How user experience and accessibility work together to create websites that are easier for more people to understand, navigate and use.", "supporting": [ "User experience (UX)", "Accessibility", "User research", "Website navigation", "Information architecture", "User interface (UI) design", "Task completion", "User journey mapping" ] }, "evergreen_use": true }, "content_profile": { "content_type": "Knowledge Hub guide", "primary_topic": "How user experience and accessibility work together to create websites that are easier for more people to understand, navigate and use.", "supporting_topics": [ "User experience (UX)", "Accessibility", "User research", "Website navigation", "Information architecture", "User interface (UI) design" ], "primary_audience": [ "Digital and web managers", "Marketing and communications teams", "Website owners", "UX and design teams", "Content teams", "Organisations planning or improving a website or digital platform" ] }, "retrieval_topics": [ "How user experience and accessibility work together to create websites that are easier for more people to understand, navigate and use.", "User experience (UX)", "Accessibility", "User research", "Website navigation", "Information architecture", "User interface (UI) design", "Task completion", "User journey mapping", "Content design", "Analytics interpretation", "Organisational knowledge in research" ], "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." } }