Skip to content
https://teachable.com

Accessibility

· 13 checks — Landmarks, headings, alt text, forms, and link quality rolled into one auditable list.
SCORE
53
GRADE
F
FIX
6
REVIEW
3
PASS
4
INFO
0
Checks
13
4 PASS 3 REVIEW 6 FIX
F
Favicon & Branding
Action
2 icon(s) detected
FIX
2 icon(s) detected
Warning::
No favicon.ico at site root
Some older browsers, bookmark tools, and RSS readers look for /favicon.ico. Add one as a fallback.
Info::
HTML icon links detected
Info::
Apple touch icon present
✗ favicon.ico Missing
✓ PNG Icons Present
✓ Apple Touch Present
✗ SVG Favicon Missing
✗ Manifest Icons Missing
✗ Multiple Sizes Missing
F
Web Manifest
Action
Valid manifest
FIX
Valid manifest
Warning::
No name or short_name
Add a name field to identify the app.
Warning::
No 192x192 icon
A 192px icon is required for PWA installation.
PWA Install Criteria Not Installable
Name ✗192×192 icon ✗512×512 icon ✗Start URL ✗Display Mode ✗
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::
6 navigation landmark(s) detected
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 6 <nav> element(s)
Back to Top
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.
B
Landmark Structure
8 landmarks
REVIEW
8 landmarks
Info::
<main> landmark present
Info::
6 <nav> landmark(s) found
Warning::
2 of 6 <nav> elements are unlabeled
Multiple navigations need aria-label to distinguish them for screen readers.
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 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

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 Page Not Found → Teachable ✓Custom Styling ✓Navigation ✓Homepage Link ✓Search Form ✗
B
Lighthouse Accessibility Audits
Score 85/100 — 4 failing, 23 passed
REVIEW
85

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.

ARIA

Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more about roles and required children elements.

Why this matters

Performance issues directly impact user engagement and conversion rates.

Failing Elements
Abagail Pumphrey BOSS PROJECT Read case study Brian Kouhi TOANIMATE Read case s… div.case-study_content-r > div.cs-slider_instance > div.cs-slider_list-wrapper > div#swiper-wrapper-d16c76219d6fdfe7

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

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.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_previous div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_previous
div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_next div.stories_wrp > div.stories-slider_instance > div.stories-slider_navigation > button.stories-slider_next
div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button
div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button div.case-study_content-r > div.cs-slider_instance > div.cs-slider_navigation > button.cs-slider_button

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
nav.nav_component > div.nav_wrapper > div.nav_content-l > a.nav_brand-link nav.nav_component > div.nav_wrapper > div.nav_content-l > a.nav_brand-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > div.footer_social-grid > a.footer_social-link
div.footer_wrp > div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > a.footer_soc2-badge-2-2 div.footer_wrp > div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0dbb-3c6d0d7e > a.footer_soc2-badge-2-2
div.padding-global > div.footer_wrp > div.footer_grid > a#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0de5-3c6d0d7e div.padding-global > div.footer_wrp > div.footer_grid > a#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0de5-3c6d0d7e

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.

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
Explore div.footer_wrp > div.footer_grid > div#w-node-_32e1ee15-dda7-66df-8f95-ff493c6d0d82-3c6d0d7e > h4.footer_title-text

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]`s are contained by their required parent element
●`[role]` values are valid
●`[aria-*]` attributes have valid values
●`[aria-*]` attributes are valid and not misspelled
●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
●`[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.
●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
○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 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
○Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
○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.
○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 Hierarchy
40 headings, 1 skip(s)
PASS
40 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 The future of your education business happens here
  • H2 Teach in every way your students want to learn
  • H2 Why 150,000 industry leaders choose Teachable
  • H2 More time for what matters
  • H2 Made for the modern learner
  • H2 Business growth that lasts
  • H2 Business growth that lasts
  • H2 Made to adapt and evolve
  • H2 Made to adapt and evolve
  • H2 Made for the modern learner
  • H2 Made for the modern learner
  • H2 Made for the modern learner
  • H2 More time for what matters
  • H2 Business growth that lasts
  • H2 Made to adapt ‍and evolve
  • H2 Think bigger and grow at a global scale
  • H2 International tax handling
  • H2 Automatic video subtitles  and translation
  • H2 Think bigger and grow at a global scale
  • H2 International tax handling
  • H2 Automatic video subtitles and and translation
  • H2 Automatic video subtitles
  • H2 and translation
  • H2 AI automations
  • H2 that work with you
  • H2 Teachable success stories write themselves
  • H2 We have plans to help you hit your biggest goals
  • H2 Create before you commit
  • H2 Your stack, supercharged
  • H2 Over 150,000 experts and businesses rely on Teachable
  • H2 Frequently asked questions
  • H3 Can I cancel my account at any time?
  • H3 Can I change my plan once I sign up?
  • H3 Are there any transaction fees?
  • H3 Who uses Teachable?
  • H2 Your expertise has always been your edge. Let’s scale it.
  • H4 Explore skipped
  • H4 Company
  • H4 Support
  • H4 Teachable

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+
Alt Text Quality
All 78 images OK
PASS
All 78 images OK
Info::
78 decorative image(s) correctly marked
78 images 78 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+
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 The future of your e…18.43:13.0:1
#000000
#F0F0F0
Pass
h1 tion business happen…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Teach in every way y…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 nt to learn18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Why 150,000 industry…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 More time18.43:13.0:1
#000000
#F0F0F0
Pass
h2 for what matters18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Made for the modern …18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Business growth18.43:13.0:1
#000000
#F0F0F0
Pass
h2 that lasts18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Business growth that…18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Made to adapt18.43:13.0:1
#000000
#F0F0F0
Pass
h2 evolve18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Made to adapt18.43:13.0:1
#000000
#F0F0F0
Pass
h2 evolve18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Made for the18.43:13.0:1
#000000
#F0F0F0
Pass
h2 modern learner18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Made for the modern …18.43:13.0:1
#000000
#F0F0F0
Pass
h2 Made for the18.43:13.0:1
#000000
#F0F0F0
Pass
h2 modern learner18.43:13.0:1
#000000
#F0F0F0
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.

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback