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 2 REVIEW 6 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-hhfo3f

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.

Favicon & Branding

Action

1 icon(s) detected

FIX

1 icon(s) detected

favicon.ico present at site root

No apple-touch-icon detected

iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.

✓ favicon.ico Present

✗ PNG Icons Missing

✗ Apple Touch Missing

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✗ Multiple Sizes Missing

Web Manifest

Action

Invalid JSON

FIX

Invalid JSON

Manifest contains invalid JSON

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

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

Link & Button Quality

1 issue(s) across 15 links and 1 buttons

REVIEW

1 issue(s) across 15 links and 1 buttons

1 link(s) with no accessible text

Links without text are announced as raw URLs by screen readers.

Got: a.scroller_anchor (#151 on page)

2 link(s) open in new tab without warning

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

Got: https://www.aaa.com/Suggestions.html; https://www.aaa.com/international

12 link(s) with descriptive text

15 links

1 empty

0 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.aaa.com/Suggestions.html	Comments - link opens in a new…	new tab	Add '(opens in new tab)' to text
https://www.aaa.com/international	International Members - link o…	new tab	Add '(opens in new tab)' to text
	(empty)	empty	Add link text or aria-label

13 links and buttons have descriptive text

Links without text are announced as raw URLs by screen readers.

a.scroller_anchor (#151 on page)

Why this matters

Links with no accessible text (empty <a></a>, image-only no alt, icon-only no aria-label) are unidentifiable to screen readers.

Source: WCAG 2.1 SC 2.4.4

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

https://www.aaa.com/Suggestions.html; https://www.aaa.com/international

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

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

h1 Find Your Local AAA Club

2.06:1

#000000

#414143

needs 3.0:1 (large text)

32px · top of page (header area)

h1 About AAA

1.78:1

#000000

#383928

needs 3.0:1 (large text)

32px · mid-page

h1 Membership

1.10:1

#000000

#10100D

needs 3.0:1 (large text)

32px · mid-page

h1 Savings & Discounts

1.27:1

#000000

#1D1F1D

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

h1 Automotive Services

2.12:1

#000000

#434343

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Home and Auto Insurance

2.12:1

#000000

#434343

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Financial Services

2.12:1

#000000

#434343

needs 3.0:1 (large text)

32px · bottom of viewport

h1 Travel

2.12:1

#000000

#434343

needs 3.0:1 (large text)

32px · bottom of viewport

h2 AAA/CAA is a federation of regional club…

2.02:1

#000000

#3E4043

needs 3.0:1 (large text)

24px · above the fold

h3 Enter your ZIP/postal code to take full …

1.94:1

#000000

#3C3D41

needs 3.0:1 (large text)

19px · above the fold

title AAA | American Automobile Association

2.06:1

#000000

#414144

needs 4.5:1 (normal text)

16px · top of page (header area)

a Skip to main content

1.83:1

#000000

#2F3B43

needs 4.5:1 (normal text)

16px · top of page (header area)

span This is where error messages should go.

1.85:1

#000000

#313C40

needs 4.5:1 (normal text)

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

label Home ZIP/postal code

2.27:1

#000000

#494746

needs 4.5:1 (normal text)

16px · above the fold

1.61:1

#000000

#313036

needs 4.5:1 (normal text)

16px · above the fold

span AAA/CAA Rights Reserved.

1.30:1

#000000

#26201A

needs 4.5:1 (normal text)

16px · above the fold

a Terms of Use

1.30:1

#000000

#262016

needs 4.5:1 (normal text)

16px · above the fold

a Privacy Policy

1.17:1

#000000

#1C1705

needs 4.5:1 (normal text)

16px · above the fold

a Comments

1.44:1

#000000

#2D2A05

needs 4.5:1 (normal text)

16px · above the fold

a International Members

1.24:1

#000000

#162002

needs 4.5:1 (normal text)

16px · mid-page

2 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
h1 Find Your Local AAA …	2.06:1	3.0:1	#000000	#414143	Fail
h1 About AAA	1.78:1	3.0:1	#000000	#383928	Fail
h1 Membership	1.10:1	3.0:1	#000000	#10100D	Fail
h1 Savings & Discounts	1.27:1	3.0:1	#000000	#1D1F1D	Fail
h1 Automotive Services	2.12:1	3.0:1	#000000	#434343	Fail
h1 Home and Auto Insura…	2.12:1	3.0:1	#000000	#434343	Fail
h1 Financial Services	2.12:1	3.0:1	#000000	#434343	Fail
h1 Travel	2.12:1	3.0:1	#000000	#434343	Fail
h2 AAA/CAA is a federat…	2.02:1	3.0:1	#000000	#3E4043	Fail
h3 Enter your ZIP/posta…	1.94:1	3.0:1	#000000	#3C3D41	Fail
title AAA \| American Autom…	2.06:1	4.5:1	#000000	#414144	Fail
a Skip to main content	1.83:1	4.5:1	#000000	#2F3B43	Fail
span This is where error …	1.85:1	4.5:1	#000000	#313C40	Fail
label Home ZIP/postal code	2.27:1	4.5:1	#000000	#494746	Fail
span Copyright ©	1.61:1	4.5:1	#000000	#313036	Fail
span AAA/CAA Rights Reser…	1.30:1	4.5:1	#000000	#26201A	Fail
a Terms of Use	1.30:1	4.5:1	#000000	#262016	Fail
a Privacy Policy	1.17:1	4.5:1	#000000	#1C1705	Fail
a Comments	1.44:1	4.5:1	#000000	#2D2A05	Fail
a International Member…	1.24:1	4.5:1	#000000	#162002	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

3 landmarks

PASS

3 landmarks

<main> landmark present

No <nav> landmark found

Skip navigation link present

Page Structure — as a screen reader sees it

Heading Hierarchy

10 headings

PASS

10 headings

Multiple H1 headings (8 found)

A page should have only one H1. Multiple H1s dilute the document outline.

H1 Find Your Local AAA Club
H2 AAA/CAA is a federation of regional clubs located throughout North America.
H3 Enter your ZIP/postal code to take full advantage of your local club's products and services. AAA/CAA clubs offer insurance, travel services, travel information including maps, guides and information
H1 About AAA duplicate H1
H1 Membership duplicate H1
H1 Savings & Discounts duplicate H1
H1 Automotive Services duplicate H1
H1 Home and Auto Insurance duplicate H1
H1 Financial Services duplicate H1
H1 Travel duplicate H1

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

Source: WCAG 2.4.6 / Google Search Central

A+

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

7 image(s) with good alt text

7 images 7 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
#zipCode	text	Home ZIP/postal code	for/id

A+

Lighthouse Accessibility Audits

Score 96/100 — 1 failing, 24 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. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
AAA membership `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
AAA discounts `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
automotive services `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
credit cards `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
TripTik `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
Trip Canvas `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
International Driving Permits `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`
passport services `div.aaa-article-summary > div.aaa-article-description > div.blk5 > a.aaa-link`

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

●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 have a discernible name

●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

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

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

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