Accessibility

Accessibility statement

We want this website to work for as many people as possible. Here is what we aim for, what we have checked, and how to tell us when we fall short.

Our aim

We design and build this website toward the Web Content Accessibility Guidelines (WCAG) 2.2 at level AA. That is a target, not a claim. This website has not been through an independent accessibility audit, and we do not state that it conforms to WCAG 2.2 AA.

What we have built in

  • Semantic page structure with landmarks, one main heading per page and a logical heading order.
  • A skip link and navigation that works with a keyboard, with visible focus indicators.
  • Text and interface colours chosen to meet WCAG contrast ratios.
  • Layouts that adapt to small screens, tested down to 320 pixels wide.
  • Reduced motion respected: animation is limited or removed if your device asks for it.
  • A contact form with labelled fields, clear error messages and status announcements for screen readers.

What we have tested

During development we ran automated checks with the axe-core testing engine on every page, at a phone width and a desktop width, and found no automatically detectable violations. Lighthouse accessibility audits also passed on the pages we sampled. These tools find only part of the possible problems.

We also tested with real keyboard presses on key pages: the order of focus, visible focus indicators, the navigation menu and its dropdowns, the question-and-answer sections, the project details overlay on the Work page and the contact form. We checked layouts from 320 to 1920 pixels wide, with text enlarged to 200%, with adjusted text spacing, and with scripts turned off.

We have not yet tested with screen readers, in Safari or Firefox, or with people who use assistive technology, and the site has not had an independent audit.

Known limitations

  • The images on the Work page are cropped screenshots and original illustrations with short text alternatives, not detailed descriptions.
  • The homepage window illustration includes a brief animation on load. It is decorative and is not shown moving if you prefer reduced motion.
  • The project details overlay uses the browser’s built-in dialog. It has been tested with real key presses and an automated scan, but not yet with screen readers or in Safari or Firefox.
  • Testing in Safari and Firefox, and with screen readers, has not been done yet.
  • Browser zoom beyond 200% has been checked only by simulating narrow screen widths.

Report a barrier

If something on this website is hard or impossible for you to use, please tell us. Use the contact form with the accessibility option already selected, or email openwindowcreative@gmail.com, and include:

  • The page address and what you were trying to do.
  • What went wrong, and the browser or assistive technology you were using, if you know it.
  • How you would like us to reply.

We will acknowledge your report and tell you what we plan to do about it.

Last updated

28 October 2026. We will revise this statement as testing progresses and as the website changes.