Accessibility

Everyone on the list gets to the door.

Evorrah holds itself to WCAG 2.2, Level AA across the public site, the client portal, the guest pages and the mail we send on your behalf. We measure it with instruments that run in this repository rather than with a certificate somebody issued once. Below is the standard, what we actually measure, what we know is not there yet, and the address to write to if something stands between you and your event.

01 · The standard

WCAG 2.2, Level AA — and the same standard behind the login.

The conformance target for every Evorrah surface is the Web Content Accessibility Guidelines 2.2 at Level AA. That includes the parts of the product most companies leave unmeasured: the rooms a client sees after signing in, the page a guest opens from an invitation, and the emails themselves.

We say substantially conformant rather than conformant, and section 03 says exactly why. A statement that claims more than its own measurements support is worth nothing to the person relying on it.

02 · What is measured

Every surface has an instrument, and the instrument is the record.

Each one runs axe-core against the WCAG 2.0, 2.1 and 2.2 A and AA rule sets, at a phone width and a desktop width, and each writes a machine-readable record naming the exact version of the code it measured. A surface that drifts away from its record turns the build red.

SurfaceWhat is measuredHow
The public websiteConformance, colour contrast, focus visibility, reflow at 320 pxEvery page, on every change
The client portalConformance, target size, focus rings measured in pixels, what a screen reader is givenEvery room and sub-view, on three browser engines
The guest RSVP pageConformance, keyboard operability, every control namedThe whole reply, start to finish
The guest event pageConformance, landmarks, skip link, target sizeBoth widths, against a live page
The AcademyConformance and target size across all eighteen guidesBoth widths
The invitation and the mailContrast in light and dark, image alt text, heading structureEvery builder we send
03 · What is not there yet

The four things we know fall short, stated plainly.

These are findings from our own measurements, not a disclaimer. Each one is recorded, each one is being worked on, and none of them should stop you asking us to do something a different way in the meantime.

Text size on the public site

Browser page zoom works. A text-only setting does not.

The public website sets its type in fixed pixel sizes, so enlarging text only in a browser's settings does not change it. Enlarging the whole page does, and we hold the layout at 200% and at 400% zoom with nothing lost and nothing to scroll sideways for. The portal and the RSVP page do respond to a text-only setting.

Touch targets

Some controls meet the standard without meeting our own floor.

WCAG 2.2 AA asks for 24 × 24 CSS pixels and every control meets it. We set ourselves a more comfortable 44 × 44 floor, and a number of secondary links — footer rows, the skip link, some Academy navigation — sit between the two.

Heading order

A few screens skip a heading level.

Twelve places in the client portal move from one heading level to another without the level in between. Every screen still has exactly one page heading and a visible landmark structure, but somebody navigating by headings will find a gap.

Testing with real assistive technology

Measured by machine and by keyboard, not yet audited by a daily screen-reader user.

We run axe-core, a real keyboard walk and a reading of the accessibility tree on Chromium, Firefox and WebKit. What we have not yet done is a review by somebody who uses JAWS, NVDA or VoiceOver every day. That is a gap in the evidence, and we would rather say so.

04 · Ask us

If something is in your way, write to us and say so.

Write to hello@evorrah.com and put Accessibility in the subject. Tell us what you were trying to do, the page or the email it happened on, and what you use to browse — a screen reader, magnification, a keyboard alone, voice control. A person reads it, and we will tell you what we find either way.

  • If you are a guest and the RSVP page is not working for you, we can take your reply by email and record it for the host.
  • If you are a client, we can send anything in the portal — the guest list, a proof, a door list — in a plain, readable format instead.
  • If you need a design produced in larger type, higher contrast or a different format for your own event, ask before the piece is approved and it costs nothing extra.
05 · How this page stays true

It is written against the records, and the records name their commit.

Every claim above corresponds to a measurement stored with the version of the code it measured. When a surface changes, its instrument is re-run and this page is reviewed against the new record — which is why sections 02 and 03 are specific enough to be wrong, and therefore specific enough to be checked.

Prepared 14 September 2026. Reviewed whenever a surface named in section 02 changes.

We use cookies and local storage to improve your experience and measure how the site performs. See our Privacy Policy.