Ghost WCAG 2.2 Checker

WCAG 2.2 for Ghost Sites

WCAG 2.2 became a W3C Recommendation in October 2023. It keeps every WCAG 2.1 requirement except 4.1.1 Parsing and adds six success criteria at Level A and AA, mostly about people with low vision, motor disabilities and cognitive disabilities. A Ghost site that meets WCAG 2.2 AA also meets 2.1 AA and 2.0 AA.

This checker runs the same free scan as the Ghost accessibility checker with the WCAG 2.2 AA preset, so the results include the 2.2 rules that automated testing can check.

On Ghost sites, WCAG 2.2 issues usually come from the theme and plugins rather than core: icon-only social links below 24 pixels, sticky headers that cover focused links, and login or comment forms that block password managers.

Who Should Run the Ghost WCAG 2.2 Checker

• Ghost site owners who want the most current, future-proof target.
• Teams redesigning a Ghost site, where adopting the latest version costs little extra.
• Organizations selling into the EU, where EN 301 549 V4.1.1 now uses WCAG 2.2.
• Anyone preparing for new rules, which tend to adopt the latest WCAG version.

The New WCAG 2.2 Criteria to Check on Ghost

• 2.4.11 Focus Not Obscured (Minimum)

  Sticky headers, cookie banners and chat widgets must not completely hide the element that has keyboard focus.

• 2.5.7 Dragging Movements

  Anything that works by dragging, such as sliders, carousels and sortable lists, needs a single-pointer alternative.

• 2.5.8 Target Size (Minimum)

  Buttons and links need a target of at least 24 by 24 CSS pixels, or enough space around them. Icon buttons and pagination links often fail.

• 3.2.6 Consistent Help

  Help such as a contact link or chat must appear in the same place on every page that has it.

• 3.3.7 Redundant Entry

  Do not ask for the same information twice in one process, such as shipping and billing addresses, without offering to fill it in.

• 3.3.8 Accessible Authentication (Minimum)

  Sign-in must not depend on a cognitive test, such as remembering a password without paste support or solving a puzzle.

Where Ghost Sites Usually Fail WCAG 2.2

These problems come up again and again on Ghost sites, and each one fails WCAG 2.2. The Ghost accessibility checker explains how to fix them in Ghost.

• Image and gallery card alt text. Images dropped into posts with no alt text, or with a caption standing in for it, and gallery cards where each image needs its own description.
• Heading structure in long posts. The post title is the page heading, so writers should start at h2. Bold text used as a heading and skipped levels break the outline of long articles.
• Embeds and bookmark cards. Embedded videos, social posts and podcasts load in iframes that need titles, and bookmark cards can produce several links with the same text.
• Membership portal and subscribe forms. The signup and subscribe forms, the portal pop-up and the announcement bar add fields, buttons and overlays that need labels and keyboard handling.
• Theme contrast and navigation. Light gray metadata, pale tag links and dark-mode color swaps often fall below the contrast minimum, and mobile navigation toggles lack a name.

Worried about ADA claims as well? The Ghost ADA compliance checker covers the Ghost risks behind most complaints.

What to Test by Hand on Ghost

Automated testing finds many, but not all, WCAG 2.2 failures. Check these yourself after the scan:

1. Tab through each page and check the focused element is never fully covered by sticky content (2.4.11).
2. Try every drag interaction with a single click or tap instead (2.5.7).
3. Sign in with a password manager and check paste works (3.3.8).
4. Rescan after each fix. Continuous monitoring rescans up to 500 URLs per domain daily and keeps a dated record in the Compliance Vault.

Start 3-day free trial

Related Guides

• WCAG 2.2 AA CheckerThe WCAG 2.2 standard in full, for any website.
• WCAG 1.1.1 Non-text Content Explained in Plain EnglishWCAG 1.1.1 Non-text Content explained simply: how to write alt text for every kind of image, icon, chart and CAPTCHA, with code examples and a test routine.
• WCAG 1.3.2 Meaningful Sequence Explained in Plain EnglishWCAG 1.3.2 Meaningful Sequence explained simply: why reading order matters, how CSS and layout tables break it, how to fix it and how to test your pages.
• WCAG 1.4.3 Contrast (Minimum) Explained in Plain EnglishWCAG 1.4.3 Contrast (Minimum) explained simply: the 4.5:1 and 3:1 ratios, what counts as large text, the exceptions, fixes and how to test your colors.
• WCAG Success Criteria LibraryLook up any criterion the scan flags, in plain language.

Ghost WCAG 2.2 Checker: Frequently Asked Questions