Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Not found

FIX

Not found

No web manifest found

No manifest at standard paths (/manifest.json, /site.webmanifest). A manifest is optional but enables PWA features like home screen installation and standalone display.

No web manifest found.

Dark Mode Support

Action

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #004650

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

Detection limited to meta tags and inline styles

External CSS files may contain prefers-color-scheme rules not visible to this scan.

Dark ModePartial Dark Mode

color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Not detected ✗

Detection limited to meta tags and inline styles.

Print Stylesheet

Action

No print styles

FIX

No print styles

No print-specific styles detected

When users print this page, they get the screen layout including navigation and non-essential elements. Add @media print rules to hide navigation and optimize layout for paper.

Print Stylesheet No Print Styles

Print stylesheet Not found ✗Inline @media print Not detected ✗

Navigation UX

Action

2 navigation pattern(s)

FIX

2 navigation pattern(s)

Skip navigation link detected

Back-to-top link detected

6 navigation landmark(s) detected

Hamburger menu detected (responsive design)

Breadcrumbs

Skip Link Skip link detected

Labeled Navigation 6 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

4 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Link & Button Quality

Action

3 issue(s) across 76 links and 10 buttons

REVIEW

3 issue(s) across 76 links and 10 buttons

3 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: /news/articles/new-life-extending-treatment-given-the-green-light-for-people-…; /news/articles/new-take-at-home-drug-recommended-for-people-with-chronic-lymp…; /news/articles/trojan-horse-treatment-recommended-for-people-with-multiple-my…

1 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.nice.org.uk/cookies

72 link(s) with descriptive text

76 links

3 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.nice.org.uk/cookies	cookie statement.(Opens in a n…	new tab	Add '(opens in new tab)' to text
/news/articles/new-life-extending-treatm…	(empty)	empty	Add link text or aria-label
/news/articles/new-take-at-home-drug-rec…	(empty)	empty	Add link text or aria-label
/news/articles/trojan-horse-treatment-re…	(empty)	empty	Add link text or aria-label

82 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

/news/articles/new-life-extending-treatment-given-the-green-light-for-people-…; /news/articles/new-take-at-home-drug-recommended-for-people-with-chronic-lymp…; /news/articles/trojan-horse-treatment-recommended-for-people-with-multiple-my…

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

Add '(opens in new tab)' to link text or aria-label.

https://www.nice.org.uk/cookies

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title NICE - File not found ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

9 icon(s) detected

REVIEW

9 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 8 fail WCAG AA

REVIEW

Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.

12 pass 8 fail WCAG AA

h2 Essential cookies

1.38:1

#000000

#002840

needs 3.0:1 (large text)

24px · above the fold

h3 Preference cookies

1.38:1

#000000

#002840

needs 3.0:1 (large text)

19px · above the fold

h3 Website usage cookies

1.38:1

#000000

#002840

needs 3.0:1 (large text)

19px · mid-page

p We use cookies to store information abou…

1.38:1

#000000

#002840

needs 4.5:1 (normal text)

16px · top of page (header area)

span For more information, view our

1.38:1

#000000

#002840

needs 4.5:1 (normal text)

16px · above the fold

span cookie statement.

1.38:1

#000000

#002840

needs 4.5:1 (normal text)

16px · above the fold

span (Opens in a new window)

1.38:1

#000000

#002840

needs 4.5:1 (normal text)

16px · above the fold

span Accept all cookies

1.38:1

#000000

#002840

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Cookies on the NICE …	7.09:1	3.0:1	#000000	#969695	Pass
h1 We produce useful an…	7.09:1	3.0:1	#000000	#969695	Pass
h2 Essential cookies	1.38:1	3.0:1	#000000	#002840	Fail
h2 Explore more from NI…	7.09:1	3.0:1	#000000	#969695	Pass
h2 My account	7.09:1	3.0:1	#000000	#969695	Pass
h2 Latest from NICE	7.09:1	3.0:1	#000000	#969695	Pass
h2 Backing the healthte…	7.09:1	3.0:1	#000000	#969695	Pass
h2 Implementation and p…	7.09:1	3.0:1	#000000	#969695	Pass
h2 More ways we support…	7.09:1	3.0:1	#000000	#969695	Pass
h2 How we're helping to…	7.09:1	3.0:1	#000000	#969695	Pass
h3 Preference cookies	1.38:1	3.0:1	#000000	#002840	Fail
h3 Website usage cookie…	1.38:1	3.0:1	#000000	#002840	Fail
h3 Marketing and advert…	7.09:1	3.0:1	#000000	#969695	Pass
title Homepage \| NICE	7.09:1	4.5:1	#000000	#969695	Pass
p Cookies are files sa…	7.09:1	4.5:1	#000000	#969695	Pass
p We use cookies to st…	1.38:1	4.5:1	#000000	#002840	Fail
span For more information…	1.38:1	4.5:1	#000000	#002840	Fail
span cookie statement.	1.38:1	4.5:1	#000000	#002840	Fail
span (Opens in a new wind…	1.38:1	4.5:1	#000000	#002840	Fail
span Accept all cookies	1.38:1	4.5:1	#000000	#002840	Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

Landmark Structure

24 landmarks

PASS

24 landmarks

<main> landmark present

6 <nav> landmark(s) found

1 of 6 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

Page Structure — as a screen reader sees it

Multiple navigations need aria-label to distinguish them for screen readers.

Why this matters

Some <nav> elements lack aria-label — screen-reader users hear 'navigation' multiple times with no way to distinguish them.

Learn more ▾

When a page has multiple <nav> regions (primary, footer, breadcrumb), each needs aria-label or aria-labelledby. AT users navigate by landmark; identical 'navigation' announcements force them to enter each one to discover purpose.

Source: WAI-ARIA Authoring Practices

Heading Hierarchy

20 headings

PASS

20 headings

Multiple H1 headings (2 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Cookies on the NICE website and services
H2 Essential cookies
H3 Preference cookies
H3 Website usage cookies
H3 Marketing and advertising cookies
H2 Explore more from NICE
H2 My account
H1 We produce useful and usable guidance for the NHS and wider health and care system. duplicate H1
H2 Latest from NICE
H3 Endometriosis now has its own fertility pathway in NICE guidance
H3 New life-extending treatment given the green light for people with rare form of bile duct cancer
H3 New take at home drug recommended for people with chronic lymphocytic leukaemia
H3 ‘Trojan horse’ treatment recommended for people with multiple myeloma
H2 Backing the healthtech that changes lives
H2 Implementation and planning
H2 More ways we support you
H2 How we're helping to deliver the NHS 10 Year Plan
H3 MHRA-NICE pathway opens for business – everything you need to know to get started
H3 Driving biosimilar adoption through collaboration
H3 Backing the healthtech that changes lives

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 3 images OK

PASS

All 3 images OK

1 decorative image(s) correctly marked

2 image(s) with good alt text

3 images 2 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 4 controls labeled

PASS

All 4 controls labeled

4 control(s) properly labeled

4 controls

4 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
input	checkbox		none
input	checkbox		none
input	checkbox		none
#autocomplete	text	Search NICE…	for/id

Lighthouse Accessibility Audits

Score 93/100 — 2 failing, 26 passed

PASS

Accessibility

These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.

ARIA

ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
Cookies on the NICE website and services Cookies are files saved on your phone… `body > div#ccc > div#ccc-module`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
nav.Legal_menu__L03tj > ul > li > a `nav.Legal_menu__L03tj > ul > li > a`
nav.Legal_menu__L03tj > ul > li > a `nav.Legal_menu__L03tj > ul > li > a`
nav.Legal_menu__L03tj > ul > li > a `nav.Legal_menu__L03tj > ul > li > a`
nav.Legal_menu__L03tj > ul > li > a `nav.Legal_menu__L03tj > ul > li > a`
nav.Legal_menu__L03tj > ul > li > a `nav.Legal_menu__L03tj > ul > li > a`
nav.Legal_menu__L03tj > ul > li > a `nav.Legal_menu__L03tj > ul > li > a`

These items highlight common accessibility best practices.

○Interactive controls are keyboard focusable

○Interactive elements indicate their purpose and state

○The page has a logical tab order

○Visual order on the page follows DOM order

○User focus is not accidentally trapped in a region

○The user's focus is directed to new content added to the page

○HTML5 landmark elements are used to improve navigation

○Offscreen content is hidden from assistive technology

○Custom controls have associated labels

○Custom controls have ARIA roles

●`[aria-*]` attributes match their roles

●`[aria-hidden="true"]` is not present on the document `<body>`

●`[role]`s have all required `[aria-*]` attributes

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.

●ARIA attributes are used as specified for the element's role

●`[aria-hidden="true"]` elements do not contain focusable descendents

●Elements use only permitted ARIA attributes

●Background and foreground colors have a sufficient contrast ratio

●Document has a `<title>` element

●`<frame>` or `<iframe>` elements have a title

●`<html>` element has a `[lang]` attribute

●`<html>` element has a valid value for its `[lang]` attribute

●Links have a discernible name

●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

○Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.

○`[role]`s are contained by their required parent element

○Elements with the `role=text` attribute do not have focusable descendents.

○ARIA toggle fields have accessible names

○ARIA `tooltip` elements have accessible names

○ARIA `treeitem` elements have accessible names

○The page contains a heading, skip link, or landmark region

○`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.

○Definition list items are wrapped in `<dl>` elements

○ARIA IDs are unique

○No form fields have multiple labels

○`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

○Input buttons have discernible text.

○`<input type="image">` elements have `[alt]` text

○Links are distinguishable without relying on color.

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Identical links have the same purpose.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.