This statement covers the accessibility of the Sri Lanka TaxiList website and this content portal. For accessible vehicles, see luggage, accessibility and special requirements.
What we aim for
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at level AA. That is a target we work toward, not a certification we hold, and the honest position is set out below.
What is in place
- Every page works from the keyboard alone, and the focused element is visibly outlined.
- Text contrast meets AA against its background; colour is never the only thing carrying meaning.
- Interactive controls are at least 44×44 pixels — the site is used mostly on phones, often by drivers, and small targets fail people with limited dexterity.
- Pages carry a single main heading with a sensible heading order beneath it.
- Form fields have real labels, and errors say what went wrong and how to fix it.
- Images that carry meaning have alternative text; decorative ones are hidden from screen readers.
- Text reflows to 320px without horizontal scrolling; tables scroll inside their own container rather than pushing the page sideways.
- Animation respects the operating system's reduce-motion setting.
- The site is usable at 200% zoom.
What is not fixed yet
Stating this plainly is more useful than claiming full compliance.
- Some pages on this content portal inherit a third-party theme whose heading levels are not ideal — headings render at the wrong level in places, which affects screen-reader navigation. We are correcting these page by page.
- A small number of legacy pages carry placeholder images that add nothing and should be removed.
- Date pickers in the booking flow are usable by keyboard but are not as clearly announced as they should be.
- Content translated into the platform's nine languages has not been reviewed by native speakers for screen-reader pronunciation.
If something blocks you
Tell us through the contact form and describe what you were trying to do, what happened, and the assistive technology you were using if any. We treat access barriers as faults, not feature requests.
If you cannot use the website at all, we will take your booking through the contact form directly rather than leaving you unable to travel.
Getting in touch
Every enquiry under this page goes through the contact form on the main site, with a category, a reference and a record of what you sent.
Last reviewed 24 August 2026.