Kadence Accessibility Checklist 2026 | WCAG 2.1 AA & EAA Compliance
Last updated: 2026-07-02
Kadence is a fast, lightweight WordPress theme paired with Kadence Blocks, a set of enhanced Gutenberg blocks that add rows, buttons, tabs, accordions, forms, and advanced layout controls to the native WordPress editor. It has become a favorite of small businesses, agencies, and bloggers who want more design flexibility than the default editor without the weight of a page-builder like Elementor or Divi. Kadence generally produces cleaner markup than heavier builders, which gives it a genuine head start on accessibility, but a clean starting point is not the same as an accessible finished page. The most common problems come from how the blocks are used rather than the theme itself: heading blocks picked for their size instead of the document structure, button blocks and icon links with unclear or missing text, interactive tabs and accordions that need correct keyboard and ARIA behavior, and brand colors applied through the global palette that quietly fail contrast. The person building the site is often not a developer and cannot see how these choices land for a keyboard or screen reader user. Because Kadence sites frequently run real businesses that sell products or collect leads, they fall under the European Accessibility Act and the ADA. This checklist covers the accessibility issues most common on Kadence-powered sites and how to fix each one in the WordPress editor and the Kadence customizer.
Common Accessibility Issues
Kadence's heading and advanced heading blocks let you set any heading level independently of how large the text looks, so pages often end up with multiple H1s, skipped levels, or large styled text that is not a heading at all. Screen reader users navigate by the heading outline, and a broken outline makes a page much harder to move through.
For each heading block, set the HTML tag to match the real structure of the page: a single H1 for the title, H2 for major sections, and H3 for subsections, without skipping levels. Use the block's font-size and typography controls to change the visual size, keeping the heading level tied to meaning rather than appearance.
Kadence's global color palette makes it easy to apply a brand color across the whole site, but light accent colors used for links, button text, or secondary copy frequently fall below the 4.5:1 ratio WCAG requires for normal text. Because the palette is applied everywhere at once, a single low-contrast color can affect dozens of pages.
Test each palette color against the backgrounds it appears on with a contrast checker, focusing on link text, button labels, and muted secondary text. Adjust the palette values in the Kadence customizer so every text pairing meets 4.5:1 (3:1 for large text); fixing it in the global palette corrects it site-wide in one place.
Kadence button and icon blocks are often left with vague labels like 'Click here' or 'Learn more', or set up as icon-only links with no text at all. Out of context, a screen reader user tabbing through links hears a list of identical or empty labels and cannot tell where each one goes.
Give every button and link descriptive text that makes sense on its own, such as 'Download the pricing guide' instead of 'Click here'. For icon-only buttons, add visible or screen-reader-only text or an aria-label describing the action, and make sure the control renders as a real button or link.
Kadence's tabs and accordion blocks are interactive widgets that must expose the right roles, states, and keyboard behavior. When headings are not real buttons, expanded/collapsed state is not conveyed, or the panels cannot be operated with the keyboard, screen reader users cannot tell a section is collapsible or reach the hidden content.
Keep Kadence's blocks up to date, since the plugin has improved the accessibility of these widgets over time, and test each tab set and accordion with the keyboard: every control should be reachable with Tab, operable with Enter or Space, and announce its expanded or collapsed state to a screen reader. If a widget cannot be operated by keyboard, replace it with a native details/summary pattern or an accessible alternative.
The Kadence form block can be configured with placeholder text standing in for labels and with required or error states shown only through color. Placeholder-only labels disappear on typing and are announced inconsistently, and color-only cues are invisible to colorblind and screen reader users, who may not know a field failed.
In the form block settings, enable a visible label for every field rather than relying on the placeholder, mark required fields with text as well as any visual indicator, and ensure validation messages render as text tied to their field. Test a failed submission with a screen reader to confirm each error is announced and reachable.
Kadence-Specific Tips
- Kadence's global palette and typography controls are the fastest place to fix accessibility: correcting a color or heading style once in the customizer applies it across every page that uses it.
- Prefer native WordPress and Kadence blocks over pasted custom HTML, since the blocks carry more of the correct structure and keeping them updated brings ongoing accessibility improvements.
- Kadence generally outputs lighter markup than page-builders, but that does not exempt you from testing: interactive blocks like tabs, accordions, and off-canvas menus still need a real keyboard and screen reader pass.
- The editor and customizer previews do not reflect assistive-technology behavior. View the published page, tab through it, and run the key interactions with a screen reader before you launch.
Recommended Tools
axe DevTools
A browser extension that scans your published Kadence pages for WCAG violations, including heading, button, and ARIA issues in Kadence Blocks.
WAVE
A web-based evaluation tool that overlays accessibility errors on your Kadence site, helping you spot heading problems, empty labels, and low contrast.
WebAIM Contrast Checker
Test the colors in your Kadence global palette against the WCAG 2.1 AA contrast thresholds before applying them site-wide.
Further Reading
Other CMS Checklists
Get our free accessibility toolkit
We're building a simple accessibility checker for non-developers. Join the waitlist for early access and a free EAA compliance checklist.
No spam. Unsubscribe anytime.