The short version
- TripStory is made to work for everyone: with a keyboard, a screen reader, voice control, magnification, high contrast or no motion at all.
- Our target is WCAG 2.2 at level AA everywhere you use TripStory, plus many AAA criteria. That is also what Israel’s IS 5568 and Europe’s EN 301 549 ask for.
- Every page of the website is checked automatically on every change to the code, in English and Hebrew and in all three themes, with an automatic keyboard walk, with text at 200% and zoomed to 400%; the app’s main screens and the partner portal are checked the same way; and everything is walked through by hand with a keyboard with every major change.
- A few things are not fully accessible yet. Each one is listed below, with a way around it.
- Something in your way? Write to accessibility@tripstory.fun. A person reads every message.
Our commitment
We want everyone to be able to turn their photos into a story, and to read, watch and share the stories other people make. Accessibility is part of how TripStory is designed and built, not an add-on.
We don’t use an accessibility overlay or a toolbar widget. When something is hard to use, we fix the product itself.
The standard we meet
Our target is conformance with the Web Content Accessibility Guidelines (WCAG 2.2 (opens in a new tab)) at level AA, in full, on everything listed under “What this statement covers”.
Beyond AA, we also meet these level AAA criteria where the product can:
- Contrast of 7:1 for text, through the High contrast theme (1.4.6)
- Main controls at least 44 by 44 pixels (2.5.5)
- A strong, always visible focus indicator (2.4.13)
- No time limits anywhere (2.2.3)
- No motion from interactions when you ask for reduced motion (2.3.3)
- Links that say where they go on their own (2.4.9)
- A heading for every section (2.4.10)
- Signing in without a memory test or a puzzle (3.3.9)
- For the film: a description of every scene, with the film waiting while a longer one is read (1.2.7), and a full written version (1.2.8)
This meets the Israeli Standard IS 5568, which adopts WCAG at level AA, as the Equal Rights for Persons with Disabilities (Service Accessibility Adjustments) Regulations, 2013, require in regulation 35, and the European standard EN 301 549 v3.2.1 (clause 9 for web pages, clause 10 for documents such as the PDF book, clause 11 for the app).
Conformance status: partially conformant. TripStory conforms with WCAG 2.2 AA except for the items under “Known limitations”, each of which has an accessible alternative.
What this statement covers
This statement covers everything people outside our team use:
- The website, tripstory.fun, in English and Hebrew: every page, including pricing, examples, the partner program and the legal pages.
- The app, app.tripstory.fun: signing in and creating an account, your library, making a trip (you can choose photos with a button as well as drop them), the building view, the story editor, the map, the film, versions, people, your account, checkout, gifts and invitations.
- Journey pages, the sample trip and its replay, and public profiles.
- The partner portal.
- Our emails, in English and Hebrew.
- The film and the PDF book made from each trip.
It doesn’t cover the admin console our own team uses.
What we built in
- Keyboard. Everything works with a keyboard alone, in a logical order, with a clearly visible focus ring. A “Skip to content” link starts every page, and focus is never hidden under a sticky bar.
- Structure. Pages are built from real headings, landmarks, lists and tables, so screen readers can move around them. Every page says its language, Hebrew pages read right to left, and words in another language are marked.
- Themes. Light, dark and high contrast. High contrast raises text to at least 7:1, drops see-through effects and outlines every control. Until you choose, it follows your system’s contrast setting, and Windows high contrast (forced colors) works too.
- Motion. “Pause motion”, at the start and in the footer of every page of the website (and “Reduce motion” in the app’s display menu), stops animations, videos that play by themselves and scrolling effects. It is already on when your system asks for reduced motion. Nothing flashes.
- Text size. Text follows your browser’s font size and can grow to 200%, and the page can be zoomed to 400%, without losing anything or scrolling sideways. Your own letter, word and line spacing keeps working.
- Forms. Every field has a visible label and says when it is required. Errors are written out next to the field, with a suggestion for fixing them. Nothing is timed.
- Signing in. No puzzles and no codes to copy: sign in with your email and a password (your password manager can fill it in, and pasting works), show the password to check what you typed, reset it by email, or use your Google account.
- Photos, maps and films. Photos have text descriptions. Every map comes with its places as a list, in order. Films have captions (the music and every spoken line), a descriptions track that says what each scene shows (while it is on, the film waits for a longer description to be read), a written version of the whole film and full keyboard controls.
- Emails. Real text, not pictures: they say their language, meet 7:1 contrast, read well with images turned off and link to this statement.
How we test
What we check, and how:
- Automated checks with axe-core (every WCAG 2.2 A and AA rule, and in the high contrast theme the AAA contrast rules too): every page of the website, in English and Hebrew, in every theme, at phone and desktop widths (320 or 390, and 1440 pixels), with text at 200% and zoomed to 400%, with a keyboard walk through every page that fails on any control without a name or hidden from screen readers, and a check that no control of a header or a menu is pushed off the screen; the app’s sign-in, sample trip, story editor and journey page, and every page of the partner portal, the same way; and every email at 320 pixels. They run on every change to the code and stop a release on any serious problem.
- Contrast measured on the rendered pages, pixel by pixel against what is really behind the text (photos, gradients), not only from our colour tokens.
- Keyboard walks through every page and flow: the order, the visible focus, nothing covered by a sticky bar, no traps.
- The accessibility tree, which is what screen readers read (names, roles, states and announcements), inspected for every interactive part.
- Zoom at 200% and 400%, text-only zoom, the WCAG text spacing settings, Windows high contrast, the contrast preference and reduced motion.
- Emails in light and dark mode and at phone width; the film’s captions and descriptions against its timeline, and in both film players in a real browser on every change; the PDF book’s text in reading order, and the contrast of its cover, measured on the photo itself.
We are adding hands-on testing with screen readers (NVDA on Windows, VoiceOver on Apple devices, TalkBack on Android) and with people who use them every day. If you use assistive technology and something doesn’t work, we especially want to hear from you.
Known limitations
These parts don’t fully meet the standard yet. Each comes with a way around it:
The PDF book
The tool we make PDFs with can’t add the tags that describe a PDF’s structure (headings, figures) to screen readers, so the book is an untagged PDF. It does carry its title, its language, its text in reading order and live links.
Alternative: the same story, photos and captions are on the journey page and in the app, fully accessible, and the book’s cover and last page link there. The last page of every book (and the cover of a private trip’s book, which has no public page) says where to ask for it in another format: write to us and we will send it.
Photo descriptions are written by AI
The descriptions of your photos and the places in them come from an AI model. They can be wrong, or miss what matters to you.
Alternative: you can correct any caption in the editor, and visitors can report one that is wrong.
The interactive map
The map itself is a picture (map tiles from OpenFreeMap and OpenStreetMap, with their own labels, often in the local language), so it can’t be explored with a screen reader.
Alternative: every place is also listed as text, in order, with its days and the distance to the next one.
Films made before 29 September 2026
Films cut before captions existed have no captions and no descriptions track until they are cut again.
Alternative: any change to the trip cuts its film again, with both; the story on the journey page tells the same trip in words.
Other companies’ windows
Google’s sign-in window and the payment provider’s checkout are made by those companies, not by us.
Alternative: signing in with your email and a password is always there, and we can take payment questions by email.
The password reset email
The email with a link to reset your password is sent by our sign-in provider (Google’s Firebase) from its own template. We ask for it in the language you use TripStory in, but it doesn’t follow our email design and doesn’t link to this statement yet.
Alternative: this statement and our accessibility mailbox are linked from every page of the app, the sign-in page included.
Feedback and contact
If something on TripStory is hard or impossible for you to use, or you need something in another format, tell us:
- Email accessibility@tripstory.fun.
- Or use the contact form and choose “Accessibility”.
It helps to know the page or the feature, what you were trying to do and, if you like, your device and the assistive technology you use. We reply as soon as we can, usually within a few working days, and tell you what we will change and when.
Accessibility coordinator: the TripStory team, accessibility@tripstory.fun.
If our answer doesn’t solve it: in Israel, you can contact the Commission for Equal Rights of Persons with Disabilities at the Ministry of Justice; in the European Union, the body that enforces accessibility law in your country.
About this statement
We prepared this statement on 29 September 2026 and last updated it on 30 September 2026, when we last reviewed the website, the app, the emails, the film and the book against WCAG 2.2. We review it with every major change, and at least once a year.
Our detailed conformance report, criterion by criterion, is available on request.