agentleFS
Sign inStart free
TangleMLTangleML/tangle-ui/.claude/skills/accessibility/SKILL.md

accessibility

Skill104 starsChanged 3 days agoApache-2.0View on GitHub

Accessibility patterns and requirements for this project. Use when creating interactive components, forms, dialogs, or any user-facing UI.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 99 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

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

    All interactive elements without visible text must have an aria-label:

    line 12
  2. Very specific:

    Use the shadcn/ui Label component for proper form associations.

    line 36
  3. Very specific:

    Use sr-only class for visually hidden but screen-reader-accessible text:

    line 80
  4. Distinctive:

    Use proper semantic elements and ARIA roles:

    line 96
  5. Distinctive:

    All focusable elements must use the project's focus-visible ring pattern:

    line 105
  6. Very specific:

    Do not remove outline-none without replacing it with a visible focus indicator.

    line 111
  7. Distinctive:

    All shadcn/ui components (Dialog, Select, Checkbox, Switch, Tabs) handle focus trapping and keyboard navigation automatically

    line 121
  8. Very specific:

    Folders in sidebar: Use role="button" with aria-expanded

    line 129
  9. Distinctive:

    Canvas keyboard shortcuts: Must not interfere with dialog/modal focus

    line 130
  10. Distinctive:

    When adding new interactive elements to the flow canvas, ensure they:

    line 132
  11. Distinctive:

    Don't capture keyboard events that should reach parent containers

    line 136

“Common” is measured: kept by at least 6 in 10 of the 99 edited versions of this file we could read. “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 Patterns

This project builds on shadcn/ui primitives which provide strong built-in a11y. Follow these patterns to maintain that standard.

ARIA Labels

All interactive elements without visible text must have an aria-label:

<Button variant="ghost" aria-label="Home">
  <Icon name="Home" />
</Button>

<div role="button" aria-expanded={isOpen} aria-label={`Folder: ${folder.name}`}>

Form Accessibility

Link inputs to labels and error messages:

<Input
  id={id}
  aria-invalid={!!error}
  aria-describedby={`${id}-hint`}
/>
{!!error && <Text tone="critical">{error.join("\n")}</Text>}
<div id={`${id}-hint`}>{hint}</div>

Use the shadcn/ui Label component for proper form associations.

Keyboard Navigation

Required keyboard support for custom interactive elements:

  • Enter/Space: Activate buttons and toggles
  • Escape: Close dialogs, cancel editing, deselect
  • Tab: Move focus between interactive elements

The Input component has built-in onEnter and onEscape props:

<Input onEnter={save} onEscape={cancel} />

Everything else handles the keys itself:

onKeyDown={(e) => {
  if (e.key === "Enter" && !e.shiftKey) {
    e.preventDefault();
    save();
  } else if (e.key === "Escape") {
    e.preventDefault();
    cancel();
  }
}

Non-button clickable elements need role="button" and tabIndex={0}:

<div role="button" tabIndex={0} title="Click to edit">
  {content}
</div>

Dialogs must prevent keyboard shortcuts from leaking to the canvas:

The dialog component already handles this — use preventKeyboardPropagation prop when needed. This stops Ctrl+A, Ctrl+C, Ctrl+V, Tab, Enter, and Escape from reaching React Flow.

Screen Reader Support

Use sr-only class for visually hidden but screen-reader-accessible text:

<DialogClose>
  <Cross2Icon />
  <span className="sr-only">Close</span>
</DialogClose>

<DialogHeader className="sr-only">
  <DialogTitle>{title}</DialogTitle>
  <DialogDescription>{description}</DialogDescription>
</DialogHeader>

Semantic HTML

Use proper semantic elements and ARIA roles:

  • Navigation — <nav aria-label="breadcrumb">
  • The current page in a breadcrumb — <span role="link" aria-disabled="true" aria-current="page">
  • Decorative separators — <li role="presentation" aria-hidden="true">
  • Alerts — <div role="alert">

Focus Styling

All focusable elements must use the project's focus-visible ring pattern:

focus-visible:ring-ring/50 focus-visible:ring-[3px] focus-visible:border-ring

Do not remove outline-none without replacing it with a visible focus indicator.

UI Primitives A11y

The project's primitives already accept AriaAttributes:

  • BlockStack and InlineStack accept all ARIA props
  • Text accepts role and ARIA props
  • Button has built-in focus-visible and disabled states
  • Input supports aria-invalid, onEnter, onEscape
  • All shadcn/ui components (Dialog, Select, Checkbox, Switch, Tabs) handle focus trapping and keyboard navigation automatically

React Flow Considerations

The pipeline editor has specific a11y needs:

  • Handles: Support click selection and Escape to deselect
  • Task nodes: Labels are interactive with visual feedback
  • Folders in sidebar: Use role="button" with aria-expanded
  • Canvas keyboard shortcuts: Must not interfere with dialog/modal focus

When adding new interactive elements to the flow canvas, ensure they:

  1. Are keyboard accessible
  2. Have appropriate ARIA labels
  3. Don't capture keyboard events that should reach parent containers

Download now (ZIP)

  • Other versions109 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 109

    1. microsoft/vscode★ 194ksame name
    2. elastic/kibana★ 21ksame name
    3. mozilla-mobile/firefox-ios★ 13ksame name
    4. midudev/preguntas-entrevista-react★ 7.8ksame name
    5. gitpod-io/openvscode-server★ 6.2ksame name
    6. posit-dev/positron★ 4.3ksame name
    7. legions-developer/evilcharts★ 3.2ksame name
    8. midudev/la-velada-web-oficial★ 1.9ksame name
    9. UI5/webcomponents★ 1.8ksame name
    10. theopenco/llmgateway★ 1.7ksame name

    99 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use author-contributions, tool-rename-deprecation and 10 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • MicrosoftSkill

      author-contributions

      Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

      Also in 7 projects that use this

    • gitpod-ioSkill

      tool-rename-deprecation

      Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

      Also in 5 projects that use this

    • MicrosoftSkill

      auto-perf-optimize

      Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

      Also in 6 projects that use this

    • DepressionCenterSkill

      project-preferences

      Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.

      Also in 5 projects that use this

    • DepressionCenterSkill

      response-style

      Write prose in plain, natural English. Apply to every response, design discussion, review comment, commit message, pull request, and document, in any task.

      Also in 5 projects that use this

    • +7 more from microsoft
  • In this repository20 other files it gives its agents.

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