Skip to content
https://trustedreviews.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
50
GRADE
F
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
F
Heading Hierarchy
Action
73 headings, 8 skip(s)
FIX
73 headings, 8 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
1 empty heading(s)
Empty headings appear in the document outline but provide no information.
  • H2 We value your privacy
  • H1 (empty)
  • H2 Oppo Find X9 Ultra vs Xiaomi 17 Ultra: Comparing the Androids
  • H2 Topping D900 DAC Review
  • H2 You can now save 21% on the Snapdragon X Elite Surface Laptop
  • H4 Latest skipped
  • H2 You can get a CoPilot AI laptop with 512GB storage and 16GB memory for less than £350
  • H2 Oppo Find X9 Ultra vs iPhone 17 Pro Max: Android or iOS?
  • H2 What is a DAC? Digital-to-analogue converters explained
  • H4 Latest Reviews skipped
  • H2 JBL Flip 7 Review
  • H2 Soundcore Space 2 Review
  • H2 Anker Soundcore Nebula P1 Review
  • H2 Oppo Find X9 Ultra Review
  • H2 Samsung Galaxy A57 5G Review
  • H2 Chipolo x Secrid Miniwallet Trackable Review
  • H2 FiiO M27 Review
  • H2 Apple MacBook Air M5 Review
  • H4 Opinion skipped
  • H2 RGB TVs have arrived… but is there anything to actually watch on them?
  • H2 The Shark BlastBoss has changed the way I clean my house
  • H2 Who is smartphone AI actually for? Because it’s not for AI users
  • H2 I’m hoping the latest Fire TV update can put an end to doomscrolling
  • H4 Best skipped
  • H2 Best Amazon Fire Tablet 2026: Great value tablets with Alexa built-in
  • H2 Best Air Purifiers 2026: Breathe cleaner air in your home
  • H2 Best Tablet for Kids 2026: Child-friendly software and parental controls
  • H2 Best Action Camera 2026: Great stabilisation in a rugged build
  • H2 Best MSI Laptop 2026: Powerful laptops for gamers and creatives
  • H2 Best 55-inch TVs 2026: Our favourite Mini-LED, OLED and 4K models
  • H2 Best Soundbar 2026: Options for all budgets tested and ranked
  • H4 Explainers skipped
  • H2 What is a DAC? Digital-to-analogue converters explained
  • H2 Google is giving you a free way to upgrade your PC – here’s how
  • H2 What is Bluetooth 6? Everything you need to know
  • H2 What is Microsoft Copilot? The AI assistant explained
  • H2 The best ways to back up your phone
  • H2 What is USB-C? The USB technology explained
  • H4 Deals skipped
  • H2 You can now save 21% on the Snapdragon X Elite Surface Laptop
  • H2 You can get a CoPilot AI laptop with 512GB storage and 16GB memory for less than £350
  • H2 Amazon has chopped 34% off the luxury Dyson Supersonic
  • H2 One of Shark’s best cordless vacs in now 32% cheaper
  • H2 Amazon still has the fantastic MacBook Neo on offer
  • H4 Tech News skipped
  • H2 Samsung adds SmartThings support to IKEA’s Matter devices
  • H2 Xbox Game Pass just got a price cut – with a huge catch
  • H2 Roberts has a new budget radio with plenty of features
  • H2 Sony may have leaked its 10th anniversary WH-1000XX headphones
  • H2 Oppo’s new flagship tablet packs a huge display and a powerful chip
  • H2 Tado just added one of its most requested smart home features
  • H2 The new Honor 600 wants to steal Google’s crown – but you probably can’t buy it yet
  • H2 Nothing’s Warp removal was just a tweak — but it might not be so easy to get it back
  • H2 It looks like Pixel phones have a battery drain issue
  • H2 Would you pay for a WhatsApp Plus service?
  • H4 Versus skipped
  • H4 Oppo Find X9 Ultra vs Xiaomi 17 Ultra: Comparing the Androids
  • H4 Oppo Find X9 Ultra vs iPhone 17 Pro Max: Android or iOS?
  • H4 Oppo Find X9 Ultra vs Oppo Find X9 Pro: What’s the difference?
  • H4 Oppo Find X9 Ultra vs Samsung Galaxy S26 Ultra: The Android flagships compared
  • H4 OLED vs QLED: Which TV should you get?
  • H4 PS5 vs Xbox Series S: The differences explained
  • H4 Apple AirPods Max 2 vs AirPods Max: Do you need to upgrade?
  • H4 DJI Osmo Pocket 4 vs 3: The differences explained
  • H4 How to
  • H4 How to enable Alexa+
  • H4 How to hide your game activity on Steam
  • H4 How to start a Jam on Spotify
  • H4 How to return a game on Steam
  • H4 How to recover deleted messages from Instagram
  • H4 How to turn your SIM into an eSIM on an iPhone
  • H4 How to download and install iOS 26
  • H4 How to make your iPhone app icons clear in iOS 26

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

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

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

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

Empty headings appear in the document outline but provide no information.

Why this matters

Empty <hN> tags break the document outline — screen-reader users navigating by heading hit dead silence.

Source: WCAG 2.4.6

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
No navigation patterns
FIX
No navigation patterns
Info::
1 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 1 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
C
Landmark Structure
Action
2 landmarks
REVIEW
2 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::
No banner (header) landmark
Warning::
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
BANNER (missing!) NAV MAIN (missing!) 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

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

B
Alt Text Quality
2 of 8 images have issues
REVIEW
2 of 8 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
6 image(s) with good alt text
8 images 6 good alt text 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

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

B
Form Accessibility
2 of 2 controls have issues
REVIEW
2 of 2 controls have issues
Warning::
2 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="s">; <input type="search" name="s">
2 controls
0 labeled
2 placeholder only
0 unlabeled
ControlTypeLabelMethod
stext(Search...)placeholder only
ssearch(Search...)placeholder only

Placeholder text disappears on focus and is not a reliable label.

<input type="text" name="s">; <input type="search" name="s">

Why this matters

Placeholder-only labels disappear when the user starts typing — they must remember what the field was for.

Learn more ▾

Placeholders are NOT labels. They vanish on input, fail color contrast checks (most are gray), and don't satisfy WCAG SC 3.3.2. Always use a real <label> alongside (or aria-labelledby).

Source: WCAG 2.1 SC 3.3.2 / Nielsen Norman

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::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Trusted Reviews ✓Custom Styling ✓Navigation ✓Homepage Link ✗Search Form ✓
C
Favicon & Branding
Action
3 icon(s) detected
REVIEW
3 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::
Multiple icon sizes detected
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 3 fail WCAG AA
REVIEW

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

17 pass 3 fail WCAG AA
h2 We value your privacy
1.27:1
#000000
on
#191F27
needs 3.0:1 (large text)
24px · top of page (header area)
title Home - Trusted Reviews
1.27:1
#000000
on
#191F27
needs 4.5:1 (normal text)
16px · top of page (header area)
div We and our
3.26:1
#000000
on
#595F67
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 We value your privac…1.27:13.0:1
#000000
#191F27
Fail
title Home - Trusted Revie…1.27:14.5:1
#000000
#191F27
Fail
div We and our3.26:14.5:1
#000000
#595F67
Fail
button partners7.89:14.5:1
#000000
#9B9FA4
Pass
div store and/or access …21.00:14.5:1
#000000
#FFFFFF
Pass
span MORE OPTIONS21.00:14.5:1
#000000
#FFFFFF
Pass
span AGREE21.00:14.5:1
#000000
#FFFFFF
Pass
span Close Menu21.00:14.5:1
#000000
#FFFFFF
Pass
a Forum21.00:14.5:1
#000000
#FFFFFF
Pass
a Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Camera Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Computing Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Home and Outdoor Rev…21.00:14.5:1
#000000
#FFFFFF
Pass
a Phone Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Tablet Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a TV & Audio Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Gaming Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Wearable Reviews21.00:14.5:1
#000000
#FFFFFF
Pass
a Best Lists21.00:14.5:1
#000000
#FFFFFF
Pass
a Audio Bests21.00:14.5:1
#000000
#FFFFFF
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 Audits
Score 95/100 — 2 failing, 25 passed
PASS
95

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.

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
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
By Kob Monney, Verity Burns div.content > div.post-meta > div.post-meta-items > span.meta-item
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
See All div.elementor-widget-container > section.block-wrap > div.block-head > a.view-link
April 18, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 18, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 18, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 18, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 18, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 17, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 17, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
See All div.elementor-widget-container > section.block-wrap > div.block-head > a.view-link
Sponsored div.elementor-element > div.elementor-widget-container > div.a-wrap > div.label
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 21, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 21, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 21, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
Sponsored div.elementor-element > div.elementor-widget-container > div.a-wrap > div.label
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 22, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 21, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 21, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 21, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 20, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 20, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
April 16, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
March 25, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
January 30, 2026 div.post-meta-items > span.meta-item > span.date-link > time.post-date
November 13, 2025 div.post-meta-items > span.meta-item > span.date-link > time.post-date
November 11, 2025 div.post-meta-items > span.meta-item > span.date-link > time.post-date
November 11, 2025 div.post-meta-items > span.meta-item > span.date-link > time.post-date
September 24, 2025 div.post-meta-items > span.meta-item > span.date-link > time.post-date
September 16, 2025 div.post-meta-items > span.meta-item > span.date-link > time.post-date
September 16, 2025 div.post-meta-items > span.meta-item > span.date-link > time.post-date

These are opportunities to improve the legibility of your content.

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
Latest div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading
Latest Reviews div.elementor-element > div.elementor-widget-container > div.block-head > h4.heading
Opinion div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading
Best div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading
Explainers div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading
Deals div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading
Tech News div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading
Versus div.elementor-widget-container > section.block-wrap > div.block-head > h4.heading

These are opportunities to improve keyboard navigation in your application.

○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.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●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
●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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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.
○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.
○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.

Send Feedback