Equal access, by design.
CCE4ME is committed to making our website usable and welcoming for everyone — including people who use assistive technologies, navigate by keyboard, or have visual, hearing, motor, or cognitive disabilities.
Our standard
This site is built to conform with WCAG 2.2 Level AA — the standard published by the W3C Web Accessibility Initiative — and the Americans with Disabilities Act (ADA). Where practical, we exceed AA and meet AAA criteria.
What we've done
- Semantic structure. Every page uses correct landmarks (
<header>,<nav>,<main>,<section>,<footer>) and a clean heading hierarchy so screen readers can navigate the page logically. - Skip-to-content link appears on focus so keyboard users can bypass the navigation (WCAG 2.4.1).
- Visible focus indicators appear on every interactive element using
:focus-visible— a 3 px high-contrast coral ring with offset (WCAG 2.4.7, 2.4.11). - All non-text content has alternatives. Decorative images use empty
alt=""; meaningful images include descriptive alternative text (WCAG 1.1.1). - Color contrast. Body text hits 7:1+ on its background. UI components and large text meet 3:1+. Coral, our action color, only appears as small text in its darker WCAG-passing variant
#B83E1Fon light backgrounds; button backgrounds use#C24A2Eso white labels pass 4.9:1 (WCAG 1.4.3, 1.4.11). - Touch targets are at least 24 × 24 CSS pixels across all interactive controls (WCAG 2.2 SC 2.5.8).
- Reduced motion. All animations — including the spinning Bloom logo, ticker, and orbital ring — disable themselves when the visitor's OS is set to
prefers-reduced-motion: reduce(WCAG 2.3.3, 2.2.2). - Forms have real labels. The newsletter input is labelled visually and via a hidden screen-reader label, with descriptive helper text linked through
aria-describedby(WCAG 3.3.2, 4.1.2). - Links that open new tabs announce that fact to screen readers via visually hidden text (WCAG 3.2.5).
- Decorative SVG icons are marked
aria-hidden="true"andfocusable="false"so they don't pollute the accessibility tree (WCAG 1.3.1). - Page language declared at the document root (
<html lang="en">) (WCAG 3.1.1). - Keyboard accessible. No content requires a mouse, hover, or specific gesture. Focus order matches the visual order (WCAG 2.1.1, 2.4.3).
- Layout reflows down to 320 CSS pixels without loss of content or function (WCAG 1.4.10).
- Text can be resized to 200% without loss of content or function (WCAG 1.4.4).
- Text spacing respects user-defined line-height, paragraph spacing, letter and word spacing (WCAG 1.4.12).
WCAG 2.2 success criteria
| Principle | Criterion | Level | Status |
|---|---|---|---|
| Perceivable | 1.1.1 Non-text content | A | Pass |
| Perceivable | 1.3.1 Info and relationships | A | Pass |
| Perceivable | 1.3.5 Identify input purpose | AA | Pass |
| Perceivable | 1.4.3 Contrast (Minimum) | AA | Pass |
| Perceivable | 1.4.10 Reflow | AA | Pass |
| Perceivable | 1.4.11 Non-text contrast | AA | Pass |
| Perceivable | 1.4.12 Text spacing | AA | Pass |
| Operable | 2.1.1 Keyboard | A | Pass |
| Operable | 2.4.1 Bypass blocks | A | Pass |
| Operable | 2.4.4 Link purpose (in context) | A | Pass |
| Operable | 2.4.7 Focus visible | AA | Pass |
| Operable | 2.4.11 Focus not obscured (minimum) — new in 2.2 | AA | Pass |
| Operable | 2.5.8 Target size (minimum) — new in 2.2 | AA | Pass |
| Understandable | 3.1.1 Language of page | A | Pass |
| Understandable | 3.2.6 Consistent help — new in 2.2 | A | Pass |
| Understandable | 3.3.2 Labels or instructions | A | Pass |
| Understandable | 3.3.7 Redundant entry — new in 2.2 | A | Pass (no multi-step forms) |
| Robust | 4.1.2 Name, role, value | A | Pass |
Limitations
Despite our best efforts, third-party content embedded from external services (such as the Glofox class scheduler, Jotform registration forms, and Mailchimp newsletter archive) may have its own accessibility characteristics that we don't fully control. Where possible we link to those tools rather than embedding them, and we test that the links are descriptive on their own.
Need help?
If you encounter an accessibility barrier on this site, please let us know. We treat accessibility issues as bugs and will fix them as quickly as possible.
Center for Creative Education
Kingston, NY
Email: hello@cce4me.org
When reporting an issue, it helps if you can include the page URL, the assistive technology you're using, and a description of what you encountered.
Standards we use
- Web Content Accessibility Guidelines (WCAG) 2.2
- Americans with Disabilities Act (ADA)
- Section 508 of the Rehabilitation Act
This statement was last reviewed on May 3, 2026.