Legal
Accessibility statement
7Analytica is built to work with a keyboard, a screen reader, zoom and reduced motion, and we test it against WCAG 2.2 level AA.
Details: Summary
Summary
7Analytica is built to work with a keyboard, a screen reader, zoom and reduced motion, and we test it against WCAG 2.2 level AA. If something does not work for you, tell us and we will help.
Built to be read by everyone.
The target is WCAG 2.2 level AA across the public website and the signed-in app. We treat a failure as a defect, not a preference. The design system sets the floor: focus rings at full strength, controls at least 44px on phones, and colour never the only signal.
Our own testing found no automated violations on the routes tested, and we fixed what it did find. We have not had an independent audit, so we describe this as a target and partial conformance, not as compliance.
Need help or another format?
Write to bhuvanchandra@7analytica.com with the page, what you were trying to do, your browser and any assistive technology. Ask for any content as plain text, a table or another format you can use. We acknowledge every report and say when a fix is planned.
If you are not satisfied with the response, you may escalate to the relevant authority in your country.
Six checks, repeated each release.
- Automated
- axe-core against WCAG 2.2 A and AA on every app and sign-in route, in light and dark themes, at desktop and phone widths, including after opening each dialog, menu and tab.
- Keyboard
- Scripted and manual Tab walks: a visible focus indicator at every stop, no traps, focus returned when a dialog closes, and a skip link on every page.
- Contrast
- Computed from the design tokens for every text and surface pair in both themes: 4.5:1 for text, 3:1 for controls and focus rings.
- Layout
- Reflow at 320 CSS pixels and 200% zoom, text spacing overrides, and touch targets of 44px on phones.
- Motion
- The reduced-motion setting is honoured, nothing flashes, and animation never carries information on its own.
- Structure
- Landmarks, headings, accessible names and live regions checked in the accessibility tree.
What the last pass showed.
34: Issues found and fixed in the last pass
Examples: focus returning to where it came from when a dialog closes, focus rings at full strength, controls of at least 44 pixels on phones, and single-key shortcuts that can be turned off.
0: axe violations on the routes tested
At 1440 and 390 pixels wide, in light and dark, in each route's default state and after opening every dialog, menu and tab.
4.75:1: Lowest text contrast measured
Computed from the colour tokens for every text and surface pair, in both themes. Controls and focus rings are at least 3.4:1.
The full report, with every finding and the method, is kept in the project as docs/A11Y-REPORT.md. We send it on request: bhuvanchandra@7analytica.com.
What can still get in the way.
- Map and globe
- The World Monitor map and the 3D globe are graphical and cannot be read with a screen reader. The same events are listed as text on the wire, which is the route to use. Write to us if the list is missing something the map shows.
- Dense charts
- Charts carry a text reading beside them, but some dense traces have no description for each point. Ask us and we will send the figures as a table.
- PDF exports
- Dossier and glossary PDFs are made without accessibility tags, so a screen reader may not read them in order. The same content is on screen as text, and we can send it in another format.
- Screen reader testing
- We checked announcements and structure in the accessibility tree. Nobody has yet walked the site with NVDA or VoiceOver, so problems that only show up in real use may remain.
- No independent audit
- Every check so far is ours. A third party has not tested the site, so we claim a target and partial conformance, not compliance.