Skip to content
https://pocket-lint.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
57
GRADE
D
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
D
Heading Hierarchy
Action
64 headings, 2 skip(s)
FIX
64 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
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: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H3 Fire Sticks are finally getting Gigabit Ethernet - but don't celebrate just yet
  • H3 4 Android Auto settings more drivers should change
  • H3 My favorite forgotten horror masterpiece is now free to stream
  • H3 How I made my Pixel home screen dance for $2
  • H3 I traded my Kindle Paperwhite for an iPad and there's no way I can go back now
  • H3 I gave my Pixel a Dynamic Island, and it puts the iPhone to shame
  • H3 Google Wallet's convenient new feature is here just in time for summer
  • H3 Pixel phones are having battery problems again - Here's what's going on
  • H3 I'm never ditching my old school iPod
  • H3 3 easy things everyone can do right now to prevent scam and robocalls
  • H3 The worst time to buy an Apple TV 4K is right now
  • H3 The new Roku City game is just a giant ad
  • H3 $1 is all it took to turn my Nothing phone into a Pixel
  • H3 Apple CarPlay just quietly rolled out a game-changing new feature
  • H3 Too many new home theater builders make this mistake
  • H3 4 CarPlay voice commands I wish more drivers knew
  • H2 Top Stories
  • H3 Apple won't tell you this about buying a new Mac, but I will
  • H3 This is what happens if you leave a Google TV device plugged in 24/7
  • H3 My favorite underrated sci-fi film is finally free to stream
  • H2 Reviews
  • H3 This $450 mini PC packs a bigger punch than I expected
  • H3 This $200 gadget ended my charging troubles once and for all
  • H3 The Samsung Galaxy S26 Ultra comes so close to having it all
  • H3 The iPad Air (M4) comes incredibly close to being the perfect tablet
  • H3 I found a $200 projector perfect for impromptu movie nights
  • H2 Latest
  • H5 Pixel phones are having battery problems again - Here's what's going on skipped
  • H5 I'm never ditching my old school iPod
  • H5 3 easy things everyone can do right now to prevent scam and robocalls
  • H5 The worst time to buy an Apple TV 4K is right now
  • H5 The new Roku City game is just a giant ad
  • H5 $1 is all it took to turn my Nothing phone into a Pixel
  • H5 Apple CarPlay just quietly rolled out a game-changing new feature
  • H5 Too many new home theater builders make this mistake
  • H5 4 CarPlay voice commands I wish more drivers knew
  • H5 How to read The Odyssey for free on your Kindle or iPad before the movie
  • H5 I improved my LG TV's picture quality instantly with these 4 tweaks
  • H5 Getting back into physical media? Here's what you need to know
  • H5 Amazon has officially removed this Fire Stick capability forever
  • H5 Pixel Glow could be your device's next bright feature
  • H5 Amazon is dropping the hammer on this Kindle app
  • H5 How I disable unwanted AI features on my Samsung Galaxy
  • H5 TV spyware keeps getting worse; here's how to protect yourself
  • H5 I can't believe after 16 years the iPad still has this day 1 problem
  • H5 I found the only car subscriptions worth paying for
  • H5 4 sneaky Ethernet problems that have nothing to do with your router or cable
  • H3 Reviews
  • H3 Editorials
  • H5 This powerful folding projector is small enough to fit in my pocket skipped
  • H5 With the Phone 4a Pro, Nothing has finally found its mid-range mojo
  • H5 I'm never taking these ultra-comfortable $230 earbuds off
  • H5 This ASUS ProArt laptop makes both the creator and the gamer inside of me happy
  • H5 This $3,000 PC might be the MacBook replacement I've been waiting for
  • H5 The newest MacBook Air is everything I want in a laptop - almost
  • H5 I wish everyone knew about this Dolby Atmos alternative, and why it's better
  • H5 SQD-Mini LED is going to change TV tech forever - Here's how I know
  • H5 Amazon can't force me to upgrade my Kindle when I can read on this device for free
  • H5 Uninstalling your browser extensions has some serious benefits
  • H5 HDMI passthrough is the most important feature that you aren't using
  • H5 Apple can finally do something interesting with the iPad. I hope they don't screw it up
  • H5 You don't need Chrome to use Gemini on PC anymore
  • H5 Windows is finally rebuilding the Start Menu and I couldn't be more excited
  • H5 Google is offering 50% off YouTube Premium today for certain subscribers

Every page should have one H1 that describes the page content.

Why this matters

No H1 means screen-reader users can't identify the page's primary topic, and Google's content-extraction degrades.

Learn more ▾

The H1 is the document title for assistive tech and a strong signal to search engines about page topic. Pages without one force screen readers to fall back to the <title> attribute or page chrome. Add a single H1 that names the page's primary subject.

Source: WCAG 2.4.6 / Google Search Central

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

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
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::
3 navigation landmark(s) detected
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 3 <nav> element(s)
Back to Top
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.
B
Landmark Structure
7 landmarks
REVIEW
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.
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 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

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

C
Form Accessibility
Action
3 of 12 controls have issues
REVIEW
3 of 12 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="checkbox" id="showMoreToggle">; <input type="checkbox" id="expandMenuListDefault">
Warning::
1 control(s) rely on placeholder only
Placeholder text disappears on focus and is not a reliable label.
Got: <input type="text" name="q" id="js-search-input">
Info::
9 control(s) properly labeled
12 controls
9 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#side_menucheckboxMenufor/id
#navItems-LatestcheckboxLatest Submenufor/id
#navItems-DevicescheckboxSubmenufor/id
#navItems-EntertainmentcheckboxSubmenufor/id
#navItems-AutomotivecheckboxAutomotive Submenufor/id
#navItems-MorecheckboxMore Submenufor/id
#navItems-Tech TrendscheckboxTech Trends Submenufor/id
#navItems-AboutcheckboxAbout Submenufor/id
#search-menucheckboxClosefor/id
#js-search-inputtext(Search Pocket-lint)placeholder only
#showMoreTogglecheckbox(none)none
#expandMenuListDefaultcheckbox(none)none

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

<input type="checkbox" id="showMoreToggle">; <input type="checkbox" id="expandMenuListDefault">

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

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

<input type="text" name="q" id="js-search-input">

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::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Pocket-lint ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
C
Favicon & Branding
Action
7 icon(s) detected
REVIEW
7 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
B
Dark Mode Support
Dark mode detected
REVIEW
Dark mode detected
Info::
prefers-color-scheme CSS detected in inline styles
Info::
Detection limited to meta tags and inline styles
External CSS files may contain prefers-color-scheme rules not visible to this scan.
Dark Mode✓ Dark Mode Supported
color-scheme meta Not set ✗Dark theme-color Not set ✗CSS indicators Detected ✓

Detection limited to meta tags and inline styles.

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 2 fail WCAG AA
REVIEW

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

18 pass 2 fail WCAG AA
title Pocket-lint | Phone, gadget, and enterta…
1.22:1
#000000
on
#021B38
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
1.22:1
#000000
on
#021B38
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Top Stories18.36:13.0:1
#000000
#ECEFFF
Pass
h2 Reviews18.36:13.0:1
#000000
#ECEFFF
Pass
h2 Latest18.36:13.0:1
#000000
#ECEFFF
Pass
h3 Reviews18.36:13.0:1
#000000
#ECEFFF
Pass
h3 Editorials18.36:13.0:1
#000000
#ECEFFF
Pass
title Pocket-lint | Phone,…1.22:14.5:1
#000000
#021B38
Fail
span Menu1.22:14.5:1
#000000
#021B38
Fail
span Sign in now18.36:14.5:1
#000000
#ECEFFF
Pass
span Close18.36:14.5:1
#000000
#ECEFFF
Pass
span Latest18.36:14.5:1
#000000
#ECEFFF
Pass
span Submenu18.36:14.5:1
#000000
#ECEFFF
Pass
span News18.36:14.5:1
#000000
#ECEFFF
Pass
span Lists18.36:14.5:1
#000000
#ECEFFF
Pass
span Features18.36:14.5:1
#000000
#ECEFFF
Pass
span Editorials18.36:14.5:1
#000000
#ECEFFF
Pass
span Guides18.36:14.5:1
#000000
#ECEFFF
Pass
span Reviews18.36:14.5:1
#000000
#ECEFFF
Pass
span Comparisons18.36:14.5:1
#000000
#ECEFFF
Pass
span Buyer's Guides18.36:14.5:1
#000000
#ECEFFF
Pass
span Deals18.36:14.5:1
#000000
#ECEFFF
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.

B
Lighthouse Accessibility Audits
Score 86/100 — 4 failing, 20 passed
REVIEW
86

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
TVS div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
CAR TECH div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
TUBI div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
TABLETS div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
APPS div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
APPS div.w-display-card-content > div.w-display-card-category > a.dc-tag-label > span
MORE div.template-grid-tall > div.featured-news > div.sentinel-featuredNews > a.section-view-all-link
SEE MORE section#top-stories > div.w-hub-widgets > div.hub-header > a.section-view-all-link
SEE MORE section#reviews > div.w-hub-widgets > div.hub-header > a.section-view-all-link
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
1 day ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
2 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 days ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Join Our Team div.footer-content-el > ul > li > a.text
Our Audience div.footer-content-el > ul > li > a.text
About Us div.footer-content-el > ul > li > a.text
Press & Events div.footer-content-el > ul > li > a.text
Media Coverage div.footer-content-el > ul > li > a.text
Contact Us div.footer-content-el > ul > li > a.text
Advertising div.footer-content-el > ul.align-right > li > a.text
Careers div.footer-content-el > ul.align-right > li > a.text
Terms div.footer-content-el > ul.align-right > li > a.text
Privacy div.footer-content-el > ul.align-right > li > a.text
Policies div.footer-content-el > ul.align-right > li > a.text

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
Pixel phones are having battery problems again - Here's what's going on div.sentinel-home-list > div.display-card > div.w-display-card-content > h5.display-card-title

These are opportunities to improve keyboard navigation in your application.

Names and labels

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links div.w-side-navigation-social > ul#menu-follow > li.social-elements > a.social-links
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number div.w-display-card-content > div.w-display-card-details > div.w-display-card-extra > a.total-info-number
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text
div.footer-content-el > ul.social-media > li.social-elements > a.text div.footer-content-el > ul.social-media > li.social-elements > a.text

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.

Best practices

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
TABLETS div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
APPS div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
APPS div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label

These items highlight common accessibility best practices.

○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
●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
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●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
○Buttons have an accessible name
○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
○Links are distinguishable without relying on color.
○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.
○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+
Alt Text Quality
All 63 images OK
PASS
All 63 images OK
Info::
63 image(s) with good alt text
63 images 63 good alt text
All images have appropriate alt text.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback