Legal · Everyone
Accessibility Statement
Glydr's accessibility commitments, where the app and website stand today, and how to ask for help.
- Version
- v0.1-draft
- Last updated
- 2026-05-16
- Jurisdiction
- Ghana
- Status
- Draft
Working draft — pending final legal review. This page describes how Glydr intends to operate during our Accra pilot. We are finalising review with Ghana-qualified counsel and will publish the signed-off version before the public launch. Questions or feedback: legal@glydr.africa.
1. Commitment
Glydr aims to be usable by everyone, regardless of disability or the assistive technology they rely on. We target conformance with the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA across the marketing website and across the mobile app.
2. Where we stand today
The marketing site at glydr.africa uses semantic HTML, supports keyboard navigation, exposes a skip-to-main-content link, and provides visible focus rings on every interactive element. We do not yet have an independent third-party WCAG audit; we plan one before public launch.
The mobile app is built with Flutter and follows the platform accessibility guidelines on iOS (VoiceOver, Dynamic Type) and Android (TalkBack, font scaling). There are known gaps in screen-reader labelling on a handful of screens that we are tracking; the most important Driver and Passenger flows have been manually tested with screen readers.
3. Known limitations
- The hero animation on glydr.africa uses a moving SVG pulse along the Accra ↔ Kumasi route. The animation is decorative and marked as such (
aria-hidden). If you find any aria-hidden marker missing on a moving graphic, that’s a bug — please report it. - Some long-form legal pages on this site use multi-column layouts that compress to a single column on mobile. If you encounter overflow or layout breakage at any specific zoom level, let us know.
- The Glydr operator console (internal admin tool) is not covered by this accessibility statement.
4. Reporting an accessibility issue
Email hello@glydr.africa with:
- where the issue happens (URL or app screen);
- your assistive technology and operating system;
- what you tried and what happened.
We aim to acknowledge accessibility reports within 5 business days and to fix high-impact issues within 30 days.
5. Future
We commission a WCAG 2.2 AA audit before public launch and will publish the conformance statement on this page once that audit is complete.