accessibility
/accessibility
Keep the TS Inspector page usable with a keyboard and a screen reader, to WCAG 2.2 AA. Use when you add or change a control, tab, table, chart, dialog, or colour in src/ui.
- Author
- hamza-u ↗
- Repository
- ts-inspector ↗
- Licence
- MIT
- Last repository change
- 07.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 07.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Keep the TS Inspector page usable with a keyboard and a screen reader, to WCAG 2.2 AA. Use when you add or change a control, tab, table, chart, dialog, or colour in src/ui.
Original author description
Keep the TS Inspector page usable with a keyboard and a screen reader, to WCAG 2.2 AA. Use when you add or change a control, tab, table, chart, dialog, or colour in src/ui.
How it works
- Controls
- Tabs
- Tables
- Charts
- Text and colour
- Check
SKILL.md preview
---
name: accessibility
description: Keep the TS Inspector page usable with a keyboard and a screen reader, to WCAG 2.2 AA. Use when you add or change a control, tab, table, chart, dialog, or colour in src/ui.
license: MIT
metadata:
origin: adapted from ECC skills/accessibility
---
# Accessibility
## Controls
- Use `<button>` for actions and `<a>` for links. Never a clickable `<div>`.
- Icon-only buttons (the theme switch) need an `aria-label`.
- The import control works with the keyboard and announces the chosen file. The drop zone is not the only way in.
- Visible focus on every control. Do not remove the outline without a replacement.
## Tabs
- Use `role="tablist"`, `role="tab"`, and `role="tabpanel"`, with `aria-selected` and `aria-controls`.
- Arrow keys move between tabs. Tab moves into the panel.
## Tables
- Real `<table>` with `<th scope="col">`. The PID table, check list, and EPG are data tables.
- A clickable error row is reachable by keyboard and says where it goes ("Go to packet 1234").
## Charts
- Each chart has a text equivalent: a caption with the key numbers, or a table toggle.
- Do not rely on colour alone. Errors need a label or icon as well as red.
- Series colours meet 3:1 contrast against the background, in both themes.
## Text and colour
- Body text contrast 4.5:1, large text 3:1, in Light and Dark.
- Status changes (analysis done, error found) go to an `aria-live="polite"` region.
- Respect `prefers-reduced-motion` for the progress bar and transitions.
## Check
- Walk the page with the keyboard only: import a file, open each tab, open an error row, export.
- Run an automated checker (axe or the browser's Lighthouse) on the built page with a fixture loaded. Fix every serious or critical finding.
- Target size at least 24 by 24 CSS px for every control.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · hamza-u/ts-inspector | 90 | MIT |
| ericrisco/rsc-harness | 100 | MIT |
| Sanit-mann/The-Insectoids | 100 | MIT |
| evanca/flutter-ai-rules | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| yonatangross/orchestkit | 100 | MIT |
| xobotyi/cc-foundry | 100 | MIT |
| krzysztofsurdy/code-virtuoso | 100 | MIT |
| andreibesleaga/gabbe | 100 | CC-BY-4.0 |
Database snapshot: 13.11.2026 · package version b46107715700 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100awesome-accessibility-audit
Read-only WCAG audit of UI and markup with a concrete fix per finding. Use when asked to check accessibility, a11y, keyboard or screen-reader support, or contrast. - 84audit-accessibility
Audit UI components and pages for accessibility (a11y) issues. Use when user says "check accessibility", "audit a11y compliance", "find WCAG violations", "is this component accessible", "run an accessibility audit", or "check screen reader support". - 90audit-a11y
Performs a multi-agent WCAG accessibility audit of the frontend codebase. This skill should be used when the user asks to "audit accessibility", "check WCAG compliance", "run an accessibility review", "a11y audit", "check screen reader support", "fix accessibility issues", or… - 95accessibility-checker
Validate WCAG compliance, check screen reader support, and audit accessibility issues. Use when ensuring accessibility, fixing WCAG violations, or implementing inclusive design. - 90wcag
Expert WCAG (Web Content Accessibility Guidelines) advisor covering WCAG 2.0, 2.1, and 2.2 — the W3C international accessibility standards. Use this skill whenever a user asks about WCAG success criteria, conformance levels (A/AA/AAA), accessibility audits, POUR principles,… - 100accessibility-auditor
Use when reviewing UI for accessibility — WCAG 2.2 AA, keyboard nav, focus, ARIA, contrast, screen-reader semantics — even on 'is this a11y-OK?' or 'mach das barrierefrei'.