Skip to content
https://huffingtonpost.co.uk

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
61
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
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'>.
favicon.ico Missing
PNG Icons Present
Apple Touch Missing
SVG Favicon Missing
Manifest Icons Missing
Multiple Sizes Missing
D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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
F
Navigation UX
Action
1 navigation pattern(s)
FIX
1 navigation pattern(s)
Info::
Skip navigation link detected
Info::
3 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 3 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality Custom 404 Page
Status Code HTTP 404 Page Title Not Found | HuffPost Custom Styling Navigation Homepage Link Search Form
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 12 fail WCAG AA
REVIEW

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

8 pass 12 fail WCAG AA
h2 FEATURED
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 LIFE
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 TOP VIDEOS
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 ENTERTAINMENT
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PARENTS
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 POLITICS
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 SHOPPING
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 POLITICS
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
h2 DON'T MISS
1.54:1
#000000
on
#2D2E2B
needs 3.0:1 (large text)
24px · bottom of viewport
title HuffPost UK: UK News and Opinion
2.14:1
#000000
on
#164B49
needs 4.5:1 (normal text)
16px · top of page (header area)
a Ukraine
3.75:1
#000000
on
#456F6D
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
a News
2.14:1
#000000
on
#164B49
needs 4.5:1 (normal text)
16px · above the fold

1 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)
ElementRatioRequiredFGBGResult
h2 FEATURED1.54:13.0:1
#000000
#2D2E2B
Fail
h2 LIFE1.54:13.0:1
#000000
#2D2E2B
Fail
h2 TOP VIDEOS1.54:13.0:1
#000000
#2D2E2B
Fail
h2 ENTERTAINMENT1.54:13.0:1
#000000
#2D2E2B
Fail
h2 PARENTS1.54:13.0:1
#000000
#2D2E2B
Fail
h2 POLITICS1.54:13.0:1
#000000
#2D2E2B
Fail
h2 SHOPPING1.54:13.0:1
#000000
#2D2E2B
Fail
h2 POLITICS1.54:13.0:1
#000000
#2D2E2B
Fail
h2 DON'T MISS1.54:13.0:1
#000000
#2D2E2B
Fail
title HuffPost UK: UK News…2.14:14.5:1
#000000
#164B49
Fail
a Skip to Main Content13.22:14.5:1
#000000
#79DBF1
Pass
div Main Menu13.23:14.5:1
#000000
#7ADBF1
Pass
button U.K. edition13.32:14.5:1
#000000
#79DCF1
Pass
a Daily Horoscopes13.32:14.5:1
#000000
#79DCF1
Pass
a Politics13.22:14.5:1
#000000
#79DBF1
Pass
a Labour13.32:14.5:1
#000000
#79DCF1
Pass
a Conservatives16.62:14.5:1
#000000
#F9E832
Pass
a Keir Starmer13.32:14.5:1
#000000
#79DCF1
Pass
a Ukraine3.75:14.5:1
#000000
#456F6D
Fail
a News2.14:14.5:1
#000000
#164B49
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.

B
Lighthouse Accessibility Audits
Score 83/100 — 4 failing, 22 passed
REVIEW
83

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

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
body.uk > div.body-wrap > div.advertisement > div.ad-leaderboard-flex__dismiss body.uk > div.body-wrap > div.advertisement > div.ad-leaderboard-flex__dismiss

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.nav__content > div.nav__left > div.notification-center > button.notification-center__button div.nav__content > div.nav__left > div.notification-center > button.notification-center__button
div.body-wrap > div.dd-widget-wrapper > div.dd-widget-input-wrapper > button.dd-widget-input-send-button div.body-wrap > div.dd-widget-wrapper > div.dd-widget-input-wrapper > button.dd-widget-input-send-button

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.dd-widget-wrapper > div.dd-widget-input-wrapper > div.dd-widget-input-field > input.dd-widget-input-field-textarea div.dd-widget-wrapper > div.dd-widget-input-wrapper > div.dd-widget-input-field > input.dd-widget-input-field-textarea

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > a.site-footer__link
div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > button#sp-privacy-btn div.site-footer__wrapper > div.site-footer__content > div.site-footer__links > button#sp-privacy-btn

These are opportunities to improve the legibility of your content.

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
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
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 are distinguishable without relying on color.
Links have a discernible name
No element has a `[tabindex]` value greater than 0
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
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
`<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
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.
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.
A
Landmark Structure
7 landmarks
PASS
7 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
3 of 3 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Page Structure — as a screen reader sees it
BANNER header NAV MAIN ASIDE CONTENTINFO footer

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

A+
Heading Hierarchy
10 headings
PASS
10 headings
Info::
Single H1 present
  • H1 HUFFPOST
  • H2 FEATURED
  • H2 LIFE
  • H2 TOP VIDEOS
  • H2 ENTERTAINMENT
  • H2 PARENTS
  • H2 POLITICS
  • H2 SHOPPING
  • H2 POLITICS
  • H2 DON'T MISS
A+
Alt Text Quality
All 58 images OK
PASS
All 58 images OK
Info::
57 decorative image(s) correctly marked
Info::
1 image(s) with good alt text
58 images 1 good alt text 57 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 1 controls have issues
PASS
1 of 1 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input>
1 controls
0 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
inputinput(none)none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

<input>

Why this matters

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

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

Send Feedback