Declaration
Accessibility statement
This is the one page on the site whose subject is whether you can read it. So it is set large, ruled like the printed thing it is, and it says plainly what works, what does not yet, and how to tell us.
- Issued by
- Event Schedule LLC
- Standard cited
- WCAG 2.1 Level AA
- Last reviewed
- 2026-05-03
- Response target
- 10 business days
- Report a barrier
- [email protected]
Notice
This page is general service information, not legal advice. Laws and standards differ by country. Confirm your obligations with qualified counsel (for example Israel, EU, UK, or US).
Scope
This statement covers the marketing site and the Event Schedule web application (including logged-in tools and public schedule pages) operated under the primary Event Schedule domain and subdomains, unless stated otherwise.
Commitment
We are working to make Event Schedule usable for people with disabilities. We aim to improve alignment with the Web Content Accessibility Guidelines (WCAG), currently documented as WCAG 2.1 Level AA, and to respect guidance commonly associated with Israeli Standard 5568 where it applies to our services.
We also take into account common web accessibility practice associated with Israeli Standard 5568 where it applies to services we operate.
Standard cited WCAG 2.1 Level AA
Conformance status
We do not claim full WCAG conformance for every screen. Large interactive areas (including calendars, ticketing, and some legacy controls) are being reviewed and improved over time. This statement describes our good-faith approach and how to report problems.
The honest version of that sentence is further down: the areas we know are behind, named.
Measures we take
We provide skip links and document structure where implemented, a built-in accessibility panel for common display adjustments, keyboard-accessible paths as we identify gaps, and contrast-aware styling in parts of the product. We train support to route accessibility feedback.
Display adjustments, spelled out
The panel is a first-party control, not a third-party overlay: four settings and a reset, each one a single change you can see. Here is every one of them and exactly what it does.
Text size
Default, Larger, Largest
The two larger steps raise the root text size to 106.25% and then 112.5%, so the whole interface grows with the words instead of one block of copy reflowing on its own.
High contrast
On or off
Lays a contrast boost over the page so text and interface edges separate further from what is behind them.
Underline links
On or off
Underlines links so they are never identified by colour alone. Pill-shaped buttons are left as they are, because an underline there reads as a mistake.
Reduce motion
On or off
Cuts animation and transition durations to almost nothing and stops smooth scrolling, for anyone whose browser or system setting is not already asking for it.
Reset all
One action
Returns all four controls to their defaults in one go.
Where to find it: the panel appears on a schedule's public pages, its calendar and its event pages, and only where that schedule has switched it on, under Advanced settings when editing a schedule. It is off until somebody turns it on, and it carries a link straight back to this page. The setting is documented here.
Where those choices are kept
Your choices live in your own browser, on that one device, and are read back on your next visit. They are not sent to us and not attached to your account, so a shared or borrowed computer keeps its own settings rather than inheriting yours.
Signed-in visitors can also hide the panel itself if they do not want it in the corner, and switch it back on from their profile settings.
Structure, keyboard and focus
Four of those measures are true of this page, right now, and you can check every one without taking our word for it.
- Press Tab from the top and the first thing you reach is a skip link that jumps the whole navigation and lands on the page itself.
- Keep going and focus is drawn rather than implied: a three pixel outline, held three pixels clear of whatever it is around.
- Links are underlined, so nothing here is identified by colour alone, and the contents list above is a real ordered list of real anchors.
- Nothing in this statement is set below thirteen pixels, the clauses are one heading each in order, and the schedule of limitations further down is marked up as a table with real row and column headers, because it is a record.
And the contrast is measured rather than assumed. Every piece of text here was checked against whatever is painted behind it, in both colour schemes, and the weakest pairing on the page still clears the standard by a wide margin.
Third-party content and services
Parts of the service rely on third parties, including payment processing (for example Stripe), optional analytics, error reporting, embedded media or maps added by organizers, outbound links to social networks, and our blog which may be hosted on a separate domain. We cannot fully control the accessibility of third-party interfaces or user-generated content; we document limits here in good faith.
Known limitations (summary)
A declaration is only worth reading if it admits something. These are the areas we know are behind, and they are set out as a record rather than a paragraph so you can find yours quickly.
| Area | What may not work yet |
|---|---|
| Calendar views | Public and admin calendar views may not yet expose ideal keyboard semantics for every view mode. |
| Legacy menus and dialogs | Some legacy menus and dialogs may need improved focus management until migrated to newer patterns. |
| Organizer embeds and outbound links | Organizer-provided embeds, images without alternative text, and linked third-party sites may not be accessible. |
| Marketing video and audio | Marketing video or audio may not always include captions or transcripts. |
We periodically review core journeys with keyboard-only use and automated checks; we update this list when gaps are closed.
Feedback and requests
If you encounter an accessibility barrier, contact us at [email protected]. We aim to respond within 10 business days. Complex fixes may require more time; we will keep you informed when possible.
Updates
This page was last reviewed on 2026-05-03. We update it when material accessibility information or known limitations change.
Last reviewed 2026-05-03
Undertaking
If you hit a wall here, we would rather know than not.
A barrier is far easier to fix when somebody says where it was. Three lines is enough, and it does not have to be tidy.
- Where you were
- The page or the address, so we can open the same thing you had open.
- What you were trying to do
- And what happened instead, in as few words as you like.
- Browser and assistive technology
- The names, and the versions if you happen to know them.
Response target 10 business days
The set
The rest of the paperwork
Privacy Policy
What we collect, who can see it, and how to have it erased.
ReadTerms of Service
The agreement that covers your use of Event Schedule.
ReadAccessibility when you selfhost
Operators who run their own installation publish their own declaration. The configuration keys are here.
ReadContact
A form, if you would rather report a barrier that way, and everything else besides.
Read