Accessibility Statement

The whole website at www.thailandka.com, in all seven languages we publish it in: English, Thai, Russian, Spanish, Italian, Hebrew and Chinese. There is no Thailandka mobile app; if we build one it gets its own statement.

Our automated scans cover the home page in all seven languages and the deeper pages in fewer — the table under How we tested says which. The catalogue is sample content and the site is not yet listed in search engines. Neither reduces what we owe you: every commitment here applies today.

We assess this site against EN 301 549 V4.1.1 (2026-09), the European accessibility standard. It takes its web requirements from WCAG 2.2 at Level AA — the Web Content Accessibility Guidelines are the international rulebook for making a website usable by disabled people, and AA is the middle of their three levels, the one regulators expect. In plain terms: you can perceive everything on the page, operate it, understand it, and rely on it working with your assistive technology.

That one claim covers Israel and Thailand too. Israeli Standard 5568 — the bar regulation 35א sets for websites — rests on the same guidelines at Level AA, and WCAG 2.2 AA meets the earlier versions underneath it. Thailand's national guidance follows WCAG as well; it does not bind a private commercial site like ours, and we test to it anyway.

Three things we do not claim: no presumption of conformity with any European directive, because no harmonised standard exists that would create one; no badge, seal or certificate, because nobody has certified this site; and no percentage score, because no honest single number exists. One thing we will not install: an accessibility overlay. Overlays do not deliver conformance, and they interfere with the assistive technology you already use.

Why not a stronger word. We have done no screen-reader testing, no testing with disabled users, and no independent audit. A full claim must also hold for complete journeys: we scan one, in Hebrew, at every step, and have not done the same in the other six languages.

These are in the site today, not plans. Each is either checked by a test we run against a production build, or structural to how the site is written.

• Everything on the pages we test works from the keyboard, with a visible focus ring — our suite walks the tab order and fails when one is missing.
• One first-level heading per page, headings that descend without skipping, and proper landmarks — checked on the home page and a legal document, and structural elsewhere.
• Colour contrast checked automatically on every page we scan, and in dark mode on the English home page. The theme follows your system setting until you choose.
• Every image carries a text description — written out where it means something, blank where it is decoration. The build checks this on the home page.
• Full right-to-left support in Hebrew, and every page declares its language and direction, so a screen reader switches voice for these English documents.
• Text can be enlarged and pages reflow to a single column at narrow widths. We have not measured that at 200% zoom in every language.
• Animated decoration stops for anyone whose system asks for reduced motion — and our scans run in that state, because it is what a motion-sensitive visitor gets.
• The map's draw-to-search also works from the keyboard, through a list of named places. It does not yet do everything drawing does.
• Serious and critical findings fail our accessibility suite, which we run against a production build before we ship. It is not yet an automatic release gate.
• The link to this statement sits in the footer of every page, in the same position in every language.

Here is what we know is imperfect or unchecked, where you will meet it, and what we are doing. The rule number is there for anyone who wants it. If you hit something that is not on this list, please tell us.

WCAG 2.2 added six criteria and we walked all six. Four bite here and appear above: 2.4.11 Focus Not Obscured, 2.5.7 Dragging Movements, 2.5.8 Target Size and 3.2.6 Consistent Help — which is why the accessibility and contact links hold the same footer position in every language, including those that mirror right to left. We meet 3.3.7 Redundant Entry: the dates and guests you enter are carried through search and never asked for twice. 3.3.8 Accessible Authentication cannot arise — there are no accounts and no login.

A statement like this may exclude content the operator did not write, fund or control. We have nothing to exclude: the catalogue is our own seeded content, and the photographs are stock images we chose and placed.

One gap to know now: those listings are a sample catalogue, so we hold no accessibility information about individual properties. Step-free access, roll-in showers and hearing loops are not described or filterable here yet — check with the property or the booking site before you book. When our partners supply that information we will show it rather than drop it on the way through.

Some rules let an operator leave a problem unfixed by arguing the fix would be an unreasonable burden. We make no such argument: nothing above is left undone because of what it would cost.

If something here stops you, or you need information in a format you can use, tell us. Give the page address, what you were trying to do, and what happened instead. Naming your browser and any assistive technology helps, but not knowing should not stop you writing. The same address is on our contact page.

Accessibility contact:to be supplied: accessibility contact address(The link to this statement is in the footer of every page, in every language.)

What we commit to: a reply within five working days; a confirmed barrier corrected as soon as we can and no later than 60 days from the day your message reaches us; that we tell you when it is done; and another way to get what you needed meanwhile. We record every message with its arrival date, so that clock runs from when you write.

There is no contact form here, deliberately. The only things you can type into this site are the search fields — dates, guests, a price range — and none of them reaches us as a message. A form built only for barrier reports would create the collection point we tell you does not exist: see what we do with data about your visit.

You do not have to come to us first, and going to a regulator does not depend on having complained to us. But telling us first is usually fastest: in Israel it starts a 60-day clock we must meet, and everywhere it is how we learn the barrier exists.

• Israel — the Commission for Equal Rights of Persons with Disabilities, at the Ministry of Justice, which supervises the Service Accessibility Regulations.
• European Union and EEA — there is no single European body. Each Member State designates its own market surveillance authority; contact the one where you live. In most Member States an organisation representing disabled people can act for you.
• Thailand — the Department of Empowerment of Persons with Disabilities, at the Ministry of Social Development and Human Security, and the Thai courts, under the Persons with Disabilities Empowerment Act B.E. 2550 (2007).

If you are not sure which authority covers you, write to us and we will tell you where to look — even when the complaint is about us. And nothing in our Terms limits your accessibility rights.

Method: self-assessment, following the structure of the W3C's Website Accessibility Conformance Evaluation Methodology, which is built to accommodate in-house evaluation. Nobody outside Thailandka prepared or reviewed it.

The automated part runs axe-core 4.13.0 from our end-to-end suite, in Chrome, against a production build — the build a visitor gets. Serious and critical findings fail the run. The rules we switch on are the WCAG 2.0, 2.1 and 2.2 A and AA sets, so the machine checks the standard we claim. Four other checks run beside it: keyboard traversal, a Hebrew right-to-left check, heading structure, and a text description on every image.

The honest limit: automated testing cannot decide whether a site conforms, because tools find only what a machine can check. The judgement calls need a person — whether the focus order makes sense, whether a link says where it goes, whether reading order survives mirroring in Hebrew. We do those by hand, on the kinds of page above.

Prepared on 9 September 2026, following an evaluation of the site and its accessibility test suite carried out on 9 September 2026. Last reviewed on 9 September 2026. We review it at least once a year, and sooner after any substantial change to the site or to the standards we test against.

Three legal systems touch this site, and none of them requires everything on this page. We do it anyway, and we mean it to be held against us.

Thailand. to be supplied: registered company name is established in Thailand. Section 15 of the Persons with Disabilities Empowerment Act B.E. 2550 (2007) prohibits discriminatory treatment, including an omission that disadvantages a disabled person where nobody meant to discriminate. We treat this site's accessibility as part of that duty. No Thai instrument imposes WCAG on a privately funded commercial website; we adopt it anyway.

Europe. We operate from Thailand and deliberately offer this service to consumers in the European Union, so we treat the European Accessibility Act, Directive (EU) 2019/882, as relevant. Whether it formally reaches us is unsettled: the one category that could cover us is "e-commerce services", defined by concluding a consumer contract, and no contract is concluded here. We do not rely on that. Its requirements on accessible identification, authentication, electronic signature and payment do not arise at all — no accounts, no login, no payment.

At the date of this statement Thailandka is a microenterprise under Article 3(23) of that Directive — fewer than ten people, and either turnover or balance-sheet total no more than two million euro — so Article 4(5) exempts us from its service accessibility requirements. As far as EU law goes we publish this voluntarily. The exemption does not touch Israeli or Thai law, does not apply to products, and ends if we cross those thresholds, which we re-check yearly. The commitments here are ones we intend to be held to, exemption or not.

Israel. The Equal Rights for Persons with Disabilities Law and the Service Accessibility Regulations set the bar at Level AA of Israeli Standard 5568 and require a statement in a prominent place. We meet that bar through WCAG 2.2 AA, and this page is that statement. The regulations relieve very small businesses below a turnover threshold and, pre-revenue, we could arguably qualify; we do not rely on that, because it evaporates on the first commission we earn. We do not employ 25 people, so no accessibility coordinator is required and we have not invented one: responsibility sits with whoever answers the address above.

We have tied these to the point where the site stops showing sample data and opens with real hotels, rather than to calendar dates we might miss.

1. Label each price field in the filters, so the lowest and highest are told apart when read aloud.
2. Extend the scans to the dark theme on every kind of page, not only the English home page.
3. Test every kind of page with a screen reader: NVDA in Firefox, VoiceOver in Safari.
4. Measure every interactive target against the minimum size, and check against regressions.
5. Make the accessibility suite a required check before deployment, so a failing run cannot ship.
6. Commission an independent audit before we open with real inventory, and publish what it says here.

Two changes ahead will change this statement, and we will update it before they ship: live partner data brings in text and images we did not write, and any consent banner we ever add becomes part of this claim — keyboard operable, dismissible, unable to trap or hide focus, or it does not ship.

The English text is the operative version. Translations are provided for convenience; if a translation and the English differ, the English governs.

Today this statement, like our other legal documents, is published in English at every language address of this site, and the notice above says so. That is not good enough for this one: a page telling you how to report a barrier is no use in a language you do not read. Full Hebrew and Thai versions are in preparation; this paragraph changes when they are published. Until then, write in any of our seven languages and we will answer in yours.

Version 1.0 — 9 September 2026

First publication. Status: partially conforms to EN 301 549 V4.1.1 / WCAG 2.2 Level AA. Seven entries in the barrier and gap table; self-assessment method and reporting route recorded.

When a barrier above is fixed we remove its row and record the change here, so you can see what moved and when.