keyboard-navigation-review
Skill1 starsChanged 48 days agoMITView on GitHub
Prüft Tastaturbedienbarkeit: Fokusreihenfolge, sichtbarer Fokus, Tastatur-Fallen, vollständige Bedienung ohne Maus. Nutzen, wenn Keyboard-Access geprüft werden soll.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- smukh/a11y-agent-skillstheir own version, first seen Sep 5, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- smukh/a11y-agent-skills★ 8same name
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.
In this repository81 other files it gives its agents.
- accessibility-action-planSkill
- accessibility-auditSkill
- accessibility-finding-explainerSkill
- accessibility-report-summarySkill
- agent-config-authoringSkill
- agents-sdkSkill
- ai-ux-patternsSkill
- alt-text-generatorSkill
- anti-ai-copySkill
- aria-usage-reviewSkill
- astro-architectureSkill
- astro-client-scriptsSkill
- astro-component-a11y-reviewSkill
- before-after-accessibility-commsSkill
- bfsg-risk-language-softenerSkill
- biomeSkill
- blog-from-transcriptSkill
- brand-voice-dnaSkill
- case-study-from-auditSkill
- client-email-after-auditSkill
- cloudflare-email-serviceSkill
- cloudflare-one-migrationsSkill
- cloudflare-oneSkill
- cloudflareSkill
- complexity-judgmentSkill
- component-doc-writerSkill
- content-clarity-a11y-checkSkill
- content-qaSkill
- conversation-retrospectiveSkill
- darkmodeSkill
- deep-researchSkill
- design-directionsSkill
- design-systemsSkill
- durable-objectsSkill
- faq-from-issuesSkill
- form-accessibility-reviewSkill
- frontend-designSkill
- handoffSkill
- i18nSkill
- image-to-webpSkill
- knowledge-baseSkill
- landing-and-site-builderSkill
- landingpage-from-briefingSkill
- lighthouse-axe-result-explainerSkill
- linkedin-post-from-contentSkill
- llm-councilSkill
- local-business-seoSkill
- mcp-builderSkill
- mdx-contentSkill
- motion-designSkill
- native-html-uiSkill
- newsletter-from-auditSkill
- overlay-tool-risk-explainerSkill
- playwrightSkill
- post-auditSkill
- remotionSkill
- sandbox-migrate-to-nextSkill
- sandbox-nextSkill
- sandbox-sdkSkill
- sandbox-stableSkill
- The first 60 shown.
The file
Files
Keyboard-Navigation-Review
Prüft, ob eine Komponente/Seite vollständig und nachvollziehbar per Tastatur bedienbar ist.
Wann verwenden
- Interaktive UI (Menüs, Modals, Tabs, Dropdowns, Formulare) soll auf Tastaturzugang geprüft werden.
Input
- Komponenten-Code oder Seite (Pfad).
- Optional: erwartete Bedien-Flows.
Prüf-Vorgehen
- Alle interaktiven Elemente per Tab erreichbar und in visueller Reihenfolge?
- Sichtbarer Fokus:
:focus-visible-Style vorhanden, keinoutline:noneohne gleichwertigen Ersatz. - Kein positiver
tabindex(tabindex="1+"zerstört die Reihenfolge). Erlaubt:0und-1. - Keine Tastatur-Falle: Fokus lässt sich immer weiterbewegen (v.a. iframes, Custom-Widgets).
- Modals/Overlays: Focus-Trap aktiv, ESC schließt, Fokus kehrt danach zum Auslöser zurück.
- Custom-Widgets: erwartete Tasten implementiert (Enter/Space bei Buttons, Pfeiltasten bei Menü/Tabs).
- Kein Fokusverlust nach Interaktion (z.B. Element entfernt → Fokus fällt auf
<body>).
Output
Je Finding:
- Problem: was per Tastatur nicht geht.
- Ort: Element/Interaktion.
- Fix: Snippet (Handler,
tabindex, Focus-Management). - Priorität: hoch (nicht bedienbar) / mittel / niedrig.
Gotchas
outline:noneohne Ersatz ist der häufigste Fehler — Fokus wird unsichtbar.div/spanals Button: brauchtrole,tabindex="0"UND Key-Handler für Enter und Space.- Nach Schließen eines Modals muss der Fokus zurückgesetzt werden, sonst springt er an den Seitenanfang.
- Positiver
tabindexgewinnt gegen DOM-Reihenfolge — verwirrend und fehleranfällig. - Hover-only-Interaktionen sind per Tastatur nicht erreichbar.
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
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.