Skip to content
https://gamblingtherapy.org

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
69
GRADE
D
FIX
4
REVIEW
5
PASS
4
INFO
0
Checks
13
4 PASS 5 REVIEW 4 FIX
D
Heading Hierarchy
Action
10 headings, 2 skip(s)
FIX
10 headings, 2 skip(s)
Critical::
No H1 heading found
Every page should have one H1 that describes the page content.
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H3 → H5 (missing H4)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H2 Providing online help forpeople experiencing gambling harm
  • H4 A global service offered by Gordon Moody, providing free practical advice and emotional support to anyone affected by gambling. skipped
  • H2 Help for you
  • H2 Their gambling
  • H2 Self Help & Resources
  • H3 Gaming
  • H3 Friends and Family
  • H3 Multilingual Forums
  • H5 Email skipped
  • H5 Social

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

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 ▾

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

D
Web Manifest
Action
Not found
FIX
Not found
Info::
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.

D
Dark Mode Support
Action
No dark mode signals
FIX
No dark mode signals
Info::
No dark mode signals detected
Consider adding CSS with @media (prefers-color-scheme: dark) and <meta name='color-scheme' content='light dark'>.
Info::
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.

D
Navigation UX
Action
2 navigation pattern(s)
FIX
2 navigation pattern(s)
Info::
Search functionality detected
Got: role-search
Info::
Skip navigation link detected
Info::
4 navigation landmark(s) detected
Breadcrumbs
Search role='search' landmark
Skip Link Skip link detected
Labeled Navigation 4 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
3 of 6 testable patterns navigation patterns detected. Strong navigation UX with multiple discovery paths.
B
Alt Text Quality
2 of 85 images have issues
REVIEW
2 of 85 images have issues
Critical::
2 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
72 decorative image(s) correctly marked
Info::
11 image(s) with good alt text
85 images 11 good alt text 72 decorative 2 missing
IssueCount
missing2 image(s)

Images without alt text are invisible to screen readers.

Why this matters

Each image without alt text is a WCAG 1.1.1 failure — invisible to screen-reader users, lost from Google Image Search.

Learn more ▾

WCAG 2.1 Level A requires text alternatives for non-decorative images. Empty alt='' is fine for decorative; meaningful images need descriptive text. Common fixes: CMS audit + bulk add, build-time linter (alt-text-required ESLint rule), CI gate on Lighthouse a11y score.

Source: WCAG 2.1 SC 1.1.1 / WebAIM Million Report

B
Favicon & Branding
4 icon(s) detected
REVIEW
4 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
Apple touch icon present
Info::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✓ Multiple Sizes Present
C
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 Help for you
1.65:1
#000000
on
#32323A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Their gambling
1.65:1
#000000
on
#32323A
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Self Help & Resources
1.65:1
#000000
on
#32323A
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Gaming
1.65:1
#000000
on
#32323A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Friends and Family
1.65:1
#000000
on
#32323A
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Multilingual Forums
1.65:1
#000000
on
#32323A
needs 3.0:1 (large text)
19px · bottom of viewport
title Gambling Therapy - Advice and support fo…
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · top of page (header area)
a Skip to the content
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · top of page (header area)
a Login
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · top of page (header area)
span English
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · top of page (header area)
span Español
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Spanish
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Português
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Portuguese (Portugal)
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Português
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Portuguese (Brazil)
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Italiano
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Italian
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span Français
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · above the fold
span French
1.32:1
#000000
on
#0A2240
needs 4.5:1 (normal text)
16px · mid-page
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h2 Help for you1.65:13.0:1
#000000
#32323A
Fail
h2 Their gambling1.65:13.0:1
#000000
#32323A
Fail
h2 Self Help & Resource…1.65:13.0:1
#000000
#32323A
Fail
h3 Gaming1.65:13.0:1
#000000
#32323A
Fail
h3 Friends and Family1.65:13.0:1
#000000
#32323A
Fail
h3 Multilingual Forums1.65:13.0:1
#000000
#32323A
Fail
title Gambling Therapy - A…1.32:14.5:1
#000000
#0A2240
Fail
a Skip to the content1.32:14.5:1
#000000
#0A2240
Fail
a Login1.32:14.5:1
#000000
#0A2240
Fail
span English1.32:14.5:1
#000000
#0A2240
Fail
span Español1.32:14.5:1
#000000
#0A2240
Fail
span Spanish1.32:14.5:1
#000000
#0A2240
Fail
span Português1.32:14.5:1
#000000
#0A2240
Fail
span Portuguese (Portugal…1.32:14.5:1
#000000
#0A2240
Fail
span Português1.32:14.5:1
#000000
#0A2240
Fail
span Portuguese (Brazil)1.32:14.5:1
#000000
#0A2240
Fail
span Italiano1.32:14.5:1
#000000
#0A2240
Fail
span Italian1.32:14.5:1
#000000
#0A2240
Fail
span Français1.32:14.5:1
#000000
#0A2240
Fail
span French1.32:14.5:1
#000000
#0A2240
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 4 failing, 27 passed
REVIEW
88

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
HELP FOR YOU div.quick-link-wrp > article.card > div.infos > h2.title
THEIR GAMBLING div.quick-link-wrp > article.card > div.infos > h2.title
Problem Gambling Severity Index (PGSI): Ferris, J., & Wynne, H. J. (2001). The … body.home > footer.footer > div.footer__secondary > span.footer__copyright
Canadian Centre on Substance Abuse footer.footer > div.footer__secondary > span.footer__copyright > a
Privacy Policy footer.footer > div.footer__secondary > span.footer__copyright > a
Terms & Conditions footer.footer > div.footer__secondary > span.footer__copyright > a
Site by Clarity Creation footer.footer > div.footer__secondary > span.footer__copyright > a
Up ↑ div.footer__secondary > div.footer__social > a.to-the-top > span.to-the-top-short
Ok div#cookie-notice > div.cookie-notice-container > span#cn-notice-buttons > button#cn-accept-cookie

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
A global service offered by Gordon Moody, providing free practical advice and e… div.swiper-slide > div.header-copy > div.header__subheading > h4
EMAIL div.footer__inner__wrap > div.footer__inner__main > div.border-heading > h5

These are opportunities to improve keyboard navigation in your application.

Names and labels

Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more about the `alt` attribute.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div > div.single-item1 > span.prev > img div > div.single-item1 > span.prev > img
div > div.single-item1 > span.next > img div > div.single-item1 > span.next > img

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn how to make links accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.wpml-ls-statics-shortcode_actions > ul > li.wpml-ls-slot-shortcode_actions > a.js-wpml-ls-item-toggle div.wpml-ls-statics-shortcode_actions > ul > li.wpml-ls-slot-shortcode_actions > a.js-wpml-ls-item-toggle

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.

○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
●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
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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 with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[aria-hidden="true"]` elements do not contain focusable descendents
●Elements use only permitted ARIA attributes
●Document has a `<title>` element
●`<frame>` or `<iframe>` elements have a title
●`<html>` element has a `[lang]` attribute
●`<html>` element has a valid value for its `[lang]` attribute
●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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Skip links are focusable.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Elements with visible text labels have matching accessible names.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○ARIA input fields have accessible names
○ARIA `meter` elements have accessible names
○ARIA `progressbar` elements have accessible names
○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
○`<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
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○Select elements have associated label elements.
○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.
A
Landmark Structure
9 landmarks
PASS
9 landmarks
Info::
<main> landmark present
Info::
4 <nav> landmark(s) found
Warning::
1 of 4 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Info::
Skip navigation link present
Info::
Search landmark present
Page Structure — as a screen reader sees it
BANNER header NAV SEARCH MAIN CONTENTINFO footer

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

A
Form Accessibility
1 of 2 controls have issues
PASS
1 of 2 controls have issues
Critical::
1 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <input type="submit">
Info::
1 control(s) properly labeled
2 controls
1 labeled
0 placeholder only
1 unlabeled
ControlTypeLabelMethod
#search-form-1searchSearch for:none
inputsubmit(none)none

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

<input type="submit">

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

A
404 Error Page
HTTP 404, custom page
PASS
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
Info::
Search form present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Page not found - Gambling Therapy ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓
A+
Print Stylesheet
Print styles detected
PASS
Print styles detected
Info::
External print stylesheet detected
Got: https://gamblingtherapy.org/wp-content/themes/gamblingtherapy/print.css?ver=1.0
Print Stylesheet ✓ Print Optimized
Print stylesheet https://gamblingtherapy.org/wp-content/themes/gamblingtherapy/print.css?ver=1.0 ✓Inline @media print Not detected ✗
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback