Skip to content
https://acuityscheduling.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
58
GRADE
D
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
D
Favicon & Branding
Action
3 icon(s) detected
FIX
3 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 Present
✗ Multiple Sizes Missing
D
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Info::
Name present: Acuity Scheduling
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
Info::
Display mode: standalone
PWA Install Criteria Not Installable
Name Acuity Scheduling ✓192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode standalone ✓
Name Acuity Scheduling Display Mode standalone Theme Color #ffffff Background Color #ffffff Icons 1 icon(s)
D
Dark Mode Support
Action
Theme color only
FIX
Theme color only
Info::
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: #1b2737
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 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.

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.
C
Landmark Structure
Action
6 landmarks
REVIEW
6 landmarks
Critical::
No <main> landmark found
Screen reader users cannot quickly navigate to the primary content. Wrap your main content in <main>.
Info::
1 <nav> landmark(s) found
Info::
No banner (header) landmark
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 (missing!) NAV MAIN (missing!) ASIDE "Open Cookie Preferences Modal" CONTENTINFO footer

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

C
Alt Text Quality
Action
10 of 101 images have issues
REVIEW
10 of 101 images have issues
Critical::
10 image(s) missing alt attribute
Images without alt text are invisible to screen readers.
Info::
41 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
101 images 50 good alt text 41 decorative 10 missing
IssueCount
missing10 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

B
404 Error Page
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
Info::
Navigation links present on 404 page
Info::
Homepage link present on 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Not Found ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
A+
Heading Hierarchy
32 headings
PASS
32 headings
Info::
Single H1 present
  • H2 Features
  • H2 Business Tools
  • H2 Solutions for
  • H2 Features
  • H2 Business Tools
  • H2 Solutions for
  • H1 Scheduling software to power exceptional client experiences
  • H2 Everything you need to run your business
  • H2 Book beautifully, 24/7
  • H2 Reduce no-shows
  • H2 Automate your day
  • H2 Boost your earnings
  • H2 Appointment software that adapts to your business
  • H3 Education and Tutoring
  • H3 Financial, Public and Legal Services
  • H3 Pet Care and Grooming
  • H3 Automotive and Maintenance
  • H3 Health and Medical
  • H3 Coaching and Experts
  • H3 Hair, Nails and Beauty Services
  • H3 Spa and Wellness
  • H3 Fitness and Sports Training
  • H2 Connect your calendar and so much more
  • H2 Knowing your name is only the beginning.
  • H2 Ready to take control of your schedule?
  • H3 Get Started
  • H3 Features
  • H3 Solutions
  • H3 Resources
  • H3 Support
  • H4 Compare
  • H3 Compare
A+
Form Accessibility
All 2 controls labeled
PASS
All 2 controls labeled
Info::
2 control(s) properly labeled
2 controls
2 labeled
0 placeholder only
0 unlabeled
ControlTypeLabelMethod
selectselectSelect languagearia-label
selectselectSelect languagearia-label
A+
Color Contrast (Screenshot)
20 text elements analyzed, 0 fail WCAG AA
PASS

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

20 pass
Show all checked elements (20)
ElementRatioRequiredFGBGResult
h1 Scheduling software …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Features18.68:13.0:1
#000000
#FAF1DC
Pass
h2 Business Tools21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Solutions for21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Features21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Business Tools21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Solutions for21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Everything you need …21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Book beautifully, 24…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Reduce no-shows21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Automate your day21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Boost your earnings21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Appointment software…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Connect your calenda…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Knowing your name is…21.00:13.0:1
#000000
#FFFFFF
Pass
h2 Ready to take contro…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Education and Tutori…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Financial, Public an…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Pet Care and Groomin…21.00:13.0:1
#000000
#FFFFFF
Pass
h3 Automotive and Maint…21.00:13.0:1
#000000
#FFFFFF
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.

A
Lighthouse Accessibility Audits
Score 94/100 — 1 failing, 25 passed
PASS
94

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

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.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img
div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img div.large-csp-carousel-frame__slide-wrapper > div.large-csp-carousel-frame__slide > picture.large-csp-carousel__main-content > img

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>`
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●Buttons have an accessible name
●`[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
●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 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
●No element has a `[tabindex]` value greater than 0
●Touch targets have sufficient size and spacing.
●Heading elements appear in a sequentially-descending order
●`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
●Document has a main landmark.
●`<video>` elements contain a `<track>` element with `[kind="captions"]`
●Identical links have the same purpose.
○`[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
○Input buttons have discernible text.
○`<input type="image">` elements have `[alt]` text
○Form elements have associated labels
○The document does not use `<meta http-equiv="refresh">`
○`<object>` elements have alternate text
○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
○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.
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback