Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

2 PASS 6 REVIEW 5 FIX

Form Accessibility

Action

4 of 8 controls have issues

FIX

4 of 8 controls have issues

2 control(s) without accessible label

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

Got: <input type="button" id="btnSendTop">; <input type="button" id="btnCancel">

2 control(s) rely on placeholder only

Placeholder text disappears on focus and is not a reliable label.

Got: <input type="text">; <input type="password">

4 control(s) properly labeled

8 controls

4 labeled

2 placeholder only

2 unlabeled

Control	Type	Label	Method
#primarysearch	text	Search	for/id
#commentemail	text	Your E-mail:	for/id
#commentsubj	text	Subject:	for/id
#comment	textarea	Describe your issue	for/id
input	password	(Password)	placeholder only
input	text	(Email)	placeholder only
#btnSendTop	button	(none)	none
#btnCancel	button	(none)	none

Form controls need a <label>, aria-label, or aria-labelledby for screen readers.

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.

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

Web Manifest

Action

Not found

FIX

Not found

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.

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

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

3 landmarks

REVIEW

3 landmarks

<main> landmark present

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

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

Heading Hierarchy

1 headings

REVIEW

1 headings

No H1 heading found

Every page should have one H1 that describes the page content.

H2 FOR FASTER ANSWERS, CHECK THESE LINKS BEFORE YOU EMAIL US:

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

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404 Page Not Found ✓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

Color Contrast (Screenshot)

Action

20 text elements analyzed, 3 fail WCAG AA

REVIEW

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

17 pass 3 fail WCAG AA 2 pass AA only

h2 FOR FASTER ANSWERS, CHECK THESE LINKS

1.00:1

#FFFFFF

needs 3.0:1 (large text)

24px · bottom of viewport

h2 YOU EMAIL US:

1.00:1

#FFFFFF

needs 3.0:1 (large text)

24px · bottom of viewport

div Sign In

3.14:1

#000000

#5C5C5C

needs 4.5:1 (normal text)

16px · top of page (header area) · over background image/gradient

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 FOR FASTER ANSWERS, …	1.00:1	3.0:1	#FFFFFF	#FFFFFF	Fail
h2 YOU EMAIL US:	1.00:1	3.0:1	#FFFFFF	#FFFFFF	Fail
title Category - All	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Search	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Sign In	3.14:1	4.5:1	#000000	#5C5C5C	Fail
a Library	6.12:1	4.5:1	#000000	#748DA8	Pass
a Cart	5.15:1	4.5:1	#000000	#4181C3	Pass
a Manage Account	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Profile	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Dashboard	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Support	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Sign Out	21.00:1	4.5:1	#000000	#FFFFFF	Pass
div Sign In	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Email	21.00:1	4.5:1	#000000	#FFFFFF	Pass
label Password	21.00:1	4.5:1	#000000	#FFFFFF	Pass
button Sign In	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Forgot Password	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Join for Free!	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a Home	21.00:1	4.5:1	#000000	#FFFFFF	Pass
a About	21.00:1	4.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.

Lighthouse Accessibility Audits

Score 87/100 — 3 failing, 24 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.

ARIA

When an element doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn how to make command elements more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`
div.container-fluid > div.clearfix > div.shelf-container > span.float-left `div.container-fluid > div.clearfix > div.shelf-container > span.float-left`

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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
form.header-search > span.input-group > span.input-group-append > button.btn `form.header-search > span.input-group > span.input-group-append > button.btn`

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
About `div.mobileMenu > ul.nav > li > a.nav-link`
Join `div.mobileMenu > ul.nav > li > a.nav-link`
Sign In `div.mobileMenu > ul.nav > li > a.nav-link`
Categories `div.d-block > div.left-nav-box > h1 > span`
Helios `div.shelf-book-title > span > span > span`
Sybil Bartel `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Duke's Indecent `div.shelf-book-title > span > span > span`
Purchase `div.shelf-book-title > span > span > span`
Golden Angel `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Correspondent `div.shelf-book-title > span > span > span`
— A Tale of Silent … `span > span > span > span`
Virginia Stone `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Woman from `div.shelf-book-title > span > span > span`
Nowhere `div.shelf-book-title > span > span > span`
Kristen Ashley `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
On the Edge of `div.shelf-book-title > span > span > span`
Shattered: A Moth… `span > span > span > span`
Kimberly Kearns `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Woman from `div.shelf-book-title > span > span > span`
Nowhere `div.shelf-book-title > span > span > span`
Kristen Ashley `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Girl in the Mist `div.shelf-book-title > span > span > span`
Kristen Ashley `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
Too Good to Be True `div.shelf-book-title > span > span > span`
Kristen Ashley `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Complete `div.shelf-book-title > span > span > span`
Cowboy Bikers M… `span > span > span > span`
Esther E. Schmidt `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Birch Creek `div.shelf-book-title > span > span > span`
Ranch Books 1-3 `div.shelf-book-title > span > span > span`
B. E. Baker `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
Edward Modern `div.shelf-book-title > span > span > span`
Richard D. Peters `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
$5.99 `div.shelf-book-bottom > div#price_1980024 > span > span.text-success`
Blood Claws Rising `div.shelf-book-title > span > span > span`
Tales of the Sangu… `span > span > span > span`
Brooke Renee `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
$7.50 `div.shelf-book-bottom > div#price_1995757 > span > span.text-success`
Dead Shifter Walking `div.shelf-book-title > span > span > span`
Kim Bair `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
$0.00 `div.shelf-book-bottom > div#price_458380 > span > span.text-success`
Ghosts of Langley `div.shelf-book-title > span > span > span`
Ryan Thompson `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
$0.00 `div.shelf-book-bottom > div#price_1914040 > span > span.text-success`
The Housemaid `div.shelf-book-title > span > span > span`
Sarah A. Denzil `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
On the Edge of `div.shelf-book-title > span > span > span`
Shattered: A Moth… `span > span > span > span`
Kimberly Kearns `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
Bodies of Water `div.shelf-book-title > span > span > span`
Alex Pendragon `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
A Suitable Brat `div.shelf-book-title > span > span > span`
R. Cooper `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
Lesbian Office `div.shelf-book-title > span > span > span`
Romance Boxed Set `div.shelf-book-title > span > span > span`
Roz Lee `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
The Hook Up `div.shelf-book-title > span > span > span`
Kindle Alexander `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
Serpent Fire: The `div.shelf-book-title > span > span > span`
Science and Mysti… `span > span > span > span`
JOJO PENWOOD `div.float-left > div.shelf-book-top > div.shelf-book-author > a`
CotH 7: Undead `div.shelf-book-title > span > span > span`
Campaign `div.shelf-book-title > span > span > span`
Paul Springsteen `div.float-left > div.shelf-book-top > div.shelf-book-author > a`

These are opportunities to improve the legibility of your content.

○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

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

●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

●All heading elements contain content.

●Identical links have the same purpose.

○`[accesskey]` values are unique

○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

○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

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

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

○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 1 images OK

PASS

All 1 images OK

1 image(s) with good alt text

1 images 1 good alt text

All images have appropriate alt text.

Link & Button Quality

1 issue(s) across 49 links and 4 buttons

PASS

1 issue(s) across 49 links and 4 buttons

1 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.btn (#42 on page)

49 link(s) with descriptive text

49 links

0 empty

0 generic text

0 new tab

1 empty buttons

Element	Text	Issue	Suggested Fix
<button>	(empty)	empty	Add button text or aria-label

52 links and buttons have descriptive text

Icon-only buttons need an aria-label so screen readers can announce them.

button.btn (#42 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

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