Skip to content
https://howtogeek.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
F
Heading Hierarchy
Action
64 headings, 4 skip(s)
FIX
64 headings, 4 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: 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.
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 3 brilliant HBO Max shows you can binge this week (April 20-26)
  • H3 Microsoft admits Game Pass is too expensive and slashes prices (with a catch)
  • H3 Apple Maps is getting ads, and it just lost the one thing that made it worth using
  • H3 Elden Ring is coming: Everything you need to know about the A24 movie
  • H3 IKEA's affordable smart home devices just got the seamless experience they deserve
  • H3 5 CPUs that are officially too old for gaming in 2026
  • H3 Amazon sued over early Fire TV Stick support—will you get paid?
  • H2 Popular News
  • H3 Stop paying for Alexa and Google Home—this open-source smart home system will never charge you
  • H3 Forget the BMW 5 Series—this Japanese sedan is more fun to drive
  • H3 Why I abandoned Gmail for a privacy-first email service—and never looked back
  • H3 This one small upgrade makes any budget turntable sound high-end
  • H3 I built a NAS from a $70 broken laptop—here's why it beats a dedicated enclosure
  • H3 I ran a dealership express lube—these 4 services help your car last 200,000 miles
  • H3 Linux users claim they want mainstream adoption, but here's why they don't
  • H3 Milwaukee makes tools Makita can't touch—here are 5 you need to see
  • H3 I wanted a repairable phone, but the Fairphone 6 still has a breaking point
  • H2 Deals Center
  • H2 News
  • H3 You’ll love Ryobi's new customizable DIY workbench
  • H3 Sony and Honda wind down their EV alliance, for now
  • H3 Tim Cook is stepping down as Apple CEO—here's his replacement
  • H3 Mercedes' 2027 electric C-Class is its sportiest version yet—EV or not
  • H3 Why OnePlus is abandoning key markets and what comes next
  • H2 Product Reviews
  • H5 The Sharge Disk Pro is the most unique portable SSD I’ve ever tested skipped
  • H5 This $2,500 robot lawnmower works brilliantly—if your yard is compatible
  • H5 Brighter, more colorful, and Matter-compatible: The outdoor string lights your patio needs
  • H2 Deals
  • H5 Save on UGREEN's Thunderbolt 5 docks and upgrade your workspace skipped
  • H5 These are the 15 best Amazon Big Spring Sale deals
  • H5 Home Depot's Spring Ryobi battery sale is a steal
  • H2 Latest
  • H5 Stop paying for Alexa and Google Home—this open-source smart home system will never charge you skipped
  • H5 Forget the BMW 5 Series—this Japanese sedan is more fun to drive
  • H5 Why I abandoned Gmail for a privacy-first email service—and never looked back
  • H5 This one small upgrade makes any budget turntable sound high-end
  • H5 I built a NAS from a $70 broken laptop—here's why it beats a dedicated enclosure
  • H5 I ran a dealership express lube—these 4 services help your car last 200,000 miles
  • H5 Linux users claim they want mainstream adoption, but here's why they don't
  • H5 Milwaukee makes tools Makita can't touch—here are 5 you need to see
  • H5 I wanted a repairable phone, but the Fairphone 6 still has a breaking point
  • H5 Stop trusting viral 3D printer hacks—they're hiding the real problems with your machine
  • H5 Digital minimalism is overrated—how more devices made me more productive
  • H5 Pixar's best movie isn't one of the old classics, it's this blockbuster from 2017
  • H5 These 3 self-hosted apps are the only reason I finally added more RAM to my NAS
  • H5 Here’s when your Samsung Galaxy will get Android 17 (One UI 9)
  • H5 5 open-source operating systems everyone mistakes for Linux
  • H5 I froze PC upgrades for a year—here's why you should do the same
  • H5 Heated beds don't fix bad 3D prints, but these 6 things do
  • H5 Power Query is the game-changing Excel feature you're not using—here are 5 ways to put it to work
  • H5 Skip the luxury badge: 5 SUVs that deliver the same experience for less
  • H5 Google made an audiophile’s dream streaming device (and killed it after 1 generation)
  • H3 Desktop
  • H3 Mobile
  • H5 Your Linux desktop is frozen, but your work isn't lost—here's how to save it skipped
  • H5 GNOME 50 is the Linux desktop update I've waited years for
  • H5 Stop trusting your shell scripts: Why ShellCheck is the tool you're missing
  • H5 I forgot FaceTime on Android still works—so did Apple
  • H5 Android's most trusted launcher is now harvesting your data
  • H5 Don't buy the Pixel 10a for the camera, buy it for the screen
  • H5 Stop dragging to fill cells: Automate Excel lists with the SEQUENCE function
  • H5 3 entertaining Netflix thrillers worth watching this week (April 20-26)
  • H5 Stop replacing your entire keyboard—swap these 7 keys instead

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

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 11 controls have issues
REVIEW
3 of 11 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::
8 control(s) properly labeled
11 controls
8 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#side_menucheckboxMenufor/id
#navItems-PC HardwarecheckboxSubmenufor/id
#navItems-Operating SystemscheckboxSubmenufor/id
#navItems-SoftwarecheckboxSubmenufor/id
#navItems-MobilecheckboxSubmenufor/id
#navItems-New TechcheckboxSubmenufor/id
#navItems-StreamingcheckboxSubmenufor/id
#search-menucheckboxClosefor/id
#js-search-inputtext(Search How-To Geek)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 How-To Geek 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.

B
Lighthouse Accessibility Audits
Score 80/100 — 6 failing, 19 passed
REVIEW
80

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.

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.w-hub-video > div#left-block-articles > div.w-control-arrows > button#previous-btn div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#previous-btn
div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#next-btn div.w-hub-video > div#left-block-articles > div.w-control-arrows > button#next-btn

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.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.

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
3 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
3 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
4 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
4 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
MORE div.template-grid-tall > div.featured-news > div.sentinel-featuredNews > a.section-view-all-link
SEE MORE section#news > div.w-hub-widgets > div.hub-header > a.section-view-all-link
SEE MORE div.left-column > div.w-hub-video > div.hub-header > a.section-view-all-link
SEE MORE div.right-column > div#left-block > div.hub-header > a.section-view-all-link
Apr 5, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Mar 26, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Mar 19, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
3 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
4 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
4 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
4 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
4 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
5 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
5 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
5 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
5 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
6 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
6 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
6 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
6 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
7 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
7 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
7 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
8 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
8 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
8 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-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
The Sharge Disk Pro is the most unique portable SSD I’ve ever tested div#left-block-articles > div.display-card > div.w-display-card-content > h5.display-card-title
Save on UGREEN's Thunderbolt 5 docks and upgrade your workspace div.hub-vertical-list > div.display-card > div.w-display-card-content > h5.display-card-title
Stop paying for Alexa and Google Home—this open-source smart home system will n… 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.

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
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
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 items highlight common accessibility best practices.

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
DEALS CENTER Updated Weekly Hand-picked savings on our favorite gear Browse D… main.w-content > div.w-promotion-offer > div.promotion-offer-box > a.dc-banner
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
`<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
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
`<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
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.
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 60 images OK
PASS
All 60 images OK
Info::
1 image(s) with alt text over 125 characters
Info::
59 image(s) with good alt text
60 images 59 good alt text
IssueCount
too long1 image(s)
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Popular News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Deals Center21.00:13.0:1
#000000
#FFFFFF
Pass
h2 News21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Product Reviews21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Deals21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Latest21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Desktop21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Mobile21.00:13.0:1
#000000
#FFFFFF
Pass
title How-To Geek - We Exp…18.76:14.5:1
#000000
#F2F2F2
Pass
span Menu18.76:14.5:1
#000000
#F2F2F2
Pass
span Sign in now21.00:14.5:1
#000000
#FFFFFF
Pass
span Close21.00:14.5:1
#000000
#FFFFFF
Pass
span News21.00:14.5:1
#000000
#FFFFFF
Pass
span Tech Deals21.00:14.5:1
#000000
#FFFFFF
Pass
span PC Hardware21.00:14.5:1
#000000
#FFFFFF
Pass
span Submenu21.00:14.5:1
#000000
#FFFFFF
Pass
span Networking21.00:14.5:1
#000000
#FFFFFF
Pass
span Storage and NAS21.00:14.5:1
#000000
#FFFFFF
Pass
span Components21.00:14.5:1
#000000
#FFFFFF
Pass
span Peripherals21.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.

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

Send Feedback