Accessibility

WCAG contrast, semantic markup and keyboard paths — handled in the system rather than in a remediation pass.

How I use it

Compliance as the default state
Token ramps built to clear WCAG contrast where the type size allows, so accessibility is not a retrofit priced as a separate engagement.
Semantic markup
Real headings, landmarks and controls. Most failures are an element given a click handler and none of the keyboard behaviour, focus handling or announcement that comes free with the correct tag.
Respecting motion preferences
Scroll and reveal effects check prefers-reduced-motion and render their final state immediately when it is set, instead of animating anyway.

Want the detail behind any of this?

I can walk through any of it in as much depth as you want.