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.

For accessible hidden labels, improved native form states and print utilities, see responsive layouts, RTL and print. These additions are available in the source preview; tests are deferred.

Current release status

These pages describe RevaCSS 2.0.0 in development. Use the documentation build for a preview or build the stylesheets from source.

The recorded acceptance checks are resolved; the validation record identifies reviewers, scope and evidence limits.

Maintainer acceptance does not establish accessibility certification. Exact device and assistive-technology versions and a new screenshot baseline were not supplied with the latest visual sign-off.

The real-device fixtures remain available for repeatable checks on your own browser and hardware. Record new results against the displayed page revision when evaluating a new release or reporting a regression.

These documents describe supported markup, application responsibilities and known browser limitations. Test your finished application with its actual content and assistive technologies.