Accessibility
Chambers serve everyone in their business community, so Pilaster has to work for everyone too: the staff who run it, and the members who use the portal.
The standard we aim for
We aim for WCAG 2.2 at level AA across this website, the staff app and the member portal. This is our own assessment: Pilaster hasn't been audited by an outside party, and we'd rather tell you that than imply otherwise.
What we do
- Pages are built from real headings, lists, tables and form labels, so screen readers can find their way around.
- We build for keyboard use: every control is meant to be reachable without a mouse, and the focused one is always visible. If you find one that isn't, that's a bug we want to hear about.
- Text and controls are checked for contrast against their backgrounds.
- If you've asked your device to reduce motion, animation is turned off.
- Controls you can't use aren't hidden: they're shown disabled, with the reason given.
- Pages are built to work at any width and when zoomed, from a phone to a large monitor.
- Images that carry information have text descriptions.
Known gaps
- The screenshots of the app on our home page are images. Their description says what they show, but not every detail in them.
- Some parts come from other companies and follow their own accessibility work: the spam check on public forms (Cloudflare Turnstile) and the card payment pages (Stripe).
- When the member portal appears inside a chamber's own website, the rest of that website is the chamber's.
Tell us about a problem
If something in Pilaster is hard or impossible for you to use, email support@pilaster.business. Tell us the page and what happened, and if it's urgent (renewing, registering for an event), we'll help you get it done another way while we fix it.