Skip to content
https://zayyancoaching.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
78
GRADE
C
FIX
6
REVIEW
2
PASS
16
INFO
0
Checks
24
16 PASS 2 REVIEW 6 FIX
F
404 Error Page
Action
Soft 404 detected
FIX
Soft 404 detected
Critical::
Soft 404: server returns HTTP 200 for non-existent pages
The server returns HTTP 200 for a path that does not exist. Search engines will index these pages, diluting your real content. Configure your server to return a proper 404 status code for missing pages.
Got: Status: 200 for /beavercheck-404-test-3yl0ud
404 Page Quality ✗ Soft 404 (HTTP 200)
Status Code: HTTP 200

The server returned HTTP 200 for a non-existent path. Search engines will index this page as real content. Configure your server to return HTTP 404 for missing pages.

F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Info::
favicon.ico present at site root
Info::
HTML icon links detected
Info::
No apple-touch-icon detected
iOS devices use this when users add your site to their home screen. Add <link rel='apple-touch-icon' sizes='180x180' href='/apple-touch-icon.png'>.
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://zayyancoaching.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://zayyancoaching.com/manifest.json

Manifest contains invalid JSON.

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
Print Stylesheet
Action
No print styles
FIX
No print styles
Info::
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 ✗
F
Navigation UX
Action
No navigation patterns
FIX
No navigation patterns
Info::
2 navigation landmark(s) detected
Info::
Hamburger menu detected (responsive design)
Info::
No breadcrumbs, search, or skip link detected
These navigation aids help users orient themselves and find content efficiently, especially on large sites.
Breadcrumbs
Search
Skip Link
Labeled Navigation 2 <nav> element(s)
Back to Top
Hamburger Menu
Sticky Navigation Cannot reliably detect (CSS-based)
2 of 6 testable patterns navigation patterns detected. Limited navigation support. Consider adding breadcrumbs, search, and skip link.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
2 <nav> landmark(s) found
Warning::
2 of 2 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
Warning::
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
BANNER header NAV 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

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

C
Color Contrast (Screenshot)
Action
20 text elements analyzed, 18 fail WCAG AA
REVIEW

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

2 pass 18 fail WCAG AA 1 pass AA only
h1 Helping Muslims work through the realiti…
2.98:1
#000000
on
#585956
needs 3.0:1 (large text)
32px · above the fold
h2 Is this you?
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
24px · mid-page
h2 How I Can Help You:
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Our Services
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Client Testimonials
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Frequently Asked Questions
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Stop Navigating the Crisis Alone.
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
24px · bottom of viewport · over background image/gradient
h3 A Single Father
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · mid-page
h3 A Young Man
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A Revert to Islam
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport
h3 A Husband
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Single Fathers
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Young Men
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Reverts to Islam
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
h3 Polygyny & Marriage
1.09:1
#000000
on
#0A0E15
needs 3.0:1 (large text)
19px · bottom of viewport · over background image/gradient
title ZayyanCoaching
1.16:1
#000000
on
#12161C
needs 4.5:1 (normal text)
16px · top of page (header area)
a Services
1.16:1
#000000
on
#12161D
needs 4.5:1 (normal text)
16px · top of page (header area)
a Our Policy
1.41:1
#000000
on
#202A1A
needs 4.5:1 (normal text)
16px · top of page (header area)

5 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)
ElementRatioRequiredFGBGResult
h1 Helping Muslims work…2.98:13.0:1
#000000
#585956
Fail
h1 and modern trials.4.42:13.0:1
#000000
#717377
Pass
h2 Is this you?1.09:13.0:1
#000000
#0A0E15
Fail
h2 How I Can Help You:1.09:13.0:1
#000000
#0A0E15
Fail
h2 Our Services1.09:13.0:1
#000000
#0A0E15
Fail
h2 Client Testimonials1.09:13.0:1
#000000
#0A0E15
Fail
h2 Frequently Asked Que…1.09:13.0:1
#000000
#0A0E15
Fail
h2 Stop Navigating the …1.09:13.0:1
#000000
#0A0E15
Fail
h3 A Single Father1.09:13.0:1
#000000
#0A0E15
Fail
h3 A Young Man1.09:13.0:1
#000000
#0A0E15
Fail
h3 A Revert to Islam1.09:13.0:1
#000000
#0A0E15
Fail
h3 A Husband1.09:13.0:1
#000000
#0A0E15
Fail
h3 Single Fathers1.09:13.0:1
#000000
#0A0E15
Fail
h3 Young Men1.09:13.0:1
#000000
#0A0E15
Fail
h3 Reverts to Islam1.09:13.0:1
#000000
#0A0E15
Fail
h3 Polygyny & Marriage1.09:13.0:1
#000000
#0A0E15
Fail
title ZayyanCoaching1.16:14.5:1
#000000
#12161C
Fail
a Services1.16:14.5:1
#000000
#12161D
Fail
a Support Our Work8.02:14.5:1
#000000
#A1A09B
Pass
a Our Policy1.41:14.5:1
#000000
#202A1A
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 Hierarchy
18 headings, 1 skip(s)
PASS
18 headings, 1 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H2 → H4 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Helping Muslims work through the realities of divorce, custody, marriage, polygyny, and modern trials.
  • H2 Is this you?
  • H3 A Single Father
  • H3 A Young Man
  • H3 A Revert to Islam
  • H3 A Husband
  • H2 How I Can Help You:
  • H2 Our Services
  • H3 Single Fathers
  • H3 Young Men
  • H3 Reverts to Islam
  • H3 Polygyny & Marriage
  • H2 Client Testimonials
  • H2 Frequently Asked Questions
  • H2 Stop Navigating the Crisis Alone.
  • H4 Services skipped
  • H4 Contact
  • H4 Socials

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

A+
Heading Text Quality
All 18 heading(s) have substantive, well-formed text
PASS
All 18 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 8 images OK
PASS
All 8 images OK
Info::
8 image(s) with good alt text
8 images 8 good alt text
All images have appropriate alt text.
A+
Form Accessibility
No form controls
PASS
No form controls
Info::
No form controls on this page
No form controls found.
A+
Form Input Types
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Form Input Quality
No form controls on this page
PASS
No form controls on this page
Info::
No form controls on this page
A+
Mobile Keyboard & Autofill
No form controls -- mobile keyboard check is N/A
PASS
No form controls -- mobile keyboard check is N/A
Info::
No form controls on this page
A+
Document Language
Lang attribute set to "en"
PASS
Lang attribute set to "en"
Info::
<html lang="en"> is set and valid
Got: en
A+
Tabindex Anti-Patterns
3 explicit tabindex attribute(s) checked, no anti-patterns
PASS
3 explicit tabindex attribute(s) checked, no anti-patterns
Info::
No tabindex anti-patterns detected
A+
Iframe Accessibility
No iframes on this page
PASS
No iframes on this page
Info::
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
Info::
All tap targets meet WCAG 2.5.5 (44x44px) sizing
A+
Mobile-Readable Font Sizes
All 91 visible text node(s) render at >= 12 CSS pixels
PASS
All 91 visible text node(s) render at >= 12 CSS pixels
Info::
All text uses legible mobile font sizes (>= 12 CSS px)
A+
PWA Depth
No PWA depth issues detected
PASS
No PWA depth issues detected
Info::
No PWA depth issues detected
A+
Mobile UX Depth
1 mobile-depth signal(s) detected
PASS
1 mobile-depth signal(s) detected
Info::
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.
A+
Lighthouse Accessibility Audits
Score 98/100 — 1 failing, 21 passed
PASS
98

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.

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
Services div.mx-auto > div.grid > div.flex > h4.text-lg

These are opportunities to improve keyboard navigation in your application.

○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
●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 have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
●Deprecated ARIA roles were not used
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
○`[aria-hidden="true"]` elements do not contain focusable descendents
○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
○Links are distinguishable without relying on color.
○List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
○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.
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback