Accessibility

Accessibility: where we stand.

A taxi is, first of all, a service for people who cannot drive. The website should follow. Here is the real state of it, unrounded.

The French version of this page is the legally binding text. This English translation is provided for convenience.

Last updated:

Compliance status

The website iaorana-taxi-tahiti.com is non-compliant with the French general accessibility improvement framework (RGAA, version 4.1.2 of 18 April 2023).

This status is not an admission of giving up: it is the only honest status until a full audit has been carried out. A site may only declare itself “partially compliant” after measuring its 106 criteria. That has not been done yet.

A voluntary approach

A useful clarification: this site is not legally required to publish this statement. The obligation in article 47 of law no. 2005-102 of 11 February 2005 covers public bodies and private companies with at least 250 million euros in turnover. A taxi business falls into neither category, and European directive 2019/882 on accessibility does not apply in French Polynesia.

This page exists anyway, because a site unusable with a keyboard or a screen reader shuts out exactly the customers a taxi is meant to serve. We take the RGAA as a compass, not as an imposed constraint.

What already works

These points have been checked in the site’s code, not assumed:

  • A “Skip to content” link at the top of every page, including the 404 error page, to skip navigation with the keyboard.
  • Footer headings are level 2, like the sections before them: the heading hierarchy does not skip a level.
  • A visible, designed focus indicator on all interactive elements.
  • Every image has a text alternative, and decorative images are explicitly hidden from screen readers.
  • Animations are disabled if your system asks to reduce motion.
  • The page language is declared and updated when you switch between French and English.
  • A dark theme and a light theme, with contrasts worked in both.
  • Buttons and links without visible text have an accessible name.
  • Navigation, drop-down menus and search open and close with the keyboard.

What still needs fixing

Known limits today:

  • The interactive map of destinations and the route overlay are not usable with a screen reader, nor fully with the keyboard. Immediate workaround: the Fares page and the home-page booking form give the same information as text and lists.
  • No test has been run with a real screen reader (NVDA, JAWS, VoiceOver) on a complete booking journey.
  • Contrasts have not been measured criterion by criterion across all components, including hover and disabled states.
  • No video or audio content is published at this time: captions and transcripts are not yet an issue.

What is planned

  1. Measure contrasts on all components and both themes, then fix those that fail.
  2. Test the booking journey with a screen reader, from choosing the trip to sending the request — that is the journey that actually matters.
  3. Provide a complete text alternative to the map, exhaustive and keyboard-navigable.
  4. Carry out the RGAA audit and replace this page’s status with a measured compliance rate.

Report a barrier

If something stops you from reaching information or booking, tell us. Describe the problem, the page concerned and, if you can, the hardware or software used:

We reply, and we fix what can be fixed quickly.

If you do not get a satisfactory answer, you may contact the Défenseur des droits (French ombudsman): online form or free post to Défenseur des droits, Libre réponse 71120, 75342 Paris Cedex 07.

And if the site still blocks you

No booking depends on this website. A call to +689 87 28 04 83 does exactly the same job, seven days a week, day and night. The phone remains the most accessible path there is, and it will never be removed.

Technical environment

The site is built in HTML, CSS and JavaScript with no framework dependency. The checks above were carried out by code review on 31 August 2026, on Chrome and Safari (macOS), using keyboard navigation. They do not replace a formal RGAA audit.