Accessibility statement

Our commitment

As a Detroit AI and robotics neighborhood center in formation, we want the public face of FutureWorks to be open in practice, not only in message. Accessibility is part of how we design and maintain this site.

We treat accessibility as ongoing work. We improve pages as we ship updates, fix issues when we learn about them, and aim for clearer structure and contrast over time.

Standards we aim for

We use the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as a design and engineering target. That means we work toward those success criteria; it is not a claim that this site is fully conformant or formally certified against WCAG 2.2 AA.

Practices already on this site

Among the patterns we already use:

• Skip link — a “Skip to content” control at the start of each page so keyboard users can bypass repeated navigation.
• Reduced motion — respect for prefers-reduced-motion, so motion and reveal effects are limited when the system requests less animation.
• Semantic structure — landmarks such as nav, main, and footer, headings in order, and labeled interactive controls.
• Keyboard focus — visible :focus-visible styles on primary links, buttons, and form fields so focus is not hidden.

These practices help, but they do not replace reporting real barriers. If something blocks you, please tell us.

Report a barrier

If you encounter an accessibility barrier on futureworks.center, email hello@futureworks.center. Include the page URL and a short description of what went wrong. We will do our best to respond and improve.