Accessibility
Last reviewed August 19, 2026.
What we are aiming for
WCAG 2.2, Level AA. That is the goal, and we are not there yet. This page says where we actually are, because a claim we cannot back is worse than no claim — the first person to hit a barrier would have been told it would not happen.
What this covers
The pages on ofuexchange.net. It does not cover services we do not run: ticketing happens on Events.com, the newsletter on Mailchimp, and sessions on whatever platform each host picks. We have no standing to vouch for those, so we do not.
How we test
Automated checks run on every change: axe against each part of the site, and a contrast check computed from the design itself so a visual tweak cannot quietly make text unreadable. That catches perhaps a third of what matters. The rest needs a person, and where we have not done that yet, it is listed below.
Fixed on August 19, 2026
- Skip-to-content link, so a keyboard user does not tab through the header on every page
- Reduced-motion support — animations stop when your system asks for that
- Muted body text raised to 4.5:1 on every background it appears on
- Focus indicator raised to 3:1, so you can see where you are
- Form field borders raised to 3:1, so you can see where a field is
- Named the mobile menu button and the social links, which were unlabelled
- Fixed a heading level that skipped, and an unlabelled table header
- Focus no longer lands behind the fixed header when you tab down a page
Known problems
- No screen-reader pass yet
- Automated tools catch roughly a third of accessibility problems. The rest needs a person with a screen reader, and we have not done that pass. The block schedule table is the part we are least sure about.
- Zoom and reflow untested
- We have not verified the site at 200% zoom or at a 320-pixel width. The schedule table is again the likely weak point.
- Blog posts depend on their authors
- Images in posts require alt text at the point of writing, but the quality of a description is a human judgment. If you find one that is unhelpful, tell us and we will fix that post.
- Session tools are not ours
- During the event, sessions run on whatever platform the host chooses. We ask hosts to enable captions where their tool supports it, and the schedule names the tool so you can check it against what you use — but we cannot make a promise about software we do not control.
Tell us
If something here does not work for you, write to hello@ofuexchange.net. Describe what happened and what you were using; you do not need to know the technical name for it. We will tell you what we can do and when.
We are also planning a pre-event session on making online events accessible. A fair number of our participants practice this better than we do, and we would rather design the rest of this with them than guess.