Accessibility.
WCAG 2.1 AA is the floor, not the goal. Aceve builds tools that people use for hours, on their worst day, on whatever device is to hand — so accessibility isn't a compliance checkbox, it's what makes the software usable at all. This page pulls together the rules that the component pages apply individually.
The four areas
Where accessibility is won or lost in an Aceve screen.
Text meets WCAG AA — 4.5:1 for body, 3:1 for large text and UI borders. Every Sprout pairing is tested in light and dark mode.
See the tested pairingsEverything you can do with a mouse works from the keyboard. Focus is always visible via --shadow-focus, tab order follows reading order, and focus is only trapped inside an open dialog.
Semantic HTML first; ARIA only where the platform falls short. Every control has an accessible name, and state changes are announced, not just shown.
Animation is short and optional. We honour prefers-reduced-motion: when a user asks for less, transitions become instant.
See the motion tokensThe checklist
The minimum every screen clears before it ships.