agentleFS
Sign inStart free
mihaimurra001mihaimurra001/preConfigProject/.agents/skills/accessibility-and-inclusive-design/SKILL.md

accessibility-and-inclusive-design

Skill1 starsChanged 2 months agoMITView on GitHub

Use when designing or reviewing user interfaces, dialogs, forms, navigation menus, and custom interactive widgets.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use native <button> instead of <div onclick="..."> with role="button".

    line 11
  2. Very specific:

    Use native <dialog>, <nav>, <main>, <header>, and <ul> elements.

    line 12
  3. Very specific:

    Never strip focus outlines (outline: none) without providing a distinct replacement :focus-visible style.

    line 13
  4. Very specific:

    Every interactive element must be reachable and operable using Tab, Enter, and Space.

    line 16
  5. Very specific:

    Add aria-label or title to icon-only buttons (<button aria-label="Închide dialogul"><svg .../></button>).

    line 22
  6. Very specific:

    Ensure form inputs have associated <label for="..."> tags.

    line 23

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accessibility (WCAG 2.2 AA & ARIA)

Software must be accessible to everyone, including keyboard-only and screen reader users:

1. Semantic HTML Over ARIA Hacks

  • Use native <button> instead of <div onclick="..."> with role="button".
  • Use native <dialog>, <nav>, <main>, <header>, and <ul> elements.
  • Never strip focus outlines (outline: none) without providing a distinct replacement :focus-visible style.

2. Complete Keyboard Navigation

  • Every interactive element must be reachable and operable using Tab, Enter, and Space.
  • Escape key must close dropdowns, tooltips, and modal dialogs.
  • Active modals must trap keyboard focus so Tab does not escape to background content.

3. Contrast & Screen Reader Clarity

  • Maintain at least 4.5:1 text-to-background contrast ratio (3:1 for large text).
  • Add aria-label or title to icon-only buttons (<button aria-label="Închide dialogul"><svg .../></button>).
  • Ensure form inputs have associated <label for="..."> tags.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free