WCAG 2.1 for Kajabi Sites
WCAG 2.1 became a W3C Recommendation in June 2018. It added criteria for mobile, low vision and cognitive accessibility to WCAG 2.0, and it is the standard named in the US Department of Justice rule for state and local government websites, in EN 301 549 V3.2.1 and in most accessibility settlements.
This checker runs the free scan with the WCAG 2.1 AA preset, so the results match the standard your contract, policy or regulator is most likely to name for a Kajabi site.
On Kajabi, WCAG 2.1 issues often come from layout settings: sections with fixed heights that cut off text when spacing increases, pale button borders, and hover effects that hide content from keyboard users.
| Published | June 5, 2018 |
|---|---|
| Success criteria at Level A and AA | 50 |
| Added to WCAG 2.0 at Level A and AA | 12 |
| Referenced by | ADA Title II rule, EN 301 549 V3.2.1 |
| Automated rules in this scan | 62 |
Who Should Run the Kajabi WCAG 2.1 Checker
- Kajabi site owners whose contracts or policies name WCAG 2.1 AA.
- State and local government bodies, under the ADA Title II rule.
- Businesses responding to an ADA demand letter, which usually cites WCAG 2.1 AA.
- Public sector bodies in the EU, under the Web Accessibility Directive.
WCAG 2.1 Criteria That Often Fail on Kajabi
-
1.3.5 Identify Input Purpose
Form fields that collect personal data, such as name, email and address, need the right autocomplete attribute.
-
1.4.10 Reflow
Content must reflow at 320 CSS pixels wide, the same as 400% zoom, without scrolling in two directions.
-
1.4.11 Non-text Contrast
Buttons, form borders, icons and focus indicators need a contrast ratio of at least 3:1.
-
1.4.12 Text Spacing
Text must stay readable when users increase line, paragraph, letter and word spacing.
-
1.4.13 Content on Hover or Focus
Tooltips and menus that appear on hover or focus must be dismissible, hoverable and stay visible.
-
4.1.3 Status Messages
Messages such as “added to cart” or form errors must be announced to screen readers without moving focus.
Where Kajabi Sites Usually Fail WCAG 2.1
These problems come up again and again on Kajabi sites, and each one fails WCAG 2.1. The Kajabi accessibility checker explains how to fix them in Kajabi.
- Video lessons without captions. Lesson videos, sales-page videos and webinar replays need captions and, ideally, a transcript, or they cannot be used by anyone who is deaf or hard of hearing.
- Inaccessible PDF downloads. Workbooks, checklists and slide handouts exported as scanned or untagged PDFs cannot be read by screen readers. Try our free PDF accessibility checker on yours.
- Opt-in forms and pop-ups. Email capture forms with placeholder-only fields, countdown timers and exit-intent pop-ups that grab attention but not focus.
- Contrast on sales pages. Light text over photos, colored buttons with white text and fine-print disclaimers in light gray often fail the contrast minimum.
- Image-heavy sections. Testimonial screenshots, offer graphics and headlines placed as images contain information that is invisible to screen reader users without alt text.
Worried about ADA claims as well? The Kajabi ADA compliance checker covers the Kajabi risks behind most complaints.
What to Test by Hand on Kajabi
Automated testing finds many, but not all, WCAG 2.1 failures. Check these yourself after the scan:
- Zoom to 400% and check nothing is cut off or needs scrolling in two directions (1.4.10).
- Apply increased text spacing with a bookmarklet and check text is still readable (1.4.12).
- Open hover menus and tooltips and check you can dismiss them with Escape (1.4.13).
- Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.
Related Guides
Kajabi WCAG 2.1 Checker: Frequently Asked Questions
Does my Kajabi site need to meet WCAG 2.1?
WCAG 2.1 AA is the standard most often cited in ADA claims and settlements, required for state and local governments under ADA Title II and used by EN 301 549 V3.2.1. For most Kajabi sites it is the practical minimum.
What is the difference between WCAG 2.1 and 2.2 for Kajabi?
WCAG 2.2 adds six Level A and AA criteria, such as target size, and removes 4.1.1 Parsing. Meeting 2.2 AA also meets 2.1 AA, so use the WCAG 2.2 checker if you want to go further.
Can the scan check every WCAG 2.1 criterion?
No automated tool can. The scan checks the criteria that can be tested automatically and lists those that need manual review, such as reflow and text spacing.
Sources
- W3C: Web Content Accessibility Guidelines (WCAG) 2.1 (opens in a new tab)
- W3C WAI: What is new in WCAG 2.1 (opens in a new tab)
- ADA.gov: Fact sheet on the ADA Title II web and mobile rule (opens in a new tab)
This page explains general accessibility patterns for Kajabi sites and is not legal advice. AccessBell is not affiliated with Kajabi. Kajabi and its logo are trademarks of their owners and are used only to identify the platform. See our disclaimer.
