More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Cognitive Accessibility Kit — neurodivergent UX

    2

    Audit, design and write UI for ADHD, autism, dyslexia, dyscalculia, anxiety and 11 more profiles. 85 checks mapped to W3C COGA and WCAG

    Free

    3 usesSecurity scanned
    Cognitive Accessibility Kit — neurodivergent UX

    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

    #IssueWho it affectsCOGA / WCAGSeverityFix
    1The form rejects "£45,000" — a normal way to write moneyDyscalculia, low numeracy, everyoneObj. 4 / check 53BlockerAccept £, commas and spaces. Strip them before validating
    2The message doesn't name the fieldADHD, dementia, older adultsObj. 4 / WCAG 3.3.1BlockerSay "Annual income"
    3It doesn't say how to fix the problemEveryoneObj. 4 / WCAG 3.3.3BlockerGive the expected format and an example
    4"Error 0x404" is a system code, not languageDyslexia, anxiety, low literacyObj. 3 / check 23MajorRemove from the UI. Log it for support
    5"Credentials" is the wrong word — income is not a loginEveryone, autistic users (literal reading)Obj. 3 / check 22MajorUse the field's own name
    6"Invalid" sounds like blame on a high-stakes money formAnxiety, stressObj. 4 / check 52MajorNeutral 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

    1. Normalise the income input (fixes #1 and makes most of these errors disappear).
    2. Replace the message text (#2–#6).
    3. 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

    Guidelines reduce harm but do not replace testing with neurodivergent people. Cannot provide legal certification or diagnose individual users.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    3 uses

    Times used to date

    Free forever

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 1 month ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed1 month ago

    What's inside

    Frequently Asked Questions

    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.

    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.

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

    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.

    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.

    New in Frontend & Web Apps