Agent skill · personamanagmentlayer
accessibility-expert
Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or when the task involves making a component, form, modal or data table usable without a mouse or with assistive technology.
What it needs
About 6k tokens when loaded.
What this skill does
Accessibility Expert Accessibility is a property of the markup and the interaction model, not a layer added afterwards. Most of it is achieved by using the right element; the rest is focus, contrast and honest testing. Core Concepts The Four Principles WCAG organises everything under POUR: Perceivable — information must be available to at least one sense that works for the user: text alternatives, captions, sufficient contrast. Operable — every function must be reachable and usable by keyboard, with enough time and no seizure triggers. Understandable — predictable behaviour, readable text, errors that explain themselves. Robust — valid markup and correct semantics, so assistive technology can interpret it. Conformance levels: A (minimum), AA (the legal and practical target), AAA (specific contexts). Regulation generally requires AA — the European Accessibility Act applies from 28 June 2025 to consumer-facing digital products and services in the EU, and Section 508 applies to US federal procurement. The Right Element Is Most of the Work Native elements bring focus behaviour, keyboard handling, state announcement and platform conventions. Recreating them with div and ARIA means reimplementing all of it, and the reimplementation is where the defects live. ARIA's First Rule Is Not to Use It Use ARIA only when no native element expresses the semantics. Incorrect ARIA is worse than none: it overrides what the browser would have reported correctly. Keyboard Everything achievable with a mouse must be achievable with a keyboard, in a sensible order, with a visible focus indicator. WCAG 2.2 added 2.4.11 Focus Not Obscured: the focused element must not be hidden behind a sticky header or cookie banner. Test by tabbing through the page with the header visible. Focus management Focus must go somewhere sensible after a view change, and must be trapped inside a modal while it is open. Returning focus to the element that opened the dialog is what keeps a keyboard user oriented. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills personamanagmentlayer/accessibility-expert