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

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

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://caniuse.com/manifest.json contains invalid JSON. Browsers cannot parse it.

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

Manifest contains invalid JSON.

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.

Heading Hierarchy

12 headings

REVIEW

12 headings

No H1 heading found

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

H3 Home
H4 Latest features
H4 Most searched features
H4 Test a feature
H4 Did you know?
H4 Third party tools
H4 Browser scores
H4 Other support sites
H3 Can I use...
H3 Support via Patreon
H3 Site links
H2 Legend

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

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

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)

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 Legend

1.82:1

#000000

#403829

needs 3.0:1 (large text)

24px · bottom of viewport

h3 Home

1.73:1

#000000

#3D3525

needs 3.0:1 (large text)

19px · above the fold

h3 Can I use...

1.82:1

#000000

#403829

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Support via Patreon

1.82:1

#000000

#403829

needs 3.0:1 (large text)

19px · bottom of viewport

h3 Site links

1.82:1

#000000

#403829

needs 3.0:1 (large text)

19px · bottom of viewport

title Can I use... Support tables for HTML5, C…

1.82:1

#000000

#403829

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · top of page (header area)

a News

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · top of page (header area)

a Compare

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · top of page (header area)

span browsers

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

a About

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

span March 5, 2026 -

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

a New feature: Lazy loading via attribute …

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

a Can I use

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

label Search

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

span Settings

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · above the fold

a Index of features

1.79:1

#000000

#3F3727

needs 4.5:1 (normal text)

16px · above the fold

button Filter features

1.76:1

#000000

#3E3627

needs 4.5:1 (normal text)

16px · mid-page

h4 Latest features

1.73:1

#000000

#3D3525

needs 3.0:1 (large text)

16px · mid-page

a Lazy loading via attribute for video & a…

1.73:1

#000000

#3D3525

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 Legend	1.82:1	3.0:1	#000000	#403829	Fail
h3 Home	1.73:1	3.0:1	#000000	#3D3525	Fail
h3 Can I use...	1.82:1	3.0:1	#000000	#403829	Fail
h3 Support via Patreon	1.82:1	3.0:1	#000000	#403829	Fail
h3 Site links	1.82:1	3.0:1	#000000	#403829	Fail
title Can I use... Support…	1.82:1	4.5:1	#000000	#403829	Fail
a Home	1.73:1	4.5:1	#000000	#3D3525	Fail
a News	1.73:1	4.5:1	#000000	#3D3525	Fail
a Compare	1.73:1	4.5:1	#000000	#3D3525	Fail
span browsers	1.73:1	4.5:1	#000000	#3D3525	Fail
a About	1.73:1	4.5:1	#000000	#3D3525	Fail
span March 5, 2026 -	1.73:1	4.5:1	#000000	#3D3525	Fail
a New feature: Lazy lo…	1.73:1	4.5:1	#000000	#3D3525	Fail
a Can I use	1.73:1	4.5:1	#000000	#3D3525	Fail
label Search	1.73:1	4.5:1	#000000	#3D3525	Fail
span Settings	1.73:1	4.5:1	#000000	#3D3525	Fail
a Index of features	1.79:1	4.5:1	#000000	#3F3727	Fail
button Filter features	1.76:1	4.5:1	#000000	#3E3627	Fail
h4 Latest features	1.73:1	3.0:1	#000000	#3D3525	Fail
a Lazy loading via att…	1.73:1	4.5:1	#000000	#3D3525	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.

Landmark Structure

5 landmarks

PASS

5 landmarks

<main> landmark present

1 <nav> landmark(s) found

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

A+

Alt Text Quality

All 2 images OK

PASS

All 2 images OK

2 image(s) with good alt text

2 images 2 good alt text

All images have appropriate alt text.

A+

Form Accessibility

All 1 controls labeled

PASS

All 1 controls labeled

1 control(s) properly labeled

1 controls

1 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#feat_search	text	Search	for/id

A+

Link & Button Quality

48 links, 5 buttons — all OK

PASS

48 links, 5 buttons — all OK

1 link(s) open in new tab without warning

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

Got: https://www.browserstack.com?ref=caniuse-source&caniuse_source=brand-asset&ut…

47 link(s) with descriptive text

48 links

0 empty

0 generic text

1 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.browserstack.com?ref=caniuse…	BrowserStack	new tab	Add '(opens in new tab)' to text

52 links and buttons have descriptive text

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

https://www.browserstack.com?ref=caniuse-source&caniuse_source=brand-asset&ut…

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+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 27 passed

PASS

100

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.

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

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

●ARIA attributes are used as specified for the element's role

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

●Heading elements appear in a sequentially-descending order

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Elements with visible text labels have matching accessible names.

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

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

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