AJL Transfer

Accessibility Statement

Status: Partially conformant with WCAG 2.2 Level AA • Last updated: October 7, 2025

Operator

keeptuned.com GmbH (AJL Transfer)

Location: Zurich, Switzerland

Commercial Register No.: CH-020.4.032.964-5

Managing Director: Shabbir Sheikh

Contact

Phone: +41 76 391 3002

Email (accessibility): accessibility@ajltransfer.com

Support: contact@ajltransfer.com

Website: ajltransfer.com

1. Status & Commitment

AJL Transfer is committed to digital accessibility so everyone can browse, book, and manage rides with dignity and independence. Our conformance target is WCAG 2.2 Level AA. We treat accessibility defects as product bugs and track them in our engineering backlog.

2. Scope of This Statement

This statement covers the public website ajltransfer.com and authenticated areas (account, bookings, admin/partner portals) unless otherwise noted for legacy modules.

3. Measures We Take

  • Semantic HTML structure with meaningful headings and landmarks (header, nav, main, footer).
  • Accessible names/labels for controls and images; descriptive page titles.
  • Logical tab order and visible focus indicators; skip-to-content link.
  • Keyboard operable components (menus, dialogs, carousels) without traps.
  • Color contrast targeting WCAG AA; non-color cues for status/errors.
  • Form validation with programmatically associated messages and ARIA live regions.
  • Responsive layouts and scalable text without loss of content/functionality.
  • Periodic manual checks with screen readers and automated audits (e.g., Axe, Lighthouse).

4. Standards & Conformance Target

Our accessibility efforts are guided by the Web Content Accessibility Guidelines (WCAG) 2.2, Level AA. We also follow WAI-ARIA Authoring Practices for interactive components when native HTML is insufficient.

5. Browser & Assistive Technology Compatibility

We aim to support current versions of major browsers (Chrome, Safari, Firefox, Edge) and common assistive technologies (e.g., NVDA, JAWS, VoiceOver, TalkBack). Older or highly customized environments may experience reduced compatibility.

6. Keyboard Navigation

  • All key flows (search, booking, checkout, account) are keyboard operable.
  • Dialogs and menus trap focus appropriately and return focus to the trigger when closed.
  • Visible focus styles help users see where they are on the page.

7. Color, Contrast & Motion

  • Text and UI elements are designed to meet or exceed AA contrast ratios.
  • We avoid relying solely on color to convey meaning; icons/text labels supplement color.
  • Reduced-motion preferences are respected where animations exist.

8. Images, Media & Alternatives

  • Informative images include descriptive alt text; decorative images are marked appropriately.
  • Video content (when used) includes captions; transcripts are provided for essential audio.
  • Map locations and charts include text alternatives or summaries where feasible.

9. Forms, Errors & Focus

  • Inputs are labeled; errors are announced to assistive tech and associated with fields.
  • Clear instructions and examples for date/time, pickup/dropoff, and payment steps.
  • Timeouts (e.g., checkout timers) include announcements and do not auto-submit without confirmation.

10. PDFs & Downloads

We are working to ensure downloadable documents (e.g., vouchers, invoices) are properly tagged and accessible. If you need an alternative format, contact us and we will provide it promptly.

11. Known Limitations

  • Some newly released components may temporarily miss ARIA attributes or accessible names.
  • Focus order can occasionally be inconsistent in popovers or complex filters.
  • Legacy PDFs may not yet be fully tagged for screen readers.

We track these items internally and prioritize fixes based on impact.

12. Improvement Roadmap

  • Quarterly accessibility audits and regression checks before major releases.
  • Automated CI checks (linting and unit tests for ARIA/label presence where applicable).
  • Contributor guidelines and code review checklist for accessible components.
  • Ongoing training for designers and engineers on inclusive design patterns.

13. Feedback & Assistance

If you encounter barriers or need content in an alternative format, please contact us. We aim to respond quickly.

Helpful info to include: page/feature URL, browser & device, any assistive tech used, and a brief description of the issue.

14. Enforcement (Switzerland)

Where applicable, accessibility concerns may also be directed to relevant Swiss public bodies or consumer protection offices. We prefer to work directly with you to resolve issues quickly.

15. Statement Metadata

  • Methodology: Self-evaluation with periodic third-party checks.
  • Technologies: HTML, WAI-ARIA, CSS, JavaScript (Next.js, Tailwind).
  • Date: Last updated October 7, 2025. Future updates will be posted on this page.