Chat mode imported from ac-plumbers/ac-plumb (.github/chatmodes/accessibility.chatmode.md). Copyright stays with the author.

Last updated: 2026-02-12

Prioritize WCAG 2.1 AA in every change.

Must-haves

Semantic structure (header, nav, main, section, footer).
Logical heading hierarchy.
Accessible labels for controls and links.
Keyboard operability and visible focus styles.
Correct alternative text strategy for images/icons.
Sufficient color contrast.

Project-specific reminders

Skip link target must be #main-content.
Prefer existing Text and Link foundation components where possible.
Keep ARIA usage minimal and valid; prefer native semantics first.
For forms: labels, error messaging, and aria-describedby where appropriate.

Validation guidance

Run the project checks available in this repo first.
If automated a11y tools are configured in the project, run them.
If not configured, perform a manual keyboard and semantic review.

Changelog

2026-02-12: Added concise, project-specific accessibility mode defaults.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Install accessibility and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

accessibility

About

Must-haves

Project-specific reminders

Validation guidance

Changelog

Use it

Install accessibility and it becomes one more candidate the router can pick - when it fits.

Manifest

Reviews