Web accessibility
LaunchKit — build & launch a complete website with Claude Code. A bundle of skills (planning, design, UI/UX, frontend, SEO, accessibility, legal) that works worldwide with first-class Israel support (Hebrew/RTL, IS 5568, Israeli privacy law).
npx -y skills add JoshBuildApp/launchkit --skill web-accessibilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when making a website usable by everyone, including people with disabilities — WCAG 2.1 AA compliance, keyboard navigation, screen readers, color contrast, focus, alt text, ARIA, and (for Israel) the legally required IS 5568 standard and accessibility statement. Triggers: "make it accessible", "a11y", "WCAG", "screen reader support", "accessibility audit", "Israeli accessibility law", "negishut", "IS 5568".
SKILL.md
3.5 KB, as published. Nobody here has run it
Web accessibility
Build it so everyone can use it — by keyboard, by screen reader, with low vision. In Israel this is also the law.
Global default — WCAG 2.1 AA
Structure & semantics
- Semantic HTML does most of the work: real
<button>,<a>,<nav>,<main>, headings in order, one<h1>. - Landmarks so screen-reader users can jump around. A "skip to content" link first.
Keyboard
- Everything works with keyboard alone: Tab order logical, no traps.
- Visible focus on every interactive element — never
outline: nonewithout a replacement. - Custom widgets (menus, modals, tabs) follow keyboard patterns and trap focus inside an open modal, returning it on close.
Color & contrast
- Text contrast ≥ 4.5:1 (≥ 3:1 for large text and UI components/icons).
- Never rely on color alone to convey meaning — add text/icon/pattern.
Images & media
- Meaningful images get descriptive
alt; decorative images getalt="". - Captions/transcripts for video and audio.
Forms
- Every input has a programmatic
<label>. Errors announced and tied to the field (aria-describedby).
ARIA — last resort
- Prefer native HTML. Use ARIA only to fill gaps, and use it correctly (bad ARIA is worse than none).
- Respect
prefers-reduced-motion; don't auto-play moving content.
Test
- Keyboard-only pass. Screen reader pass (VoiceOver/NVDA). Automated check (axe/Lighthouse) — automated catches ~30%, so test manually too.
🇮🇱 Israel — IS 5568 (mandatory by law)
- Israeli law (Equal Rights for Persons with Disabilities Act) requires most public-facing websites to meet IS 5568, which is based on WCAG 2.0 AA (the global section above covers and exceeds it).
- Accessibility statement (
hatzharat negishut): a dedicated page is required, naming the accessibility coordinator and contact, the standard followed, and known limitations. Link it in the footer. - Provide a clear contact route for accessibility problems.
- Hebrew screen-reader support: correct
lang="he"anddir="rtl", logical reading order in RTL, test with NVDA/JAWS/VoiceOver in Hebrew. - Non-compliance carries real legal/financial exposure — treat it as a launch blocker, not a nice-to-have. (For the statement's legal wording, see
web-legal.)
🔌 Power-ups (installed skills)
accessibility-audit— WCAG 2.1 AA patterns for React (semantic HTML, ARIA, keyboard, contrast).- 🇮🇱
israeli-accessibility-compliance— IS 5568, the legally required accessibility statement, Hebrew screen-reader testing. Pair withgithub-actions-ilto gate IS-5568 checks in CI.
Checklist
- Semantic HTML + landmarks + skip link
- Full keyboard operability, visible focus, no traps
- Contrast ≥ 4.5:1; meaning never by color alone
- alt text correct (descriptive vs. empty)
- Labeled forms, announced errors
- ARIA only where needed, correct; reduced-motion respected
- Manual keyboard + screen-reader test done
- (Israel) IS 5568 met + accessibility statement page published + coordinator listed