Keyboard and focus
Primary navigation, guided choices, filters, accordions and actions use native interactive controls with visible keyboard focus. Skip links move past repeated navigation.
ACCESSIBILITY
Support information should remain usable when attention, time or dexterity are limited.
Aurora targets WCAG 2.2 AA and also treats cognitive load as a safety concern. That means plain choices, visible focus, keyboard access, large touch targets and reduced-motion support are product requirements, not decoration.
Responsive reading
Layouts collapse to a single reading column where needed, while service comparison becomes horizontally scrollable instead of compressing content into unreadable cells.
Motion
Non-essential transitions and ambient movement respect the user's reduced-motion preference.
Language and cognitive load
Support journeys avoid requiring a diagnosis, legal label or complete story before showing options. Emergency routes stay visually distinct from ordinary navigation.
RELEASE STANDARD
Code-level accessibility is necessary, but it is not the final certification.
Automated and source-level checks can catch important defects, but Aurora should not claim independent WCAG certification without appropriate browser, assistive-technology and human acceptance testing.
When a defect prevents someone from reaching essential support, it is a release defect rather than a cosmetic backlog item.