Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 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

No dark mode signals

FIX

No dark mode signals

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 ModeNo Dark Mode Detected

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 ✗

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 Page not found - 404 error ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Color Contrast (Screenshot)

Action

20 text elements analyzed, 17 fail WCAG AA

REVIEW

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

3 pass 17 fail WCAG AA

h1 Health and Safety Executive

1.66:1

#000000

#333333

needs 3.0:1 (large text)

32px · bottom of viewport

h1 What to do if you find or disturb asbest…

1.66:1

#000000

#333333

needs 3.0:1 (large text)

32px · bottom of viewport

h2 Popular

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Industries A to Z

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Topics A to Z

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Featured

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Information and services

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 About HSE

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Link URLs in this page

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Footer links

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Support links

1.66:1

#000000

#333333

needs 3.0:1 (large text)

24px · bottom of viewport

h3 About

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Products

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Industries

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Topics

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 About

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Products

1.66:1

#000000

#333333

needs 3.0:1 (large text)

19px · bottom of viewport

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Health and Safety Ex…	1.66:1	3.0:1	#000000	#333333	Fail
h1 What to do if you fi…	1.66:1	3.0:1	#000000	#333333	Fail
h2 Popular	1.66:1	3.0:1	#000000	#333333	Fail
h2 Industries A to Z	1.66:1	3.0:1	#000000	#333333	Fail
h2 Topics A to Z	1.66:1	3.0:1	#000000	#333333	Fail
h2 Featured	1.66:1	3.0:1	#000000	#333333	Fail
h2 Information and serv…	1.66:1	3.0:1	#000000	#333333	Fail
h2 About HSE	1.66:1	3.0:1	#000000	#333333	Fail
h2 Link URLs in this pa…	1.66:1	3.0:1	#000000	#333333	Fail
h2 Footer links	1.66:1	3.0:1	#000000	#333333	Fail
h2 Support links	1.66:1	3.0:1	#000000	#333333	Fail
h3 Search HSE.GOV.UK	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Industries	18.43:1	3.0:1	#000000	#F0F0F0	Pass
h3 Topics	6.37:1	3.0:1	#000000	#8D8E8A	Pass
h3 About	1.66:1	3.0:1	#000000	#333333	Fail
h3 Products	1.66:1	3.0:1	#000000	#333333	Fail
h3 Industries	1.66:1	3.0:1	#000000	#333333	Fail
h3 Topics	1.66:1	3.0:1	#000000	#333333	Fail
h3 About	1.66:1	3.0:1	#000000	#333333	Fail
h3 Products	1.66:1	3.0:1	#000000	#333333	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

11 landmarks

PASS

11 landmarks

<main> landmark present

3 <nav> landmark(s) found

2 of 3 <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

33 headings

PASS

33 headings

Multiple H1 headings (2 found)

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

H3 Search HSE.GOV.UK
H3 Industries
H3 Topics
H3 About
H3 Products
H1 Health and Safety Executive
H1 What to do if you find or disturb asbestos duplicate H1
H2 Popular
H2 Industries A to Z
H2 Topics A to Z
H2 Featured
H2 Flower supplier fined after worker suffers life-changing injuries[10]
H2 HSE launches consultation on workplace injury and illness reporting[12]
H2 Construction firm and director sentenced after worker fell through stairwell[14]
H2 Information and services
H3 RIDDOR[17]
H3 Training and events[18]
H3 Apply, notify or report[19]
H3 Public consultations[20]
H3 COSHH[21]
H3 The law[22]
H2 About HSE
H3 Sarah Albon[23]
H3 Sarah Newton[24]
H3 Our mission[25]
H3 Careers[26]
H2 Link URLs in this page
H2 Footer links
H3 Industries
H3 Topics
H3 About
H3 Products
H2 Support links

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 5 images OK

PASS

All 5 images OK

1 decorative image(s) correctly marked

4 image(s) with good alt text

5 images 4 good alt text 1 decorative

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#gsc-i-id1	text	search	aria-label

A+

Link & Button Quality

105 links, 8 buttons — all OK

PASS

105 links, 8 buttons — all OK

105 link(s) with descriptive text

105 links

0 empty

0 generic text

0 new tab

0 empty buttons

All links and buttons have descriptive accessible text.

113 links and buttons have descriptive text

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 passed

PASS

100

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.

○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

●`[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

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

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

●Links are distinguishable without relying on color.

●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

●Touch targets have sufficient size and spacing.

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

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

○Elements with `role="dialog"` or `role="alertdialog"` 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

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

○`<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

○Form elements have associated labels

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

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

○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.

○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.