Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

12 PASS 5 REVIEW 7 FIX

Landmark Structure

Action

No landmarks

FIX

No landmarks

No <main> landmark found

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

No <nav> landmark found

No banner (header) landmark

No contentinfo (footer) landmark

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.

No landmarks detected

Screen reader users have no way to navigate by region.

Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.

Why this matters

Without a <main> landmark, screen-reader users can't skip past the navigation to the page content — every page starts with re-reading the menu.

Learn more ▾

The <main> element marks the page's primary content area. Assistive tech offers a 'jump to main' shortcut — but only if <main> exists. Without it, every page navigation forces re-reading the header. Wrap your primary content in a single <main>.

Source: WAI-ARIA / WCAG 2.4.1

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

Link & Button Quality

Action

12 issue(s) across 104 links and 22 buttons

FIX

12 issue(s) across 104 links and 22 buttons

6 link(s) with no accessible text

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

Got: https://twitter.com/ggbreakingpoint/; https://www.instagram.com/breakingpoint.gg/; https://www.youtube.com/c/BreakingPointGG?sub_confirmation=1/; https://www.twitch.tv/ggbreakingpoint/; https://discord.gg/VHfAqUDB7J; https://www.reddit.com/r/GGBreakingPoint/

2 link(s) open in new tab without warning

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

Got: https://www.gamblingtherapy.org/; https://www.begambleaware.org/

6 button(s) with no accessible text

Icon-only buttons need an aria-label so screen readers can announce them.

Got: button.mantine-focus-auto (#236 on page); button#mantine-osnrzq7bz-target; button.mantine-focus-auto (#249 on page); button.mantine-focus-auto (#256 on page); button.mantine-focus-auto (#287 on page); button.mantine-focus-auto (#1046 on page)

96 link(s) with descriptive text

104 links

6 empty

0 generic text

2 new tab

6 empty buttons

Element	Text	Issue	Suggested Fix
https://twitter.com/ggbreakingpoint/	(empty)	empty	Add link text or aria-label
https://www.instagram.com/breakingpoint.…	(empty)	empty	Add link text or aria-label
https://www.youtube.com/c/BreakingPointG…	(empty)	empty	Add link text or aria-label
https://www.twitch.tv/ggbreakingpoint/	(empty)	empty	Add link text or aria-label
https://discord.gg/VHfAqUDB7J	(empty)	empty	Add link text or aria-label
https://www.reddit.com/r/GGBreakingPoint…	(empty)	empty	Add link text or aria-label
https://www.gamblingtherapy.org/	18+ Bet Responsibly	new tab	Add '(opens in new tab)' to text
https://www.begambleaware.org/	gambleaware	new tab	Add '(opens in new tab)' to text
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label
<button>	(empty)	empty	Add button text or aria-label

112 links and buttons have descriptive text

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

https://twitter.com/ggbreakingpoint/; https://www.instagram.com/breakingpoint.gg/; https://www.youtube.com/c/BreakingPointGG?sub_confirmation=1/; https://www.twitch.tv/ggbreakingpoint/; https://discord.gg/VHfAqUDB7J; https://www.reddit.com/r/GGBreakingPoint/

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.gamblingtherapy.org/; https://www.begambleaware.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

Icon-only buttons need an aria-label so screen readers can announce them.

button.mantine-focus-auto (#236 on page); button#mantine-osnrzq7bz-target; button.mantine-focus-auto (#249 on page); button.mantine-focus-auto (#256 on page); button.mantine-focus-auto (#287 on page); button.mantine-focus-auto (#1046 on page)

Why this matters

Buttons with no accessible text (icon-only, no aria-label) can't be activated by voice control or understood by screen readers.

Source: WCAG 2.1 SC 4.1.2

Tap Target Adequacy

Action

10 tap target(s) too small or too close together

FIX

10 tap target(s) too small or too close together

10 tap target(s) too small or too close to neighbors

WCAG 2.5.5 (Level AAA) requires interactive targets to be at least 44x44 CSS pixels; WCAG 2.5.8 (Level AA, added in 2.2) requires 24x24 minimum. Failing targets cause mis-taps for users with motor impairments, large fingers, or shaky hands -- and are a major bounce-rate driver on mobile commerce flows. Lighthouse measures rendered rects + adjacent-element spacing; the failing list is in the Lighthouse 'tap-targets' audit detail panel.

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

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 ✗

Lighthouse Accessibility Audits

Action

Score 67/100 — 9 failing, 23 passed

FIX

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.app-main-content > div#main-navigation > div.m_8bffd616 > button.mantine-focus-auto `div.app-main-content > div#main-navigation > div.m_8bffd616 > button.mantine-focus-auto`
div.app-main-content > div#main-navigation > div.m_8bffd616 > button.mantine-focus-auto `div.app-main-content > div#main-navigation > div.m_8bffd616 > button.mantine-focus-auto`
div#main-navigation > div.m_8bffd616 > div.m_4081bf90 > button.mantine-focus-auto `div#main-navigation > div.m_8bffd616 > div.m_4081bf90 > button.mantine-focus-auto`
div.m_8bffd616 > div.MatchesHeader-module__tM9Baq__container > div.m_8bffd616 > button.mantine-focus-auto `div.m_8bffd616 > div.MatchesHeader-module__tM9Baq__container > div.m_8bffd616 > button.mantine-focus-auto`
div.m_8bffd616 > div.MatchesHeader-module__tM9Baq__container > div.m_8bffd616 > button.mantine-focus-auto `div.m_8bffd616 > div.MatchesHeader-module__tM9Baq__container > div.m_8bffd616 > button.mantine-focus-auto`

Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
div.m_8bffd616 > div.m_46b77525 > div.m_6c018570 > input#mantine-en29hxcfi `div.m_8bffd616 > div.m_46b77525 > div.m_6c018570 > input#mantine-en29hxcfi`

Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
span > span > span > iframe `span > span > span > iframe`

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.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto `div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto`
div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto `div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto`
div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto `div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto`
div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto `div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto`
div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto `div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto`
div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto `div.m_8bffd616 > div.Footer-module__gM8NQq__links > div.m_4081bf90 > a.mantine-focus-auto`

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.

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
50% `div.m_8bffd616 > div.m_8bffd616 > div.m_8bffd616 > p.mantine-focus-auto`
50% `div.m_8bffd616 > div.m_8bffd616 > div.m_8bffd616 > p.mantine-focus-auto`
18+ Bet Responsibly `div.m_8bffd616 > a > div.m_8bffd616 > p.mantine-focus-auto`
Privacy Policy `div.CookiePopup-module__KQghyG__container > div.m_6d731127 > p.mantine-focus-auto > a.CookiePopup-module__KQghyG__link`
Terms of Service `div.CookiePopup-module__KQghyG__container > div.m_6d731127 > p.mantine-focus-auto > a.CookiePopup-module__KQghyG__link`
Privacy Policy `div.CookiePopup-module__KQghyG__container > div.m_6d731127 > p.mantine-focus-auto > a.CookiePopup-module__KQghyG__link`
Terms of Service `div.CookiePopup-module__KQghyG__container > div.m_6d731127 > p.mantine-focus-auto > a.CookiePopup-module__KQghyG__link`

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
slide item 1 `div.NewsCarousel-module__rjcGsG__carouselContainer > div.carousel-root > div.carousel > ul.control-dots`

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Why this matters

Informational: a Permissions-Policy directive showing feature -> allowed origins.

Source: MDN Permissions-Policy

Failing Elements
head > meta `head > meta`
head > meta `head > meta`

Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
slide item 1 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 2 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 3 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 4 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 5 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 6 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 7 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
slide item 8 `div.carousel-root > div.carousel > ul.control-dots > li.dot`
More News `div.RenderHomePage-module__Q1xadG__gridItem1 > div.m_6d731127 > div.m_e615b15f > a`
More News `div.m_6d731127 > div.m_e615b15f > a > button.mantine-focus-auto`

One main landmark helps screen reader users navigate a web page. Learn more about landmarks.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
html `html`

These items highlight common accessibility best practices.

○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

●Image elements have `[alt]` attributes

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

●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 are distinguishable without relying on color.

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

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

●Deprecated ARIA roles were not used

●The page contains a heading, skip link, or landmark region

●Uses ARIA roles only on compatible elements

●Image elements do not have `[alt]` attributes that are redundant text.

●Identical links have the same purpose.

●Elements with visible text labels have matching accessible names.

○`[accesskey]` values are unique

○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

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

○Heading elements appear in a sequentially-descending order

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

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

Heading Hierarchy

No headings

REVIEW

No headings

No headings found

Headings (H1-H6) create the document outline for screen reader navigation.

No headings found

Headings create the document outline for screen reader navigation.

Headings (H1-H6) create the document outline for screen reader navigation.

Why this matters

A page with zero headings is unnavigable by assistive tech and reads as one undifferentiated wall of text.

Learn more ▾

Screen reader users navigate by jumping between H1-H6 elements. A page with no headings has no skip targets — users have to read every word linearly. Adding a heading hierarchy (one H1, then H2 sections, optional H3 subsections) makes the page skimmable for both AT and human readers.

Source: WCAG 1.3.1 / W3C WAI

Mobile-Readable Font Sizes

99% of visible text renders at >= 12 CSS px (2 below threshold)

REVIEW

99% of visible text renders at >= 12 CSS px (2 below threshold)

2 text node(s) render below 12 CSS pixels on mobile

Mobile browsers default the root font-size to 16 px; text below ~ 12 px (75% of root) is hard to read without zooming. WCAG 1.4.4 (Resize Text) requires the page to support 200% zoom without loss of functionality -- which most layouts handle, but small base text still costs readability and conversion. Audit which selectors set sizes below 12 px (often footers, fine print, table cells) and bump them to 14-16 px or use rem units that scale with user preferences. Examples: <p> 10.0px ("3 of 8"); <p> 10.0px ("May 10, 2026 7:00 PM").

404 Error Page

Action

HTTP 404, custom page

REVIEW

HTTP 404, custom page

Correct 404 status code returned

Got: HTTP 404

Custom styled 404 page

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title 404: This page could not be found. ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗

Favicon & Branding

121 icon(s) detected

REVIEW

121 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)

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

title Breaking Point

1.27:1

#000000

#1F1F1F

needs 4.5:1 (normal text)

16px · top of page (header area)

p News

1.25:1

#000000

#1D1D1D

needs 4.5:1 (normal text)

16px · top of page (header area)

p Matches

1.22:1

#000000

#1B1B1B

needs 4.5:1 (normal text)

16px · top of page (header area)

p Events

1.18:1

#000000

#181818

needs 4.5:1 (normal text)

16px · top of page (header area)

p CDL

1.14:1

#000000

#141414

needs 4.5:1 (normal text)

16px · above the fold

p Stats

1.14:1

#000000

#141414

needs 4.5:1 (normal text)

16px · above the fold

p Fantasy

1.17:1

#000000

#171717

needs 4.5:1 (normal text)

16px · above the fold

p Cards

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

p Games

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

p Black Ops 7

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

span All Matches

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

p ~32 minutes

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

p CDL Major 3 Qualifier

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · above the fold

p Paris Gentle Mates

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

p Miami Heretics

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

p ~2 hours

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

p CDL Major 3 Qualifier

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

p Los Angeles Thieves

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

p G2 Minnesota

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

p ~3 hours

1.35:1

#000000

#242424

needs 4.5:1 (normal text)

16px · mid-page

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
title Breaking Point	1.27:1	4.5:1	#000000	#1F1F1F	Fail
p News	1.25:1	4.5:1	#000000	#1D1D1D	Fail
p Matches	1.22:1	4.5:1	#000000	#1B1B1B	Fail
p Events	1.18:1	4.5:1	#000000	#181818	Fail
p CDL	1.14:1	4.5:1	#000000	#141414	Fail
p Stats	1.14:1	4.5:1	#000000	#141414	Fail
p Fantasy	1.17:1	4.5:1	#000000	#171717	Fail
p Cards	1.35:1	4.5:1	#000000	#242424	Fail
p Games	1.35:1	4.5:1	#000000	#242424	Fail
p Black Ops 7	1.35:1	4.5:1	#000000	#242424	Fail
span All Matches	1.35:1	4.5:1	#000000	#242424	Fail
p ~32 minutes	1.35:1	4.5:1	#000000	#242424	Fail
p CDL Major 3 Qualifie…	1.35:1	4.5:1	#000000	#242424	Fail
p Paris Gentle Mates	1.35:1	4.5:1	#000000	#242424	Fail
p Miami Heretics	1.35:1	4.5:1	#000000	#242424	Fail
p ~2 hours	1.35:1	4.5:1	#000000	#242424	Fail
p CDL Major 3 Qualifie…	1.35:1	4.5:1	#000000	#242424	Fail
p Los Angeles Thieves	1.35:1	4.5:1	#000000	#242424	Fail
p G2 Minnesota	1.35:1	4.5:1	#000000	#242424	Fail
p ~3 hours	1.35:1	4.5:1	#000000	#242424	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.

A+

Heading Text Quality

No headings to evaluate -- check is N/A

PASS

No headings to evaluate -- check is N/A

A+

Alt Text Quality

1 of 130 images have issues

PASS

1 of 130 images have issues

1 image(s) with filename as alt text

129 image(s) with good alt text

130 images 129 good alt text 1 generic

Issue	Count
filename	1 image(s)

Form Accessibility

1 of 1 controls have issues

PASS

1 of 1 controls have issues

1 control(s) without accessible label

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

Got: <input id="mantine-u77cji511">

1 controls

0 labeled

0 placeholder only

1 unlabeled

Control	Type	Label	Method
#mantine-u77cji511	input	(none)	none

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

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+

Form Input Types

1 form control(s) checked, no type mismatches

PASS

1 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

1 form control(s) checked, no input-semantic issues

PASS

1 form control(s) checked, no input-semantic issues

All form input semantics look correct

A+

Mobile Keyboard & Autofill

No autofill-eligible form controls

PASS

No autofill-eligible form controls

No autofill-eligible form controls (no name/email/tel/address fields)

A+

Document Language

Lang attribute set to "en"

PASS

Lang attribute set to "en"

<html lang="en"> is set and valid

Got: en

A+

Tabindex Anti-Patterns

8 explicit tabindex attribute(s) checked, no anti-patterns

PASS

8 explicit tabindex attribute(s) checked, no anti-patterns

No tabindex anti-patterns detected

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

A+

Web Manifest

PWA-ready

PASS

PWA-ready

Meets PWA install criteria

Name present: Breaking Point COD

192x192 icon present

512x512 icon present

Display mode: standalone

PWA Install Criteria ✓ Installable

Name Breaking Point COD ✓192×192 icon ✓512×512 icon ✓Start URL /onboarding ✓Display Mode standalone ✓

Name Breaking Point COD Display Mode standalone Theme Color #7b38ab Background Color #242424 Icons 118 icon(s)

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

2 mobile-depth signal(s) detected

PASS

2 mobile-depth signal(s) detected

Browser-chrome `theme-color` meta tag present

The page sets `<meta name="theme-color" content="...">`, which Android Chrome uses to tint the status bar and iOS Safari uses for the toolbar background. Brand polish that costs nothing and Just Works.

Viewport `viewport-fit=cover` -- supports notched / dynamic-island devices

The viewport meta declares `viewport-fit=cover`, which lets the page draw into the safe-area edges (notch, dynamic island, home indicator) on iPhone X+ devices. Pair with `env(safe-area-inset-*)` CSS to keep critical UI inside the inset rectangle while letting backgrounds extend edge-to-edge.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.