Accessibility Policy

1. Our Commitment

Eyecosystems is committed to ensuring digital accessibility for people with disabilities, with particular focus on users who are blind or visually impaired (BVI). This commitment is not incidental — it is inseparable from our mission. We build and maintain human-verified accessibility data infrastructure so that cities and communities are more navigable for everyone. Our own platform must reflect that same standard.

We actively work to increase the accessibility and usability of eyecosystems.com and all associated web properties in conformance with applicable standards. We continuously review and improve our digital experience to remove barriers and ensure that assistive technology users can access the same information and functionality as all other users.

Our accessibility program is led by people who work directly with BVI communities and verified by members of the Eye Spy Foundation network.

---

2. Standards We Follow

The Eyecosystems platform is designed to conform to the Web Content Accessibility Guidelines (WCAG) 2.1 at Level AA, published by the World Wide Web Consortium (W3C). WCAG 2.1 AA is widely recognized as the applicable standard under the ADA, Section 508, and most global accessibility laws.

Our target conformance encompasses all four WCAG principles:

We also align with Section 508 of the Rehabilitation Act for government and enterprise procurement contexts, and with EN 301 549 for European compliance.

---

3. Accessibility Features

The following accessibility features are implemented across Eyecosystems web properties:

Navigation and Structure

• Skip navigation link at the top of every page, allowing screen reader users and keyboard navigators to bypass repeated navigation menus and jump directly to main content
• Consistent, logical heading hierarchy (h1 → h2 → h3) across all pages to support efficient navigation by assistive technologies
• Semantic HTML landmarks (nav, main, footer, section, article) enabling landmark-based navigation
• All navigation menus are keyboard-operable; the mobile hamburger menu is fully accessible via keyboard including Escape key dismissal
• ARIA labels and aria-current="page" attributes to identify the active page in navigation

Visual Design and Color

• All text-to-background color combinations meet or exceed WCAG 2.1 AA contrast ratios (4.5:1 for body text, 3:1 for large text and UI components)
• Focus indicators are clearly visible on all interactive elements using a 3px solid outline that meets WCAG 2.2 focus appearance criteria
• Information is never conveyed by color alone — status badges, charts, and data visualizations include text labels or patterns
• Body text is set at a minimum of 0.875rem (14px) with comfortable line-height for readability

Forms and Inputs

• All form inputs have associated labels (visible or screen-reader-only as appropriate)
• Required fields are indicated programmatically using aria-required="true"
• Error messages are descriptive and associated with the relevant input field
• Autocomplete attributes are applied to common fields to support assistive technology and reduce cognitive load

Images and Media

• All meaningful images include descriptive alt text
• Decorative images are marked with aria-hidden="true" and empty alt attributes to prevent screen reader announcement
• Inline SVG icons used in navigation and UI are accompanied by accessible labels or aria-hidden="true" where decorative

Interactive Components

• All interactive elements are reachable and operable via keyboard (Tab, Enter, Space, Escape, arrow keys as appropriate)
• Modals and overlays trap focus while open and restore focus on close
• ARIA roles, states, and properties are used to communicate component behavior to assistive technologies
• Animations respect the prefers-reduced-motion media query; users who have set this preference will not see motion-based effects

---

4. Known Limitations

While we strive for full WCAG 2.1 AA conformance, we acknowledge the following known limitations that we are actively working to address:

We perform accessibility reviews with each major product update and prioritize resolving identified issues. We conduct periodic third-party audits and user testing with BVI community members.

---

5. Feedback & Contact

We welcome feedback on the accessibility of the Eyecosystems platform. If you encounter barriers while using our site or have suggestions for improvement, we want to hear from you.

Please include in your message:

• The URL or page where you encountered the issue
• The assistive technology and browser you were using (if applicable)
• A description of what you were trying to do and what happened

We commit to responding to accessibility feedback within 5 business days and to providing a substantive response or workaround within 30 days.