Design and engineering requirements
- Keyboard navigation, visible focus, a skip link, semantic headings, and named controls.
- Responsive reflow, large touch targets, layouts that work well with zoom, and support for device safe areas.
- Fallbacks for reduced motion and forced colours, with text, controls, borders, focus, and status states designed for contrast.
- Text equivalents for status, connection, notification, meeting, loading, error, and offline changes.
- No instruction, status, or meaning conveyed by colour alone.
Known limitation and continuing verification
Gravity continually verifies keyboard use, zoom and reflow, text scaling, rotation, reduced motion, and real mobile journeys. VoiceOver and TalkBack checks are to be repeated when core journeys or interface patterns change.
Automated checks and engineering intent do not establish conformance. Gravity therefore does not claim certification or full WCAG 2.2 level AA conformance.
The optional founder message includes synchronized English captions and a written summary beside it. On the Swedish page, the video remains in English and the product context is provided in Swedish beside it.
The Swedish product and legal copy is maintained as an independent Swedish version. Report factual errors, unclear wording, or accessibility barriers through Gravity support.
Report a barrier
Use Gravity support and describe the page, assistive technology, device, and action you were trying to complete.
Do not include passwords, login links, access tokens, private messages, precise location, or another member’s personal data.