Skip to content
https://pcworld.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
54
GRADE
F
FIX
5
REVIEW
6
PASS
2
INFO
0
Checks
13
2 PASS 6 REVIEW 5 FIX
D
Alt Text Quality
Action
3 of 23 images have issues
FIX
3 of 23 images have issues
Critical::
3 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Critical::
3 image-in-link without alt text
An image inside a link with no alt creates an empty link.
Info::
20 image(s) with good alt text
23 images 20 good alt text 3 missing
IssueCount
missing3 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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

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::
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
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
0 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
3 landmarks
REVIEW
3 landmarks
Info::
<main> landmark present
Warning::
No <nav> landmark found
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 MAIN CONTENTINFO footer

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
Heading Hierarchy
25 headings
REVIEW
25 headings
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
  • H3 Bing is the anti-AI search engine you should be using
  • H3 I switched to Starlink. These are the 6 biggest surprises
  • H3 Investigation: Are RAM prices dropping, or is it all illusion?
  • H3 Lenovo Yoga 7a review: A capable 2-in-1 with weak graphics
  • H3 LATEST STORIES
  • H3 Best VPNs for torrenting: 5 top picks for speed, privacy, and security
  • H3 Microsoft's next Windows 11 update targets stability and speed
  • H3 Flat-rate AI plans are broken. Blame AI agents
  • H3 Massive 49-inch OLED ultrawide monitor drops to $700 (now $300 off)
  • H3 Microsoft officially says you don't need extra antivirus on Windows 11
  • H3 Even trusted apps can spread PC malware now
  • H3 Anker's 2-in-1 docking station with pop-out hub hits its best price
  • H3 This Lenovo Legion 5i with RTX 5060, 32GB RAM, and OLED is $400 off
  • H3 Lenovo Yoga 7a review: A capable 2-in-1 with weak graphics
  • H3 This mini PC packs 32GB RAM and only costs $409 with our code
  • H3 Today’s best laptop deals: Save big on work, school, home use, and gaming
  • H3 Bing is the anti-AI search engine you should be using
  • H3 I switched to Starlink. These are the 6 biggest surprises
  • H3 Best computer deals from desktops to all-in-ones
  • H3 This prompt trick forces AI to stop flattering you and think harder
  • H3 One reason to use Edge: It now teases new Windows features
  • H3 The best PCIe 4.0 SSDs for blistering storage speeds
  • H3 Acer's RTX 5070 Helios Neo 16 AI drops to $1,500 (now $350 off)
  • H3 Best Chromebooks 2026: Top picks for work, school, and more
  • H3 April's Windows 11 update is trapping some PCs in a boot loop

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

C
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found | PCWorld ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 4 fail WCAG AA
REVIEW

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

16 pass 4 fail WCAG AA 5 pass AA only
title PCWorld
1.24:1
#000000
on
#3C0A0F
needs 4.5:1 (normal text)
16px · top of page (header area)
a News
1.24:1
#000000
on
#3C0A0F
needs 4.5:1 (normal text)
16px · top of page (header area)
a All News
3.00:1
#000000
on
#595959
needs 4.5:1 (normal text)
16px · top of page (header area)
a Accessories
2.82:1
#000000
on
#555555
needs 4.5:1 (normal text)
16px · top of page (header area)
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h3 Bing is the anti-AI …3.00:13.0:1
#000000
#595959
Pass
h3 I switched to Starli…3.00:13.0:1
#000000
#595959
Pass
h3 Investigation: Are R…3.00:13.0:1
#000000
#595959
Pass
h3 Lenovo Yoga 7a revie…3.00:13.0:1
#000000
#595959
Pass
h3 LATEST STORIES3.00:13.0:1
#000000
#595959
Pass
title PCWorld1.24:14.5:1
#000000
#3C0A0F
Fail
a News1.24:14.5:1
#000000
#3C0A0F
Fail
a All News3.00:14.5:1
#000000
#595959
Fail
a Accessories2.82:14.5:1
#000000
#555555
Fail
a Business11.18:14.5:1
#000000
#BDBDBD
Pass
a Entertainment21.00:14.5:1
#000000
#FFFFFF
Pass
a Gaming21.00:14.5:1
#000000
#FFFFFF
Pass
a Laptops21.00:14.5:1
#000000
#FFFFFF
Pass
a Mobile21.00:14.5:1
#000000
#FFFFFF
Pass
a Monitors21.00:14.5:1
#000000
#FFFFFF
Pass
a PCs & Components21.00:14.5:1
#000000
#FFFFFF
Pass
a Security21.00:14.5:1
#000000
#FFFFFF
Pass
a Smart Home Security21.00:14.5:1
#000000
#FFFFFF
Pass
a Software21.00:14.5:1
#000000
#FFFFFF
Pass
a Storage21.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+
Form Accessibility
All 1 controls labeled
PASS
All 1 controls labeled
Info::
1 control(s) properly labeled
1 controls
1 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
#footerSelectselectSelect Foundry Networkaria-label
A+
Lighthouse Accessibility Audits
Score 95/100 — 2 failing, 28 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.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
a.floating-anchor > div.item-inner > div.item-image > img a.floating-anchor > div.item-inner > div.item-image > img
a.floating-anchor > div.item-inner > div.item-image > img a.floating-anchor > div.item-inner > div.item-image > img
a.floating-anchor > div.item-inner > div.item-image > img a.floating-anchor > div.item-inner > div.item-image > img

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.

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
MORE STORIES div.articleFeed > div.articleFeed-inner > div.articleFeed-button > a.btn
POLICIES Expand Policies div.primaryFooter-menu-wrap > ul#footer-primary > li#menu-item-100000311-footer-primary > button.menu-toggle-button
ABOUT Expand About div.primaryFooter-menu-wrap > ul#footer-secondary > li#menu-item-100000322-footer-secondary > button.menu-toggle-button
PCWORLD CATEGORIES Expand submenu for PCWorld Categories div.primaryFooter-menu-wrap > ul#third-column-footer-menu > li#third-column-footer-menu-item-one > button.menu-toggle-button
SUBSCRIBE Expand submenu for Subscribe div.primaryFooter-menu-wrap > ul#forth-column-footer-menu > li#third-column-footer-menu-item > button.menu-toggle-button
○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
●`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
●Select elements have associated label elements.
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Background and foreground colors have a sufficient contrast ratio
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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.
●Heading elements appear in a sequentially-descending order
●Document has a main landmark.
●Deprecated ARIA roles were not used
●ARIA IDs are unique
●Identical links have the same purpose.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements 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
○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
○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.
○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