https://barometer.thenationalconversation.org.uk

Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

16 PASS 3 REVIEW 5 FIX

Favicon & Branding

Action

No icons detected

FIX

No icons detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

No favicon or icon links detected

Your site will show the browser's generic page icon in tabs, bookmarks, and home screens.

✗ favicon.ico Missing

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

1 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Mobile-Readable Font Sizes

Action

75% of visible text renders at >= 12 CSS px (6 below threshold)

REVIEW

75% of visible text renders at >= 12 CSS px (6 below threshold)

6 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <div> 11.0px ("Postcodes are used only to find your loc..."); <h3> 10.0px ("Famous front doors – tap to look inside"); <span> 10.0px ("Tap to look inside"); <span> 10.0px ("Tap to look inside"); <div> 11.0px ("Famous addresses score as their local au...").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 14 fail WCAG AA

REVIEW

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

6 pass 14 fail WCAG AA 1 pass AA only

h1 How connected is your postcode?

2.22:1

#000000

#464645

needs 3.0:1 (large text)

32px · top of page (header area) · over background image/gradient

h3 Famous front doors – tap to look insid…

1.22:1

#000000

#1B1B19

needs 3.0:1 (large text)

19px · mid-page

title How connected is your postcode? – The …

1.54:1

#000000

#2E2E2D

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span the national

2.44:1

#000000

#4C4C4B

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

span conversation

1.32:1

#000000

#222221

needs 4.5:1 (normal text)

16px · top of page (header area)

div How lonely is your area? Do your neighbo…

2.15:1

#000000

#444443

needs 4.5:1 (normal text)

16px · above the fold

b But they can't say what it's like to liv…

1.23:1

#000000

#1C1C1B

needs 3.0:1 (large text)

16px · above the fold

span That's where you come in.

1.29:1

#000000

#20201E

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Local figures cover England only – the…

1.48:1

#000000

#2B2B2A

needs 4.5:1 (normal text)

16px · above the fold

button Look up

1.74:1

#000000

#363635

needs 4.5:1 (normal text)

16px · above the fold · over background image/gradient

div Postcodes are used only to find your loc…

1.37:1

#000000

#252524

needs 4.5:1 (normal text)

16px · above the fold

div Or pick your area directly:

1.29:1

#000000

#20201F

needs 4.5:1 (normal text)

16px · above the fold

button Show

1.26:1

#000000

#1E1E1C

needs 4.5:1 (normal text)

16px · mid-page

span Buckingham Palace

1.29:1

#000000

#20201F

needs 4.5:1 (normal text)

16px · mid-page

5 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 How connected is you…	2.22:1	3.0:1	#000000	#464645	Fail
h2 Find your area	3.54:1	3.0:1	#000000	#646462	Pass
h2 The data has had its…	19.24:1	3.0:1	#000000	#F5F5F3	Pass
h2 Is it right about yo…	19.24:1	3.0:1	#000000	#F5F5F3	Pass
h2 How does it compare?	19.24:1	3.0:1	#000000	#F5F5F3	Pass
h3 Famous front doors �…	1.22:1	3.0:1	#000000	#1B1B19	Fail
title How connected is you…	1.54:1	4.5:1	#000000	#2E2E2D	Fail
span the national	2.44:1	4.5:1	#000000	#4C4C4B	Fail
span conversation	1.32:1	4.5:1	#000000	#222221	Fail
div How lonely is your a…	2.15:1	4.5:1	#000000	#444443	Fail
b But they can't say w…	1.23:1	3.0:1	#000000	#1C1C1B	Fail
span That's where you com…	1.29:1	4.5:1	#000000	#20201E	Fail
div Local figures cover …	1.48:1	4.5:1	#000000	#2B2B2A	Fail
button Look up	1.74:1	4.5:1	#000000	#363635	Fail
div Postcodes are used o…	1.37:1	4.5:1	#000000	#252524	Fail
div Or pick your area di…	1.29:1	4.5:1	#000000	#20201F	Fail
button Show	1.26:1	4.5:1	#000000	#1E1E1C	Fail
span Buckingham Palace	1.29:1	4.5:1	#000000	#20201F	Fail
span Tap to look inside	19.24:1	4.5:1	#000000	#F5F5F3	Pass
span Coronation Street	19.24:1	4.5:1	#000000	#F5F5F3	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

Skip navigation link is missing (WCAG 2.4.1)

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Page Structure — as a screen reader sees it

Add a skip link as the first focusable element so keyboard users can bypass repeated navigation.

Why this matters

Without a skip-nav link, keyboard users tab through every nav item before reaching content — every page, every visit.

Learn more ▾

WCAG 2.4.1 (Bypass Blocks) requires a mechanism to skip past repeated content. The standard implementation is a 'Skip to main content' link that's the first focusable element, visually hidden until focused. Three lines of HTML + four of CSS.

Source: WCAG 2.1 SC 2.4.1

A+

Heading Hierarchy

6 headings

PASS

6 headings

Single H1 present

H1 How connected is your postcode?
H2 Find your area
H3 Famous front doors – tap to look inside
H2 The data has had its say.
H2 Is it right about your area?
H2 How does it compare?

A+

Heading Text Quality

All 6 heading(s) have substantive, well-formed text

PASS

All 6 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

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
#pc	text	Enter your postcode	aria-label
#areapick	input	Pick your local area	aria-label
#guess	range	Your guess: share of people who say many of their neighbours can be trusted, percent	aria-label
#cmppick	input	Pick an area to compare	aria-label

Link & Button Quality

5 links, 4 buttons — all OK

PASS

5 links, 4 buttons — all OK

4 link(s) open in new tab without warning

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

Got: https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…; https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…; https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…; https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…

1 link(s) with descriptive text

5 links

0 empty

0 generic text

4 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.national-conversation.ox.ac.…	Take the National Conversation…	new tab	Add '(opens in new tab)' to text
https://www.national-conversation.ox.ac.…	Have your say – take the sur…	new tab	Add '(opens in new tab)' to text
https://www.national-conversation.ox.ac.…	Have your say – take the sur…	new tab	Add '(opens in new tab)' to text
https://www.national-conversation.ox.ac.…	Have your say →	new tab	Add '(opens in new tab)' to text

5 links and buttons have descriptive text

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

https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…; https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…; https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…; https://www.national-conversation.ox.ac.uk/?utm_source=connection-barometer&u…

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

A+

Form Input Types

4 form control(s) checked, no type mismatches

PASS

4 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

4 form control(s) checked, no input-semantic issues

PASS

4 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en-GB"

PASS

Lang attribute set to "en-GB"

<html lang="en-GB"> is set and valid

Got: en-GB

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 22 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

●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

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

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

●Links have a discernible name

●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

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

○Links are distinguishable without relying on color.

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

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

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

○Identical links have the same purpose.

○Elements with visible text labels have matching accessible names.

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