Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

5 PASS 4 REVIEW 4 FIX

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

Manifest at https://dummies.com/manifest.json contains invalid JSON. Browsers cannot parse it.

Got: https://dummies.com/manifest.json

Manifest contains invalid JSON.

Dark Mode Support

Action

No dark mode signals

FIX

No dark mode signals

No dark mode signals detected

Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.

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.

Print Stylesheet

Action

No print styles

FIX

No print styles

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

4 navigation landmark(s) detected

No breadcrumbs, search, or skip link detected

These navigation aids help users orient themselves and find content efficiently, especially on large sites.

Breadcrumbs

Skip Link

Labeled Navigation 4 <nav> element(s)

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.

Landmark Structure

11 landmarks

REVIEW

11 landmarks

<main> landmark present

4 <nav> landmark(s) found

4 of 4 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

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

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

404 Error Page

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - dummies ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Lighthouse Accessibility Audits

Score 89/100 — 3 failing, 26 passed

REVIEW

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.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`

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
Privacy Policy `div.osano-cm-window > div#f29b777a-5cec-470a-b589-d73332270af9 > div.osano-cm-dialog__content > a.osano-cm-storage-policy`
Third Parties `div#f29b777a-5cec-470a-b589-d73332270af9 > div.osano-cm-dialog__content > p.osano-cm-content__drawer-links > a.osano-cm-drawer-links__link`
Manage Preferences `div.osano-cm-window > div#f29b777a-5cec-470a-b589-d73332270af9 > div.osano-cm-dialog__buttons > button.osano-cm-manage`
Accept All `div.osano-cm-window > div#f29b777a-5cec-470a-b589-d73332270af9 > div.osano-cm-dialog__buttons > button.osano-cm-accept-all`
Reject Non-Essential `div.osano-cm-window > div#f29b777a-5cec-470a-b589-d73332270af9 > div.osano-cm-dialog__buttons > button.osano-cm-denyAll`

These are opportunities to improve the legibility of your content.

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.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet `div.h_explore_swiper > div.swiper_navigation-wrapper > div.swiper_pagination-wrapper > button.swiper_pagination_bullet`
youtube icon `div#w-node-_029b1814-1b75-5dd3-0db8-962c8cfd622a-8cfd621b > ul.social-icons > li > a.link-block-79`

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

●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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Image elements have `[alt]` attributes

●Form elements have associated labels

●`[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.

●`[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

●Links have a discernible name

●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements

●No element has a `[tabindex]` value greater than 0

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

○`<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

○Links are distinguishable without relying on color.

○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Select elements have associated label elements.

○Skip links are focusable.

○Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.

○`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.

○`[lang]` attributes have a valid value

○`<video>` elements contain a `<track>` element with `[kind="captions"]`

○Tables have different content in the summary attribute and `<caption>`.

○All heading elements contain content.

○Uses ARIA roles only on compatible elements

○Image elements do not have `[alt]` attributes that are redundant text.

○Elements with visible text labels have matching accessible names.

○Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.

○`<td>` elements in a large `<table>` have one or more table headers.

A+

Heading Hierarchy

27 headings

PASS

27 headings

Single H1 present

H2 Book & Article Categories
H2 Collections
H2 Book & Article Categories
H2 Book & Article Categories
H2 Collections
H1 Solar Power For Dummies
H2 Explore books
H3 Heading
H2 Ask Dummies AI
H2 Collections we are loving
H3 Just for the love of it
H3 For those keen on being green
H3 Find that loving feeling
H3 BYOB (be your own boss)
H3 Career shifting
H2 Made for dummies
H3 How to Choose the Right Golf Club - For Dummies
H3 ‍
H3 How to Change a Tire - For Dummies
H2 Avengers For Dummies
H2 We recommend
H3 Test Prep Help
H3 For Your Business: Dummies Custom
H3 All Things AI
H3 Quick Links
H3 Connect
H3 About Dummies

A+

Alt Text Quality

All 216 images OK

PASS

All 216 images OK

1 image(s) with alt text over 125 characters

11 decorative image(s) correctly marked

204 image(s) with good alt text

216 images 204 good alt text 11 decorative

Issue	Count
too long	1 image(s)

A+

Form Accessibility

All 6 controls labeled

PASS

All 6 controls labeled

6 control(s) properly labeled

6 controls

6 labeled

0 placeholder only

0 unlabeled

Control	Type	Method
#Filter	radio	none
#Filter	radio	none
#Filter	radio	none
#Filter	radio	none
#Filter	radio	none
#Filter	radio	none

Link & Button Quality

179 links, 0 buttons — all OK

PASS

179 links, 0 buttons — all OK

14 link(s) open in new tab without warning

Add '(opens in new tab)' to link text or aria-label.

Got: https://www.youtube.com/@fordummies; https://www.youtube.com/@fordummies; https://support.dummies.com/s/; https://study.learning.wiley.com/; https://www.facebook.com/ForDummies; https://www.instagram.com/fordummies/; https://twitter.com/ForDummies; https://www.youtube.com/user/fordummies; https://www.wiley.com/terms-of-use; https://www.wiley.com/copyright (+4 more)

165 link(s) with descriptive text

179 links

0 empty

0 generic text

14 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.youtube.com/@fordummies	Browse More	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/@fordummies	Browse More	new tab	Add '(opens in new tab)' to text
https://support.dummies.com/s/	Contact Us	new tab	Add '(opens in new tab)' to text
https://study.learning.wiley.com/	Activate Online Content	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/ForDummies	Follow us on Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/fordummies/	Follow us on Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com/ForDummies	Find us on X	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/user/fordummies	youtube icon	new tab	Add '(opens in new tab)' to text
https://www.wiley.com/terms-of-use	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.wiley.com/copyright	Copyright © 2000-2026	new tab	Add '(opens in new tab)' to text
https://www.wiley.com/	John Wiley & Sons, Inc.	new tab	Add '(opens in new tab)' to text
https://www.marvel.com	© 2026 MARVEL	new tab	Add '(opens in new tab)' to text
https://www.wiley.com/terms-of-use	Terms of Use	new tab	Add '(opens in new tab)' to text
https://www.wiley.com/privacy	Privacy Policy	new tab	Add '(opens in new tab)' to text

165 links and buttons have descriptive text

Add '(opens in new tab)' to link text or aria-label.

https://www.youtube.com/@fordummies; https://www.youtube.com/@fordummies; https://support.dummies.com/s/; https://study.learning.wiley.com/; https://www.facebook.com/ForDummies; https://www.instagram.com/fordummies/; https://twitter.com/ForDummies; https://www.youtube.com/user/fordummies; https://www.wiley.com/terms-of-use; https://www.wiley.com/copyright (+4 more)

Why this matters

Links with target="_blank" without rel="noopener" leak the originating page's window context — security and UX issue.

Learn more ▾

Without rel="noopener", the new tab can navigate the original tab via window.opener (tab-nabbing attack). Modern browsers default to noopener for target=_blank but only since recent versions. Always set rel="noopener noreferrer" explicitly.

Source: MDN target / OWASP

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)

Element	Ratio	Required	FG	BG	Result
h1 Solar Power For Dumm…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Book & Article Categ…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Collections	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Book & Article Categ…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Book & Article Categ…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Collections	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Explore books	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Ask Dummies AI	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Collections we are l…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Made for dummies	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 Avengers For Dummies	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h2 We recommend	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 Heading	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 Just for the love of…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 For those keen on be…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 Find that loving fee…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 BYOB (be your own bo…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 Career shifting	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 How to Choose the Ri…	18.27:1	3.0:1	#000000	#EDEFF5	Pass
h3 ‍	18.27:1	3.0:1	#000000	#EDEFF5	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.