Accessibility

We want this site to be usable by everyone, and we would rather say plainly where it stands than claim a certificate we do not have. We aim at WCAG 2.1 Level AA. We have not been formally audited against it.

What we have actually done

• The site is written as HTML with real headings, landmarks and lists, so a screen reader gets a structure rather than a wall of divs.
• Every page starts with a "Skip to content" link, and the whole site can be operated from the keyboard with a visible focus outline on everything focusable.
• Body text is a pale bone on a dark warm ground, chosen to clear the AA contrast threshold. Type over photographs sits on a scrim rather than on luck.
• Photographs of our work carry real alt text describing the building. Decorative and atmospheric images carry empty alt text so they are skipped rather than announced - the difference is enforced by the build, not left to memory.
• Form fields have real labels, errors are announced politely as they happen, and inputs are set at 16px so iOS does not zoom the page when you tap one.
• Tap targets are sized to the 24px minimum in WCAG 2.2, including the small monospace links in the header and footer.
• Reduced motion is respected everywhere. If your system asks for reduced motion, transitions are dropped and the animated landscape on the home page does not run at all - the script checks before it starts rather than animating and then apologising.

Where we know it falls short

• The home page is a scroll-driven landscape. Under reduced motion it becomes a static page, and every destination in it is reachable from the menu, but it is still the least conventional page here and the one most likely to give trouble. If it does, /studio and /work carry the same material in an ordinary layout.
• Our checks so far have been keyboard navigation, contrast, and reading the markup. We have not tested this site against a range of screen readers and assistive technology, and until we have, treat the standard above as what we are building toward rather than something we have proven.

Tell us when it does not work

This is the part we actually want. If something on this site is difficult or impossible to use, email brian@offsite.camp and say what page it was and what happened. A person reads it. We will reply within a few working days, and if you need something here in another format - a document, a plain-text version of a page - ask and we will send it.