Skip to content
https://sprytal.com

Accessibility

· 24 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
74
GRADE
C
FIX
7
REVIEW
4
PASS
13
INFO
0
Checks
24
13 PASS 4 REVIEW 7 FIX
D
Mobile Keyboard & Autofill
Action
1/1 eligible field(s) missing autocomplete or inputmode
FIX
1/1 eligible field(s) missing autocomplete or inputmode
Warning::
1 field(s) missing recommended autocomplete attribute
WCAG 1.3.5 (Level AA): inputs whose purpose maps to a Common Input Purpose value should declare it via `autocomplete=`. Required for password managers, browser autofill, and assistive tech that customizes inputs (e.g., simplified keyboards). Mobile autofill in particular cuts form-completion time by 30-50% when these are present. Affected purposes: email.
Got: <input type="text" name="email" id="email">
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-zkpskp
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.

D
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'>.
Info::
SVG favicon detected — scales perfectly to any size
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✓ SVG Favicon Present
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Invalid JSON
FIX
Invalid JSON
Warning::
Manifest contains invalid JSON
Manifest at https://sprytal.com/manifest.json contains invalid JSON. Browsers cannot parse it.
Got: https://sprytal.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::
1 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 1 <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
Heading Hierarchy
31 headings, 2 skip(s)
REVIEW
31 headings, 2 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.
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 Websites Built for Growth.
  • H2 Everything You Need for a Better Website
  • H3 Website Design & Development
  • H3 Website Redesign
  • H3 WordPress Development
  • H3 Landing Pages
  • H3 Performance & SEO
  • H3 Website Maintenance & Support
  • H2 Built to Work With You
  • H3 Growth Focused
  • H3 Direct Communication
  • H3 Performance & SEO
  • H3 Clean Code
  • H3 Transparent Process
  • H3 Long-term Partnership
  • H2 A clear path from idea to growth
  • H4 Discover skipped
  • H4 Plan
  • H4 Design
  • H4 Develop
  • H4 Launch
  • H4 Grow
  • H2 Built for Businesses at Every Stage
  • H4 Starting a Business skipped
  • H4 Growing a Business
  • H4 Redesigning Your Website
  • H4 Generating More Leads
  • H2 Questions before we get started?
  • H2 Let's Build Something That Works.
  • H3 Services
  • H3 Newsletter

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 ▾

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

B
Form Accessibility
2 of 3 controls have issues
REVIEW
2 of 3 controls have issues
Critical::
2 control(s) without accessible label
Form controls need a <label>, aria-label, or aria-labelledby for screen readers.
Got: <textarea name="g-recaptcha-response">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">
Info::
1 control(s) properly labeled
3 controls
1 labeled
0 placeholder only
2 unlabeled
ControlTypeLabelMethod
#emailtextEmailaria-label
g-recaptcha-responsetextarea(none)none
#g-recaptcha-response-100000textarea(none)none

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

<textarea name="g-recaptcha-response">; <textarea name="g-recaptcha-response" id="g-recaptcha-response-100000">

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

C
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 Websites
1.28:1
#000000
on
#0A1E43
needs 3.0:1 (large text)
32px · above the fold
h2 Everything You Need for a Better Website
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built to Work With You
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
24px · bottom of viewport
h2 A clear path from idea to growth
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Built for Businesses at Every Stage
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Questions before we get started?
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
24px · bottom of viewport
h2 Let's Build Something That Works.
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
24px · bottom of viewport
h3 Website Design & Development
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Website Redesign
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 WordPress Development
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Landing Pages
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Performance & SEO
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Website Maintenance & Support
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Growth Focused
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Direct Communication
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Performance & SEO
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Clean Code
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Transparent Process
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Long-term Partnership
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
h3 Services
1.29:1
#000000
on
#0B1F44
needs 3.0:1 (large text)
19px · bottom of viewport
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Websites1.28:13.0:1
#000000
#0A1E43
Fail
h2 Everything You Need …1.29:13.0:1
#000000
#0B1F44
Fail
h2 Built to Work With Y…1.29:13.0:1
#000000
#0B1F44
Fail
h2 A clear path from id…1.29:13.0:1
#000000
#0B1F44
Fail
h2 Built for Businesses…1.29:13.0:1
#000000
#0B1F44
Fail
h2 Questions before we …1.29:13.0:1
#000000
#0B1F44
Fail
h2 Let's Build Somethin…1.29:13.0:1
#000000
#0B1F44
Fail
h3 Website Design & Dev…1.29:13.0:1
#000000
#0B1F44
Fail
h3 Website Redesign1.29:13.0:1
#000000
#0B1F44
Fail
h3 WordPress Developmen…1.29:13.0:1
#000000
#0B1F44
Fail
h3 Landing Pages1.29:13.0:1
#000000
#0B1F44
Fail
h3 Performance & SEO1.29:13.0:1
#000000
#0B1F44
Fail
h3 Website Maintenance …1.29:13.0:1
#000000
#0B1F44
Fail
h3 Growth Focused1.29:13.0:1
#000000
#0B1F44
Fail
h3 Direct Communication1.29:13.0:1
#000000
#0B1F44
Fail
h3 Performance & SEO1.29:13.0:1
#000000
#0B1F44
Fail
h3 Clean Code1.29:13.0:1
#000000
#0B1F44
Fail
h3 Transparent Process1.29:13.0:1
#000000
#0B1F44
Fail
h3 Long-term Partnershi…1.29:13.0:1
#000000
#0B1F44
Fail
h3 Services1.29:13.0:1
#000000
#0B1F44
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.

B
Lighthouse Accessibility Audits
Score 88/100 — 3 failing, 19 passed
REVIEW
88

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.sppb-addon-content > form#chronoform-newsletter > div.stackable > button#Send div.sppb-addon-content > form#chronoform-newsletter > div.stackable > button#Send

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
Get a Free Website Review div.hero-grid > div.hero-copy > div.hero-actions > a.primary-btn
© 2026 Sprytal. All rights reserved. Sitemap div#sppb-addon-add_copyright > div.sppb-addon > div.sppb-addon-content > p.footer-bottom-text
2026 div.sppb-addon > div.sppb-addon-content > p.footer-bottom-text > span#sprytalFooterYear
Sitemap div.sppb-addon > div.sppb-addon-content > p.footer-bottom-text > 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
Discover div.container > div.process-track > div.process-step > h4
Starting a Business div.container > div.industries-grid > div.industry-card > h4

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Image elements have `[alt]` attributes
●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.
●Links have a discernible name
●Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
●List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
●Touch targets have sufficient size and spacing.
●Document has a main landmark.
○`[accesskey]` values are unique
○`button`, `link`, and `menuitem` elements have accessible names
○Deprecated ARIA roles were not used
○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
○`[role]`s have all required `[aria-*]` attributes
○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
○`[role]` values are valid
○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.
○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.
A
Landmark Structure
4 landmarks
PASS
4 landmarks
Info::
<main> landmark present
Info::
1 <nav> landmark(s) found
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 Menu" MAIN CONTENTINFO footer

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

A+
Heading Text Quality
All 31 heading(s) have substantive, well-formed text
PASS
All 31 heading(s) have substantive, well-formed text
Info::
Heading text quality is clean -- no placeholder, length, or styling issues
A+
Alt Text Quality
All 2 images OK
PASS
All 2 images OK
Info::
2 image(s) with good alt text
2 images 2 good alt text
All images have appropriate alt text.
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
Info::
Input "email" should use type="email" (currently type="text")
Field name "email" suggests type="email". Wrong type loses mobile keyboard hints, browser autofill, and free format validation. Change to <input type="email">.
A+
Form Input Quality
3 form control(s) checked, no input-semantic issues
PASS
3 form control(s) checked, no input-semantic issues
Info::
All form input semantics look correct
A+
Document Language
Lang attribute set to "en-gb"
PASS
Lang attribute set to "en-gb"
Info::
<html lang="en-gb"> is set and valid
Got: en-gb
A+
Tabindex Anti-Patterns
No explicit tabindex attributes found
PASS
No explicit tabindex attributes found
Info::
No explicit tabindex attributes found
A
Iframe Accessibility
1/2 iframe(s) missing title; 0 placeholder(s)
PASS
1/2 iframe(s) missing title; 0 placeholder(s)
Warning::
<iframe> missing title attribute (src="")
WCAG 4.1.2: iframes need a title attribute so screen readers can announce what's embedded. Without one, the announcement is just "iframe" -- the user has no way to decide whether to enter or skip.
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 116 visible text node(s) render at >= 12 CSS pixels
PASS
All 116 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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback