Accessibility
· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.FFavicon & BrandingAction1 icon(s) detectedFIX
DWeb ManifestActionNot foundFIX
No web manifest found.
DDark Mode SupportActionTheme color onlyFIX
Detection limited to meta tags and inline styles.
DPrint StylesheetActionNo print stylesFIX
BAlt Text Quality1 of 13 images have issuesREVIEW
| Issue | Count |
|---|---|
| missing | 1 image(s) |
Images without alt text are invisible to screen readers.
Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.
Learn more ▾ ▴
WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.
Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report
An image inside a link with no alt creates an empty link.
Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.
Learn more ▾ ▴
An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.
Source: WCAG 2.1 SC 2.4.4
CLink & Button QualityAction1 issue(s) across 119 links and 7 buttonsREVIEW
| Element | Text | Issue | Suggested Fix |
|---|---|---|---|
| https://blog.ons.gov.uk/ | Blog | new tab | Add '(opens in new tab)' to text |
| /census | (empty) | empty | Add link text or aria-label |
| https://nwp-prototype.ons.gov.uk/ | Explore the ONS preview site | new tab | Add '(opens in new tab)' to text |
| /surveys | Taking part in a survey? … | img no alt | Add alt attribute to the image |
| /surveys | Taking part in a survey? … | img no alt | Add alt attribute to the image |
| https://twitter.com/ONS | X | new tab | Add '(opens in new tab)' to text |
| https://www.instagram.com/officefornatio… | new tab | Add '(opens in new tab)' to text | |
| https://www.facebook.com/ONS | new tab | Add '(opens in new tab)' to text | |
| https://www.linkedin.com/company/office-… | new tab | Add '(opens in new tab)' to text | |
| https://consultations.ons.gov.uk/ | Consultations | new tab | Add '(opens in new tab)' to text |
| https://www.statsusernetwork.ons.gov.uk/ | Discussion forums | new tab | Add '(opens in new tab)' to text |
| https://public.govdelivery.com/accounts/… | Email alerts | new tab | Add '(opens in new tab)' to text |
| http://www.nationalarchives.gov.uk/doc/o… | Open Government Licence v3.0 | new tab | Add '(opens in new tab)' to text |
Links without text are announced as raw URLs by screen readers.
/census
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
Image-only links need alt text on the image (or aria-label on the link) so screen readers can announce them.
a[href="/surveys"]; a[href="/surveys"]
Image-only links with no alt are unidentifiable to screen-reader users — link's destination is invisible.
Source: WCAG 2.1 SC 2.4.4
Add '(opens in new tab)' to link text or aria-label.
https://blog.ons.gov.uk/; https://nwp-prototype.ons.gov.uk/; https://twitter.com/ONS; https://www.instagram.com/officefornationalstatistics/; https://www.facebook.com/ONS; https://www.linkedin.com/company/office-for-national-statistics; https://consultations.ons.gov.uk/; https://www.statsusernetwork.ons.gov.uk/; https://public.govdelivery.com/accounts/UKONS/subscribers/new; http://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/
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
A+Landmark Structure24 landmarksPASS
AHeading Hierarchy34 headingsPASS
- H2 Cookies on ons.gov.uk
- H1 Main figures
- H2 Employment
- H2 Inflation
- H2 GDP
- H2 UK population
- H2 Employment
- H2 Inflation
- H2 GDP
- H2 UK population
- H2 GDP
- H2 Inflation
- H2 UK population
- H2 Employment
- H2 Try our new preview site
- H2 Latest releases
- H2 Taking part in a survey?
- H2 Taking part in a survey?
- H2 Latest releases
- H1 In focus duplicate H1
- H2 A guide to data, statistics and the ONS
- H2 Statistics from across the UK
- H2 Census 2031
- H2 Economic statistics and surveys improvement plan
- H1 Around the ONS duplicate H1
- H2 Explore local statistics
- H2 Other government statistics
- H2 Navigating Numbers - the ONS data education programme
- H2 Secure Research Service
- H2 Is this page useful?
- H2 Footer links
- H2 Help
- H2 About ONS
- H2 Connect with us
A page should have only one H1. Multiple H1s dilute the document outline.
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
AForm Accessibility1 of 5 controls have issuesPASS
| Control | Type | Label | Method |
|---|---|---|---|
| #nav-search | search | Search for a keyword(s) or time series ID | for/id |
| #description-field | textarea | How should we improve this page? | for/id |
| #name-field | text | Name (optional) | for/id |
| #email-field | text | Email (optional) | for/id |
| #feedback-form-submit | submit | (none) | none |
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
<input type="submit" id="feedback-form-submit">
Form controls without labels — assistive tech announces 'edit text' with no context; users can't complete forms.
Source: WCAG 2.1 SC 3.3.2
A404 Error PageHTTP 404, custom pagePASS
A+Color Contrast (Screenshot)20 text elements analyzed, 0 fail WCAG AAPASS
Analyzes text contrast against the actual rendered page, including background images, gradients, and overlays that CSS-based tools cannot detect.
Show all checked elements (20)
| Element | Ratio | Required | FG | BG | Result |
|---|---|---|---|---|---|
| h1 Main figures | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 In focus | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h1 Around the ONS | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Cookies on ons.gov.u… | 16.67:1 | 3.0:1 | #000000 | #E5E5E5 | Pass |
| h2 Try our new preview … | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Taking part in a sur… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Taking part in a sur… | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Is this page useful? | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Footer links | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Help | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 About ONS | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| h2 Connect with us | 21.00:1 | 3.0:1 | #000000 | #FFFFFF | Pass |
| title Home - Office … | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| p Cookies are small fi… | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| p We would like to set | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| a additional cookies | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| p to remember your set… | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| button Accept additional co… | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| button Reject additional co… | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
| a Manage settings | 16.67:1 | 4.5:1 | #000000 | #E5E5E5 | Pass |
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.
A+Lighthouse Accessibility AuditsScore 100/100 — 0 failing, 27 passedPASS
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.