How accessible Kabora is

Kabora works to the Web Content Accessibility Guidelines, version 2.2, level AA (WCAG 2.2 AA). That covers the website, and the phone app wherever the guidelines apply to an app.

No one outside Kabora has checked it yet. What follows is Kabora’s own account. It is not a certificate.

• Every page, by machine

  An automated sweep opens every page of the website and runs axe-core, a widely used accessibility checker, against the WCAG 2.2 A and AA rules. It checks color contrast in light and in dark, whether you chose dark in Kabora’s menu or your device chose it for you.

• The code itself

  Checks that run on every change read the code, so that every form control on the website has a name a screen reader can say.

• The keyboard alone

  Tests book a stay using only the keyboard, and check that you can always see which control the keyboard is on.

• Zoom and narrow windows

  Kabora has gone through the website’s pages zoomed to twice their size, and at 320 pixels wide, looking for anything cut off and anything that scrolls sideways.

• Larger text on your phone

  In the phone app, text follows the size you set on your phone. Kabora has gone through the app at the largest sizes looking for anything clipped or overlapping, and checks hold the screens that broke.

• What a screen reader is given

  On every screen of booking a stay in the app, Kabora has read the name and role each control gives a screen reader, using tools that show them.

Nobody has yet used Kabora from start to finish with a screen reader turned on, such as VoiceOver or NVDA. Kabora has read what a screen reader is given, and a label has been heard spoken on a phone. But no person has tested whether the whole of it makes sense by ear. That is the next thing Kabora owes.

Automated checks find only part of what gets in people’s way: the makers of axe-core put what it can find at about 57% of accessibility problems. Whether a description is right, or a page reads in a sensible order, takes a person, and Kabora does not check all of that yet.

Some of what you read is written by hosts: a listing’s description, and the words on a host’s own booking site. Kabora holds the pages it builds to the standard, but it cannot answer for every host’s words.

If something on Kabora stopped you, or took far more effort than it should have, write to accessibility@kabora.app. Name the page, what you were trying to do, and what got in the way. Kabora will confirm that it received your report.

Trust says how Kabora is run and what protects your data. Help center answers questions about booking and hosting.