Accessibility Compliance Overview

Introduction

This memo outlines the steps taken and features implemented to ensure our web application complies with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA. Our goal is to provide an inclusive experience for all users, including those with disabilities. For us, this applies to:

• GoActive! web

• GoActive! app 2.0

• Kiosk

• Self Service Station

Areas of Focus and Implementation

We have focused our compliance efforts across several key areas, including but not limited to:

Perceivable

This section details how we've made sure our content is perceivable by all users.

• Text Alternatives:

  • Images: All non-decorative images now include descriptive alt text.

  • Multimedia: Transcripts are provided for all pre-recorded audio, and captions are available for pre-recorded video content.

• Adaptable:

  • Structure: Content is structured using proper semantic HTML (<header>, <nav>, <main>, <footer>, headings, lists) to ensure logical reading order and navigation.

  • Presentation: Separation of content from presentation is maintained through CSS.

• Distinguishable:

  • Color Contrast: All text and essential graphical elements meet a minimum contrast ratio of 4.5:1 (or 3:1 for large text).

Operable

This section details how we've made sure our content is operable by all users.

• Keyboard Accessible:

  • Navigation: All interactive elements are fully operable via keyboard only, with a clear and visible focus indicator.

  • Traps: There are no keyboard traps within the application.

• Seizures and Physical Reactions:

  • No Flashing: Content does not contain any flashing elements that could trigger seizures (no more than three flashes in any one-second period).

• Navigable:

  • Page Titles: Each page has a clear and descriptive title.

  • Focus Order: The tabbing order is logical and intuitive.

  • Link Purpose: The purpose of each link is clear from its text or context.

Understandable

This section details how we've made sure our content is understandable by all users.

• Predictable:

  • On Focus: Changes of context do not occur solely upon receiving focus.

  • On Input: Changes of context do not occur solely upon changing the setting of a user interface component.

  • Consistent Navigation: Navigational mechanisms are consistent throughout the application.

  • Consistent Identification: Components with the same functionality are identified consistently.

• Input Assistance:

  • Error Identification: Input errors are clearly identified to the user.

  • Labels or Instructions: Labels or instructions are provided for all form fields.

  • Error Suggestion: Suggestions for correcting input errors are provided when possible.

Robust

This section details how we've made sure our content is robust to be interpreted by a wide range of user agents.

• Valid HTML: Markup is well-formed and does not contain syntax errors.

• Descriptive Alt-tags: All images include descriptive alt text that accurately conveys their purpose and meaning.

• ARIA-attributes:  We utilize ARIA attributes to improve the accessibility of custom components.

Testing and Validation

To ensure compliance, we have performed the following:

• Automated Testing: Utilized automated accessibility checkers (Silktide, Google Chrome Dev Tools) to identify common accessibility issues.

• Manual Review: Conducted thorough manual reviews of the application's interface and functionality.

• Assistive Technology Testing: Tested with various assistive technologies, including screen readers and keyboard navigation.

Future Steps

We are committed to maintaining and improving the accessibility of our web application. Ongoing efforts will include:

• Regular accessibility audits of any new features.

• Staying updated with the latest WCAG guidelines and best practices.