Accessibility statement

We aim to meet the Web Content Accessibility Guidelines 2.2 at the AA level across calcis.dev, the estimator, the dashboard, and the public documentation pages. WCAG 2.2 AA is the target used by the Australian Human Rights Commission under the Disability Discrimination Act 1992, the EU under EN 301 549, the UK under the Public Sector Bodies Accessibility Regulations, and U.S. ADA Title III settlements.

We test against AA in two ways: automated scans on every deploy (axe-core via the build pipeline) and periodic manual review with a screen reader (NVDA on Windows, VoiceOver on macOS) and keyboard-only navigation.

• Semantic HTML landmarks (header, nav, main, footer) so screen-reader users can jump between regions.
• Keyboard navigation for all interactive controls: Tab moves focus, Enter or Space activates, Escape dismisses dialogs.
• Visible focus outlines on every focusable control, kept intact in both light and dark themes.
• Colour contrast of at least 4.5:1 for body text and 3:1 for UI components and large text, verified in both themes.
• Dark mode that respects your system preference (prefers-color-scheme) and does not rely on colour alone to convey meaning.
• Text can be resized up to 200% without loss of content or functionality, and the layout reflows down to a 320px viewport.
• Form labels, button names, and image alt text are programmatically associated and descriptive.
• No motion-triggered content or auto-playing media. The site has no ads and no popovers that interrupt reading.

We do not claim full AA conformance yet. Known gaps we are working on:

• Forecast range controls on /estimator. Some advanced sliders and toggles are not yet exposed with appropriate ARIA state to screen readers.
• Agentic cost waterfall. The hierarchical breakdown is rendered as a styled list; we are improving the semantics for screen-reader-driven navigation.
• Charts. The pricing comparison charts currently rely on visual layout; we are adding tabular text equivalents.
• Prompt editor. The editor uses native textarea for broad compatibility, but very long prompts can be awkward to navigate with a screen reader; we are evaluating lighter-weight alternatives.

If we introduce a new feature and it falls short of AA, we aim to fix the gap in the same release or, at most, the next one, and we document the issue here in the meantime.

Calcis is tested against recent versions of:

• Chrome, Edge, Firefox, and Safari on desktop.
• Safari on iOS and Chrome on Android.
• NVDA and JAWS on Windows; VoiceOver on macOS and iOS; TalkBack on Android.

We do not actively test on browsers more than two major versions behind the current release. If you hit an issue on an older browser, tell us and we will try to help or suggest an upgrade path.

If you encounter a barrier using Calcis, please tell us. Include:

• The page URL where the issue appears.
• A short description of what you were trying to do.
• The assistive technology, operating system, and browser you were using.
• Any error message or screen-reader output.

Email us at calcis.dev@gmail.com with the subject line “Accessibility”. We aim to acknowledge your message within 3 business days and to resolve or schedule a fix within 10 business days.

This statement is provided to meet the following obligations and expectations:

• Australia.Disability Discrimination Act 1992 (Cth) and the Australian Human Rights Commission's accessibility guidance for online services.
• United States.Title III of the Americans with Disabilities Act, Section 508 of the Rehabilitation Act where applicable to government procurement, and state-level accessibility acts including California's Unruh Civil Rights Act.
• European Union. The European Accessibility Act (2019/882) and EN 301 549, which references WCAG 2.1/2.2 AA.
• United Kingdom. Equality Act 2010; for public-sector use, the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
• Canada. Accessible Canada Act for federally regulated services; provincial law such as the AODA in Ontario for applicable users.

If you are unhappy with our response to an accessibility complaint you may contact:

• The Australian Human Rights Commission (humanrights.gov.au).
• Your national or regional disability-rights or accessibility regulator.