Accessibility

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

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Checks

13 PASS 3 REVIEW 8 FIX

Landmark Structure

Action

5 landmarks

FIX

5 landmarks

No <main> landmark found

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

3 <nav> landmark(s) found

3 of 3 <nav> elements are unlabeled

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

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.

Page Structure — as a screen reader sees it

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

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

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

Action

34 headings, 3 skip(s)

FIX

34 headings, 3 skip(s)

Multiple H1 headings (13 found)

A page should have only one H1. Multiple H1s dilute the document outline.

Heading level skipped: H1 → H3 (missing H2)

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

Heading level skipped: H1 → H4 (missing H2)

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

Heading level skipped: H2 → H4 (missing H3)

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

H1 Welcome To Inclusion Health
H1 Our Occupational Therapy Services duplicate H1
H3 Pediatric Occupational Therapy skipped
H3 Occupational Therapy For Seniors
H3 Occupational Therapy For Adults
H1 Specialized Occupational Therapy Services duplicate H1
H4 Sensory Profile skipped
H4 Toilet Training Programme
H4 Handwriting Programme
H4 Return to Work and Case Management
H4 Hospital Discharge and Home Health
H4 Home Modification Assessments
H4 Ergonomics
H4 Wheelchair Seating and Positioning
H2 Frequently Asked Questions
H1 What is occupational therapy? duplicate H1
H1 What age groups do you provide occupational therapy services for? duplicate H1
H1 How can occupational therapy benefit children? duplicate H1
H1 Can occupational therapy help seniors with aging-related challenges? duplicate H1
H1 What services do you provide for adults? duplicate H1
H1 How can I schedule an appointment or learn more about your services? duplicate H1
H1 What funding sources do you accept? duplicate H1
H1 How long are the occupational therapy sessions? duplicate H1
H1 Is occupational therapy covered by insurance? duplicate H1
H1 Where are your locations? duplicate H1
H2 Get in Touch With Us
H2 Take the first step towards improved health, independence, and well-being.
H4 Contact Inclusion Health today and let us help you unlock your full potential. skipped
H5 Sitemap
H5 Legal
H5 Contact
H5 Hours
H5 Locations
H5 Social Media

A page should have only one H1. Multiple H1s dilute the document outline.

Why this matters

Multiple H1s blur the page's primary topic — screen-reader users and Google both prefer one H1.

Learn more ▾

HTML5's outline algorithm technically allows multiple H1s within sectioning content, but no browser implements it. In practice: one H1 per page. Use H2-H6 for subsections.

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 ▾

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

Action

3 of 20 images have issues

FIX

3 of 20 images have issues

3 image(s) missing alt attribute

Images without alt text are invisible to screen readers.

3 image-in-link without alt text

An image inside a link with no alt creates an empty link.

16 decorative image(s) correctly marked

1 image(s) with good alt text

20 images 1 good alt text 16 decorative 3 missing

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

An image inside a link with no alt creates an empty link.

Why this matters

Image-only links with no alt create empty links — screen-reader users hear 'link' with no destination context.

Learn more ▾

An <a><img></a> with no img alt is the worst-case for accessibility: AT announces the link but can't describe where it goes. Either add alt to the image OR add aria-label to the link.

Source: WCAG 2.1 SC 2.4.4

Link & Button Quality

Action

11 issue(s) across 52 links and 2 buttons

FIX

11 issue(s) across 52 links and 2 buttons

4 link(s) with no accessible text

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

Got: https://inclusionhealth.ca/; https://inclusionhealth.ca/at-home-therapies/; https://inclusionhealth.ca/functional-capacity-evals/; https://inclusionhealth.ca/stroke-rehab-ot/

7 link(s) with generic text

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

Got: https://inclusionhealth.ca/our-services/pediatric-occupational-therapy/ ("LEARN MORE"); https://inclusionhealth.ca/our-services/occupational-therapy-for-seniors/ ("LEARN MORE"); https://inclusionhealth.ca/our-services/occupational-therapy-for-adults/ ("LEARN MORE"); https://inclusionhealth.ca/at-home-therapies/ ("Read More"); https://inclusionhealth.ca/functional-capacity-evals/ ("Read More"); https://inclusionhealth.ca/stroke-rehab-ot/ ("Read More"); https://inclusionhealth.ca/privacy-policy/ ("Learn more")

10 link(s) open in new tab without warning

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

Got: https://www.facebook.com/profile.php?id=61561567422596; https://www.instagram.com/inclusion_health; https://twitter.com; https://www.facebook.com/profile.php?id=61561567422596; https://www.instagram.com/inclusion_health; https://twitter.com; https://www.facebook.com/profile.php?id=61561567422596; https://www.instagram.com/inclusion_health; https://twitter.com; https://designfoundry.agency/

31 link(s) with descriptive text

52 links

4 empty

7 generic text

10 new tab

0 empty buttons

Element	Text	Issue	Suggested Fix
https://www.facebook.com/profile.php?id=…	Visit our Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/inclusion_heal…	Visit our Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com	Visit our Twitter	new tab	Add '(opens in new tab)' to text
https://www.facebook.com/profile.php?id=…	Visit our Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/inclusion_heal…	Visit our Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com	Visit our Twitter	new tab	Add '(opens in new tab)' to text
https://inclusionhealth.ca/	(empty)	empty	Add link text or aria-label
https://inclusionhealth.ca/our-services/…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Pediatric Occupational Therapy
https://inclusionhealth.ca/our-services/…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Occupational Therapy For Seniors
https://inclusionhealth.ca/our-services/…	LEARN MORE	generic text	Replace with descriptive text
Before: LEARN MORE Suggested: Occupational Therapy For Adults
https://inclusionhealth.ca/at-home-thera…	(empty)	empty	Add link text or aria-label
https://inclusionhealth.ca/at-home-thera…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: At Home Therapies
https://inclusionhealth.ca/functional-ca…	(empty)	empty	Add link text or aria-label
https://inclusionhealth.ca/functional-ca…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Functional Capacity Evals
https://inclusionhealth.ca/stroke-rehab-…	(empty)	empty	Add link text or aria-label
https://inclusionhealth.ca/stroke-rehab-…	Read More	generic text	Replace with descriptive text
Before: Read More Suggested: Stroke Rehab Ot
https://www.facebook.com/profile.php?id=…	Visit our Facebook	new tab	Add '(opens in new tab)' to text
https://www.instagram.com/inclusion_heal…	Visit our Instagram	new tab	Add '(opens in new tab)' to text
https://twitter.com	Visit our Twitter	new tab	Add '(opens in new tab)' to text
https://designfoundry.agency/	Design Foundry	new tab	Add '(opens in new tab)' to text
https://inclusionhealth.ca/privacy-polic…	Learn more	generic text	Replace with descriptive text
Before: Learn more Suggested: Privacy Policy

33 links and buttons have descriptive text

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

https://inclusionhealth.ca/; https://inclusionhealth.ca/at-home-therapies/; https://inclusionhealth.ca/functional-capacity-evals/; https://inclusionhealth.ca/stroke-rehab-ot/

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://inclusionhealth.ca/our-services/pediatric-occupational-therapy/ ("LEARN MORE"); https://inclusionhealth.ca/our-services/occupational-therapy-for-seniors/ ("LEARN MORE"); https://inclusionhealth.ca/our-services/occupational-therapy-for-adults/ ("LEARN MORE"); https://inclusionhealth.ca/at-home-therapies/ ("Read More"); https://inclusionhealth.ca/functional-capacity-evals/ ("Read More"); https://inclusionhealth.ca/stroke-rehab-ot/ ("Read More"); https://inclusionhealth.ca/privacy-policy/ ("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.facebook.com/profile.php?id=61561567422596; https://www.instagram.com/inclusion_health; https://twitter.com; https://www.facebook.com/profile.php?id=61561567422596; https://www.instagram.com/inclusion_health; https://twitter.com; https://www.facebook.com/profile.php?id=61561567422596; https://www.instagram.com/inclusion_health; https://twitter.com; https://designfoundry.agency/

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

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

3 navigation landmark(s) detected

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 3 <nav> element(s)

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.

Favicon & Branding

Action

3 icon(s) detected

REVIEW

3 icon(s) detected

No favicon.ico at site root

Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.

HTML icon links detected

Apple touch icon present

Multiple icon sizes detected

✗ favicon.ico Missing

✓ PNG Icons Present

✓ Apple Touch Present

✗ SVG Favicon Missing

✗ Manifest Icons Missing

✓ Multiple Sizes Present

Color Contrast (Screenshot)

Action

20 text elements analyzed, 2 fail WCAG AA

REVIEW

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

18 pass 2 fail WCAG AA 16 pass AA only

h1 Welcome To Inclusion Health

2.85:1

#000000

#535279

needs 3.0:1 (large text)

32px · mid-page · over background image/gradient

h1 Our Occupational Therapy Services

2.47:1

#000000

#3B4B79

needs 3.0:1 (large text)

32px · mid-page

1 contrast failures on background images/gradients

These failures are invisible to CSS-based accessibility tools like Lighthouse. The text may be fine on a solid background, but fails when rendered over an image or gradient.

Show all checked elements (20)

Element	Ratio	Required	FG	BG	Result
h1 Welcome To Inclusion…	2.85:1	3.0:1	#000000	#535279	Fail
h1 Our Occupational The…	2.47:1	3.0:1	#000000	#3B4B79	Fail
h1 Specialized Occupati…	4.02:1	3.0:1	#000000	#706980	Pass
h1 What is occupational…	4.02:1	3.0:1	#000000	#706980	Pass
h1 What age groups do y…	4.02:1	3.0:1	#000000	#706980	Pass
h1 How can occupational…	4.02:1	3.0:1	#000000	#706980	Pass
h1 Can occupational the…	4.02:1	3.0:1	#000000	#706980	Pass
h1 What services do you…	4.02:1	3.0:1	#000000	#706980	Pass
h1 How can I schedule a…	4.02:1	3.0:1	#000000	#706980	Pass
h1 What funding sources…	4.02:1	3.0:1	#000000	#706980	Pass
h1 How long are the occ…	4.02:1	3.0:1	#000000	#706980	Pass
h1 Is occupational ther…	4.02:1	3.0:1	#000000	#706980	Pass
h1 Where are your locat…	4.02:1	3.0:1	#000000	#706980	Pass
h2 Frequently Asked Que…	4.02:1	3.0:1	#000000	#706980	Pass
h2 Get in Touch With Us	4.02:1	3.0:1	#000000	#706980	Pass
h2 Take the first step …	4.02:1	3.0:1	#000000	#706980	Pass
h3 Pediatric Occupation…	5.08:1	3.0:1	#000000	#767B9B	Pass
h3 Occupational Therapy…	4.02:1	3.0:1	#000000	#706980	Pass
h3 Occupational Therapy…	4.02:1	3.0:1	#000000	#706980	Pass
title Occupational Therapy…	19.95:1	4.5:1	#000000	#F9F9F9	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.

Lighthouse Accessibility Audits

Score 84/100 — 5 failing, 21 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
Make A Referral `div#_header_row-3-161 > div.oxy-header-container > div#_header_right-6-161 > a#link_button-28-161`
CONTACT US `div.ct-section-inner-wrap > div#new_columns-8-55 > div#div_block-10-55 > a#link_button-298-7`
Design Foundry `section#section-3-48 > div.ct-section-inner-wrap > div#text_block-5-48 > a`

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
Pediatric Occupational Therapy `div.ct-section-inner-wrap > div#new_columns-306-7 > div#div_block-309-7 > h3#headline-311-7`
Sensory Profile `div.ct-section-inner-wrap > div#new_columns-323-7 > div#div_block-326-7 > h4#headline-328-7`
Contact Inclusion Health today and let us help you unlock your full potential. `div.ct-section-inner-wrap > div#new_columns-8-55 > div#div_block-10-55 > h4#headline-17-55`

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.oxy-posts > div.oxy-post > a > img.oxy-post-image `div.oxy-posts > div.oxy-post > a > img.oxy-post-image`
div.oxy-posts > div.oxy-post > a > img.oxy-post-image `div.oxy-posts > div.oxy-post > a > img.oxy-post-image`
div.oxy-posts > div.oxy-post > a > img.oxy-post-image `div.oxy-posts > div.oxy-post > a > img.oxy-post-image`

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#_header_row-7-161 > div.oxy-header-container > div#_header_left-8-161 > a#link-23-161 `div#_header_row-7-161 > div.oxy-header-container > div#_header_left-8-161 > a#link-23-161`
div#_posts_grid-373-7 > div.oxy-posts > div.oxy-post > a `div#_posts_grid-373-7 > div.oxy-posts > div.oxy-post > a`
div#_posts_grid-373-7 > div.oxy-posts > div.oxy-post > a `div#_posts_grid-373-7 > div.oxy-posts > div.oxy-post > a`
div#_posts_grid-373-7 > div.oxy-posts > div.oxy-post > a `div#_posts_grid-373-7 > div.oxy-posts > div.oxy-post > a`

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.

Best practices

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

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

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

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

●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

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

○`<object>` elements have alternate text

○Select elements have associated label elements.

○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 34 heading(s) have substantive, well-formed text

PASS

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

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

A+

Form Accessibility

All 7 controls labeled

PASS

All 7 controls labeled

7 control(s) properly labeled

7 controls

7 labeled

0 placeholder only

0 unlabeled

Control	Type	Label	Method
#wpforms-59-field_0	text	First	for/id
#wpforms-59-field_0-last	text	Last	for/id
#wpforms-59-field_6	text	Phone Number *	for/id
#wpforms-59-field_1	email	Email *	for/id
#wpforms-59-field_3	text	Which City Are You Located In	for/id
#wpforms-59-field_2	textarea	Comment or Message	for/id
#wpforms-59-field_4_1	checkbox	By proceeding, you agree to our Terms of Service & Privacy Policy.	for/id

A+

Form Input Types

1 input(s) using type=text where a specific type would help

PASS

1 input(s) using type=text where a specific type would help

Input "wpforms[fields][6]" should use type="tel" (currently type="text")

Field name "wpforms[fields][6]" suggests type="tel". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="tel">.

A+

Form Input Quality

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

PASS

7 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-CA"

PASS

Lang attribute set to "en-CA"

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

Got: en-CA

A+

Tabindex Anti-Patterns

No explicit tabindex attributes found

PASS

No explicit tabindex attributes found

A+

Iframe Accessibility

No iframes on this page

PASS

No iframes on this page

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+

Mobile-Readable Font Sizes

All 102 visible text node(s) render at >= 12 CSS pixels

PASS

All 102 visible text node(s) render at >= 12 CSS pixels

All text uses legible mobile font sizes (>= 12 CSS px)

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 instagram ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✓

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.