Account dropdown

Updated 2026-05-19

Overview Content Accessibility Code

Accessibility

• Keyboard & Focus
  - All interactive elements are keyboard accessible - No keyboard traps - Logical focus order - Use Tab for forward and Shift+Tab for backward - Only focusable items that are visually visible should be
  arrow-key traversal between items; Tab moves to/from the navigation region
• Interactions
  - Dragging interactions should also provide single-pointer or keyboard alternative. A single-pointer alternative means the action can be done with simple clicks or taps (no holding, no dragging). - Av
• ARIA Guidance
  - Visible Labels: Every interactive element has a visible text label. - Label Persistence: Labels remain visible when the field is focused or filled (no placeholder-only labels). - The 1:1 Rule: The a
  use aria-current=page on the active item; nav landmark on the container
• Color & Contrast
  Check Ratio -------------- Body text (< 18pt) 4.5:1 minimum Large text (≥ 18pt or 14pt bold) 3:1 minimum UI components, icons, focus indicators 3:1 minimum Rules: - Use accessible color palettes and t
• Feedback & Errors
  - Explain what happened and how to fix it - Error messages appear near the field they relate to - Use aria-live="polite" for non-critical status updates - Use aria-live="assertive" only for critical,

Cross-cutting accessibility

See the full WCAG 2.2 AA guidance for criteria that apply to every component.