Built for Everyone.
Tested and Improved.
We want every traveler to be able to use this site, regardless of ability or the technology they rely on. This statement explains what we do, how we test, and where we still fall short.
Conformance Status
TravelThailand.org aims to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA. We believe the site substantially conforms to this standard, though some content may not yet meet every criterion.
What We Have Done
Accessibility work on this site includes:
- Text and background colours that meet a contrast ratio of at least 4.5:1 for body text.
- Semantic HTML with proper heading structure and landmark elements.
- Descriptive labels on interactive controls, including sliders and navigation.
- Touch targets sized for comfortable use on mobile devices.
- Alternative text on images that carry meaning.
- Full keyboard navigation, with a visible focus indicator.
- Responsive layouts that work when text is enlarged.
How We Test
We test with automated auditing tools, including Google Lighthouse, alongside manual keyboard testing and review across desktop and mobile screen sizes. Automated tools detect only part of what matters, so manual checks form a necessary part of our process.
Known Limitations
We have not yet completed a full audit with assistive screen-reader software. Some third-party content, such as embedded booking widgets and partner links, is outside our direct control and may not meet the same standard.
Where we identify a barrier, we work to remove it.
No Accessibility Overlay
This site does not use an accessibility overlay, toolbar, or plugin widget. Those tools can interfere with the assistive technology people already use. We prefer to build accessibility into the site itself.
Feedback
If you encounter an accessibility barrier on this site, or need information in a different format, please contact us at info@travelthailand.org. Tell us the page address and what happened, and we will respond as quickly as we can.
Your feedback helps us find problems our own testing missed.
Last Reviewed
20 September 2026