How does this kit differ from standard WCAG accessibility checkers?

Unlike standard tools that focus on code-based fixes like alt-text, this kit addresses 'invisible' barriers by auditing 85 specific cognitive checks for neurodivergent profiles like ADHD, autism, and dyslexia.

Can I use this skill during the initial design phase, or is it only for auditing finished products?

Yes, the kit includes a 12-rule design baseline and copy-pasteable CSS tokens, making it easy to implement cognitive accessibility directly into your Figma flows or frontend code.

Which specific user profiles are covered in the Do/Don't tables?

The skill covers 16 distinct profiles, including neurodivergent conditions, age-related changes (children and older adults), and situational factors like high stress or anxiety.

Does using this skill help my project meet legal compliance standards?

The skill provides a direct mapping to global legal standards including WCAG 2.2, the European Accessibility Act (EAA), and Section 508, helping you justify these improvements to stakeholders.

Does the kit help with UX writing and microcopy?

Absolutely. In addition to UI checks, it includes specific instructions for rewriting complex error messages and instructions into plain language optimized for legibility and reduced cognitive load.

Cognitive Accessibility Kit — neurodivergent UX

Example session with this skill installed

Review this error message from our mortgage application form and rewrite it:

"Invalid Input: Error 0x404. Please check your credentials and try again."

It appears when someone types their annual income as "£45,000".

Read your context and instructions
Compiled the cognitive accessibility kit

Audit

#	Issue	Who it affects	COGA / WCAG	Severity	Fix
1	The form rejects "£45,000" — a normal way to write money	Dyscalculia, low numeracy, everyone	Obj. 4 / check 53	Blocker	Accept £, commas and spaces. Strip them before validating
2	The message doesn't name the field	ADHD, dementia, older adults	Obj. 4 / WCAG 3.3.1	Blocker	Say "Annual income"
3	It doesn't say how to fix the problem	Everyone	Obj. 4 / WCAG 3.3.3	Blocker	Give the expected format and an example
4	"Error 0x404" is a system code, not language	Dyslexia, anxiety, low literacy	Obj. 3 / check 23	Major	Remove from the UI. Log it for support
5	"Credentials" is the wrong word — income is not a login	Everyone, autistic users (literal reading)	Obj. 3 / check 22	Major	Use the field's own name
6	"Invalid" sounds like blame on a high-stakes money form	Anxiety, stress	Obj. 4 / check 52	Major	Neutral tone, no blame words

Rewrite

Best fix: no error at all. Accept "£45,000", "45000" and "45 000" as the same value.

If something still can't be read (for example, letters), show this next to the field:

Enter your annual income before tax as a number, for example 45,000

And at the top of the page, as a link to the field:

There is a problem — Annual income: enter a number, for example 45,000

Code

<label for="income">Annual income before tax</label>
<p id="income-hint">For example, £45,000</p>
<p id="income-error" class="error" role="alert">
  <span aria-hidden="true">⚠</span>
  Enter your annual income as a number, for example 45,000
</p>
<input id="income" name="income" inputmode="decimal"
       aria-describedby="income-hint income-error" aria-invalid="true">

// Accept the formats people actually type
const value = Number(input.value.replace(/[£,\s]/g, ''));

Quick wins this week

Normalise the income input (fixes #1 and makes most of these errors disappear).
Replace the message text (#2–#6).
Check that nothing the person typed is cleared on error (check 55). This can't be assessed from one message.

Guidelines reduce obvious harm. They don't replace testing with neurodivergent people. If the form hasn't been tested with them, start with references/research-guide.md.

Connects securely to your tools. The creator never sees your data.

About this skill

Most accessibility reviews check contrast, alt text and keyboard focus, then stop. That leaves out the largest group of disabled users. This skill covers what comes after those checks.

What it does

Audits a screen, flow, Figma file or code against 85 checks in 14 categories. Each finding is mapped to a W3C COGA objective or a WCAG criterion and rated Blocker, Major or Minor.
Designs flows, forms and dashboards from a 12-rule baseline and copy-pasteable CSS tokens.
Rewrites UI copy, error messages and instructions in plain language.
Covers 16 profiles with Do/Don't tables: ADHD, autism, dyslexia, dyscalculia, colour blindness, legibility, D/deaf, dementia, older adults, children, teenagers, anxiety, stress, mental health, trauma, left-handed users.
Builds the business case with a map to WCAG, EAA, Section 508 and EN 301 549.
Plans research with neurodivergent participants without harming them.

Three things it insists on

Neurodivergence is a difference in cognition, not a deficit.
The fix is almost never a "mode". Make the accessible version the default.
Guidelines reduce obvious harm. They don't replace testing with neurodivergent people.

Sources

W3C COGA "Making Content Usable", UK Home Office and DWP/HMRC accessibility guidance, and more. All cited inside the skill.

Free. Licence CC BY-NC-SA 4.0. Source: https://github.com/bairamilona/cognitive-accessibility-kit

How to use

Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

Reviews

No reviews yet

Be one of the first to try it. Every listed skill passes our trust checks below.

Security scanned

Passed our 8-point scan before listing

1 install

Downloaded by developers to date

Free forever

No account required to browse

Cognitive Accessibility Kit — neurodivergent UX