Vetride Accessibility Review: Web & Mobile App Evaluation

by SLV Team 58 views

Hey everyone! We're diving deep into the accessibility review of Vetride, both the website and the native mobile app. This is super important to ensure that all Veterans, including those with disabilities, can easily access transportation to and from their VA appointments. This review falls under the department-of-veterans-affairs and va.gov-team discussion category, so let's get started!

Quick Summary: ADE Accessibility Review of Vetride

Quick Summary: This is an ADE accessibility review of the Vetride website and native mobile app. Our goal is to identify any accessibility issues and ensure Vetride meets the highest standards for all Veterans.

Description of the Work

We're requesting a standard ADE (Accessibility Design & Evaluation) accessibility evaluation process for both the Vetride website and the native mobile app. While Vetride is a VA product, this review will be similar to recent COTS (Commercial Off-The-Shelf) product evaluations that ADE has produced. This means we'll be applying the same rigorous standards and processes to ensure a thorough assessment.

Background

Vetride is a crucial service designed to help Veterans get transportation to and from their VA appointments. We've heard from the Blinded Veterans Association members that integrating Vetride with VAHB (VA Health and Benefits mobile app) could be a game-changer. Transportation can be a major hurdle for this population, and we want to make things as smooth as possible.

VAHB is exploring the exciting possibility of launching Vetride directly from within the app. To make this a reality, we need to ensure that every part of Vetride is accessible and meets OCTO's (Office of the Chief Technology Officer) "accessibility beyond compliance" standards. The great news is that Vetride is already 508 compliant, which is fantastic news! This is a strong foundation to build upon.

ADE, we're counting on you! Please coordinate closely with @Logan-Smith1 (he's super responsive on Slack) to arrange access, test accounts, and anything else you need to conduct a comprehensive evaluation. Your expertise is invaluable in making Vetride truly accessible for all our Veterans.

About the Team

To give you a clear picture of who's involved, here's a breakdown of the team:

  • Team name: VAHB
  • Product name: Vetride
  • Vetride product owners: @Logan-Smith1 and Johnathon.CobleHarrison@va.gov
  • VAHB leads: @mmiddaugh @rtwell
  • Slack Channel: #va-mobile-app (but Ryan suggested we might create a new Slack channel specifically for this work. We'll keep you posted!)

Supporting Artifacts

To aid in your review, here are some helpful resources:

  • Vetride site - Take a look at the live site to get a feel for the user experience.
  • Artifact 2 - Placeholder for additional documentation
  • Artifact 3 - Placeholder for additional documentation

ADE Tasks

To ensure clarity and focus, here's a breakdown of the tasks we anticipate ADE will undertake:

TIP: Customize ADE Tasks as needed. These are just starting points!

  • [ ] Collaborate task - Let's keep the lines of communication open and work together seamlessly.
  • [ ] ADE Support task - Provide your expert support and guidance throughout the process.
  • [ ] Document task - Thorough documentation is key to ensuring long-term accessibility.
  • [ ] Review task - Conduct a meticulous review of the Vetride web and native mobile app.

Acceptance Criteria

To help us define success, here are the acceptance criteria we'll use to evaluate the accessibility review:

TIP: Customize ADE Acceptance Criteria as needed. These are examples to guide our thinking.

  • [ ] Acceptance Criteria Example 1 - Specific criteria to be defined
  • [ ] Acceptance Criteria Example 2 - Specific criteria to be defined
  • [ ] Acceptance Criteria Example 3 - Specific criteria to be defined

ADE Internal

This section is for the ADE team to manage the internal aspects of the review process:

Ticket Updates

  • [ ] Connect to an Epic or Intake (what body of work is this a part of?) - Ensuring alignment with broader initiatives.
  • [ ] Label with Originator/Team (product team or stakeholder requesting support; ADE if internal) - For clear tracking and accountability.
  • [ ] Label date in the Open Date field - To maintain accurate timelines.
  • [ ] Label with Estimate (level of effort expected for this ticket) - For resource planning.
  • [ ] Add Assignee(s) name(s) to ticket (include Lakwi) - Assigning ownership and responsibilities.
  • [ ] Add Assignee(s) name(s) to each task they will complete via handle tag (if known) - Clear task assignments.
  • [ ] Select a Priority Level - To ensure timely completion of critical tasks.
  • [ ] Update date in Last Checked field - To keep track of progress.
  • [ ] Label with Actual (level of effort it took to complete this ticket) - For process improvement and future estimations.
  • [ ] Update date in Closed Date - To mark the completion of the review.
  • [ ] Read Important Notifications (ADE Internal) at the bottom of this ticket. - Staying informed about process updates.
  • [ ] Delete Important Notifications (ADE Internal) at the bottom of this ticket, after reading. - Keeping the ticket clean and focused.

CAUTION

Important Notifications (ADE Internal)

Please delete the following alerts after reading and/or prior to saving this ticket template.

  • Related Tickets
  • About this Template

Last updated: 2/25/2025

Related Tickets

Review important information related to connecting tickets

Tasks are Now Sub-Issues

  • Related tickets are no longer being tracked in task lists, due to the planned depreciation of tasks by GitHub in April 2025.
  • Instead, related tickets will be connected to tickets via sub-issues.
Connecting Tickets
  • To connect an existing ticket, choose the drop-down from "create sub-issue" and select "add existing issue"
  • To connect a new issue, choose the drop-down from "create sub-issue" and select "create sub-issue," and select the respective template.

Please delete this alert after reading and/or prior to saving this ticket template.

About this Template

Review guidance for completing this ticket template
  • Template Purpose:
    • To quickly spin up child work tickets that can connect to intake tickets.
    • To quickly generate internal work tickets for the ADE team to track their internal work.
    • This ticket does not include all of the language in the intake ticket.
  • New Ticket:

Ticket Fields and Formatting

  • Ticket Title Examples: Based on our menu of services, to maintain consistent formatting, also refer to existing tickets as well for guidance.
    • Internal Work:
      • [ADE Support] ADE - Work being done
      • [ADE Documentation] ADE - Work being done
      • [ADE Process Work] ADE- Work being done
    • Child Tickets for Intakes:
      • [ADE Audit] Team Name - Project Name
      • [ADE Design Review] Team Name - Project Name
      • [ADE Research] Team Name - Project Name (Month(s) of Research)
  • Ticket Labels:
    • ADE at minimum.
    • Do not use intake label on this ticket.
    • Search ADE in labels list to view additional available labels, which will follow the naming structure ADE XYZ

Please delete this alert after reading and/or prior to saving this ticket template.

This detailed review process will help us ensure that Vetride is not only functional but also truly accessible to all Veterans, regardless of their abilities. Thanks for your dedication to this important mission, guys!