Last updated 19 November 2026. Version 1.0.

1. How far this site meets the standard

We aim for citorah.com to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. The site has not had a full accessibility audit, by us or by anyone else, and it does not meet them yet: section 3 lists the issues we know about.

The checks in section 5 are limited, and automated checks find only some kinds of problem, so there may be others we don’t know about yet.

2. What we found works

  • An automated check of fifteen pages and this one, in the light and the dark look, on a computer screen and on a phone screen, found no failures of the WCAG 2.2 A and AA rules it tests once the sections that rise into view had finished doing so (see section 3).
  • Every page we checked has its language set to British English and one main heading. On all of them but the page shown for an address that doesn’t exist, the first press of the Tab key reaches a “Skip to content” link that goes straight to the main content.
  • Links, buttons and fields show a 2-pixel outline when they have keyboard focus, and cards show it around the whole card. In the light look the outline is dark red, with a contrast of 10.5:1 against the page; in the dark look it is pale pink, at about 10:1.
  • The pages we checked fit a screen 320 pixels wide without the page scrolling sideways. The row of destinations in the header scrolls sideways inside its own strip.
  • The site follows your device’s light or dark setting, and the switch in the header and at the foot of the page changes it. If your device asks for reduced motion, sections no longer rise into view as you scroll.
  • Every place on a destination map is also in a list beside it, with a link to the place’s own page.
  • There is no video or audio on the site.

3. Known issues

As of the date at the top, these parts of the site do not meet WCAG 2.2 AA:

  • The map’s list on a phone. On a phone, the list of places on a destination map sits in a panel at the bottom of the screen. While the panel is lowered, the Tab key still moves through the places in it, out of sight. (2.4.7 Focus Visible; 2.4.11 Focus Not Obscured (Minimum))
  • The focus outline over photos. On cards that sit on a photo, such as the guides on the home page, the outline can be hard to see where the photo is a similar shade: we measured 1.25:1 in one place in the light look. (1.4.11 Non-text Contrast)

We also know of these, which make the site harder to use but which we have not counted as failures of WCAG 2.2 AA:

  • When the search box at the top of the home page has focus, it shows it only with a slightly stronger edge and a faint glow, which is easy to miss.
  • On a computer, when you move back up a map’s list of places with Shift and Tab, the heading of each group can cover up to about two thirds of the place that has focus.
  • While a section is still rising into view at the bottom of the screen, its text is paler than the contrast minimum. Once it is in view, or if your device asks for reduced motion, the same text passes.
  • On a screen 320 pixels wide, the menu button on the map pages runs 2 pixels past the edge.

4. What we are doing about it

We plan to fix the issues in section 3. When a fix goes live, we check it, take the issue off this list and update the date at the top.

5. How we checked this site

On 19 November 2026 we checked a copy of the site built from its code on a computer, not the live site. We ran axe-core 4.14, an automated checker, with its WCAG 2.0, 2.1 and 2.2 rules at levels A and AA, on fifteen pages: the home page, explore, Lisbon, Lisbon’s restaurants, a bar’s page, a Lisbon guide, the Lisbon map, trips, saved, a search, stays, how this works, privacy, contact and the page shown for an address that doesn’t exist. Each was checked 1,280 pixels wide and 375 pixels wide, in the light look and the dark look, and so was this page before it was published. Four pages were checked again with reduced motion.

On six of those pages (the home page, Lisbon, the Lisbon map, trips, privacy and contact), in the light look, and on three in the dark look, we also pressed Tab through every link, button and field and back again, up to 150 of them a page, to see that each one shows where the keyboard focus is and isn’t hidden behind anything, and checked the pages at 320 pixels wide. We worked out the contrast of the focus outline with the WCAG formula, looked at a few focused cards, links and the map on screen, and read the site’s code and styles for the rest of section 2.

The maps themselves, beyond their list of places, the trip planner’s controls and the quick search were not checked in detail. The site has not been tested with a screen reader or voice control, at 200% or 400% zoom, in Windows high-contrast mode, or by people who use assistive technology, and it has not had an external audit. We will update this statement when it has.

6. Telling us about a problem

If something on citorah.com is hard to use, or you need what’s on a page in another form, email hello@citorah.com or use the contact page. Tell us the page’s address, what went wrong, and what you were using, for example a screen reader, magnification or voice control. We’ll reply by email.

7. If you’re not happy with our reply

In England, Scotland and Wales, the Equality Advisory and Support Service can advise you. In Northern Ireland, the Equality Commission for Northern Ireland can.

8. About this statement

TicketWave HQ Ltd, which is responsible for Citorah, prepared this statement on 19 November 2026 from the checks in section 5. It is reviewed whenever a fix for an issue in section 3 goes live, and at least once a year.

Privacy · Terms · How this works · Corrections

10. Changes to this statement

  • Version 1.0, 19 November 2026: first published, after the checks in section 5.