Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

15 PASS 6 REVIEW 3 FIX

404 Error Page

Action

HTTP 404, bare page

FIX

HTTP 404, bare page

Correct 404 status code returned

Got: HTTP 404

Bare server default 404 page

The 404 page has no custom styling. Users hitting a broken link see a generic error with no way to navigate back. Add a custom 404 page with your site navigation and a search bar.

404 Page Quality Default 404 Page

Status Code HTTP 404 ✓Page Title Page not found | ADHD Reading ✓Custom Styling ✗Navigation ✗Homepage Link ✗Search Form ✗

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

1 navigation landmark(s) detected

Hamburger menu detected (responsive design)

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 1 <nav> element(s)

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

2 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

Multiple <main> landmarks (2 found)

A page should have only one <main> landmark.

1 <nav> landmark(s) found

No banner (header) landmark

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

A page should have only one <main> landmark.

Why this matters

Multiple <main> elements violate the spec — there must be exactly one per page.

Learn more ▾

HTML5 spec: 'authors must not include more than one main element' visible to AT at the same time. Multiple <main>s confuse AT and break the 'jump to main content' shortcut. Refactor to a single <main> with nested <section>/<article>.

Source: HTML5 spec

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

Tap Target Adequacy

Action

8 tap target(s) too small or too close together

REVIEW

8 tap target(s) too small or too close together

8 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

Mobile-Readable Font Sizes

95% of visible text renders at >= 12 CSS px (22 below threshold)

REVIEW

95% of visible text renders at >= 12 CSS px (22 below threshold)

22 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <span> 10.0px ("Edit"); <span> 10.0px ("Fullscreen"); <span> 10.0px ("Import"); <span> 10.0px ("Emphasis mode"); <span> 10.0px ("Bionic Reading").

Favicon & Branding

7 icon(s) detected

REVIEW

7 icon(s) detected

favicon.ico present at site root

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✓ favicon.ico Present

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✓ Manifest Icons Present

✓ Multiple Sizes Present

Dark Mode Support

Dark mode detected

REVIEW

Dark mode detected

prefers-color-scheme CSS detected in inline styles

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.

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 20 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 ADHD Reading Extensi…	3.80:1	3.0:1	#000000	#666874	Pass
h2 Reading Features	3.80:1	3.0:1	#000000	#666874	Pass
h2 Trusted by	3.80:1	3.0:1	#000000	#666874	Pass
h2 Simple pricing for c…	3.80:1	3.0:1	#000000	#666874	Pass
h2 Common	3.80:1	3.0:1	#000000	#666874	Pass
h2 Start Reading Better…	3.80:1	3.0:1	#000000	#666874	Pass
h3 Bionic Reading	3.80:1	3.0:1	#000000	#666874	Pass
h3 Semantic Bold	3.80:1	3.0:1	#000000	#666874	Pass
h3 Semantic Highlight	3.80:1	3.0:1	#000000	#666874	Pass
h3 Typography Controls	3.80:1	3.0:1	#000000	#666874	Pass
h3 Preset Modes	3.80:1	3.0:1	#000000	#666874	Pass
h3 13 Languages	3.80:1	3.0:1	#000000	#666874	Pass
h3 What is ADHD Reading	3.80:1	3.0:1	#000000	#666874	Pass
h3 Why do you need it	3.80:1	3.0:1	#000000	#666874	Pass
h3 How does it work	3.80:1	3.0:1	#000000	#666874	Pass
h3 Immersive Deep Readi…	3.80:1	3.0:1	#000000	#666874	Pass
h3 Efficient Quick Scan…	3.80:1	3.0:1	#000000	#666874	Pass
h3 Get ADHD Reading Now	3.80:1	3.0:1	#000000	#666874	Pass
h3 Free	3.80:1	3.0:1	#000000	#666874	Pass
h3 Pro	3.80:1	3.0:1	#000000	#666874	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+

Heading Hierarchy

50 headings

PASS

50 headings

Single H1 present

H1 ADHD Reading Extension to Reclaim Your Focus
H2 Core ADHD Reading Features
H3 Bionic Reading
H3 Semantic Bold
H3 Semantic Highlight
H3 Typography Controls
H3 Preset Modes
H3 13 Languages
H2 Simple Flow·Regain Control
H3 What is ADHD Reading
H3 Why do you need it
H3 How does it work
H3 Immersive Deep Reading
H3 Efficient Quick Scanning
H3 Get ADHD Reading Now
H2 Trusted by Real Readers
H2 Simple pricing for calmer reading
H3 Free
H3 Pro
H3 Lifetime
H2 Common Questions
H3 About Product
H4 What is ADHD Reading?
H4 How is it different from standard highlighters?
H4 Which browsers are supported?
H4 Is there a mobile app?
H4 Is the software free?
H3 Core Features
H4 What emphasis modes are available?
H4 What is Bionic Reading?
H4 How does Focus Highlighting work?
H4 Does it support TTS (Text-to-Speech)?
H4 Does it support PDF reading?
H3 Usage & Customization
H4 Can I adjust typography and spacing?
H4 Does it support other languages?
H4 Can settings sync across sites?
H4 What if I don't like the colors?
H4 What if layout breaks?
H3 Privacy & Safety
H4 Do I need an account to use it?
H4 Do you collect my reading data?
H4 Will it slow down my browser?
H4 How do I update to the latest version?
H4 Where can I provide feedback?
H2 Start Reading Better Today
H3 Product
H3 Legal
H3 Friendly Links
H3 Medical Disclaimer

A+

Heading Text Quality

All 50 heading(s) have substantive, well-formed text

PASS

All 50 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Alt Text Quality

All 35 images OK

PASS

All 35 images OK

35 image(s) with good alt text

35 images 35 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 13 controls labeled

PASS

All 13 controls labeled

13 control(s) properly labeled

13 controls

13 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
select	select	Select language	aria-label
input	file	Import	none
input	checkbox		none
emphasis-mode	radio		none
emphasis-mode	radio		none
emphasis-mode	radio		none
input	range	Overall Size	none
input	range	Letter spacing	none
input	range	Emphasis density	none
input	range	Emphasis strength	none
input	checkbox		none
input	checkbox		none
input	range	Emphasis strength	none

Link & Button Quality

48 links, 23 buttons — all OK

PASS

48 links, 23 buttons — all OK

25 link(s) open in new tab without warning

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

Got: https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://www.freeai.run/product/adhd-reading; https://tooldirs.com/product/adhd-reading; https://www.toolpilot.ai/products/adhd-reading; https://www.startupfa.st/projects/adhd-reading-2448; https://deeplaunch.io/product/adhd-reading; https://firstlook.tools/product/adhd-reading-7326 (+15 more)

23 link(s) with descriptive text

48 links

0 empty

0 generic text

25 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://chromewebstore.google.com/detail…	Get ADHD Reading	new tab	Add '(opens in new tab)' to text
https://chromewebstore.google.com/detail…	Get ADHD Reading	new tab	Add '(opens in new tab)' to text
https://chromewebstore.google.com/detail…	Install extension	new tab	Add '(opens in new tab)' to text
https://chromewebstore.google.com/detail…	Install Now	new tab	Add '(opens in new tab)' to text
https://www.freeai.run/product/adhd-read…	Featured on FreeAI	new tab	Add '(opens in new tab)' to text
https://tooldirs.com/product/adhd-readin…	Featured on ToolDirs	new tab	Add '(opens in new tab)' to text
https://www.toolpilot.ai/products/adhd-r…	Featured on ToolPilot	new tab	Add '(opens in new tab)' to text
https://www.startupfa.st/projects/adhd-r…	Powered by Startup Fast	new tab	Add '(opens in new tab)' to text
https://deeplaunch.io/product/adhd-readi…	Featured on DeepLaunch.io	new tab	Add '(opens in new tab)' to text
https://firstlook.tools/product/adhd-rea…	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/adhd-reading	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://toolrain.com/item/adhd-reading	Listed on ToolRain	new tab	Add '(opens in new tab)' to text
https://navfolders.com/item/adhd-reading	NavFolders	new tab	Add '(opens in new tab)' to text
https://seedaud.io/	Seed Audio AI	new tab	Add '(opens in new tab)' to text
https://productshotai.app/	Product Shot AI	new tab	Add '(opens in new tab)' to text
https://m3u8-player.net/	M3U8 Player	new tab	Add '(opens in new tab)' to text
https://www.freeai.run/product/adhd-read…	Featured on FreeAI	new tab	Add '(opens in new tab)' to text
https://tooldirs.com/product/adhd-readin…	Featured on ToolDirs	new tab	Add '(opens in new tab)' to text
https://www.toolpilot.ai/products/adhd-r…	Featured on ToolPilot	new tab	Add '(opens in new tab)' to text
https://www.startupfa.st/projects/adhd-r…	Powered by Startup Fast	new tab	Add '(opens in new tab)' to text
https://deeplaunch.io/product/adhd-readi…	Featured on DeepLaunch.io	new tab	Add '(opens in new tab)' to text
https://firstlook.tools/product/adhd-rea…	Featured on First Look	new tab	Add '(opens in new tab)' to text
https://turbo0.com/item/adhd-reading	Listed on Turbo0	new tab	Add '(opens in new tab)' to text
https://toolrain.com/item/adhd-reading	Listed on ToolRain	new tab	Add '(opens in new tab)' to text
https://navfolders.com/item/adhd-reading	NavFolders	new tab	Add '(opens in new tab)' to text

46 links and buttons have descriptive text

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

https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://chromewebstore.google.com/detail/adhd-reading/dgihjimekmhphkbnnnomcbe…; https://www.freeai.run/product/adhd-reading; https://tooldirs.com/product/adhd-reading; https://www.toolpilot.ai/products/adhd-reading; https://www.startupfa.st/projects/adhd-reading-2448; https://deeplaunch.io/product/adhd-reading; https://firstlook.tools/product/adhd-reading-7326 (+15 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+

Form Input Types

13 form control(s) checked, no type mismatches

PASS

13 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

13 form control(s) checked, no input-semantic issues

PASS

13 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

1 explicit tabindex attribute(s) checked, no anti-patterns

PASS

1 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: ADHD Reading

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name ADHD Reading ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓

Name ADHD Reading Display Mode standalone Theme Color #8b5cf6 Background Color #ffffff Icons 2 icon(s)

A+

PWA Depth

1 PWA signal(s) surfaced

PASS

1 PWA signal(s) surfaced

Manifest has no maskable icon

Android 12+ Adaptive Icons crop non-maskable icons to a circle or squircle -- frequently hiding important parts of the logo. Add at least one icon entry with `"purpose": "maskable"` (or `"any maskable"`) and a maskable-aware design (16% safe-zone padding around the inner mark).

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

Lighthouse Accessibility Audits

Score 93/100 — 3 failing, 28 passed

PASS

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
EMPHASIS MODE `section.card > div#typography-content > div.section-block > span.section-label`

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
blue `div#focus-content > div.color-picker-group > div#focus-color-picker > button.color-btn`
yellow `div#focus-content > div.color-picker-group > div#focus-color-picker > button.color-btn`
green `div#focus-content > div.color-picker-group > div#focus-color-picker > button.color-btn`
pink `div#focus-content > div.color-picker-group > div#focus-color-picker > button.color-btn`
gray `div#focus-content > div.color-picker-group > div#focus-color-picker > button.color-btn`
Bionic Reading `div.grid > div > div.mt-3 > button.h-2`
Semantic Highlight `div.grid > div > div.mt-3 > button.h-2`
Semantic Bold `div.grid > div > div.mt-3 > button.h-2`

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
FreeAI `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
ToolDirs `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
ToolPilot `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
Startup Fast `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
DeepLaunch.io `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
First Look `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
Turbo0 `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
ToolRain `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
NavFolders `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
FreeAI `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
ToolDirs `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
ToolPilot `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
Startup Fast `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
DeepLaunch.io `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
First Look `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
Turbo0 `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
ToolRain `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`
NavFolders `section.footer-backlink-section > div.footer-backlink-grid > div.footer-backlink-row > a.footer-backlink-card`

○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

●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

●ARIA input fields have accessible names

●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 are distinguishable without relying on color.

●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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

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

●Identical links have the same purpose.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements 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

○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

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