Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

8 PASS 2 REVIEW 3 FIX

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: #ffffff

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 ✗

Favicon & Branding

16 icon(s) detected

REVIEW

16 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 Present

✓ Multiple Sizes Present

Color Contrast (Screenshot)

20 text elements analyzed, 0 fail WCAG AA

REVIEW

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

20 pass 19 pass AA only

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Helping you get info…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Cookies on the Gambl…	19.77:1	3.0:1	#000000	#F8F8F8	Pass
h2 Check a licensed gam…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Popular on the websi…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Gambling licence inf…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Help and support	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Find published stati…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Our work	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Action we've taken	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Latest news	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Consultations	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Latest blog posts	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Sign up to e-bulleti…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Feedback	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Complaints and queri…	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 User research	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Gambling Commission	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Information	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 Follow us	4.22:1	3.0:1	#000000	#1B789D	Pass
h2 National Gambling He…	4.22:1	3.0:1	#000000	#1B789D	Pass

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

6 landmarks

PASS

6 landmarks

<main> landmark present

2 <nav> landmark(s) found

1 of 2 <nav> elements are unlabeled

Multiple navigations need aria-label to distinguish them for screen readers.

Skip navigation link present

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

A+

Heading Hierarchy

22 headings

PASS

22 headings

Single H1 present

H2 Cookies on the Gambling Commission website
H1 Helping you get information about gambling in Great Britain and find support when you need it
H2 Check a licensed gambling business
H2 Popular on the website
H2 Gambling licence information, guidance and advice for businesses and individuals
H2 Help and support
H2 Find published statistics and research in our hub
H2 Our work
H3 Who we are and what we do
H2 Action we've taken
H2 Latest news
H2 Consultations
H2 Latest blog posts
H2 Sign up to e-bulletin
H2 Feedback
H2 Complaints and queries
H2 User research
H2 Gambling Commissionwebsites
H2 Information
H2 Follow us
H2 National Gambling Helpline
H3 Newsletter

Alt Text Quality

All 7 images OK

PASS

All 7 images OK

6 image(s) with alt text over 125 characters

1 image(s) with good alt text

7 images 1 good alt text

Issue	Count
too long	6 image(s)

A+

Form Accessibility

All 2 controls labeled

PASS

All 2 controls labeled

2 control(s) properly labeled

2 controls

2 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#search-field	text	Search the website	for/id
#feedback	textarea	Feedback	for/id

Link & Button Quality

91 links, 12 buttons — all OK

PASS

91 links, 12 buttons — all OK

6 link(s) open in new tab without warning

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

Got: https://www.gamcare.org.uk; https://cloud.google.com/terms/service-terms; https://cloud.google.com/terms/data-processing-addendum; https://twitter.com/GamRegGB; https://www.linkedin.com/company/gambling-commission?trk=biz-companies-cym; https://www.youtube.com/channel/UCl0HlHox5LBs4bMS5d491AA

85 link(s) with descriptive text

91 links

0 empty

0 generic text

6 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.gamcare.org.uk	National Gambling Helpline (op…	new tab	Add '(opens in new tab)' to text
https://cloud.google.com/terms/service-t…	Google Cloud Platform Service …	new tab	Add '(opens in new tab)' to text
https://cloud.google.com/terms/data-proc…	Cloud Data Processing Addendum…	new tab	Add '(opens in new tab)' to text
https://twitter.com/GamRegGB	X (formerly Twitter) …	new tab	Add '(opens in new tab)' to text
https://www.linkedin.com/company/gamblin…	LinkedIn (opens in …	new tab	Add '(opens in new tab)' to text
https://www.youtube.com/channel/UCl0HlHo…	YouTube (opens in ne…	new tab	Add '(opens in new tab)' to text

97 links and buttons have descriptive text

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

https://www.gamcare.org.uk; https://cloud.google.com/terms/service-terms; https://cloud.google.com/terms/data-processing-addendum; https://twitter.com/GamRegGB; https://www.linkedin.com/company/gambling-commission?trk=biz-companies-cym; https://www.youtube.com/channel/UCl0HlHox5LBs4bMS5d491AA

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 We can't find that page ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Gambling Commission

192x192 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Gambling Commission ✓192×192 icon ✓512×512 icon ✗Start URL https://www.gamblingcommission.gov.uk ✓Display Mode standalone ✓

Name Gambling Commission Display Mode standalone Theme Color #FFFFFF Background Color #FFFFFF Icons 1 icon(s)

A+

Lighthouse Accessibility Audits

Score 100/100 — 0 failing, 26 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

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

●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

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

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

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