Accessibility

Draft — for review before publishing. This is review-ready draft copy prepared by the Astoundz team. Before it goes live, the “what we've done so far” list below must be checked against a real keyboard, screen-reader, and contrast pass of the built site, and every [PLACEHOLDER] filled in. Nothing here claims full conformance, and it should not, until it has been tested.

Last updated: [PLACEHOLDER: date to be set on the day this is approved and published]

This site is about voices being heard. It would be a strange thing to build one that shuts people out.

So accessibility isn't a box we check once before launch and forget. It's part of how every new page, form, and section gets built and reviewed here — the same discipline as checking a page for a broken link or a typo, not a separate, optional pass.

What we're aiming for

We're working toward the Web Content Accessibility Guidelines (WCAG) 2.1, Level AA. We're not claiming we've arrived — we're telling you where we're headed and inviting you to hold us to it.

What we've done so far

• The site is built to work with a keyboard alone, and with screen readers.
• Text and background colors are checked for contrast — including the small print. Especially the small print.
• Every image that carries meaning has a written description.
• Headings are in real order, so you can navigate by structure instead of hunting.
• Motion is gentle by default, and if your device asks for reduced motion, the animation stops.
• There's a “skip to content” link at the top of every page.
• We don't use an accessibility overlay widget. They tend to get in the way more than they help.

[PLACEHOLDER: before publish, run a manual keyboard + screen-reader + contrast pass and confirm this list matches what the build actually ships — delete any line that isn't true on launch day.]

Where we know we fall short

Some parts of this site embed things other companies built, like the music player. We don't control how those behave — but tell us if one gives you trouble and we'll find another way to get you what you came for.

[PLACEHOLDER: after a launch audit, list any real known issues here, honestly and specifically. If testing genuinely turns up nothing outstanding, replace this with: “We test as we build, and we haven't found an outstanding issue we're not already fixing. If you find one, we'd genuinely like to know.”]

Tell us and we'll fix it

If something here doesn't work for you, please write. Tell us the page, what you were trying to do, and what happened. You don't need to know the technical words for it.

[PLACEHOLDER: Tatiana/Caleb to provide a dedicated accessibility contact email.] In the meantime, use the contact page.

We'll get back to you within a few business days [PLACEHOLDER: confirm an exact response window — proposed 5 business days] and tell you either that it's fixed or what we're doing about it. If the fix is going to take a while, we'll find you another way to get what you needed in the meantime.

If you'd rather not use the website at all

That's completely fine. Write to us and we'll answer your questions about lessons, gatherings and retreats directly, in whatever format works for you.