Accessibility statement.
What this site does to be usable by everyone, what still falls short, and how to tell me when something gets in your way.
The short version. I want this site to work for everyone, including people using a screen reader, a keyboard, magnification, or reduced motion. Most of it does. A few things don't yet, and rather than claim otherwise, they're listed below by name.
What I'm aiming for
The standard is WCAG 2.2 Level AA — the widely used international benchmark for web accessibility. This site is partially conformant: most of it meets that bar, and the specific places it doesn't are named further down.
I'd rather publish an honest account with gaps in it than a confident one that isn't true. If you find something not on this list, I want to hear about it.
What's in place
These were checked page by page across the site:
- A skip link on every page, so keyboard users can jump straight past the navigation to the content.
- Proper page structure — one main heading per page, a correctly marked main content area, and a declared page language, so screen readers can navigate and pronounce things correctly.
- Every image has alt text. Decorative images are deliberately marked as such so screen readers skip them instead of reading out noise.
- Every form field has a visible label — not just placeholder text, which disappears as soon as you start typing.
- Keyboard navigation works throughout. Menus open on keyboard focus, not only on hover, and focus stays visible as you move through the page.
- Text meets or exceeds the contrast standard — main body text measures about 9:1 against the background and headings about 14:1, well past the 4.5:1 required. Peach accent text was corrected in August 2026 and now passes too; see below.
- You can zoom. Nothing locks the page scale, so pinch-zoom and browser zoom both work.
- Motion can be turned off — see below.
Movement and animation
There's a fair amount of gentle motion here — scrolling banners, photographs that drift slowly, text that fades in as you scroll. All of it respects your system's "reduce motion" setting. Turn that on in your operating system and the animations stop: banners hold still, photos stop drifting, and content simply appears rather than sliding in.
Nothing on this site flashes, strobes, or plays audio on its own.
Fixed since this page first went up
This statement originally listed two contrast failures. Both have been corrected, and the numbers are here so the claim is checkable rather than just asserted:
- Accent text. The peach used for small labels measured 2.66:1 and the highlighted word in headings measured 2.01:1 — both below standard. Small accent text is now 4.86:1, which passes at any size, and the large heading accents are 3.56:1, which passes the bar that display-size text has to meet.
- A secondary grey used for introductory lines was 4.34:1, just under. It is now 5.07:1.
Peach is still peach where it can't cause a problem — as background fills, borders, and on the dark footer, where it was already well clear of the standard and darkening it would have made things worse. What changed is peach used as type on a light background.
Where it still falls short
One known issue:
The speaker kit page
The speaker kit is exported from a different tool rather than hand-built like the rest of the site. As a result it's missing a skip link, a main landmark, and a declared page language. It's a supporting document rather than a main page, but it's the weakest page here for assistive technology, and rebuilding it properly is the fix.
How this was checked
This is a self-assessment, not a certified audit. I reviewed the site's structure, headings, alt text, form labels, keyboard behavior, motion settings, and measured color contrast directly. No independent accessibility firm has reviewed it, and it has not been tested by people who use assistive technology day to day — which is the most valuable kind of testing, and something I'd welcome.
If something doesn't work for you
Please tell me. You don't need to know the technical term for the problem, and you don't need to be polite about it — "I couldn't read this" or "I couldn't get past this with my keyboard" is genuinely enough to act on.
Email angie@angiecarel.com and say what page you were on and what happened. I'll reply, and if you need the information in another format — plain text, a document, or just me telling you over a call — I'll get it to you that way.
Angie Carel — Fort Wayne, Indiana. See also the privacy policy and terms of use.