Accessibility
Parker AI should work for everyone. I build to the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA and treat accessibility as part of quality, not an afterthought.
Last reviewed:
What's in place
- • Semantic HTML with a logical heading structure and landmarks.
- • Full keyboard operability with a visible focus indicator in both themes.
- • A skip link and a dismissible mobile menu that manages focus.
- • Color contrast targeted at WCAG AA; color is never the only signal.
- • Labeled form fields, announced errors, and honest copy in plain language.
- • Respect for the “reduce motion” system preference.
- • A dark theme option alongside the light default.
Known limitations
I review accessibility by hand and design to WCAG 2.2 AA, but there's been no formal independent audit yet, so some issues may remain. The booking calendar is an embedded third party tool (Cal.com) whose internals I don't control. If it gives you trouble, the written form on the contact page books a call just as well, or email me directly.
Run into a barrier?
Tell me and I'll help you get what you needed in the meantime. I acknowledge accessibility reports within one business day; if the fix takes longer, I'll send a progress update or a practical workaround. Email hello@getparkerai.com with the page and what went wrong.