Skip to content
https://makeuseof.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
55
GRADE
D
FIX
5
REVIEW
7
PASS
1
INFO
0
Checks
13
1 PASS 7 REVIEW 5 FIX
F
Heading Hierarchy
Action
56 headings, 4 skip(s)
FIX
56 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 I stopped reaching for ChatGPT when Excel could do it three times faster
  • H3 I created a custom Windows 11 install that's faster than Microsoft's version
  • H3 LLMs hallucinate the most when you ask them to do this
  • H3 My keyboard’s battery was draining fast until I switched this one setting
  • H3 I thought I fixed my RAM spikes until I found these tasks hiding in Windows Scheduler
  • H3 Xbox Game Pass is about to get less expensive — is Microsoft actually listening to us?
  • H3 I opened the same 10 tabs in Chrome, Edge, Firefox, and Brave — this one uses the least
  • H3 7 underrated HBO shows you still have time to catch up on before they end
  • H3 I didn’t expect my phone to pull off this physics experiment, but it did
  • H3 These 5 Obsidian plugins made my markdown cleaner than I thought possible
  • H3 I tested four Linux tiling window managers and one of them clearly won me over
  • H3 Soundcore Space 2 review: I finally found budget ANC headphones I actually like
  • H3 This headphone feature fixes the most annoying Bluetooth problem I had
  • H3 I ran one open-source tool and deleted 150GB of hidden Windows junk in minutes
  • H3 6 small home upgrades that actually add value when you sell
  • H3 Samsung's leaked smart glasses could finally beat Ray-Bans if they nail these 4 things
  • H2 Must Reads
  • H5 I set up Bitwarden on my own server for free and my passwords are now completely under my control skipped
  • H5 3 easy ways to supercharge your smart home using Home Assistant — without spending a dime
  • H5 5 Windows Terminal commands I wish I'd known years ago
  • H2 PC & Mobile
  • H5 I uninstalled 5 apps I used every day once I found out Android already does all of it skipped
  • H5 Linux keeps getting faster and more stable, and this programming language is why
  • H5 Windows Photos was slowing me down — this free replacement fixed that instantly
  • H2 Latest
  • H5 7 underrated HBO shows you still have time to catch up on before they end skipped
  • H5 I didn’t expect my phone to pull off this physics experiment, but it did
  • H5 These 5 Obsidian plugins made my markdown cleaner than I thought possible
  • H5 I tested four Linux tiling window managers and one of them clearly won me over
  • H5 Soundcore Space 2 review: I finally found budget ANC headphones I actually like
  • H5 This headphone feature fixes the most annoying Bluetooth problem I had
  • H5 I ran one open-source tool and deleted 150GB of hidden Windows junk in minutes
  • H5 6 small home upgrades that actually add value when you sell
  • H5 Samsung's leaked smart glasses could finally beat Ray-Bans if they nail these 4 things
  • H5 This hidden Excel Automation feature is way more useful than it gets credit for
  • H5 I found 5 hidden Android permissions that were destroying my battery life
  • H5 I didn’t realize how much Android was missing until I used this app
  • H5 If your PC won't boot after Windows 11's April update, try this first
  • H5 I solved my read-it-later bookmarks problem with a reading inbox in Obsidian
  • H5 Your NVMe SSD might be running at half speed because of this BIOS setting
  • H5 5 reasons I’m only buying Matter-compatible smart home devices now
  • H5 This hard-hitting crime drama quietly became one of the biggest shows on Netflix
  • H5 Your PC draws power even when turned off — here's the one-minute fix
  • H5 This free design tool replaced my Canva Pro subscription overnight
  • H5 7 weird USB devices that are surprisingly useful to keep around
  • H3 Technology Explained
  • H3 PC & Mobile
  • H5 I built my own Steam Machine, and I love it skipped
  • H5 5 signs that you should walk away from that used GPU
  • H5 I own 3 PC gaming handhelds, and this is the one I barely use
  • H5 These 3 Android Auto features made my car feel like mine
  • H5 I used a simple Linux command to watch what apps do to my files in real time
  • H5 This $4 Android app brought me more peace of mind than I expected
  • H5 I didn’t buy a Raspberry Pi or mini PC — I used this instead for my home server
  • H5 Your old phone has 5 sensors built in that can trigger smart home automations
  • H5 I bought my first Milwaukee power tool and now I understand why professionals swear by them

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 10 controls have issues
REVIEW
3 of 10 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::
7 control(s) properly labeled
10 controls
7 labeled
1 placeholder only
2 unlabeled
ControlTypeLabelMethod
#side_menucheckboxMenufor/id
#navItems-PC & MobilecheckboxSubmenufor/id
#navItems-TechnicalcheckboxTechnical Submenufor/id
#navItems-SoftwarecheckboxSoftware Submenufor/id
#navItems-ScreencheckboxSubmenufor/id
#navItems-HomecheckboxSubmenufor/id
#search-menucheckboxClosefor/id
#js-search-inputtext(Search MakeUseOf)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 MakeUseOf ✓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, 20 fail WCAG AA
REVIEW

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

0 pass 20 fail WCAG AA
h2 Must Reads
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h2 PC & Mobile
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Latest
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Technology Explained
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
19px · bottom of viewport
h3 PC & Mobile
1.37:1
#000000
on
#252525
needs 3.0:1 (large text)
19px · bottom of viewport
title MUO - Technology, Simplified.
1.15:1
#000000
on
#1E1212
needs 4.5:1 (normal text)
16px · top of page (header area)
span Menu
1.15:1
#000000
on
#1E1212
needs 4.5:1 (normal text)
16px · top of page (header area)
span Sign in now
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · top of page (header area)
span Close
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · top of page (header area)
span PC & Mobile
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Submenu
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Windows
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Linux
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Android
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Apple
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Technical
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Submenu
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Tech Explained
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · above the fold
span Security
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · mid-page
span Software
1.37:1
#000000
on
#252525
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Must Reads1.37:13.0:1
#000000
#252525
Fail
h2 PC & Mobile1.37:13.0:1
#000000
#252525
Fail
h2 Latest1.37:13.0:1
#000000
#252525
Fail
h3 Technology Explained1.37:13.0:1
#000000
#252525
Fail
h3 PC & Mobile1.37:13.0:1
#000000
#252525
Fail
title MUO - Technology, Si…1.15:14.5:1
#000000
#1E1212
Fail
span Menu1.15:14.5:1
#000000
#1E1212
Fail
span Sign in now1.37:14.5:1
#000000
#252525
Fail
span Close1.37:14.5:1
#000000
#252525
Fail
span PC & Mobile1.37:14.5:1
#000000
#252525
Fail
span Submenu1.37:14.5:1
#000000
#252525
Fail
span Windows1.37:14.5:1
#000000
#252525
Fail
span Linux1.37:14.5:1
#000000
#252525
Fail
span Android1.37:14.5:1
#000000
#252525
Fail
span Apple1.37:14.5:1
#000000
#252525
Fail
span Technical1.37:14.5:1
#000000
#252525
Fail
span Submenu1.37:14.5:1
#000000
#252525
Fail
span Tech Explained1.37:14.5:1
#000000
#252525
Fail
span Security1.37:14.5:1
#000000
#252525
Fail
span Software1.37:14.5:1
#000000
#252525
Fail

Methodology: The top 20 text elements by font size were checked. Background color was sampled from the desktop screenshot using a 5-point pattern. WCAG 2.1 AA requires 4.5:1 for normal text and 3:1 for large text.

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
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
By  div.w-display-card-details > div.w-display-card-meta > div.w-author > span.meta_txt
5 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
6 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
7 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
10 HOURS AGO div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.pinned-article-date
SEE MORE div.left-column > div#left-block > div.hub-header > a.section-view-all-link
Apr 21, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Apr 21, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Apr 21, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
SEE MORE div.right-column > div#left-block > div.hub-header > a.section-view-all-link
Apr 21, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Apr 21, 2026 div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
Apr 21, 2026 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
7 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
10 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
13 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
22 hours ago div.w-display-card-details > div.w-display-card-meta > div.meta_txt > span.display-card-date
23 hours 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
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

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
I set up Bitwarden on my own server for free and my passwords are now completel… div.hub-vertical-list > div.display-card > div.w-display-card-content > h5.display-card-title
I uninstalled 5 apps I used every day once I found out Android already does all… div.hub-vertical-list > div.display-card > div.w-display-card-content > h5.display-card-title
7 underrated HBO shows you still have time to catch up on before they end 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.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
WINDOWS TIPS div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
XBOX GAME PASS div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
BROWSER div.display-card > div.w-display-card-content > div.w-display-card-category > a.dc-tag-label
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.

○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 55 images OK
PASS
All 55 images OK
Info::
55 image(s) with good alt text
55 images 55 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