LEARN

Behaviour and accessibility

CSS supplies presentation. HTML supplies semantics and native interactions; your application supplies the remaining behaviour.

Keep native interactions

  • Buttons perform actions; links navigate to real destinations.
  • Details and summary provide disclosures. A shared name requests native exclusive groups.
  • Checkboxes and switches retain native checked, disabled and keyboard behaviour.
  • The top menu uses native auto popovers for outside-click and Escape dismissal.

The CSS-only tabs pattern uses radio selection. Toolbars use ordinary labelled groups. Neither claims the ARIA tab or toolbar keyboard contract.

Supply meaningful markup

  • Use a logical heading hierarchy and a name for each navigation landmark.
  • Associate labels and help text with form controls. Write errors in words.
  • Use visible status text alongside colour, badges and progress indicators.
  • Keep decorative SVGs and placeholders hidden from assistive technology; name icon-only buttons.
  • Use current-page semantics for navigation and non-interactive markup for unavailable links.

What your application owns

Routing, pagination results, form processing, validation messages, live announcements, loading completion and image fallback are outside the CSS core. Modal dialog focus behaviour is not supplied by dialog styling alone. Static alerts have no automatic dismissal or announcement.

The native menu has a known browser-dependent limitation: closing nested panels may not restore focus to the opener consistently. In-page links may leave a panel open. See the top-menu behaviour notes.

Use the complete build for the shared preference utilities. Some standalone modules depend on tokens, base and common utilities; a module filename is not a self-contained accessibility guarantee.

Current release status

RevaCSS 1.0.0 — Erisian is the first public GitHub distribution release. Its release notes record automated validation and known limits. Six manual checks remain open: nested focus recovery, the reported edge device, real-device coverage, screen readers, actual zoom and print, and approved visual baselines. Start with the real-device checks for navigation, glass and animated edges.

These documents describe supported markup and known limits; they do not claim WCAG certification or completed manual acceptance. npm publication remains on hold.