Skip to content
https://Www.uswitch.com/broadband/

Accessibility

· 23 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
5
REVIEW
5
PASS
13
INFO
0
Checks
23
13 PASS 5 REVIEW 5 FIX
D
404 Error Page
Action
HTTP 403, custom page
FIX
HTTP 403, custom page
Warning::
Unexpected status code: HTTP 403
Expected HTTP 404 but received 403. This may confuse search engine crawlers.
Got: HTTP 403
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 403 ✗Page Title Server error ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
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::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Breadcrumbs
Search
Skip Link Skip link detected
Labeled Navigation 1 <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
Landmark Structure
Action
5 landmarks
REVIEW
5 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
Skip navigation link present
Warning::
Skip link target(s) don't exist on page: #us-main-content
The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.
Page Structure — as a screen reader sees it
BANNER header NAV MAIN (missing!) ASIDE CONTENTINFO footer

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

The skip-link anchor (e.g., `href="#main"`) points at an ID that has no corresponding element on the page. Activating the link does nothing -- a silent WCAG 2.4.1 failure that the visual link presence hides. Add `id="main"` (or whichever matches the href) to the target landmark.

Why this matters

Skip link points at an ID that doesn't exist on the page. The link looks fine visually but does nothing when activated -- silent WCAG 2.4.1 failure.

Learn more ▾

Find the target landmark (typically <main> or the first <h1>) and add `id="..."` matching the skip link's href fragment. Test by tabbing to the skip link and pressing Enter -- focus should jump to the target.

Source: WCAG 2.1 SC 2.4.1

B
Heading Hierarchy
78 headings, 2 skip(s)
REVIEW
78 headings, 2 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Select cookie preferences
  • H1 Compare broadband deals
  • H2 Some of our best broadband deals - May 2026
  • H2 Special offers
  • H2 Package
  • H2 Download speeds
  • H2 Connection type
  • H2 Home phone
  • H2 Awards and recognition
  • H2 Provider
  • H2 Contract length
  • H2 Monthly cost
  • H5 Deals checked by skipped
  • H2 Our expert's recommended broadband deal
  • H3 Pros
  • H3 Cons
  • H3 Award-winning reliability
  • H2 How does our broadband postcode checker work?
  • H2 How to save on your next broadband deal
  • H3 1. If you're out of contract, you can switch right now for free
  • H3 2. Sticking with the same provider can be expensive
  • H3 3. Know what 'value' means to you
  • H3 4. You could upgrade your connection and still reduce your bill
  • H3 5. If you watch a lot of TV, bundle it
  • H3 6. Don't disregard customer service
  • H3 7. If you're moving home, you may need to take action
  • H2 Broadband providers you can compare with Uswitch
  • H3 How to find the right broadband provider for what you need
  • H3 2026 Uswitch Telecoms Awards: our best-rated providers
  • H3 Regional broadband providers are challenging the big brands
  • H2 Our experts' broadband provider reviews
  • H3 Uswitch broadband provider reviews
  • H2 One Touch Switch: simpler broadband switching
  • H2 What type of broadband package should I choose?
  • H3 Broadband-only
  • H3 Broadband and home phone
  • H3 Broadband and TV
  • H3 Broadband, home phone, TV, mobile
  • H2 What happens after I switch broadband?
  • H2 Broadband price rises in 2026 explained
  • H2 Can I get a low-income broadband social tariff?
  • H2 How to haggle for a better broadband deal
  • H2 Why choose Uswitch for broadband?
  • H3 Hard-fought value
  • H3 Deals tailored to you
  • H3 You can trust us
  • H2 Which types of broadband connection are in my area?
  • H3 Full fibre
  • H3 Part-fibre
  • H3 Cable (Virgin Media)
  • H3 Satellite broadband
  • H3 Mobile broadband
  • H3 Copper ADSL
  • H2 What internet speed do I need?
  • H5 0-50 Mbps skipped
  • H5 51-100 Mbps
  • H5 101-500 Mbps
  • H5 500+ Mbps
  • H3 What is my current broadband speed?
  • H3 Take a broadband speed test
  • H3 What’s the fastest broadband in my area?
  • H3 What can affect your broadband speed?
  • H4 1. The type of broadband you have
  • H4 2. Your distance to the nearest broadband exchange or cabinet
  • H4 3. Where your Wi-Fi router is
  • H4 4. The time of day
  • H4 Why is broadband speed advertised as an 'average'?
  • H3 Broadband postcode checker
  • H2 Compare broadband deals in your local area
  • H2 What our customers are saying
  • H2 Compare broadband, TV and phone deals
  • H2 Frequently asked questions
  • H2 Read our broadband guides
  • H3 About these results
  • H3 How our site works
  • H3 Studies & statistics methodology
  • H3 Get the Uswitch app
  • H3 You are in safe hands

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

C
Tabindex Anti-Patterns
Action
0 positive, 7 -1-on-focusable
REVIEW
0 positive, 7 -1-on-focusable
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
Info::
tabindex="-1" on naturally-focusable <a>
tabindex="-1" removes an element from the keyboard tab order. Naturally-focusable elements (links, buttons, form controls) become unreachable for keyboard users. (Common false-positive: hidden honeypot fields. Verify the element is genuinely interactive before removing the tabindex.)
C
Favicon & Branding
Action
5 icon(s) detected
REVIEW
5 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
A+
Heading Text Quality
All 78 heading(s) have substantive, well-formed text
PASS
All 78 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 77 images OK
PASS
All 77 images OK
Info::
11 decorative image(s) correctly marked
Info::
66 image(s) with good alt text
77 images 66 good alt text 11 decorative
All images have appropriate alt text.
A+
Form Accessibility
All 40 controls labeled
PASS
All 40 controls labeled
Info::
40 control(s) properly labeled
40 controls
40 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#cp_chk0checkboxEssentialfor/id
#cp_chk1checkboxPerformancefor/id
#cp_chk2checkboxMarketingfor/id
#cp_chk3checkboxFunctionalityfor/id
#cp_chk4checkboxSocialfor/id
#querysearchsearch USwitcharia-label
#capture-form-combobox-postcode-inputtextEnter your postcode to find addressesaria-label
#sort-selectselectSort Optionsaria-label
#«r18R2mhl»checkboxnone
#«r18R36hl»checkboxnone
#«r18R2mil»checkboxnone
#«r18R36il»checkboxnone
#«r18R16jl»radionone
#«r18R1ajl»radionone
#«r18R1ejl»radionone
#«r18R1ijl»radionone
#«r18R1mjl»radionone
#«r18R2mkl»checkboxnone
#«r18R36kl»checkboxnone
#«r18R2mll»checkboxnone
#«r18R36ll»checkboxnone
#«r18R3mll»checkboxnone
#«r18R1mml»checkboxnone
#«r18R4mnl»checkboxnone
#«r18R56nl»checkboxnone
#«r18R5mnl»checkboxnone
#«r18R66nl»checkboxnone
#«r18R6mnl»checkboxnone
#«r18R76nl»checkboxnone
#«r18R7mnl»checkboxnone
#«r18Rmol»checkboxnone
#«r18Rqol»checkboxnone
#«r18Rmpl»checkboxnone
#«r18Rqpl»checkboxnone
#«r18Rupl»checkboxnone
#capture-form-combobox-postcode-inputtextEnter your postcode to find addressesaria-label
#footer-links-0checkboxCompare Dealsfor/id
#footer-links-1checkboxAboutfor/id
#footer-links-2checkboxHelp & Supportfor/id
#footer-links-3checkboxLegalfor/id
A+
Form Input Types
40 form control(s) checked, no type mismatches
PASS
40 form control(s) checked, no type mismatches
Info::
No input-type mismatches detected
A+
Form Input Quality
40 form control(s) checked, no input-semantic issues
PASS
40 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Mobile Keyboard & Autofill
No autofill-eligible form controls
PASS
No autofill-eligible form controls
Info::
No autofill-eligible form controls (no name/email/tel/address fields)
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A
Iframe Accessibility
1/1 iframe(s) missing title; 0 placeholder(s)
PASS
1/1 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="/~partytown/partytown-sandbox-sw.html?1778416768588")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
Font-size measurement not available for this scan
PASS
Font-size measurement not available for this scan
Info::
Font-size measurement not available for this scan
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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 96/100 — 2 failing, 33 passed
PASS
96

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.

Navigation

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more about heading order.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Deals checked by section._expertReviewSection_1w2sb_1 > div._flexContainer_1w2sb_13 > div > h5
div.builder-03c17c9ce2b24adf89b7ef79bf80243b > div.builder-9e1790ec1ba04d618553a64cc4236970 > div.first:*:mt-0 > h5 div.builder-03c17c9ce2b24adf89b7ef79bf80243b > div.builder-9e1790ec1ba04d618553a64cc4236970 > div.first:*:mt-0 > h5

These are opportunities to improve keyboard navigation in your application.

Tables and lists

Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Virgin Media div > broadband-scope.broadband-scope > div.single-deal-card-ee662c50-e426-4c4f-b74b-09836e3d08dd > li._wrapper_1lxgn_1

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

○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.
●Select elements have associated label elements.
●`button`, `link`, and `menuitem` elements have accessible names
●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>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
●`[lang]` attributes have a valid value
●Document has a main landmark.
●Deprecated ARIA roles were not used
●No form fields have multiple labels
●Uses ARIA roles only on compatible elements
●Identical links have the same purpose.
●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.
○`[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
○`<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
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Skip links are focusable.
○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
○`<video>` elements contain a `<track>` element with `[kind="captions"]`
○Tables have different content in the summary attribute and `<caption>`.
○All heading elements contain content.
○Image elements do not have `[alt]` attributes that are redundant text.
○Elements with visible text labels have matching accessible names.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback