Accessibility
What works, and what we have not tested.
We want this site to be usable by everyone who lands on it. This page sets out what has been done, what has not been checked, and what to do if you hit something that does not work.
What we aim at
The Web Content Accessibility Guidelines, version 2.2, at level AA. That is the target the site is built against.
It is a target rather than a claim. This site has not been independently audited, and we are not going to tell you it conforms when nobody outside the studio has tested it.
What has been done
- Text and background contrast is measured rather than eyeballed, in both light and dark, and every piece of body and interface text meets the AA ratio.
- The site can be operated by keyboard. Focus is visible, focus order follows the page, and nothing traps you: the small-screen menu closes on Escape and returns focus to the control that opened it.
- If your system asks for reduced motion, the site honours it. Animation and transitions are suppressed, and the entrance shows a single still drawing instead of a sequence.
- Headings run in order and describe the section beneath them, so the page can be navigated by heading.
- The drawings are decorative and are marked as such, so a screen reader passes over them rather than reading out geometry.
- The typeface is served from this site rather than a font service, and text remains selectable and resizable. Nothing is an image of text.
- Colour is never the only thing carrying meaning.
- With JavaScript unavailable the page still renders in full, rather than leaving content invisible.
What we know is not ideal
The site opens with an entrance that covers the page on a first visit. It is a labelled dialog with a single control, and it is replaced by a still image if you have asked for reduced motion, but it is still something between you and the site that most sites do not have.
The line drawings carry meaning at a glance that their surrounding copy has to carry in words. We believe the copy stands alone, but that is our judgement, not a tested finding.
The site has not been tested with every combination of screen reader and browser, and it has not been reviewed by anyone who relies on assistive technology day to day.
Tell us when it does not work
If something on this site is difficult or impossible to use, write to hello@officestud.io and say what you were trying to do, what happened, and what you were using. A rough description is fine; you do not need to identify the standard it breaches.
We will reply within five working days, tell you plainly whether it is something we can fix, and give you a date if it is. If we cannot fix it quickly, we will find another way to get you what you came for.
Why this page exists
Office Studio's argument is that a website is part of how a business works, not decoration on top of it. A site that cannot be used by some of the people it is meant to serve is a system with a fault in it, whatever it looks like.
This page was last updated on 28 July 2026.