Built for everyone to use.

Updated November 2, 2026

01What we aim for

We want everyone to be able to use page-page.com and the websites we build and run for our clients, including people who use a screen reader, a keyboard only, voice control, or a bigger text size. Our target is the WCAG 2.1 AA standard, the one most laws and courts point to.

02How we build

Every site we build gets the same care: text you can read against its background, a layout that works at any size and zoom level, every control reachable by keyboard, a label on every form field, a description on every image that matters, headings in a sensible order, and nothing that flashes. Our chat assistant, Penny, works by keyboard and with a screen reader too. We check these things before a site goes live and when we change it.

We do not use accessibility overlay widgets. They promise a quick fix and tend to get in the way. We fix the site itself instead.

03Tell us about a problem

If something on this site, or on a site we run, is hard for you to use, please tell us. Email [email protected] with the page address and what happened. We read every message, we will try to fix what is ours to fix, and we can send you the information another way in the meantime.

04What is outside our control

Some parts of a site are not ours. Content a client adds or sends us later, such as photos without descriptions or a PDF menu, is theirs to fix, and we help when they ask. Tools from other companies that a client asks us to include, like a booking widget or a map, follow those companies' own rules. We tell clients about these limits before launch and pick tools with care.

This statement describes what we aim for and how we work. It is not a certification. Questions: [email protected].