Access is a product requirement.

Our product target is WCAG 2.2 Level AA. This is a development target, not a claim that every route, state, browser, or assistive-technology combination currently conforms. Desmarto has not completed an independent formal accessibility certification.

• Shared navigation includes a skip link and visible keyboard focus styling.
• Dialogs and sheets in the shared component system support keyboard operation and Escape dismissal.
• Display Studio and Workspace hide inactive controls from keyboard focus when their control trays are visually hidden.
• Core calculator inputs use visible labels, and result visualizations provide text or table alternatives.
• Responsive checks include 320px layouts and representative reflow at a 400% equivalent CSS viewport.

• Semantic HTML landmarks and a logical heading hierarchy.
• ARIA labels on visualizations and complex controls.
• Core financial visualizations include text or table alternatives.
• Form labels are associated with inputs.
• Important shared status messages use live regions where implemented.

• Theme tokens are designed toward AA contrast for normal text and controls.
• Core statuses pair color with labels, icons, or text.
• Light, Dark, and OLED themes are included in visual and keyboard QA.

Shared motion styles respect the prefers-reduced-motion media query. Some browser-native fullscreen and scrolling behavior remains controlled by the browser.

• The supported responsive target begins at 320 CSS pixels.
• Core flows are tested across mobile, tablet portrait, tablet landscape, and desktop layouts.
• Primary controls target comfortable touch areas; dense secondary controls remain under review.
• Pages are expected to reflow when text is zoomed rather than requiring users to zoom out.

• ARIA labels describing visualization content.
• Screen-reader text summaries.
• Non-color distinction where appropriate.
• Responsive scaling for different screen sizes.

Complex board layouts, drag-and-resize Workspace editing, third-party browser fullscreen behavior, and the full route catalog still need broader assistive-technology testing. Some compact secondary controls may not yet reach the preferred touch size. Text alternatives reduce risk for charts, but they have not been verified in every screen reader.

If you encounter an accessibility barrier, include the route, task, browser, assistive technology, and what prevented completion. Do not include confidential personal information.