NHSnhs.uk
Accessibility Score
Issues Found
Issues Found
ModerateAll page content should be contained by landmarks6 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Failing Elements
<h2>Cookies on the NHS website</h2>
Fix any of the following:
- Some page content is not contained by landmarks
<p>We use some cookies to make this website work.</p>
Fix any of the following:
- Some page content is not contained by landmarks
<p> Help improve online NHS services by also accepting analytics cookies. </p>
Fix any of the following:
- Some page content is not contained by landmarks
<p> Your choice will be remembered for other online NHS services, such as the NHS App. </p>
Fix any of the following:
- Some page content is not contained by landmarks
<li> <a id="nhsuk-cookie-banner__link" href="/our-policies/choose-your-cookie-settings/">Choose your cookie settings</a> </li>
Fix any of the following:
- Some page content is not contained by landmarks
<a class="nhsuk-skip-link" data-module="nhsuk-skip-link" href="#maincontent" data-nhsuk-skip-link-init="">Skip to main content</a>
Fix any of the following:
- Some page content is not contained by landmarks
Passed Audits
<html> element must have a lang attribute1 element
Screen readers need language information to switch between pronunciation libraries. Without a specified language, screen readers default to the user's preferred language, resulting in incorrect pronunciation that sounds like a strange accent and makes content difficult or impossible to understand.
Audit Elements
<html lang="en">
<html> element must have a valid value for the lang attribute1 element
Screen readers use language-specific sound libraries for proper pronunciation. Invalid language attributes cause screen readers to use the wrong library, making text sound like a confusing accent or completely unintelligible, especially for multilingual users who access content in multiple languages.
Audit Elements
<html lang="en">
<li> elements must be contained in a <ul> or <ol>45 elements
Lists require proper semantic hierarchy with ul or ol parent elements and li child elements. This structure allows screen readers to announce when users enter a list, how many items it contains, and which item they're currently on, providing essential context for understanding the content.
Audit Elements
<li> <button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#"> Accept analytics cookies </button> </li>
<li> <button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#"> Reject analytics cookies </button> </li>
<li> <a id="nhsuk-cookie-banner__link" href="/our-policies/choose-your-cookie-settings/">Choose your cookie settings</a> </li>
<li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li>
<li class="nhsuk-header__navigation-item">
<a class="nhsuk-header__navigation-link" href="/health-a-to-z/">
Health A to Z
</a>
</li><li class="nhsuk-header__navigation-item">
<a class="nhsuk-header__navigation-link" href="/nhs-services/">
NHS services
</a>
</li><li class="nhsuk-header__navigation-item">
<a class="nhsuk-header__navigation-link" href="/live-well/">
Healthy living
</a>
</li><li class="nhsuk-header__navigation-item">
<a class="nhsuk-header__navigation-link" href="/mental-health/">
Mental health
</a>
</li><li class="nhsuk-header__navigation-item">
<a class="nhsuk-header__navigation-link" href="/social-care-and-support/">
Care and support
</a>
</li><li>
Showing first 10 of 45 audited elements.
<svg> elements with an img role must have alternative text1 element
SVG images need text alternatives so their information can be accessed through any sensory modality - visual, auditory, or tactile. Text alternatives enable screen readers to convert visual information into speech or braille, support future translation into sign language, and ensure content is accessible regardless of a user's sensory abilities.
Audit Elements
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<ul> and <ol> must only directly contain <li>, <script> or <template> elements11 elements
Lists must contain only li elements as direct children (besides non-content elements like script or style). When other content elements appear within ul or ol tags, screen readers cannot properly inform users they're listening to list items, breaking the expected list navigation experience.
Audit Elements
<ul>
<ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul>
<ul class="nhsuk-header__navigation-list">
<ul class="nhsuk-list beta-link-list">
<ul class="app-list-signage nhsuk-list-links--one-column">
<ul class="nhsuk-grid-row nhsuk-card-group">
<ul class="nhsuk-grid-row nhsuk-card-group">
<ul class="nhsuk-footer__list">
<ul class="nhsuk-footer__list">
<ul class="nhsuk-footer__list">
Showing first 10 of 11 audited elements.
All page content should be contained by landmarks244 elements
Content should be organized within high-level landmark regions like <header>, <navigation>, <main>, and <footer>. Content outside these sections is difficult to find and its purpose may be unclear, making navigation inefficient for screen reader users who rely on landmarks to understand page structure.
Audit Elements
<div>
<div id="nhsuk-cookie-banner" data-nosnippet="">
<div class="nhsuk-cookie-banner" id="cookiebanner">
<div class="nhsuk-width-container">
<ul>
<li> <button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#"> Accept analytics cookies </button> </li>
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#"> Accept analytics cookies </button>
<li> <button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#"> Reject analytics cookies </button> </li>
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#"> Reject analytics cookies </button>
<a id="nhsuk-cookie-banner__link" href="/our-policies/choose-your-cookie-settings/">Choose your cookie settings</a>
Showing first 10 of 244 audited elements.
ARIA attributes must be used as specified for the element's role7 elements
Using ARIA attributes where they're not expected causes unpredictable behavior in assistive technologies. Following the ARIA specification ensures that screen readers and other tools can properly interpret and communicate your content's meaning to people with disabilities.
Audit Elements
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<nav class="nhsuk-header__account" aria-label="Account"> <ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul> </nav>
<nav class="nhsuk-header__navigation" id="header-navigation" aria-label="Primary navigation">
ARIA attributes must conform to valid names7 elements
Misspelled or non-existent ARIA attributes cannot perform their intended accessibility function. Assistive technologies rely on correctly spelled, current ARIA attributes to convey proper user interface behaviors and structural information to people with disabilities.
Audit Elements
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<nav class="nhsuk-header__account" aria-label="Account"> <ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul> </nav>
<nav class="nhsuk-header__navigation" id="header-navigation" aria-label="Primary navigation">
ARIA attributes must conform to valid values7 elements
ARIA attributes must contain correctly spelled values that match the attribute's expected options. Invalid values prevent the accessibility feature from working, making content inaccessible to assistive technology users who depend on these attributes for navigation and interaction.
Audit Elements
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<nav class="nhsuk-header__account" aria-label="Account"> <ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul> </nav>
<nav class="nhsuk-header__navigation" id="header-navigation" aria-label="Primary navigation">
ARIA hidden element must not be focusable or contain focusable elements14 elements
Elements with aria-hidden="true" are removed from the accessibility API but remain keyboard-focusable, creating confusion about their visibility state. When users tab to these hidden elements, screen readers stay silent, leaving users unaware of what they've focused on or why nothing is being announced.
Audit Elements
<svg class="nhsuk-icon nhsuk-icon--search" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true" focusable="false">
<span class="nhsuk-hero__arrow" aria-hidden="true"></span>
<svg class="nhsuk-icon nhsuk-icon--chevron-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon--chevron-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon--arrow-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon--arrow-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon--arrow-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon--arrow-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon--arrow-right-circle" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" width="16" height="16" focusable="false" aria-hidden="true">
<svg class="nhsuk-icon nhsuk-icon__chevron-right" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" aria-hidden="true" focusable="false">
<path d="M15.5 12a1 1 0 0 1-.29.71l-5 5a1 1 0 0 1-1.42-1.42l4.3-4.29-4.3-4.29a1 1 0 0 1 1.42-1.42l5 5a1 1 0 0 1 .29.71z"></path>
</svg>Showing first 10 of 14 audited elements.
ARIA role should be appropriate for the element9 elements
Invalid ARIA role and HTML element combinations can break accessibility for entire sections of your application. When roles are used incorrectly, assistive technologies may report confusing or nonsensical information to users, making it impossible for them to understand and interact with the interface properly.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<form class="nhsuk-header__search-form" id="search" action="/search/" method="get" role="search">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<ul class="autocomplete__menu autocomplete__menu--inline autocomplete__menu--hidden" id="search-field__listbox" role="listbox"></ul>
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
<footer class="nhsuk-footer" role="contentinfo">
ARIA roles used must conform to valid values8 elements
Invalid ARIA role values prevent assistive technologies from understanding and communicating the element's purpose to users. Without valid roles, screen readers cannot provide information about the element's features, properties, or how users should interact with it.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<form class="nhsuk-header__search-form" id="search" action="/search/" method="get" role="search">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
<footer class="nhsuk-footer" role="contentinfo">
aria-hidden="true" must not be present on the document body1 element
Setting <body aria-hidden="true" hides all page content from assistive technologies while leaving it visible on screen. This creates a confusing experience where keyboard users can still tab to elements, but screen readers remain completely silent, providing no information about what's focused.
Audit Elements
<body class=" js-enabled nhsuk-frontend-supported">
autocomplete attribute must be used correctly1 element
Missing or incorrect autocomplete values make forms inaccessible to screen reader users. Screen readers cannot provide adequate information about form fields without proper autocomplete attributes, preventing users from understanding what information is required and how to complete forms correctly.
Audit Elements
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
Banner landmark should not be contained in another landmark1 element
Banner landmarks must be top-level to effectively designate the header portion of the page. Nested banner landmarks fail to provide the structural information screen reader users need to navigate efficiently through the page layout.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
Buttons must have discernible text3 elements
Screen reader users cannot determine the purpose of buttons without an accessible name. Without a name, users don't know what action the button will perform when activated.
Audit Elements
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#"> Accept analytics cookies </button>
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#"> Reject analytics cookies </button>
<button class="nhsuk-button nhsuk-button--small" type="submit">
Contentinfo landmark should not be contained in another landmark1 element
The contentinfo landmark must be at the top level to help screen reader users quickly navigate to footer information. When nested inside another landmark, it becomes harder to find, defeating its purpose of providing quick access to content information.
Audit Elements
<footer class="nhsuk-footer" role="contentinfo">
Deprecated ARIA roles must not be used8 elements
Deprecated ARIA roles are not recognized by modern screen readers and assistive technologies. Using outdated roles means some users cannot access essential information or functionality on your site.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<form class="nhsuk-header__search-form" id="search" action="/search/" method="get" role="search">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
<footer class="nhsuk-footer" role="contentinfo">
Document should have one main landmark1 element
Every page should have exactly one main landmark that identifies the primary content. Without a main landmark, screen reader users must navigate through all content linearly to find what they're looking for, making page navigation difficult and time-consuming.
Audit Elements
<html lang="en">
Document should not have more than one banner landmark1 element
Multiple banner landmarks force screen reader users to sort through duplicate options to find header information. Each page should have only one banner landmark to enable quick, predictable navigation to the header without overwhelming users with unnecessary choices.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
Document should not have more than one contentinfo landmark1 element
Multiple contentinfo landmarks force screen reader users to sort through extra options to find footer information. Each page should have only one content info landmark to enable quick, predictable navigation without overwhelming users with duplicate structural markers.
Audit Elements
<footer class="nhsuk-footer" role="contentinfo">
Document should not have more than one main landmark1 element
Multiple main landmarks confuse screen reader users about where the primary content is located. Each page should have only one main landmark so users can quickly and predictably navigate to the primary content area.
Audit Elements
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
Documents must have <title> element to aid in navigation1 element
The page title is the first thing screen reader users hear when loading a page. Without a descriptive, unique title, users must read through the entire page to understand its contents and purpose, wasting valuable time on every page visit.
Audit Elements
<html lang="en">
Elements must meet minimum color contrast ratio thresholds73 elements
People with low vision or color blindness cannot read text that lacks sufficient contrast with its background. With nearly three times more people having low vision than total blindness, and 8% of men and 0.4% of women having color deficiencies, adequate contrast is essential for making text readable to millions of users.
Audit Elements
<h2>Cookies on the NHS website</h2>
<p>We use some cookies to make this website work.</p>
<p> Help improve online NHS services by also accepting analytics cookies. </p>
<p> Your choice will be remembered for other online NHS services, such as the NHS App. </p>
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#"> Accept analytics cookies </button>
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#"> Reject analytics cookies </button>
<a id="nhsuk-cookie-banner__link" href="/our-policies/choose-your-cookie-settings/">Choose your cookie settings</a>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a>
<a class="nhsuk-header__navigation-link" href="/health-a-to-z/">
Health A to Z
</a>Showing first 10 of 73 audited elements.
Elements must only use permitted ARIA attributes7 elements
Using prohibited ARIA attributes prevents important information from reaching assistive technology users. It also causes assistive technologies to behave inconsistently as they attempt to compensate for the error.
Audit Elements
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<nav class="nhsuk-header__account" aria-label="Account"> <ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul> </nav>
<nav class="nhsuk-header__navigation" id="header-navigation" aria-label="Primary navigation">
Elements must only use supported ARIA attributes7 elements
Using ARIA attributes in roles where they're not allowed can disable accessibility for entire sections of your application. Invalid attribute-role combinations create conflicts that cause assistive technologies to report incorrect or nonsensical information about your interface.
Audit Elements
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<nav class="nhsuk-header__account" aria-label="Account"> <ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul> </nav>
<nav class="nhsuk-header__navigation" id="header-navigation" aria-label="Primary navigation">
Form elements must have labels1 element
Form labels are essential for screen reader users to understand what information each field requires. Without proper labels, screen readers cannot identify input expectations, fields don't receive focus when announced, and users with motor impairments lose the benefit of larger clickable areas that labels provide.
Audit Elements
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
Form elements should have a visible label1 element
The title and aria-describedby attributes provide supplementary hints, not labels. Screen readers treat these as advisory information rather than true labels, which prevents them from properly conveying the form element's purpose. Form fields need proper labels that can be programmatically determined.
Audit Elements
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
Form field must not have multiple label elements1 element
Multiple labels on the same form field cause inconsistent behavior across screen reader and browser combinations. Some will read the first label, others the last, and some will read both, creating confusion about what information the field requires.
Audit Elements
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
Heading levels should only increase by one18 elements
Headings convey page structure for screen reader users the same way text size does for sighted users. Properly ordered headings (h1 through h6) allow screen reader users to quickly navigate and understand content structure, saving significant time and frustration while also improving search engine optimization.
Audit Elements
<h2>Cookies on the NHS website</h2>
<h1 class="nhsuk-u-margin-bottom-3">
<span class="app-main-heading">NHS website for England</span>
<span class="app-sub-heading">Find information and services to help you manage your health</span>
</h1><h2 class="nhsuk-card__heading nhsuk-heading-m">
<a class="nhsuk-card__link" href="/health-a-to-z/">Health A to Z</a>
</h2><h2 class="nhsuk-card__heading nhsuk-heading-m"><a class="nhsuk-card__link" href="/nhs-services/">NHS services</a></h2>
<h2>Manage your health</h2>
<h2>NHS services</h2>
<h3 class="
nhsuk-card__heading
nhsuk-heading-m
">
Help from NHS 111
</h3><h2>Featured</h2>
<h3 class="
nhsuk-card__heading
nhsuk-heading-m
">
<a class="nhsuk-card__link" href="/nhs-services/vaccination-and-booking-services/book-covid-19-vaccination/">
Book a COVID-19 vaccination appointment
</a>
</h3><h3 class="
nhsuk-card__heading
nhsuk-heading-m
">Showing first 10 of 18 audited elements.
Headings should not be empty18 elements
Screen readers announce headings to help users navigate page structure. Empty headings confuse users and prevent them from understanding the page's organization. Headings should only be used to convey structure, not for visual styling, and must contain accessible text that screen readers can announce.
Audit Elements
<h2>Cookies on the NHS website</h2>
<h1 class="nhsuk-u-margin-bottom-3">
<span class="app-main-heading">NHS website for England</span>
<span class="app-sub-heading">Find information and services to help you manage your health</span>
</h1><h2 class="nhsuk-card__heading nhsuk-heading-m">
<a class="nhsuk-card__link" href="/health-a-to-z/">Health A to Z</a>
</h2><h2 class="nhsuk-card__heading nhsuk-heading-m"><a class="nhsuk-card__link" href="/nhs-services/">NHS services</a></h2>
<h2>Manage your health</h2>
<h2>NHS services</h2>
<h3 class="
nhsuk-card__heading
nhsuk-heading-m
">
Help from NHS 111
</h3><h2>Featured</h2>
<h3 class="
nhsuk-card__heading
nhsuk-heading-m
">
<a class="nhsuk-card__link" href="/nhs-services/vaccination-and-booking-services/book-covid-19-vaccination/">
Book a COVID-19 vaccination appointment
</a>
</h3><h3 class="
nhsuk-card__heading
nhsuk-heading-m
">Showing first 10 of 18 audited elements.
IDs used in ARIA and labels must be unique3 elements
Duplicate IDs break the accessibility of ARIA elements, form labels, and table headers. When IDs are duplicated, assistive technologies and scripts only reference the first instance, causing subsequent elements with the same ID to be ignored or incorrectly associated.
Audit Elements
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<ul class="autocomplete__menu autocomplete__menu--inline autocomplete__menu--hidden" id="search-field__listbox" role="listbox"></ul>
<span id="search-field__assistiveHint" style="display: none;">When autocomplete results are available use up and down arrows to review and enter to select. Touch device users, explore by touch or with swipe gestures.</span>
Inline text spacing must be adjustable with custom stylesheets1 element
Single-spaced text makes it difficult for people with cognitive disabilities to track lines while reading. Providing line spacing between 1.5 to 2 helps these users start a new line more easily after finishing the previous one.
Audit Elements
<section class="nhsuk-hero nhsuk-hero--image nhsuk-hero--image-description beta-hero-variant" style="background-image: url("https://assets.nhs.uk/nhsuk-cms/images/test5_4nG3bKJ.width-1000.png");">Interactive controls must not be nested4 elements
Nested interactive elements create empty tab stops where screen readers remain silent. When users tab to a focusable element inside another interactive control, they receive no information about its name, role, or state, creating a confusing and broken navigation experience.
Audit Elements
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#"> Accept analytics cookies </button>
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#"> Reject analytics cookies </button>
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<button class="nhsuk-button nhsuk-button--small" type="submit">
Interactive elements must have a visible focus indicator54 elements
Sighted keyboard users rely on a visible focus indicator to know where they are on the page. When focus styles are missing, too subtle, or have insufficient contrast against the surrounding colors, users cannot tell which element will respond when they press Enter or Space, making keyboard navigation slow and error-prone. This especially affects people with motor impairments who cannot use a mouse and people with low vision who need clear, high-contrast indicators.
Audit Elements
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept_analytics" href="#">
<button class="nhsuk-button" id="nhsuk-cookie-banner__link_accept" href="#">
<a id="nhsuk-cookie-banner__link" href="/our-policies/choose-your-cookie-settings/">
<a class="nhsuk-skip-link" data-module="nhsuk-skip-link" href="#maincontent" data-nhsuk-skip-link-init="">
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--focused a..." id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<button class="nhsuk-button nhsuk-button--small" type="submit">
<a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">
<a class="nhsuk-header__navigation-link" href="/health-a-to-z/">
<a class="nhsuk-header__navigation-link" href="/nhs-services/">
Showing first 10 of 54 audited elements.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination5 elements
Each landmark on a page must have either a unique role or a unique accessible name. Duplicate landmarks confuse screen reader users about which section they're navigating to, making it difficult to efficiently move through the page structure.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
<nav class="nhsuk-header__account" aria-label="Account"> <ul class="nhsuk-header__account-list"> <li class="nhsuk-header__account-item"> <a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a> </li> </ul> </nav>
<nav class="nhsuk-header__navigation" id="header-navigation" aria-label="Primary navigation">
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
<footer class="nhsuk-footer" role="contentinfo">
Links must have discernible text50 elements
Keyboard users and screen reader users can only interact with links that have accessible names and can receive focus. Without proper names, users don't know where links lead. Without keyboard focus, users who cannot use a mouse cannot activate the links at all.
Audit Elements
<a id="nhsuk-cookie-banner__link" href="/our-policies/choose-your-cookie-settings/">Choose your cookie settings</a>
<a class="nhsuk-skip-link" data-module="nhsuk-skip-link" href="#maincontent" data-nhsuk-skip-link-init="">Skip to main content</a>
<a class="nhsuk-header__service-logo" href="/" aria-label="NHS homepage">
<a class="nhsuk-header__account-link" href="https://www.nhs.uk/nhs-app/account/">My account</a>
<a class="nhsuk-header__navigation-link" href="/health-a-to-z/">
Health A to Z
</a><a class="nhsuk-header__navigation-link" href="/nhs-services/">
NHS services
</a><a class="nhsuk-header__navigation-link" href="/live-well/">
Healthy living
</a><a class="nhsuk-header__navigation-link" href="/mental-health/">
Mental health
</a><a class="nhsuk-header__navigation-link" href="/social-care-and-support/">
Care and support
</a><a class="nhsuk-card__link" href="/health-a-to-z/">Health A to Z</a>
Showing first 10 of 50 audited elements.
Main landmark should not be contained in another landmark1 element
The main landmark must be at the top level and not nested inside other landmarks. This ensures screen reader users can quickly navigate to the primary content without searching through complex hierarchy, making page navigation simpler and more predictable.
Audit Elements
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
Page must have means to bypass repeated blocks1 element
Keyboard-only users must tab through all navigation and header content before reaching the main content, which can take several minutes and cause physical pain for users with motor limitations. Bypass mechanisms like skip links allow these users to jump directly to main content, saving time and reducing fatigue.
Audit Elements
<html lang="en">
Page should contain a level-one heading1 element
Screen reader users use keyboard shortcuts to jump directly to the first h1, expecting to land at the main content. Without an h1 or with a misplaced one, users must listen to more of the page to understand its structure, wasting valuable time on every page visit.
Audit Elements
<html lang="en">
Required ARIA attributes must be provided8 elements
ARIA widget roles need required attributes to describe their current state. Without these attributes, screen readers cannot communicate essential information like whether a checkbox is checked or a slider's current value, leaving users unable to interact effectively with the widget.
Audit Elements
<header class="nhsuk-header" role="banner" data-module="nhsuk-header" data-nhsuk-header-init="">
<svg class="nhsuk-header__logo" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 200 80" height="40" width="100" focusable="false" role="img" aria-label="NHS">
<form class="nhsuk-header__search-form" id="search" action="/search/" method="get" role="search">
<div id="search-field__status--A" role="status" aria-atomic="true" aria-live="polite"></div>
<div id="search-field__status--B" role="status" aria-atomic="true" aria-live="polite"></div>
<input aria-expanded="false" aria-owns="search-field__listbox" aria-autocomplete="list" aria-describedby="search-field__assistiveHint" autocomplete="off" class="autocomplete__input autocomplete__input--default" id="search-field" name="q" placeholder="Search" type="text" role="combobox">
<main class="nhsuk-main-wrapper app-main-wrapper--no-padding app-homepage" id="maincontent" role="main">
<footer class="nhsuk-footer" role="contentinfo">
Users should be able to zoom and scale the text up to 500%1 element
The user-scalable="no" and restrictive maximum-scale parameters prevent people with low vision from zooming to read content. Users who rely on browser zoom to enlarge text are blocked from accessing content at a readable size, violating their need to scale pages up to 5x zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">
Zooming and scaling must not be disabled1 element
Setting user-scalable="no" or maximum-scale less than 2 prevents people with low vision from zooming to read content. Users who enlarge text in their browsers are blocked from making content readable, violating accessibility guidelines that require supporting at least 200% zoom.
Audit Elements
<meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no">