Accessiblilty

What Is Web Accessibility

Web accessibility is about making websites, digital services, and online content usable by everyone, including people with disabilities. Building with accessibility in mind is about removing barriers to access. It helps ensure that people who rely on assistive technologies, like screen readers, voice commands, or keyboard navigation, have equal access to services and information.

The Web Content Accessibility Guidelines (WCAG) are organized by four key principles: Perceivable, Operable, Understandable, and Robust. These principles provide a framework for determining if web content is accessible to all users, no matter the disability or device:

  • Perceivable: Is content presented in ways that all users can perceive?
  • Operable: Are interface elements navigable and usable by all users?
  • Understandable: Is information clear and behavior predictable?
  • Robust: Is the content compatible with assistive technology?
"The power of the Web is in its universality. Access by everyone regardless of disability is an essential aspect.”
– Sir Tim Berners-Lee

Accessibility Policy

Current ITS Policy

This policy recognizes the importance of universal accessibility and establishes minimum accessibility requirements to ensure that Information and Communication Technology (“ICT”), including applications, websites, and other digital interfaces, developed, procured, maintained, or used by State Entities (“SE”) are accessible to all users, including those with disabilities.

Learn More

Recommendations

  • WCAG Compliance: Target WCAG 2.1 Level AA compliance for all web applications, content, and mobile applications by June 25, 2026, as required by the DOJ Rule. Upgrade web applications to WCAG 2.2 Level AA compliance by January 1, 2027, in accordance with New York State Technology Law (STL) Section 103-d.
  • Accessibility Training: Make sure all user interface designers and developers receive basic accessibility training. (See learning resource links below.) Key team members should have a comprehensive understanding of accessibility and WCAG 2.2 AA compliance.
  • Accessibility Testing: Conduct manual accessibility testing of ICT before production use and prior to any significant changes. Incorporate this testing into a standard development and QA process with key milestones.
  • Documentation and Records: Keep documented testing reports for each ICT and maintain an updated list of all ICTs along with their current compliance status. Clearly display a link labeled “Accessibility” in the footer of the SE's website home page, providing contact information for accessibility inquiries.

Our Approach

How does our team make sure our design system is accessible to all?

While there are numerous ways to check for accessibility, here are just a few:

Color Contrast: Ensure sufficient contrast between text and background colors using a dedicated checker.

WebAim is recommended.

Element Sizing: Larger interactive elements (minimum 44x44 pixels as recommended by WCAG) make it easier for users with limited dexterity or those using assistive technologies to tap or click accurately.

Focus States: Ensures interactive elements like buttons and links clearly indicate focus when navigated with a keyboard.

Keyboard Navigation: Designing a website or application so users can navigate and interact with it using only a keyboard, without needing a mouse. This is essential for accessibility, especially for people with disabilities.

It typically includes:

  • Tab key to move between links, buttons, and form fields.
  • Enter/Spacebar to activate buttons and links.
  • Arrow keys to scroll or navigate within menus.
  • Escape key to close pop-ups or dialogs.

Screen Reader Testing:  "Screen reader testing" means checking how well a website or app works for visually impaired users who rely on screen reader software. It ensures that text, images, and interactive elements are properly read aloud and usable with keyboard commands.

Prioritizing accessibility in our design system allows all users, regardless of ability, navigate and interact with our products effectively. By following these best practices, we create a more inclusive experience for everyone. Accessibility is not just a feature; it’s a fundamental part of good design that benefits all users.