Accessibility

The platform is built with the following accessibility practices in place:

• Semantic page structure: pages use appropriate landmark elements, heading hierarchies, and sectioning so content is navigable by structure
• Keyboard navigation: all interactive elements are reachable and operable via keyboard
• Visible focus states: focused elements display a consistent outline so keyboard position is always visible
• Responsive layouts: pages adapt to mobile, tablet, and desktop viewports without horizontal overflow or loss of content
• Form labels: all form inputs and interactive controls have associated labels, including screen-reader-only labels where a visual label would disrupt layout
• Alt text: meaningful images and diagrams have descriptive alternative text; decorative images are hidden from assistive technologies
• Screen-reader-friendly navigation: navigation landmarks are labelled, active page state is communicated viaaria-current, and status messages are delivered through live regions

The following accessibility improvements were completed as part of a recent quality pass:

• Skip-to-main link: a keyboard-visible link appears at the top of every page, allowing users to bypass the navigation header and jump directly to main content
• Navigation current page state:aria-current="page"is applied to the active item in the desktop nav, mobile drawer, and mobile bottom navigation bar
• Mobile drawer semantics: the mobile navigation drawer now usesrole="dialog"andaria-modal="true", and moves focus to the close button on open
• HPOA tool input labels: the question input and email delivery input in the HPOA Comparison Tool now have associated labels accessible to screen readers
• Accessible status messages: email delivery status and loading states in the tool interface are announced via live regions
• Focus styles on content links: inline links in legal and reference pages now display a consistent focus outline
• Heading hierarchy: corrected a structural issue where column headings inside a section were rendered at the same level as the section heading

Some accessibility improvements continue to evolve as the platform matures. Current known limitations include:

• The mobile navigation drawer and the HPOA tool password panel do not yet use a full focus trap. Keyboard focus can move outside these components while they are open.
• AI-generated answer content is rendered as markdown and may vary in structure. Heading levels and list nesting within answers are determined by the model response.
• The system architecture diagram on the System Design page is a complex SVG. An alt text description is provided, but a fully detailed text alternative is not yet available.

We will address these limitations in future updates.

If you encounter an accessibility barrier or usability issue on this site, please contact us. We take these reports seriously and will respond as promptly as we can.

hello@sympathetictechnology.com

See also our System Design and Security pages for technical details about how the platform is built.