Accessibility
Mulling meets WCAG 2.1 AA for everything it draws and announces. This page covers what it handles and what your app still needs to do.
What screen readers hear
Section titled “What screen readers hear”- Changes are spoken through one announcer for the whole page: a hidden live region, the part of a page that screen readers read aloud when it changes. Changes are gathered for a quarter of a second and repeats are dropped. The latest state wins, so several loaders or fast changes never talk over each other.
erroris announced assertively: it interrupts whatever the screen reader is saying. Every other state is polite, waiting until it finishes.- Inside an open modal dialog, the region goes inside the dialog, since screen readers ignore everything outside it.
- Each loader is a labeled image, so it’s still described when someone moves to it.
doneanderrorare still spoken if you remove the loader right after setting them.announce: 'off'makes each loader its ownrole="status"element, with its words as hidden text inside. Use it only if your app already announces progress some other way.
Motion
Section titled “Motion”- Every loader follows the user’s reduced-motion setting by default (
reducedMotion: 'auto'). The calm version doesn’t move; it fades between 80% and 100% opacity, so it keeps at least 3:1 contrast (WCAG 1.4.11). - Loaders animate for as long as the work runs. If a wait can last more than 5 seconds next to other content, give people a way to pause it with
paused. WCAG 2.2.2 asks for this. This site’s “Pause motion” control, in the header (in the menu on phones), does exactly that.
Forced colors
Section titled “Forced colors”In Windows High Contrast and other forced-colors modes, where the system replaces a page’s colors, loaders switch to the system text color, so they never disappear.
What your app should do
Section titled “What your app should do”- Use labels that describe the work (“Searching 14 sources”, “Answer ready”), not just “Loading”.
- If a visible status line sits next to the loader, mark the loader decorative (
label: null, or thedecorativeattribute) so it isn’t announced twice. - Set
aria-busy="true"on the area being updated while the AI works, and remove it when the answer arrives. - Don’t turn off
reducedMotion: 'auto'unless you offer your own motion setting.