Designed for more people to
move with confidence.

AkiGO seeks to provide digital experiences that are usable by as many people as reasonably possible, including people who use screen readers, keyboards, voice control, switch devices, magnification, captions, alternative input devices, and other assistive technologies.

We intend to consider accessibility throughout planning, design, development, testing, content creation, support, and product updates rather than treating it as a one-time task.

AkiGO is committed to designing and improving its websites and digital products in alignment with the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA.

WCAG provides testable guidance for making digital content more perceivable, operable, understandable, and robust. Although AkiGO is working toward WCAG 2.2 Level AA alignment, we do not represent that every page, screen, component, or third-party integration has achieved full conformance.

Accessibility obligations may also arise under applicable disability, consumer-protection, transportation, employment, and public-accommodation laws.

This statement applies to AkiGO digital experiences that link to it, including the marketing website, rider application, driver application, delivery features, business tools, help content, safety content, account experiences, and support workflows.

Separate accessibility requirements or accommodations may apply to employment, business partnerships, transportation services, healthcare-related services, physical facilities, or other specialized programs.

Depending on the page, application, device, and stage of development, AkiGO seeks to support:

• Semantic headings and page landmarks
• Descriptive page titles and link text
• Visible keyboard focus indicators
• Form labels and required-field identification
• Error messages that explain how to correct a problem
• Text resizing and browser zoom support
• Reduced reliance on color alone
• Alternative text for meaningful visual content
• Consistent navigation and help locations
• Touch targets designed for practical interaction

Interactive content should be operable using a keyboard or equivalent input method. Users should be able to move through links, buttons, menus, forms, dialogs, and other controls in a logical order.

Focus indicators should remain visible and should not be obscured by sticky headers, overlays, or other content. Keyboard focus should not become trapped except where a properly managed modal experience requires it.

AkiGO seeks to provide readable text, sufficient contrast, scalable layouts, understandable spacing, and controls that do not rely only on color, position, shape, or animation to communicate meaning.

• Text should remain usable when enlarged or zoomed.
• Content should reflow where reasonably possible without requiring unnecessary horizontal scrolling.
• Status, error, warning, and success information should use text or icons in addition to color.
• Motion and animation should avoid unnecessary flashing and should respect reduced-motion settings where supported.

AkiGO strives to support commonly used assistive technologies, including screen readers, screen magnifiers, voice-recognition software, keyboard-only navigation, switch devices, and mobile accessibility features. We use semantic HTML, meaningful heading order, page landmarks, form labels, accessible names, status announcements, and alternative text to support accessible navigation.

Decorative images should generally be hidden from assistive technologies, while meaningful images should provide an equivalent text alternative. Complex maps, charts, and visualizations may require a text-based alternative.

Forms should provide visible labels, clear instructions, understandable required-field indicators, and error messages that identify the affected field and explain how to correct the problem.

Where practical, forms should preserve valid information after an error and avoid requiring users to repeatedly enter the same information. Authentication should not unnecessarily depend on memory, puzzles, or inaccessible interactions.

When AkiGO publishes prerecorded video with meaningful spoken content, we seek to provide captions or an equivalent alternative. Audio-only content should include a transcript where reasonably necessary.

Important visual information in video may require audio description or an equivalent text explanation. Media should not autoplay with sound without an accessible method to pause, stop, or control it.

AkiGO’s rider and driver experiences are designed to support applicable mobile accessibility features, including screen readers, dynamic text where supported, logical focus order, accessible touch targets, device orientation, and clear labels for controls.

Location, maps, gestures, notifications, live trip updates, and safety workflows are evaluated with assistive technologies such as iOS VoiceOver, Android TalkBack, keyboard access, switch control, magnification, and voice input whenever practical.

Accessibility is an ongoing process. AkiGO regularly evaluates digital experiences, reviews user feedback, and improves accessibility as new features are designed, developed, tested, and released.

Accessibility considerations are incorporated into product planning, design reviews, engineering, content creation, and quality assurance whenever practical. Testing may include automated tools, keyboard review, screen-reader testing, contrast evaluation, zoom and reflow checks, and manual review of important user journeys.

AkiGO designs its website to work with current versions of major browsers, including Google Chrome, Apple Safari, Mozilla Firefox, and Microsoft Edge, as well as modern iOS and Android devices.

Accessibility behavior can vary by browser, operating system, assistive technology, device settings, and software version. Keeping browsers, operating systems, applications, and assistive technologies up to date may provide the best experience.

AkiGO is still developing and testing parts of the Platform. Known or reasonably anticipated limitations may include:

We update this section as testing identifies specific barriers and as remediation work is completed.

AkiGO may use third-party maps, payment interfaces, app-store pages, identity services, communication tools, documents, embedded content, and other integrations.

We do not fully control the accessibility of third-party services. We consider accessibility when selecting and configuring providers and seek to offer an alternative where reasonably possible when a third-party barrier prevents access.

If a digital feature, document, form, map, or piece of content is not accessible to you, contact AkiGO and describe the information or service you need.

Where reasonably possible, AkiGO provides information in an alternative format, assists with completing a process, explains a visual element, or offers another access method.

Alternative access may depend on the request, available technology, safety, identity verification, legal requirements, and the nature of the service.

Accessibility feedback is welcome. Helpful reports may include:

• The page, feature, or screen where the issue occurred
• A short description of the accessibility barrier
• The device and browser or app version being used
• The assistive technology being used, if applicable
• The format or alternative that would be most helpful

Do not include passwords, verification codes, complete payment card numbers, or unnecessary sensitive information in an accessibility report.

AkiGO reviews accessibility reports based on severity, user impact, frequency, safety implications, technical complexity, available alternatives, and the scope of the affected service.

We do not promise a fixed resolution time. Some issues may be addressed quickly, while others may require design changes, engineering work, vendor coordination, legal review, or a broader product update.

When practical, we provide a temporary alternative while a longer-term correction is evaluated.

AkiGO may update this Accessibility Statement as our products, standards, testing practices, known limitations, contact methods, and legal obligations change.

The revised statement will display an updated “Last Updated” date. Significant accessibility changes may also be described through other appropriate communications.

To report an accessibility barrier, request an alternative format, or ask an accessibility question, contact:

As AkiGO evolves, this Accessibility Statement may be updated to reflect improvements, new features, additional contact methods, and expanded accessibility support.