Every premium and members-only resource for $9.99/month, as a no-commitment subscription. See the plans

PalateKit

Sign in
Menu

Request a resource

Describe the resource you are missing in one sentence. We will email you when it is published.

0 / 280

A page, a video or an image online.

Unlock PalateKit

Unlock everything

Plan

Paying means accepting our terms of sale.

Secure payment by Stripe. Receipts and invoices sent by email.

Welcome back

Sign in to install, download or save this resource. A free account is enough for free resources.

PalateKit Pick

WCAG 2.2 web accessibility review v1.0.0

Use this resource to review and fix the accessibility of a website or web page

New

  • 568 downloads
  • 131 likes
  • 184 saves

$4.99

Lifetime access to this resource, with its updates.

Install with the CLI

In a terminal, from the folder you want:

npx --yes palatekit@latest install better-accessibility

With no option, the skill goes to ~/.agents/skills/; add --agent claude-code (or codex, cursor…) to target an agent.

First time: connect the CLI with

npx --yes palatekit@latest login

The agent walks your page by keyboard, then with a screen reader in mind, and ties every failure to a WCAG 2.2 criterion. It writes the fix in your project code and hands back a report ranked by severity, ending with a Block or Approve verdict.

Mostly picked by

Updated November 2, 2026

Accessibility report ranked by severity and WCAG criterion

Details

Works in
Install guides
Generates with
Your agent's model
Licence
MIT

Similar resources

View all

What you get

  • SKILL.md with the review rules, exact thresholds and report format
  • Six detailed guides: focus and keyboard, forms, hit areas, motion and zoom, screen readers, semantics and ARIA
  • A table of faulty code patterns to look for, each with its fix

Good fit for

  • You just had a page built and want to know if it works by keyboard
  • You must meet an accessibility requirement for a client or public tender
  • You want to fix the forms and modal windows of an online shop

Not for

  • Measuring or choosing colors: the skill flags weak contrast without fixing it
  • Auditing a native mobile app
  • Getting a conformance certificate: a real screen reader test is still needed

Tags

  • accessibility
  • wcag
  • aria
  • keyboard
  • forms

About

You say

"Review my home page and checkout form: keyboard, focus, accessible names, form errors. Fix what blocks users and give me the report."

Accessibility report ranked by severity and WCAG criterion

Skill published by jakubkrehel under the MIT license.

Show more

Prerequisites

You bring
The code or URL of the page to review and The target level if not WCAG 2.2 AA

How to use it

  1. Copy the skill folder into your agent's skills folder
  2. Ask for a review of a page or flow, pointing to the files involved
  3. Read the findings table, approve the fixes and test with a real screen reader

Content preview

Files

  • focus-and-keyboard.md6.5 KB
  • forms.md3.5 KB
  • hit-areas.md3.3 KB
  • LICENSE1.1 KB
  • motion-and-zoom.md2.4 KB
  • NOTICE-PALATEKIT.md0.4 KB
  • screen-readers.md4.6 KB
  • semantics-and-aria.md4.6 KB
  • SKILL.md10.8 KB

Origin and licence

Modified by PalateKit

Author
jakubkrehel
Source
github.com/jakubkrehel/skills/tree/592aedc44d7d5b3e29740984252902f3e5402a1c/skills/better-accessibility
Licence
MIT

Notice

Version modifiée de « better-accessibility » (jakubkrehel, MIT) : traduction française et fiche par PalateKit.

User reviews

–

No ratings yet

Loading reviews…

Delete your review?

Your rating and comment will be removed from the page.

Frequently asked questions

Does the skill depend on other skills?

No. It mentions neighbouring skills (colors, typography, layout) for topics it leaves out, but works alone with the bundled guides.

Can I change the target level?

Yes. It defaults to WCAG 2.2 A and AA criteria; tell the agent if you need a different scope.