Skip to content

Accessibility · Accesibilidad

Accessibility.

We treat accessibility as a launch requirement, not a nice-to-have. The target is WCAG 2.1 AA across every public page, with AAA where it is reasonable.

What is in place

  • Semantic HTML, never div soup. Real headings in order. Real lists, real landmarks.
  • Visible focus rings on every interactive element, using the design system token.
  • Skip-to-content link on every page.
  • Keyboard navigation for the full site. No mouse-only interactions.
  • Reduced-motion support: animations cut to near-zero when prefers-reduced-motion is on.
  • Text contrast at AA minimum on every surface, AAA on body text against the cream background.
  • Real alt text on meaningful images. Decorative images get empty alt.
  • Bilingual screen reader support: html lang switches with locale, and inline lang attributes mark passages in the other language.
  • Touch targets sized to 44 by 44 pixels minimum.

Known limitations

  • Concept rendering placeholders are decorative until the production renderings are uploaded with full alt text.
  • The interactive citywide map is in development. When published it will include keyboard navigation and an alternate text list of every park.
  • The native survey and signup forms will follow an accessible pattern with inline error messages, aria-invalid and aria-describedby, an error summary, and focus management on submit.

How to report an issue

Email newburghplaygrounds@gmail.com with the page URL, the device and browser you are on, and what you ran into. We respond within five business days.

Accesibilidad, en español

Tratamos la accesibilidad como requisito de lanzamiento, no como un extra. El objetivo es WCAG 2.1 AA en todas las páginas públicas. Si encuentras una barrera, escribe a newburghplaygrounds@gmail.com y respondemos en cinco días hábiles.