Accessibility for Apollo Advisors°.

Accessibility commitment

Apollo aims to keep public routes, authenticated surfaces, navigation, forms, and content structures usable with keyboard navigation, readable hierarchy, and consistent interaction patterns.

Design and interaction expectations

Accessibility is treated as a platform requirement rather than a post-launch patch.

• Navigation should remain usable across desktop and mobile breakpoints.
• Focus states should stay visible and intentional.
• Content hierarchy should remain readable before final copy is written.
• Motion should remain restrained and respectful of reduced-motion preferences.

Known platform boundaries

Accessibility work continues as Apollo evolves. Some routes may still be placeholder-first while content, search, and future workspaces are being expanded.

As the platform moves from placeholder structure into production content, accessibility review should remain part of every launch pass.

Feedback and support

If an accessibility barrier is encountered, the operator support channel should be used so the issue can be reviewed and resolved with clear ownership.

Use usage@apolloadvisor.com for accessibility support or feedback.