Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

6 PASS 3 REVIEW 4 FIX

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

Theme color only

FIX

Theme color only

Theme-color present but no dark variant

A theme-color is set but no dark-specific variant was found. The browser toolbar may not adapt for dark mode users.

Got: #f5f5f5

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 ModePartial Dark Mode

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

1 navigation pattern(s)

FIX

1 navigation pattern(s)

Back-to-top link detected

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)

3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.

Heading Hierarchy

5 headings, 2 skip(s)

REVIEW

5 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H4 (missing H3)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Heading level skipped: H4 → H6 (missing H5)

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

H1 There is Hope.
H2 START YOUR RECOVERY JOURNEY.
H4 Not sure you have a problem? skipped
H6 More about Gamblers Anonymous skipped
H4 Life-Line Bulletin

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Screen reader users navigate by jumping between headings (H1 → H2 → H3). Skipping (H1 → H3) breaks the sense of hierarchy. Use sequential levels even if you don't like the default styling — restyle with CSS instead. WCAG 1.3.1 (Info and Relationships) treats this as an A failure.

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.

Why this matters

Skipping heading levels breaks the document outline — screen-reader users lose track of section nesting.

Learn more ▾

Source: WCAG 2.1 SC 1.3.1 / W3C WAI

Favicon & Branding

4 icon(s) detected

REVIEW

4 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, 15 fail WCAG AA

REVIEW

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

5 pass 15 fail WCAG AA 1 pass AA only

h2 START YOUR RECOVERY JOURNEY.

2.52:1

#000000

#4E4E4E

needs 3.0:1 (large text)

24px · bottom of viewport

title Home - Gamblers Anonymous

1.61:1

#000000

#1D343C

needs 4.5:1 (normal text)

16px · top of page (header area)

span Make a Contribution

1.61:1

#000000

#1D343C

needs 4.5:1 (normal text)

16px · top of page (header area)

span About Gamblers Anonymous

2.56:1

#000000

#4F4F4F

needs 4.5:1 (normal text)

16px · above the fold

span History

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · above the fold

span Resources

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · above the fold

span Gamblers Anonymous Literature (Digital)

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · above the fold

span Recovery Program

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · above the fold

span Unity Program

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · above the fold

span Questions & Answers

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · mid-page

span 20 Questions

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · mid-page

span Gam-Anon: Help Friends & Family

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · mid-page

span Regional Service Offices and Intergroup …

2.60:1

#000000

#505050

needs 4.5:1 (normal text)

16px · mid-page

span Life-Line Bulletin

2.65:1

#000000

#515151

needs 4.5:1 (normal text)

16px · mid-page

span Shop

2.95:1

#000000

#585858

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h2 START YOUR RECOVERY …	2.52:1	3.0:1	#000000	#4E4E4E	Fail
title Home - Gamblers Anon…	1.61:1	4.5:1	#000000	#1D343C	Fail
span Make a Contribution	1.61:1	4.5:1	#000000	#1D343C	Fail
span Online Bookstore	9.29:1	4.5:1	#000000	#A5AEB1	Pass
span My Account	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span U.S. Hotlines	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span FIND A MEETING	21.00:1	4.5:1	#000000	#FFFFFF	Pass
span Home	6.84:1	4.5:1	#000000	#939393	Pass
span About Gamblers Anony…	2.56:1	4.5:1	#000000	#4F4F4F	Fail
span History	2.60:1	4.5:1	#000000	#505050	Fail
span Resources	2.60:1	4.5:1	#000000	#505050	Fail
span Gamblers Anonymous L…	2.60:1	4.5:1	#000000	#505050	Fail
span Recovery Program	2.60:1	4.5:1	#000000	#505050	Fail
span Unity Program	2.60:1	4.5:1	#000000	#505050	Fail
span Questions & Answers	2.60:1	4.5:1	#000000	#505050	Fail
span 20 Questions	2.60:1	4.5:1	#000000	#505050	Fail
span Gam-Anon: Help Frien…	2.60:1	4.5:1	#000000	#505050	Fail
span Regional Service Off…	2.60:1	4.5:1	#000000	#505050	Fail
span Life-Line Bulletin	2.65:1	4.5:1	#000000	#515151	Fail
span Shop	2.95:1	4.5:1	#000000	#585858	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

4 landmarks

PASS

4 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 3 images OK

PASS

All 3 images OK

3 decorative image(s) correctly marked

3 images 3 decorative

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
s	text	Search	aria-label

Link & Button Quality

1 issue(s) across 41 links and 2 buttons

PASS

1 issue(s) across 41 links and 2 buttons

1 link(s) with generic text

Generic link text like 'click here' doesn't describe the destination.

Got: https://gamblersanonymous.org/recovery-program ("Learn More")

2 link(s) open in new tab without warning

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

Got: https://www.gam-anon.org/; https://www.gam-anon.org/

38 link(s) with descriptive text

41 links

0 empty

1 generic text

2 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://gamblersanonymous.org/	Gamblers-Anon-Header-Logo	img no alt	Add alt attribute to the image
https://www.gam-anon.org/	Gam-Anon: Help Friends & Famil…	new tab	Add '(opens in new tab)' to text
https://gamblersanonymous.org/recovery-p…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Recovery Program
https://www.gam-anon.org/	Gam-Anon: Help Friends & Famil…	new tab	Add '(opens in new tab)' to text

40 links and buttons have descriptive text

Generic link text like 'click here' doesn't describe the destination.

https://gamblersanonymous.org/recovery-program ("Learn More")

Why this matters

Generic anchor text ('click here', 'read more', 'learn more') tells screen readers and search engines nothing about the destination.

Learn more ▾

Out-of-context lists of links read by AT (one navigation pattern) become useless when every link says 'click here'. Use the destination's title or topic as anchor text. Doubles as SEO win — Google passes anchor-text relevance to the destination.

Source: WCAG 2.4.4 / Google Search Central

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

https://www.gam-anon.org/; https://www.gam-anon.org/

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

404 Error Page

HTTP 404, custom page

PASS

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

Navigation links present on 404 page

Homepage link present on 404 page

Search form present on 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Gamblers Anonymous ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Lighthouse Accessibility Audits

Score 94/100 — 3 failing, 22 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
Stay connected with us `div.wpb_text_column > div.wpb_wrapper > p > strong`

These are opportunities to improve the legibility of your content.

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
Not sure you have a problem? `div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > h4`
More about Gamblers Anonymous `div.wpb_wrapper > div.wpb_text_column > div.wpb_wrapper > h6`

These are opportunities to improve keyboard navigation in your application.

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
0 `div.l-subheader-h > div.l-subheader-cell > div.w-cart > a.w-cart-link`

○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

●`[aria-hidden="true"]` elements do not contain focusable descendents

●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

●No element has a `[tabindex]` value greater than 0

●Touch targets have sufficient size and spacing.

●Document has a main landmark.

●Deprecated ARIA roles were not used

●Identical links have the same purpose.

○`[accesskey]` values are unique

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

○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

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

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

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