Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

14 PASS 5 REVIEW 5 FIX

404 Error Page

Action

Soft 404 detected

FIX

Soft 404 detected

Soft 404: server returns HTTP 200 for non-existent pages

The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.

Got: Status: 200 for /beavercheck-404-test-hyew41

404 Page Quality ✗ Soft 404 (HTTP 200)

Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

Got: https://blacksonblondes.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

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

5 landmarks

REVIEW

5 landmarks

<main> landmark present

2 <nav> landmark(s) found

2 of 2 <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

Heading Hierarchy

3 headings

REVIEW

3 headings

No H1 heading found

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

H2 ACCESS BEYOND THIS PAGE IS RESTRICTED TO ADULTS (18+)* ONLY
H2 TERMS AND CONDITIONS TO ENTER THIS SITE
H2 Watch Anytime, Anywhere

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

Mobile-Readable Font Sizes

Action

88% of visible text renders at >= 12 CSS px (7 below threshold)

REVIEW

88% of visible text renders at >= 12 CSS px (7 below threshold)

7 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: <div> 11.0px ("This site is a site owned and operated b..."); <div> 11.0px ("Please visit"); <a> 11.0px ("Epoch.com"); <div> 11.0px ("authorized sales agents. | For Billing I..."); <a> 11.0px ("SEGPAY.com").

Favicon & Branding

5 icon(s) detected

REVIEW

5 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 Missing

✓ Multiple Sizes Present

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 ACCESS BEYOND THIS PAGE IS RESTRICTED TO…

1.10:1

#000000

#1A0C05

needs 3.0:1 (large text)

24px · top of page (header area)

h2 TERMS AND CONDITIONS TO ENTER THIS SITE

1.07:1

#000000

#0C0C0C

needs 3.0:1 (large text)

24px · above the fold

h2 Watch Anytime, Anywhere

1.12:1

#000000

#141210

needs 3.0:1 (large text)

24px · bottom of viewport

title Blacks on Blondes

1.01:1

#000000

#030202

needs 4.5:1 (normal text)

16px · top of page (header area)

p *The following Website, including all we…

1.09:1

#000000

#180C05

needs 4.5:1 (normal text)

16px · top of page (header area)

a Exit Here

1.01:1

#000000

#030101

needs 4.5:1 (normal text)

16px · top of page (header area)

a Enter

1.00:1

#000000

needs 4.5:1 (normal text)

16px · above the fold

p By clicking ‘enter’ you affirm that …

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · above the fold

p You are at least eighteen (18) years of …

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · above the fold

p You will have read, understood, and agre…

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · above the fold

a terms and conditions

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · above the fold

p and

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · above the fold

a privacy policy

1.10:1

#000000

#101010

needs 4.5:1 (normal text)

16px · above the fold

p You agree that sexually explicit materia…

1.15:1

#000000

#161515

needs 4.5:1 (normal text)

16px · mid-page

p You agree that sexually explicit materia…

1.19:1

#000000

#191818

needs 4.5:1 (normal text)

16px · mid-page

p You will use the material available on t…

1.17:1

#000000

#181718

needs 4.5:1 (normal text)

16px · mid-page

p You will NOT expose minors to the sexual…

1.17:1

#000000

#181718

needs 4.5:1 (normal text)

16px · mid-page

p You will take the appropriate steps in o…

1.16:1

#000000

#171617

needs 4.5:1 (normal text)

16px · mid-page

a Microsoft Family Safety

1.16:1

#000000

#171516

needs 4.5:1 (normal text)

16px · mid-page

a Google Safety Centre

1.15:1

#000000

#161515

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 ACCESS BEYOND THIS P…	1.10:1	3.0:1	#000000	#1A0C05	Fail
h2 TERMS AND CONDITIONS…	1.07:1	3.0:1	#000000	#0C0C0C	Fail
h2 Watch Anytime, Anywh…	1.12:1	3.0:1	#000000	#141210	Fail
title Blacks on Blondes	1.01:1	4.5:1	#000000	#030202	Fail
p *The following Websi…	1.09:1	4.5:1	#000000	#180C05	Fail
a Exit Here	1.01:1	4.5:1	#000000	#030101	Fail
a Enter	1.00:1	4.5:1	#000000	#000000	Fail
p By clicking ‘enter…	1.18:1	4.5:1	#000000	#181818	Fail
p You are at least eig…	1.18:1	4.5:1	#000000	#181818	Fail
p You will have read, …	1.18:1	4.5:1	#000000	#181818	Fail
a terms and conditions	1.18:1	4.5:1	#000000	#181818	Fail
p and	1.18:1	4.5:1	#000000	#181818	Fail
a privacy policy	1.10:1	4.5:1	#000000	#101010	Fail
p You agree that sexua…	1.15:1	4.5:1	#000000	#161515	Fail
p You agree that sexua…	1.19:1	4.5:1	#000000	#191818	Fail
p You will use the mat…	1.17:1	4.5:1	#000000	#181718	Fail
p You will NOT expose …	1.17:1	4.5:1	#000000	#181718	Fail
p You will take the ap…	1.16:1	4.5:1	#000000	#171617	Fail
a Microsoft Family Saf…	1.16:1	4.5:1	#000000	#171516	Fail
a Google Safety Centre	1.15:1	4.5:1	#000000	#161515	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.

A+

Heading Text Quality

1 heading-text-quality issue(s) detected

PASS

1 heading-text-quality issue(s) detected

2 heading(s) are all-uppercase (excluding short acronyms)

Headings rendered in all-uppercase are a styling choice that should be done via CSS (`text-transform: uppercase`), not by typing the text in caps. Capitalized text is read letter-by-letter by some screen readers (e.g., "H-E-L-L-O W-O-R-L-D" instead of "hello world"). It's also a soft signal of CMS-migration artifacts where the original lowercase intent was lost.

Got: 2 all-caps heading(s)

A+

Alt Text Quality

All 53 images OK

PASS

All 53 images OK

53 image(s) with good alt text

53 images 53 good alt text

All images have appropriate alt text.

A+

Form Accessibility

No form controls

PASS

No form controls

No form controls on this page

No form controls found.

Link & Button Quality

81 links, 0 buttons — all OK

PASS

81 links, 0 buttons — all OK

20 link(s) open in new tab without warning

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

Got: https://account.microsoft.com/family/about; https://safety.google/families/; https://support.apple.com/en-ca/HT201304; https://www.qustodio.com/en/; https://www.netnanny.com/; https://www.mobicip.com/; https://www.kaspersky.ca/safe-kids; https://epoch.com/; https://cs.segpay.com; https://form.jotform.com/contentinquiries/report-content-violations (+10 more)

61 link(s) with descriptive text

81 links

0 empty

0 generic text

20 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://account.microsoft.com/family/abo…	Microsoft Family Safety	new tab	Add '(opens in new tab)' to text
https://safety.google/families/	Google Safety Centre	new tab	Add '(opens in new tab)' to text
https://support.apple.com/en-ca/HT201304	Apple Parental Control Measure…	new tab	Add '(opens in new tab)' to text
https://www.qustodio.com/en/	Qustodio	new tab	Add '(opens in new tab)' to text
https://www.netnanny.com/	Net Nanny	new tab	Add '(opens in new tab)' to text
https://www.mobicip.com/	Mobicip	new tab	Add '(opens in new tab)' to text
https://www.kaspersky.ca/safe-kids	Kaspersky Safe Kids	new tab	Add '(opens in new tab)' to text
https://epoch.com/	Epoch.com	new tab	Add '(opens in new tab)' to text
https://cs.segpay.com	SEGPAY.com	new tab	Add '(opens in new tab)' to text
https://form.jotform.com/contentinquirie…	Content Removal	new tab	Add '(opens in new tab)' to text
https://www.asacp.org/?content=validate&…	ASACP	new tab	Add '(opens in new tab)' to text
https://www.rtalabel.org/?content=valida…	RTA	new tab	Add '(opens in new tab)' to text
/en/partners	Partners	new tab	Add '(opens in new tab)' to text
http://www.famedollars.com/	Affiliate Program	new tab	Add '(opens in new tab)' to text
https://www.famesupport.com/	Support	new tab	Add '(opens in new tab)' to text
https://epoch.com/	Epoch.com	new tab	Add '(opens in new tab)' to text
https://cs.segpay.com	SEGPAY.com	new tab	Add '(opens in new tab)' to text
https://form.jotform.com/contentinquirie…	Content Removal	new tab	Add '(opens in new tab)' to text
https://www.asacp.org/?content=validate&…	ASACP	new tab	Add '(opens in new tab)' to text
https://www.rtalabel.org/?content=valida…	RTA	new tab	Add '(opens in new tab)' to text

61 links and buttons have descriptive text

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

https://account.microsoft.com/family/about; https://safety.google/families/; https://support.apple.com/en-ca/HT201304; https://www.qustodio.com/en/; https://www.netnanny.com/; https://www.mobicip.com/; https://www.kaspersky.ca/safe-kids; https://epoch.com/; https://cs.segpay.com; https://form.jotform.com/contentinquiries/report-content-violations (+10 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

No form controls on this page

PASS

No form controls on this page

A+

Form Input Quality

No form controls on this page

PASS

No form controls on this page

A+

Mobile Keyboard & Autofill

No form controls -- mobile keyboard check is N/A

PASS

No form controls -- mobile keyboard check is N/A

No form controls on this page

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

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

PASS

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

No tabindex anti-patterns detected

Iframe Accessibility

1/1 iframe(s) missing title; 0 placeholder(s)

PASS

1/1 iframe(s) missing title; 0 placeholder(s)

WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

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.

A+

Lighthouse Accessibility Audits

Score 98/100 — 1 failing, 23 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.

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
Sign up for exclusive offers & FREE CONTENT! `div.component-EmailGrabber-Wrapper > div.EmailGrabber > div.Raw > h4`

These are opportunities to improve keyboard navigation in your application.

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

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

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

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

●Touch targets have sufficient size and spacing.

●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.

●Document has a main landmark.

○`[accesskey]` values are unique

○`button`, `link`, and `menuitem` elements have accessible names

○Deprecated ARIA roles were not used

○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.

○ARIA input fields have accessible names

○ARIA `meter` elements have accessible names

○ARIA `progressbar` elements have accessible names

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

○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

○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

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

○Identical links have the same purpose.

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

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