We want everyone to be able to use Tiki-Toki and the timelines people make with it. Our target is the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA, and the parts of the site listed below partially meet it.
What this statement covers
- Published timelines, viewed on tiki-toki.com or embedded on another website, with the WCAG option turned on.
- Signing up and logging in, the account page, and the timeline editor (new and classic).
- The home page and the FAQs.
We are still reviewing the other pages on tiki-toki.com, such as the blog. This statement will be updated as they are done.
How accessible it is
In the parts covered, you can:
- use everything with a keyboard, with a visible focus ring and skip links past menus and long lists
- browse a timeline's stories as a list, including in the 3D view
- zoom to 400% or use a narrow window without content being cut off
- read text that meets contrast minimums, including over the colours and pictures timeline authors choose
- turn off motion and pause auto-play
Known limitations
- We have not yet tested with screen readers, or in browsers other than Chromium, the engine behind Chrome.
- Alt text, video captions and audio transcripts in a timeline are written by its author. We prompt authors to add them, but cannot check them.
- Map stories and the old Flash media player are not covered.
- On the account page, an unreadable date is replaced by “Not a valid date”, so you need to type it again.
- At very narrow widths, the classic editor's Help panel goes off screen. The new editor does not have this problem.
Detailed reports
Two Accessibility Conformance Reports (VPAT® 2.5) give criterion-by-criterion results:
Feedback and contact
If something on Tiki-Toki is hard to use, or you need content in another format, email hello@tiki-toki.com. Tell us the page or timeline and what went wrong.
How we tested
Webalon assessed these parts of Tiki-Toki itself in October 2026, with automated checks (axe-core, WCAG 2.2 A and AA rules), keyboard-only testing, contrast measurement, and zoom and narrow-window checks, in Chromium. No independent audit has been done yet.
This statement was prepared on 21 October 2026.