Accessibility

A portfolio is worth nothing if people cannot get into it. This site aims to meet the Web Content Accessibility Guidelines 2.2 at Level AA, and is built and tested with that target in mind rather than retrofitted afterwards.

• Keyboard access — every link, button, form field and filter is reachable and operable with a keyboard alone, in a logical order, with a visible focus ring. A skip link jumps straight past the navigation to the main content.
• Screen readers — pages use real landmarks and one descriptive heading level per section, images carry alternative text unless they are purely decorative, and form errors are announced rather than only shown in colour.
• Contrast and text — body and interface text meets the 4.5:1 contrast minimum, and the layout reflows without loss of content when text is enlarged to 200% or the window is narrowed to a phone width.
• Motion — animation is limited to short, purposeful transitions, and all of it is disabled automatically when your system is set to reduce motion. Nothing autoplays with sound.
• Forms — every field has a persistent visible label, required fields are marked in text, and validation messages say what to do rather than only that something is wrong.
• Touch targets — interactive elements are sized for a thumb, which is how most people will actually reach this site.

Being honest about the gaps is more useful than claiming perfection:

• Photography and film are inherently visual. Alternative text describes each image, but it cannot fully substitute for seeing the work — if you would like a written description of a particular project, ask and one will be written for you.
• Video captions are being added across the back catalogue. New films ship with captions from the start.
• Third-party embeds, such as a booking calendar, are outside direct control. Where one presents a barrier, the same task can always be completed by email or WhatsApp instead.

Automated checks run against the accessibility tree during development, and pages are manually walked through with a keyboard only and with a screen reader. Automated tools catch perhaps a third of real problems, so the manual pass is the one that matters.

If something here blocked you, please say so — it will be treated as a bug, not a suggestion. Tell me the page, what you were trying to do, and the browser or assistive technology you were using, and you will get a reply within five working days with either a fix or a date for one.

Use the contact details published in the site footer.