Skip to content
https://bt.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
64
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
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
Theme color only
FIX
Theme color only
Info::
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: #553a99
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 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.

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.
C
404 Error Page
Action
Could not test
REVIEW
Could not test
Info::
404 page could not be tested
The 404 page check encountered an error. This may be due to a timeout or network issue.

404 page quality check not available.

C
Favicon & Branding
Action
17 icon(s) detected
REVIEW
17 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::
Apple touch icon present
Info::
SVG favicon detected — scales perfectly to any size
Info::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✓ SVG Favicon Present
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 10 pass AA only
title Broadband, TV Packages, TNT Sports & Mob…
1.29:1
#000000
on
#2A0A5A
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip Navigation
1.29:1
#000000
on
#2A0A5A
needs 4.5:1 (normal text)
16px · top of page (header area)
span Upgrade broadband
1.76:1
#000000
on
#373737
needs 4.5:1 (normal text)
16px · above the fold · over background image/gradient
span Broadband accessories
1.08:1
#000000
on
#0F0D0E
needs 4.5:1 (normal text)
16px · mid-page

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 Exclusive deals just…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Add Entertainment fo…5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Copyrights5.24:13.0:1
#000000
#7F7F7F
Pass
h2 Privacy preference c…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Manage consent prefe…5.24:13.0:1
#000000
#7F7F7F
Pass
h3 Cookie List5.24:13.0:1
#000000
#7F7F7F
Pass
title Broadband, TV Packag…1.29:14.5:1
#000000
#2A0A5A
Fail
a Skip Navigation1.29:14.5:1
#000000
#2A0A5A
Fail
a For the home5.24:14.5:1
#000000
#7F7F7F
Pass
a For business and pub…5.24:14.5:1
#000000
#7F7F7F
Pass
a For global business5.24:14.5:1
#000000
#7F7F7F
Pass
span Broadband5.17:14.5:1
#000000
#7E7E7E
Pass
span Broadband4.96:14.5:1
#000000
#7B7B7B
Pass
li For new customers4.96:14.5:1
#000000
#7B7B7B
Pass
span BT Broadband deals4.96:14.5:1
#000000
#7B7B7B
Pass
span Discover broadband4.96:14.5:1
#000000
#7B7B7B
Pass
span Student deals4.96:14.5:1
#000000
#7B7B7B
Pass
li For existing custome…4.96:14.5:1
#000000
#7B7B7B
Pass
span Upgrade broadband1.76:14.5:1
#000000
#373737
Fail
span Broadband accessorie…1.08:14.5:1
#000000
#0F0D0E
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.

A
Landmark Structure
8 landmarks
PASS
8 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
2 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 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
20 headings
PASS
20 headings
Info::
Single H1 present
  • H1 Upgrade your home with BT Broadband
  • H2 Exclusive deals just for you
  • H2 Add Entertainment for £5 for 6 months
  • H2 BT + EE, the ultimate home entertainment
  • H2 EE TV has something for everyone
  • H2 The best sport in HD
  • H2 Build your perfect BT package
  • H2 Get best of both BT and EE
  • H2 SMART TECH. BIG BRANDS
  • H2 Copyrights
  • H2 Privacy preference centre
  • H3 Manage consent preferences
  • H4 Strictly Necessary Cookies
  • H4 Analytical Cookies
  • H4 Preference Cookies
  • H4 Marketing Cookies
  • H4 Business Analytical Cookies
  • H4 Business Preference Cookies
  • H4 Business Marketing Cookies
  • H3 Cookie List
A+
Alt Text Quality
All 49 images OK
PASS
All 49 images OK
Info::
43 decorative image(s) correctly marked
Info::
6 image(s) with good alt text
49 images 6 good alt text 43 decorative
All images have appropriate alt text.
A
Form Accessibility
1 of 12 controls have issues
PASS
1 of 12 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
11 control(s) properly labeled
12 controls
11 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#ot-group-id-1checkboxAnalytical Cookiesfor/id
#ot-group-id-2checkboxPreference Cookiesfor/id
#ot-group-id-3checkboxMarketing Cookiesfor/id
#ot-group-id-5checkboxBusiness Analytical Cookiesfor/id
#ot-group-id-6checkboxBusiness Preference Cookiesfor/id
#ot-group-id-7checkboxBusiness Marketing Cookiesfor/id
#vendor-search-handlertextCookie list searcharia-label
#chkbox-idcheckboxcheckbox labelfor/id
#select-all-hosts-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-groups-handlercheckboxcheckbox labelfor/id
#select-all-vendor-leg-handlercheckboxcheckbox labelfor/id
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

A+
Lighthouse Accessibility Audits
Score 100/100 — 1 failing, 30 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.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
BT Broadband Reliable. Fast BT’s trusted network with brilliant services​ View … nav.swiper > div#swiper-wrapper-84aaedcef74fcdf5 > div.swiper-slide > a
iPhone offer Latest. iPhone 17 Pro New exclusive offer - BT Broadband customers… nav.swiper > div#swiper-wrapper-84aaedcef74fcdf5 > div.swiper-slide > a
Cookie Policy div#onetrust-group-container > div#onetrust-policy > div#onetrust-policy-text > a.ot-cookie-policy-link
○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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○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.

Send Feedback