Accessibility statement
How we work to make this website usable for everyone, what we have not yet tested, and how to tell us about a barrier.
Our goal
We want every visitor to be able to read this website, move around it and contact us, whether they use a mouse, a keyboard only, a screen reader, a phone held in one hand or a zoomed browser. The standard we aim at is the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA, published by the W3C.
We use the word "aim" on purpose. A site only conforms to WCAG when it has been tested against every success criterion, and we have not yet had an independent audit of this site. Until we have, we will not claim conformance. What we can do is tell you plainly what we have built in, where we know the gaps are, and how to reach us when something gets in your way.
This statement covers websitedevelopmentbangkok.com in English and Thai. If you want the general background on what accessible sites need, from colour contrast to form labels, our guide to website accessibility for Thai businesses covers it in more depth. This page is narrower: it is our own statement about our own site.
What we have done
These are the measures built into the site's templates, so they apply to every page rather than being fixed one page at a time.
- Headings in order. Each page has one main heading, and sections follow it with second and third level headings, so screen reader users can jump through a page by its structure.
- A skip link. The first thing a keyboard user reaches is a link that jumps past the menu straight to the main content.
- Visible keyboard focus. Links, buttons and form fields show a clear focus outline when you move through them with the Tab key, and the menu panels open and close from the keyboard and report their state to assistive technology.
- Colour contrast. Text and background colours come from a small set of design tokens chosen with contrast in mind, rather than being picked page by page.
- Text alternatives. Images that carry meaning have alt text; purely decorative graphics are hidden from screen readers so they do not add noise.
- Reduced motion. If your device is set to reduce motion, the site turns off its animations and transitions.
- Language set per page. English pages are marked as English and Thai pages as Thai, so a screen reader switches to the right voice and pronunciation. Language versions are linked to each other so you can change language from any page.
- Accessible names for icons. Icon-only controls, such as the phone button in the header, carry a text name that assistive technology reads out.
- Forms with labels. Every form field has a visible label tied to it, not just placeholder text that disappears when you type.
Known limits
We would rather list our gaps than hide them. As of this statement, these are the ones we know about.
No independent audit yet
The checks so far have been our own: keyboard walk-throughs, contrast checks on the colour tokens and automated checks on the page templates. We have not yet commissioned a full WCAG 2.2 AA audit, and we have not tested every page with people who rely on assistive technology every day. Some issues only show up that way.
Screen reader coverage
We have not tested every combination of screen reader, browser and device. Thai text is marked with the correct language, but how naturally it is read aloud depends on the voice installed on your phone or computer, which is outside our control.
Services we link to
Some routes to us leave this site. WhatsApp and email apps have their own interfaces and their own accessibility, and we cannot change them. If one of those gets in your way, the other contact routes below are there so you are never stuck with a single channel.
New content
We publish new articles over time. The templates keep headings, focus and language settings consistent, but a new image or table can still slip through without the care it needs. Tell us if you find one.
Report a barrier
If any part of this site stops you from reading something, using a form or getting in touch, please tell us. The most useful reports say which page you were on, what you were trying to do, and what you use to browse, for example a screen reader, keyboard only or screen magnification. You do not need to know the technical cause.
- Email: service@websitedevelopmentbangkok.com
- WhatsApp or call: +66 93 004 4098
- Our office hours are every day, 10:00 to 19:00 Bangkok time, in English or Thai
Every route is listed on the page where you can get in touch with our team. If you would rather browse than search the menus, the full site map lists every page as a plain set of links. Anything personal you send in a report is handled as set out in our PDPA privacy notice, and use of the site generally falls under our terms of service.
Accessibility on the sites we build
The same habits go into client work. When we plan a custom website design, we set contrast, heading structure, focus states and form labels in the design system from the start, because adding them after launch costs more and is usually done less well. Bilingual sites get the correct language marking on every Thai and English page.
About this statement
This statement was written on 27 September 2026. We will review it by 27 September 2027, and sooner if we change the site's templates or complete an audit.
Sources
Common questions
Does this website meet WCAG 2.2?
We aim for WCAG 2.2 level AA and have built the templates with that target in mind: ordered headings, a skip link, visible focus, contrast-checked colours, labelled forms and reduced motion support. We do not claim full conformance, because that needs an independent audit against every success criterion and we have not had one yet. When an audit is done, we will update this statement with the result.
How do I report an accessibility problem?
Email service@websitedevelopmentbangkok.com or send a WhatsApp message to +66 93 004 4098, in English or Thai. Tell us the page, what you were trying to do and what you use to browse, such as a screen reader or keyboard only. If a form is the problem, those two channels work without it, so you can still reach us while we look into the fault.
Do you build accessible websites for clients?
Yes. Accessibility is part of how we design and build every site, not an add-on: contrast and type sizes are set in the design, headings follow a logical order, forms have proper labels and error messages, and interactive parts work from the keyboard. If your organisation has to meet a specific WCAG level, tell us at the start so that target is written into the quote.
Is the Thai content accessible to screen readers?
Thai pages are marked with the Thai language code, so screen readers that support Thai switch to a Thai voice instead of reading the text with English pronunciation. Headings, links and form labels on Thai pages are written in Thai too. How natural the reading sounds still depends on the Thai voice installed on your device, which we cannot control, so tell us if a page reads badly.
Questions about this page
Email us at service@