cg-web-accessibility

A button is a <button>, a link is an <a href>, a field has a <label>. The skill sets an order of preference — native semantics, browser features, CSS, and ARIA only where native semantics are not enough — and forbids ARIA that papers over the wrong element.

An accessibility widget can offer preferences such as larger text or reduced motion. It cannot write correct alt text, fix the focus order or make a checkout usable with a screen reader. So Claude always remediates the source and treats the toolbar as an additional layer.

A real button on every page opens an accessible dialog: larger text, text spacing, line height, contrast modes, highlighted links, paused animations, hidden images, a reading-friendly font, a larger cursor, a page structure navigator and a reset. Preferences are stored locally only — no external service, no tracking, no personal data.

Automated scans with axe or Lighthouse catch part of the problems. The skill adds a keyboard pass, at least one real screen reader, a mobile pass and a 200 % text-size pass, and checks every toolbar mode against the rest of the page.

The skill is explicit that a button in the corner is not a legal status — not for WCAG, not for EN 301 549 and not for Germany's BFSG:

Solve it with native HTML where possible, reach for ARIA and JavaScript only when needed, add preferences on top, and verify with real assistive technology at the end.