Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

11 PASS 8 REVIEW 5 FIX

Link & Button Quality

Action

13 issue(s) across 76 links and 7 buttons

FIX

13 issue(s) across 76 links and 7 buttons

5 link(s) with no accessible text

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

Got: https://warriorsuccesssystems.com/; https://warriorsuccesssystems.com/; tel:+19047242100; https://warriorsuccesssystems.com/; https://warriorsuccesssystems.com/

8 link(s) with generic text

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

Got: https://cp.mystudio.io/e/?=9047242100/3207/838615//1784744491 ("Learn More"); /warrior-leadership-framework/ ("Learn More"); /school-growth-playbook/ ("Learn More"); /videos/ ("Learn More"); /gallery/ ("Learn More"); /warrior-fitness-programming-guide/ ("Learn More"); /warrior-insights-blog/ ("Learn More"); /inner-circle-previews/ ("Learn More")

63 link(s) with descriptive text

76 links

5 empty

8 generic text

0 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://warriorsuccesssystems.com/	(empty)	empty	Add link text or aria-label
https://warriorsuccesssystems.com/	(empty)	empty	Add link text or aria-label
tel:+19047242100	(empty)	empty	Add link text or aria-label
https://warriorsuccesssystems.com/	(empty)	empty	Add link text or aria-label
https://warriorsuccesssystems.com/	(empty)	empty	Add link text or aria-label
https://cp.mystudio.io/e/?=9047242100/32…	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: 1784744491
/warrior-leadership-framework/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Warrior Leadership Framework
/school-growth-playbook/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: School Growth Playbook
/videos/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Videos
/gallery/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Gallery
/warrior-fitness-programming-guide/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Warrior Fitness Programming Guide
/warrior-insights-blog/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Warrior Insights Blog
/inner-circle-previews/	Learn More	generic text	Replace with descriptive text
Before: Learn More Suggested: Inner Circle Previews

70 links and buttons have descriptive text

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

https://warriorsuccesssystems.com/; https://warriorsuccesssystems.com/; tel:+19047242100; https://warriorsuccesssystems.com/; https://warriorsuccesssystems.com/

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

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

https://cp.mystudio.io/e/?=9047242100/3207/838615//1784744491 ("Learn More"); /warrior-leadership-framework/ ("Learn More"); /school-growth-playbook/ ("Learn More"); /videos/ ("Learn More"); /gallery/ ("Learn More"); /warrior-fitness-programming-guide/ ("Learn More"); /warrior-insights-blog/ ("Learn More"); /inner-circle-previews/ ("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

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

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 ✗

Navigation UX

Action

No navigation patterns

FIX

No navigation patterns

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

Hamburger Menu

Sticky Navigation Cannot reliably detect (CSS-based)

1 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.

Landmark Structure

3 landmarks

REVIEW

3 landmarks

<main> landmark present

No <nav> landmark 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

Heading Hierarchy

14 headings, 2 skip(s)

REVIEW

14 headings, 2 skip(s)

Single H1 present

Heading level skipped: H2 → H5 (missing H3)

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

Heading level skipped: H2 → H5 (missing H3)

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

H1 Some peopletrain martial arts. Others become Warriors.
H2 The Warrior Legacy
H2 The Warrior System
H2 Join the Warrior Inner Circle
H2 Warrior Certifications
H2 Train at Warrior Headquarters
H2 Stop Guessing.Start Growingwith Warrior.
H2 Become a Warrior Founder
H2 Warrior Resources
H2 Ready to Join the Warrior Movement?
H5 Get Started Today! skipped
H2 Reach Out To Us
H5 Get Started Today! skipped
H2 Ready to grow your school?

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

Alt Text Quality

2 of 4 images have issues

REVIEW

2 of 4 images have issues

2 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

2 image(s) with good alt text

4 images 2 good alt text 2 missing

Issue	Count
missing	2 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

Mobile-Readable Font Sizes

90% of visible text renders at >= 12 CSS px (21 below threshold)

REVIEW

90% of visible text renders at >= 12 CSS px (21 below threshold)

21 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: <span> 11.2px ("Scroll"); <div> 11.2px ("Years Leading"); <div> 11.2px ("Instructors Trained"); <div> 11.2px ("Core Pillars"); <span> 10.4px ("Combat System").

404 Error Page

HTTP 404, custom page

REVIEW

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

404 Page Quality ✓ Custom 404 Page

Status Code HTTP 404 ✓Page Title Page not found - Warrior Martial Arts ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗

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, 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 Some people

1.05:1

#000000

#090807

needs 3.0:1 (large text)

32px · bottom of viewport

h1 train martial arts.

1.05:1

#000000

#090807

needs 3.0:1 (large text)

32px · bottom of viewport

h2 The Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 The Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Join the Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Train at Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Stop Guessing.

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Start Growing

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Become a Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Warrior

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to Join the

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Reach Out To Us

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

h2 Ready to grow your school?

1.05:1

#000000

#090807

needs 3.0:1 (large text)

24px · bottom of viewport

title Welcome To Warrior Success Systems - War…

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a Home

1.00:1

#000000

needs 4.5:1 (normal text)

16px · top of page (header area)

a About

1.05:1

#000000

#090807

needs 4.5:1 (normal text)

16px · top of page (header area)

a The System

1.08:1

#000000

#0E0D0A

needs 4.5:1 (normal text)

16px · top of page (header area)

a Certifications

1.09:1

#000000

#0F0E0A

needs 4.5:1 (normal text)

16px · above the fold

a Events

1.09:1

#000000

#0F0E0A

needs 4.5:1 (normal text)

16px · above the fold

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Some people	1.05:1	3.0:1	#000000	#090807	Fail
h1 train martial arts.	1.05:1	3.0:1	#000000	#090807	Fail
h2 The Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 The Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 Join the Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 Train at Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 Stop Guessing.	1.05:1	3.0:1	#000000	#090807	Fail
h2 Start Growing	1.05:1	3.0:1	#000000	#090807	Fail
h2 Become a Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 Warrior	1.05:1	3.0:1	#000000	#090807	Fail
h2 Ready to Join the	1.05:1	3.0:1	#000000	#090807	Fail
h2 Reach Out To Us	1.05:1	3.0:1	#000000	#090807	Fail
h2 Ready to grow your s…	1.05:1	3.0:1	#000000	#090807	Fail
title Welcome To Warrior S…	1.00:1	4.5:1	#000000	#000000	Fail
a Home	1.00:1	4.5:1	#000000	#000000	Fail
a About	1.05:1	4.5:1	#000000	#090807	Fail
a The System	1.08:1	4.5:1	#000000	#0E0D0A	Fail
a Certifications	1.09:1	4.5:1	#000000	#0F0E0A	Fail
a Events	1.09:1	4.5:1	#000000	#0F0E0A	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.

Lighthouse Accessibility Audits

Score 88/100 — 3 failing, 24 passed

REVIEW

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
SUMMIT `body.home > main#theme-main > section#events > div.events-bg-text`

These are opportunities to improve the legibility of your content.

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.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid `div.portrait-frame > div.portrait-placeholder > div.mt-3 > img.img-fluid`
div.row > div.col-lg-10 > div.lc-block > img.img-fluid `div.row > div.col-lg-10 > div.lc-block > img.img-fluid`

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.fixed-top > div.container-fluid > div.d-flex > a.navbar-brand `div.fixed-top > div.container-fluid > div.d-flex > a.navbar-brand`
div.container-fluid > div.d-flex > div.live-shortcode > a.navbar-brand `div.container-fluid > div.d-flex > div.live-shortcode > a.navbar-brand`
div.container-fluid > div.d-flex > div.live-shortcode > a.btn `div.container-fluid > div.d-flex > div.live-shortcode > a.btn`

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

●`[role]` values are valid

●`[aria-*]` attributes have valid values

●`[aria-*]` attributes are valid and not misspelled

●Buttons have an accessible name

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

●Select elements have associated label elements.

●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

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

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

●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

●ARIA IDs are unique

●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

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

○The document does not use `<meta http-equiv="refresh">`

○`<object>` elements have alternate text

○Skip links are focusable.

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

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

○Elements with visible text labels have matching accessible names.

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

Heading Text Quality

All 14 heading(s) have substantive, well-formed text

PASS

All 14 heading(s) have substantive, well-formed text

Heading text quality is clean -- no placeholder, length, or styling issues

A+

Form Accessibility

All 14 controls labeled

PASS

All 14 controls labeled

14 control(s) properly labeled

14 controls

14 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#input_1_1_3	text	First	for/id
#input_1_1_6	text	Last	for/id
#input_1_3	email	Email(Required)	for/id
#input_1_4	tel	Phone(Required)	for/id
#input_1_5	select	Program	for/id
#input_1_7	textarea	Tell Us About Yourself	for/id
#input_1_6	select	Location	for/id
#input_1_1_3	text	First	for/id
#input_1_1_6	text	Last	for/id
#input_1_3	email	Email(Required)	for/id
#input_1_4	tel	Phone(Required)	for/id
#input_1_5	select	Program	for/id
#input_1_7	textarea	Tell Us About Yourself	for/id
#input_1_6	select	Location	for/id

A+

Form Input Types

14 form control(s) checked, no type mismatches

PASS

14 form control(s) checked, no type mismatches

No input-type mismatches detected

A+

Form Input Quality

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

PASS

14 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-US"

PASS

Lang attribute set to "en-US"

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

Got: en-US

A+

Tabindex Anti-Patterns

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

PASS

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

No tabindex anti-patterns detected

A+

Iframe Accessibility

All 1 iframe(s) have descriptive titles

PASS

All 1 iframe(s) have descriptive titles

All 1 iframe(s) have title attributes

A+

Tap Target Adequacy

All tap targets meet WCAG 2.5.5/2.5.8 sizing

PASS

All tap targets meet WCAG 2.5.5/2.5.8 sizing

All tap targets meet WCAG 2.5.5 (44x44px) sizing

A+

PWA Depth

No PWA depth issues detected

PASS

No PWA depth issues detected

A+

Mobile UX Depth

1 mobile-depth signal(s) detected

PASS

1 mobile-depth signal(s) detected

No `<meta name="theme-color">` -- browser chrome falls back to default

Without `theme-color`, Android Chrome's status bar and iOS Safari's toolbar fall back to a generic gray. Adding a single hex color in `<meta name="theme-color" content="#0066cc">` tints them to your brand color across all mobile browsers.

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