1. Our commitment
Fortwit Technology Limited aims to make Tag Along usable by people with disabilities, including people who use assistive technology. Our accessibility work covers the website, mobile applications and important user journeys such as registration, event discovery, hosting, joining, messaging, reporting and account deletion.
2. Standard and current status
Our target for web content is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We use relevant accessibility principles and platform guidance for native mobile features. WCAG is a technical target; applicable accessibility law may require additional measures.
Current conformance status: not assessed. A completed accessibility audit has not been verified for the launch build. We do not claim that Tag Along is fully or partially conformant, independently certified or free of barriers. This status will be updated after a documented assessment.
3. Design and testing priorities
- Screen-reader support through meaningful headings, labels, names, roles, states and logical reading order; text alternatives for informative images and controls.
- Keyboard and switch access, a visible focus indicator and predictable focus movement, including in menus, cookie settings, dialogs and error messages.
- Readable contrast, text resizing and reflow, usable touch targets, and information that does not depend only on colour, sound or gesture.
- Accessible sign-in and verification, clear form instructions, useful error recovery, and support for password managers and pasting codes where appropriate.
- Captions or equivalent information for relevant video/audio, controls for moving content, reduced-motion support and avoidance of harmful flashing.
These are improvement and verification priorities, not a claim that every item has already been implemented. Testing should include people using assistive technology and the complete journeys needed to achieve a task.
4. Content from hosts and third parties
Event media, captions, descriptions, linked booking pages and embedded services may contain barriers. We ask hosts to provide clear text descriptions, accurate access information and captions or alternatives for meaningful media. We review reported barriers and work with contributors or providers to address them; external content is not a blanket exemption from our own duties.
5. Tell us about a barrier
If you cannot use a part of Tag Along or need information in another format, contact Fortwit Technology Limited at Tagalong@fortwit.com or 6B Abiola Okeke Close, Medina Estate, Gbagada, Lagos, Nigeria. Use “Tag Along accessibility” in the subject where practical.
Tell us the page or app screen, the task you were trying to complete and what prevented it. If useful and you are comfortable sharing, include your device, browser or app version, assistive technology and preferred way to receive a reply. You do not need to disclose a diagnosis or send medical evidence to report an access barrier.
6. How we respond
We aim to acknowledge accessibility requests within 5 business days and provide a substantive response, workable alternative or remediation update within 15 business days. Where a fix takes longer, we explain the next steps and expected timing. Urgent barriers affecting safety, reporting, privacy rights or account deletion receive priority.
Where reasonably possible, we provide the requested information or help complete the task in an accessible way without an additional accessibility charge. If the usual contact or form is itself inaccessible, the company email and postal contact remain available as alternative routes.
7. Ongoing assessment and improvement
We will keep a record of accessibility issues, their impact, ownership and progress. Assessments should combine automated checks with manual testing of keyboard use, screen readers, magnification, colour/contrast and mobile accessibility features. We prioritise blockers to essential tasks and reassess after material changes.
When a formal review is completed, the statement will identify its date, scope, method, tested technologies, verified limitations and planned corrections. Until then, the conformance status remains unassessed. We do not treat passing an automated scanner alone as proof of accessibility.
8. Escalation and statement updates
If our response does not resolve the problem, ask for an accessibility review through the same contact. This does not affect your ability to complain to a competent equality, disability, consumer or other authority, or use a remedy available under local law.
We update this statement when an assessment or material service change provides new information. The adopted statement will show its effective and last-reviewed dates. The technical targets in this statement do not limit any accessibility duty imposed by applicable law.