Skip to content
https://calendly.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
59
GRADE
D
FIX
5
REVIEW
3
PASS
5
INFO
0
Checks
13
5 PASS 3 REVIEW 5 FIX
F
Heading Hierarchy
Action
53 headings, 6 skip(s)
FIX
53 headings, 6 skip(s)
Info::
Single H1 present
Warning::
Heading level skipped: H1 → H4 (missing H2)
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.
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: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H4 → H6 (missing H5)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
Warning::
Heading level skipped: H2 → H5 (missing H3)
Skipping heading levels breaks the document outline. Screen readers may interpret missing levels as structural errors.
  • H1 Easy scheduling ahead
  • H4 Share your booking page skipped
  • H4 Reduce no-shows and stay on track
  • H2 Trusted by more than 100,000 of the world’s leading organizations
  • H2 Calendly makes scheduling simple
  • H3 Connect your calendars
  • H3 Add your availability
  • H3 Connect conferencing tools
  • H3 Customize your event types
  • H3 Share your scheduling link
  • H2 Connect Calendly to the tools you already use
  • H4 Google suite skipped
  • H4 Microsoft suite
  • H2 More than a scheduling link
  • H3 Browser extensions
  • H3 Automated workflows
  • H3 Routing forms
  • H3 Round robin & collective events
  • H3 Admin management
  • H2 More than a scheduling link
  • H3 Payment collection
  • H3 Automated workflows
  • H3 Routing forms
  • H3 Round robin & collective events
  • H3 Admin management
  • H2 Pick the perfect plan for your team
  • H4 Free skipped
  • H3 Always free
  • H4 Standard
  • H3 $10
  • H4 Teams
  • H3 $16
  • H4 Enterprise
  • H6 Starts at skipped
  • H3 $15k
  • H4 Free
  • H3 Always free
  • H4 Standard
  • H3 $10
  • H4 Teams
  • H3 $16
  • H4 Enterprise
  • H6 Starts at skipped
  • H3 $15k
  • H2 Discover how businesses grow with Calendly
  • H2 Built to keep your organization secure
  • H2 Power up your scheduling
  • H5 Product skipped
  • H5 Integrations
  • H5 Calendly
  • H5 Resources
  • H5 Company
  • H5 Downloads

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

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

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

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::
3 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 3 <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
6 landmarks
REVIEW
6 landmarks
Info::
<main> landmark present
Info::
3 <nav> landmark(s) found
Warning::
1 of 3 <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
404 Error Page
Action
HTTP 404, custom page
REVIEW
HTTP 404, custom page
Info::
Correct 404 status code returned
Got: HTTP 404
Info::
Custom styled 404 page
404 Page Quality ✓ Custom 404 Page
Status Code HTTP 404 ✓Page Title Calendly.com ✓Custom Styling ✓Navigation ✗Homepage Link ✗Search Form ✗
C
Favicon & Branding
Action
12 icon(s) detected
REVIEW
12 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::
Multiple icon sizes detected
✓ favicon.ico Present
✓ PNG Icons Present
✗ Apple Touch Missing
✗ SVG Favicon Missing
✓ Manifest Icons Present
✓ Multiple Sizes Present
A+
Alt Text Quality
All 58 images OK
PASS
All 58 images OK
Info::
8 decorative image(s) correctly marked
Info::
50 image(s) with good alt text
58 images 50 good alt text 8 decorative
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+
Web Manifest
PWA-ready
PASS
PWA-ready
Info::
Meets PWA install criteria
Info::
Name present: Calendly
Info::
192x192 icon present
Info::
512x512 icon present
Info::
Display mode: standalone
PWA Install Criteria ✓ Installable
Name Calendly ✓192×192 icon ✓512×512 icon ✓Start URL / ✓Display Mode standalone ✓
Name Calendly Display Mode standalone Theme Color #006BFF Background Color #ffffff Icons 10 icon(s)
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 Easy scheduling ahea…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Trusted by more than20.65:13.0:1
#000000
#FDFDFD
Pass
h2 of the world’s lea…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Calendly makes sched…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Connect Calendly to …20.65:13.0:1
#000000
#FDFDFD
Pass
h2 More than a20.65:13.0:1
#000000
#FDFDFD
Pass
h2 scheduling link20.65:13.0:1
#000000
#FDFDFD
Pass
h2 More than a20.65:13.0:1
#000000
#FDFDFD
Pass
h2 scheduling link20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Pick the perfect pla…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Discover how busines…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Built to keep your o…20.65:13.0:1
#000000
#FDFDFD
Pass
h2 Power up your schedu…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Connect your calenda…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Add your availabilit…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Connect conferencing…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Customize your event…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Share your schedulin…20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Browser extensions20.65:13.0:1
#000000
#FDFDFD
Pass
h3 Automated workflows20.65:13.0:1
#000000
#FDFDFD
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 99/100 — 2 failing, 27 passed
PASS
99

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
Share your booking page div.HomepageAnimatedHero__AnimatedImageWrapper-sc-bd3e3dd9-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > h4.Heading-sc-d3a6f8a6-0
Google suite div.Wrapper-sc-a490ef01-0 > a.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > h4.Heading-sc-d3a6f8a6-0
Free div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > h4.text-main-800n
Starts at div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > h6.Heading-sc-d3a6f8a6-0
Product div.Flex-sc-61e9caf1-0 > div.Grid-sc-bcbe7726-0 > div.Flex-sc-61e9caf1-0 > h5.Heading-sc-d3a6f8a6-0

These are opportunities to improve keyboard navigation in your application.

Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
App Store div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > a.ButtonBase-sc-3564e05a-0
Chrome extension div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > a.ButtonBase-sc-3564e05a-0
Edge extension div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > a.ButtonBase-sc-3564e05a-0
Firefox extension div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > a.ButtonBase-sc-3564e05a-0
Safari extension div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > a.ButtonBase-sc-3564e05a-0
Outlook add-in div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > div.Flex-sc-61e9caf1-0 > a.ButtonBase-sc-3564e05a-0
○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.
●`button`, `link`, and `menuitem` elements have accessible names
●ARIA attributes are used as specified for the element's role
●Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
●`[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.
●Document has a main landmark.
●Deprecated ARIA roles were not used
●Identical links have the same purpose.
○`[accesskey]` values are unique
○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
○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.
○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