Your brand, checked for contrast, applied everywhere
The theme editor sets your logo, splash screen, colours and typography for an event, and those choices reach every screen an attendee sees. As you pick colours, each foreground and background pair is measured against the WCAG AA contrast threshold and the result is shown to you.
What this looks like in the product
The contrast result appears beside the colour, at the moment it can still be changed cheaply.
- One theme, every screen
- Logo, splash, colours and typography flow through the app, the browser event site and your email.
- WCAG AA contrast check
- Every colour pair is measured against the AA threshold and the result is surfaced as you edit.
- Advisory, never blocking
- The check warns and asks you to confirm. It has never blocked a save and it will not start.
- Live theme changes
- Publishing a theme change reaches attendees without an app update or a store review.
- Per-event themes
- An organisation running several events gives each one its own identity.
The theme editor
- Logo and splash screen
- Primary and accent colours
- Typography
- Contrast: this pair measures 3.1:1
- Confirm anyway, or adjust
The contrast check advises. It does not block.
This is a deliberate product decision and it is worth explaining, because a competitor could describe the same feature as enforcement and sound stronger.
A brand palette is not something an event organizer is allowed to change. It arrives from a brand team, it is in a guideline document, and the person setting up the app has no authority to darken it because a tool told them to. A checker that refuses to save would not produce an accessible app; it would produce an organizer who abandons the theme editor, ships the default colours, and loses the branding that was the reason to buy a branded app in the first place.
So the check measures every pair, shows the ratio, says plainly when a pair falls below AA, and asks the person to confirm. What that produces is an organizer who knows. Frequently they take the number back to the brand team, which is exactly the conversation that should be happening, and one that a blocked save would have ended in frustration instead.
We describe this as advisory everywhere, including here, because describing an advisory check as enforcement would be the kind of small dishonesty that a procurement team is right to punish.
What the check does
Measures every colour pair you set against the WCAG AA ratio and shows the result beside the swatch while you are still editing it.
What it never does
Block a save. A pair that falls short is flagged and confirmed, and the decision about your own brand stays yours.
What one theme reaches
- The mobile app
- Splash, navigation, headings, buttons and accents on every screen, on iOS and Android.
- The browser event site
- The same identity for attendees who did not install anything, so the two do not look like different events.
- Campaigns and invites carry the branding and a consistent signature footer, so the pre-event email and the app agree.
- Per event
- An agency or an organisation with several events themes each one separately rather than picking one house style for all of them.
Because the theme is served from the backend rather than compiled into a build, changing it is immediate. A colour corrected the night before the event is corrected for everyone, with no app update and no store review in the way.
Accessibility, stated at the level we can actually support
Contrast checking on themes is a real, shipped capability and it is the one we can describe precisely. It is not the same as a conformance claim for the whole product, and we are not going to imply otherwise.
What is true today: every theme colour pair is measured against WCAG AA and the result is surfaced to the person choosing the colours. What we do not have is a published VPAT, a third-party accessibility audit, or a WCAG conformance statement for the applications as a whole.
If your procurement process requires a VPAT or an independent audit report, ask us directly rather than inferring an answer from this page. That is the honest position, and it is more useful to a public-sector or association buyer than a vaguer claim would be.
For a buyer screening on accessibility: what we can evidence is the per-theme AA contrast check. We do not currently hold a VPAT or a third-party audit, and we would rather you learn that here than three weeks into an evaluation.
What theming will not do
- No layout changes. Colours, type and logo, not screen structure or tab order.
- No custom fonts uploaded from your brand kit beyond the typography options offered.
- No per-screen or per-session theming. A theme belongs to an event.
- No dark mode toggle themed separately.
- No CSS or code injection anywhere.
Who cares about this most
Organisations with a brand team that will review the app before it ships, which is most corporates and every agency's client. Associations and public-sector bodies, whose procurement screens on accessibility and who ask questions that deserve an accurate answer.
And, in practice, the person setting the theme at nine at night the week before the event, who benefits most from being told that their brand's light grey on white measures three to one before four hundred people have to read it.
Last updated
What it costs
- Free up to 50
- activated attendees, on one live event
- $5
- per activated attendee beyond 50
- $4,750
- the most one event can ever cost, whatever happens past 1,000
Activated means the person claimed their invite and opened the app. Not when you import them, not when the invite is delivered, and not if they register and stay home.
Questions people actually ask
Does the contrast check stop us saving a failing colour?
No, and it never has. It measures each pair, shows the ratio, says plainly when the pair is below WCAG AA, and asks you to confirm. Blocking the save would push organizers away from the theme editor entirely, which produces less accessible events rather than more. We describe it as advisory because that is what it is.
Is event67 WCAG AA conformant?
The theme contrast check is measured against WCAG AA and is a real, shipped capability. That is not the same as a conformance claim for the whole product, and we do not make one. There is no published VPAT and no third-party audit report today. If your procurement needs either, ask us rather than assuming.
Can we change the theme after the event has started?
Yes, immediately. The theme is served from the backend, so a correction reaches every attendee without an app update or a store review. This is the usual reason a theme gets fixed at eleven at night rather than lived with.
Can we use our own fonts?
Typography is chosen from the options the theme editor offers rather than by uploading a font from your brand kit. If exact typeface matching is a hard brand requirement, raise it before you commit.
Can one organisation run different themes for different events?
Yes. Themes belong to events, not to organisations, which is what makes the product workable for an agency running several clients or a company running an internal all-hands and a public user conference in the same quarter.
Keep reading
Features this shapes
Event types that lean on this
See it in your own event
Your first 50 attendees are free on every event, so the smallest version of this costs nothing to try.