Accessibility Statement
We want Georithm to be usable by as many people as possible, including people who use assistive technology. This page describes the accessibility standard we work toward, the steps we take to meet it, where we currently fall short, and how to reach us if something isn't working for you.
- Version
- v1.0
- Last updated
- 29 July 2026
Georithm is working toward conformance with the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA, across Georithm's web application. This is a target we design and test against on an ongoing basis, not a certification or a claim of full compliance.
Accessibility is treated as an ongoing programme of improvement rather than a one-time project, given the complexity of a data-dense, map-based product.
We aim to build Georithm with the following practices:
- Semantic HTML markup so that assistive technologies can interpret page structure correctly
- Keyboard navigability for core workflows, including forms, menus and dashboards
- Visible focus states so keyboard users can track their position on the page
- Colour contrast choices designed to meet WCAG AA guidance within our dark interface theme
- Respecting operating-system and browser preferences for reduced motion
- Clear, programmatically associated labels on form fields and controls
Interactive maps and data-dense visualisations are inherently challenging to make fully accessible, particularly for screen-reader and keyboard-only users, because they rely on spatial and visual interaction.
Where a map or chart is not fully accessible, we aim to provide a non-map alternative, such as:
- Sortable data tables presenting the same underlying information
- CSV export of the data behind a map or chart
- Textual summaries describing key findings shown visually
We are continuing to improve these alternatives and welcome specific feedback on where they fall short.
We aim for Georithm to work with recent versions of major browsers (such as Chrome, Firefox, Safari and Edge) combined with commonly used screen readers (such as NVDA, JAWS and VoiceOver). Older or less common browser and assistive technology combinations may not be fully supported.
We use a combination of automated accessibility scanning tools during development and periodic manual review, including keyboard-only navigation checks and screen-reader spot checks of key workflows. Automated tools cannot catch every issue, so we treat manual review and user feedback as essential complements to tooling.
If you encounter an accessibility barrier while using Georithm, or need information in an alternative format, please contact us at jerogz@georithm.info describing the page or feature involved and the assistive technology you are using, if applicable.
We aim to acknowledge accessibility feedback within a few business days and to provide a substantive response, workaround, or alternative format within a reasonable timeframe based on the complexity of the request.
If you feel your accessibility concern has not been adequately addressed, you may request escalation to a supervisor by replying to your original correspondence, or contact us via our general legal contact channel described in our Legal Notice page.
Accessibility work at Georithm is continuous. As we release new features, we aim to review them against our accessibility target before and after launch, and to prioritise fixes for issues that materially block use of the product.
This document is provided as an original template for Georithm and is maintained by the account owner. It is app-owned editable content and is not legal advice or an independent certification. Replace every bracketed placeholder with your company details and have the final text reviewed by a qualified adviser before relying on it.