Disciplines / Performance & accessibility
Built for Real People.
Responsive / WCAG 2.2 / Core Web Vitals / Real devices
Pages that load fast and work for everyone.
01 / The principleFast / Readable / Operable
Fast / and usable
Performance is
a design decision.
How fast a page loads and whether it works with a keyboard are decided early, mostly by the layout. Fixing them at the end costs far more, so I deal with them from the first sketch.
02 / Quality dimensionsThree things
What people notice first.
01
Clear to read.
Enough contrast, readable type, and not too much crammed onto a small screen.
02
Easy to operate.
Everything reachable by keyboard, a visible focus ring, and controls that say what happened.
03
Fast to respond.
Small files, little JavaScript, and taps that respond straight away.
03 / Built into the workFour checks
Checked on every page.
01
Design
Contrast, focus states, and text that can be enlarged without breaking the layout.
02
Development
Light images, form fields with proper labels, page landmarks and clear error messages.
03
Testing
Every width from 320 px up, the whole site by keyboard only, and a slow connection.
04
Monitoring
Real-user numbers after launch, so a page that gets slower is noticed and fixed.
04 / Quality is visibleTwo very different sites
Different readers, same rules.
An engineer reading a technical spec and someone browsing a stylist’s site want different things. Both need clear navigation, text they can read, and pages that respond quickly.
Read the standards
05 / Beyond the metricOn Lighthouse scores
A score / is a hint
A perfect score
is not the whole story.
Automated audits catch only part of the accessibility problems. The rest needs someone to try the page with a keyboard and a screen reader, and to read the text. I aim for 100 in Lighthouse, but I don’t treat it as proof.
Start something worthwhile / 2026
Built to Work for More.
Send me a page that feels slow or awkward and I’ll tell you why.
Start a project