AI Headshots is committed to ensuring that aiheadshots.ai and app.aiheadshots.ai are accessible to people with disabilities. We work to align with the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA as the international benchmark, and we comply with applicable US laws including the Americans with Disabilities Act (ADA) and Section 508.
What we do
- Semantic HTML throughout. Headings, landmarks, lists, and forms use the correct elements so screen readers announce content meaningfully.
- Keyboard-navigable. Every interactive element (links, buttons, the dropdown nav, the audience pill, the before/after slider, every form) is reachable and operable by keyboard. Tab order follows the visual reading order.
- Color contrast. Body text + primary controls target a contrast ratio of 4.5:1 minimum (per WCAG AA). Large headlines target 3:1 minimum.
- Focus indicators. Visible focus rings on every interactive control. Never hidden behind
outline: nonewithout a replacement. - Alt text on every photographic asset. Decorative images use empty alt attributes; meaningful images carry descriptive text.
- ARIA where semantic HTML isn't enough. The audience switcher, the dropdown menus, the before/after slider, the tabs in the Product mock, the Teams pricing toggle, and all form errors carry appropriate ARIA roles and live-region announcements.
- Reduced motion respected. The hero marquee, the scroll reveals, the before/after sweep — all of them check
prefers-reduced-motionand disable animation when set. - Resizable text. The whole site scales cleanly up to 200% browser zoom without horizontal scrolling or content loss.
Tested with
- VoiceOver (macOS, iOS)
- NVDA + JAWS (Windows)
- Chrome, Safari, Firefox, Edge — keyboard-only navigation
- iOS Voice Control and Switch Control
- Automated audits: axe-core, Lighthouse Accessibility, Pa11y
Known limitations
We're a small team and we're honest about where we still have work to do:
- The interactive Product dashboard mock at /product uses synthetic chrome that mimics our real app. The mock is semantically labeled but isn't a fully accessible application surface.
- A few embedded videos and animated bento cards don't yet have captioned alternatives. We're adding them quarterly.
- The blog content in /blog is reviewed manually for heading order and alt text, but historical posts may still have minor issues we're working through.
If you encounter an accessibility issue we haven't listed here, please report it. We treat accessibility bugs the same as functional bugs — they ship in our regular release cycle.
How to report an issue
Email contact@thestudiopod.com with the subject line “Accessibility.” Include:
- The page URL where you encountered the issue
- The assistive technology you're using (if applicable)
- A description of what you expected vs. what happened
We acknowledge accessibility reports within 24 hours and respond with a fix or remediation plan within five business days.
Alternative formats
If you need information from this site in an alternative format — large print, screen-reader-friendly document, plain-text email — we'll send it to you. Just ask.
Compliance status
We self-assess as partially conformant with WCAG 2.1 Level AA. “Partially conformant” means that most of our pages meet the standard, with a small set of identified issues (listed above) that we're actively remediating.
Our target: full WCAG 2.1 AA conformance by end of Q4 2026.
Contact
Joseph West · Founder · AI Headshots by Studio Pod
Email: contact@thestudiopod.com
Based in Houston, Texas.



.png)