Skip to content

Legal

Accessibility

Our commitment to making paytech.studio usable by as many people as possible, however they browse.

Last updated

PayTech Studio wants this site to be usable by everyone, including people who rely on a screen reader, navigate by keyboard, browse at high zoom or reduced contrast, or use switch or voice control software. Accessibility is something we design and build for, not something added afterwards.

Conformance target

We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA across the site. These guidelines explain how to make web content more accessible to people with a wide range of disabilities, and are the standard most commonly referenced by accessibility law worldwide.

What we do

  • Semantic, structured markup with a logical heading order and a "skip to content" link on every page.
  • Colour combinations checked for sufficient contrast against both dark and light content.
  • Interactive elements — links, buttons and form fields — reachable and operable by keyboard alone, with a visible focus state.
  • Text that reflows and remains readable when zoomed or resized, rather than relying on fixed layouts.
  • Motion and animation kept subtle, and reduced further for visitors whose system is set to prefer reduced motion.
  • Meaningful alternative text on informative images, and decorative graphics hidden from assistive technology.

Known limitations

We test the site regularly, but some areas may not yet fully meet this standard — for example, third-party embeds we do not control, or older content published before an accessibility issue was identified. Where we know of a limitation, we prioritise fixing it and note it here until it is resolved.

Feedback

If you find any part of this site difficult to use, or need information on it in a different format, please tell us. We aim to respond within five working days and to agree a reasonable timescale for putting things right.

Contact us

Email hello@paytech.studio with "Accessibility" in the subject line, including the page you were on and the assistive technology you were using, if relevant — it helps us reproduce and fix the issue faster.

Build with us

Run into an accessibility issue?

Tell us where you are heading and we will help you find the right shape, team and pace to get there.