Accessibility Statement

The standard I target

This site is built to meet Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. WCAG is the international consensus standard for web accessibility and is the standard most commonly referenced in U.S. accessibility law and industry practice.

I treat WCAG 2.1 AA as a launch requirement and an ongoing discipline — not a one-time checkbox.

What that looks like in practice

The site is designed and built with the following accessibility characteristics:

• Keyboard navigation works for every interactive element on every page. Tab order follows a logical reading order, focus is visible, and Escape closes overlays.
• Screen-reader compatibility through semantic HTML — proper heading hierarchy, descriptive link text, alt text on meaningful images, and ARIA attributes where native semantics are insufficient.
• Color contrast meets or exceeds WCAG AA ratios (4.5:1 for body text, 3:1 for large text and UI components). Color is never the sole means of conveying information.
• Reduced motion is honored — animations and smooth-scroll respect the prefers-reduced-motion browser setting.
• Text scaling works without breaking the layout when the browser is zoomed up to 200%.
• Forms include visible labels, associated error messages, plain-language validation, and accessible consent checkboxes that are operable by keyboard and screen reader.

What I do not claim

To be straightforward about the limits of this statement:

• This site has not yet been audited by an independent third-party accessibility specialist. A third-party audit is on the post-launch roadmap.
• I do not claim certification under any specific accessibility certification scheme.
• Some third-party content (for example, embedded maps, scheduling tools, or carrier portals) may not fully conform to WCAG 2.1 AA. Where third-party content is used, I will note known limitations and provide an accessible alternative path where possible.

Known limitations

None at launch.

[REVIEW: confirm "none at launch" claim during compliance review; update if any limitation is identified]

Reporting an accessibility issue

If something on this site doesn't work for you, please let me know. Accessibility issues are treated as real bugs, not feature requests.

Email [email protected] with:

• A short description of what you encountered
• The page URL where it happened
• The device, browser, and assistive technology you were using (if you know)

I'll respond within a reasonable timeframe and work to resolve the issue. There is no specific service-level guarantee, but I take this seriously.

How I review accessibility ongoing

The site is checked against accessibility requirements at multiple points:

• Automated checks (axe-core or equivalent) run during development to catch common violations.
• Manual keyboard and screen-reader spot-checks happen before substantive page changes are merged.
• A third-party accessibility audit is planned for 3–6 months after launch, once content has stabilized. Findings from that audit will be incorporated and this statement will be updated.

Changes to this statement

I may update this Accessibility Statement as the site evolves and as I learn more from audits, user feedback, and changes to the standards I follow. The version and "Last reviewed" date at the top of this page reflect the current revision.