Accessibility
Accessibility is a build requirement here, not an afterthought.
This is enforced in our own build process on every project, not just promised in a proposal.
We treat WCAG and the POUR principles as the standard we build against on every project, not something applied at the end. Here is what that means in practice.
Perceivable
Text and background color combinations are checked against a minimum 4.5 to 1 contrast ratio before shipping. Content does not rely on color alone to communicate meaning or state.
Operable
Every interactive element is verified to show a visible keyboard focus state, confirmed directly through testing, not assumed. Every page is fully navigable by keyboard alone, confirmed the same way. Every animation and motion sequence respects a visitor's reduced motion preference, with a fully legible, static fallback.
Understandable
Semantic, correctly structured markup is used throughout. List elements are actual lists, headings follow a real hierarchy, not just visual styling made to look like one, so the structure a screen reader announces matches the structure a sighted visitor sees.
Robust
Every page is measured against a minimum Lighthouse accessibility score of 90 before it ships, enforced in the build pipeline as a real gate, not a manual check that can be skipped under deadline pressure.
See it, not just read it
Two of these practices, live on this page.
Reduced motion
Focus order
Tab through these to see the focus order and the visible focus state directly.
Where this is still being formalized
The automated gate you can see above (a minimum Lighthouse accessibility score of 90, contrast checks, reduced motion handling, and visible focus states) runs on every page today. That part is real and enforced.
Manual keyboard-only and screen reader walkthroughs, as a formal, repeatable QA step for every client project, are being built into our process now. We are stating that honestly rather than implying it is already a completed practice. We do not hold a formal WCAG certification. Certification is a distinct, third party audit status we have not obtained. What is true today is that WCAG and POUR are the framework we build against.
Reporting an issue
If you encounter an accessibility barrier anywhere on this site, tell us directly. Use the contact page and describe what you ran into.