First View Accessibility Conformance Report

This report contains:

  • First View Accessibility Commitment
  • WCAG 2.1 AA VPAT – First View Mobile App
  • WCAG 2.1 AA VPAT – First View District Dashboard
  • Notes
  • Terms
  • Disclaimer

First View Accessibility Commitment

First Student’s First View vehicle tracking product suite is committed to providing accessible digital experiences to its users and strives to conform to accessibility standards. Both the First View Mobile App and the First View District Dashboard have been evaluated using a combination of automated and manual accessibility testing. While the platforms support the majority of WCAG 2.1 AA success criteria, certain areas partially conform and are part of our ongoing accessibility improvement efforts. Accessibility considerations are incorporated into our product development process, and we continue to review and enhance accessibility over time.

VPAT® – First View Mobile App

WCAG Edition: WCAG 2.1

Name of Product/Version: First View Mobile App (iOS and Android)

Report Date: April 2026

This ACR is a living report and accurate at the date of publishing. Changes may be made to the document as updates are made to our product.

Product Description: 
First View is a mobile application designed for caregivers to track student transportation, receive notifications, and view bus location and trip-related information.

Evaluation Methods Used: 
Automated testing using BrowserStack Accessibility tools and manual testing with VoiceOver (iOS) and TalkBack (Android).

Applicable Standards/Guidelines: WCAG 2.1 Levels A and AA


First View Mobile App - Level A



Criteria

Conformance

Remarks

1.1.1 Non-text Content

Partially Supports

Some icons, map badges, and images lack fully descriptive alternative text for screen readers.

1.2.1 Audio-only and Video-only

Not Applicable

No audio-only or video-only prerecorded content is provided.

1.2.2 Captions (Prerecorded)

Not Applicable

No prerecorded video content is present.

1.2.3 Audio Description or Media Alternative

Not Applicable

No prerecorded video content is present.

1.3.1 Info and Relationships

Supports

Currently controls, sliders and dynamic content are fully programmatically associated with labels or structure.

1.3.2 Meaningful Sequence

Supports

Content is presented in a logical reading order.

1.3.3 Sensory Characteristics

Supports

Instructions do not rely solely on sensory characteristics.

1.4.1 Use of Color

Supports

Color is not the sole means of conveying information.

1.4.2 Audio Control

Not Applicable

No audio that plays automatically.

2.1.1 Keyboard

Supports

Interactive elements and sliders are operable via assistive technology keyboard navigation.

2.1.2 No Keyboard Trap

Supports

No keyboard traps identified.

2.1.4 Character Key Shortcuts

Not Applicable

No character key shortcuts implemented.

2.2.1 Timing Adjustable

Not Applicable

No time limits imposed.

Does not exist in Parent View for now

2.2.2 Pause, Stop, Hide

Not Applicable

No moving or auto-updating content requiring control.

Does not exist in Parent View for now

2.3.1 Three Flashes or Below Threshold

Not Applicable

No flashing content present.

Does not exist in Parent View for now

2.4.1 Bypass Blocks

Not Applicable

Mobile application do not use repeated page blocks.

2.4.2 Page Titled

Supports

Screens provide appropriate titles for assistive technologies.

2.4.3 Focus Order

Partially Supports

Focus order issues identified in scrollable views and bottom sheets.

2.4.4 Link Purpose (In Context)

Supports

Links within text-based documents are consistently accessible when screen readers are enabled.

2.5.1 Pointer Gestures

Supports

Multi-point gestures are not required.

2.5.2 Pointer Cancellation

Not Applicable

Actions can be canceled before completion.

Does not exist in Parent View for now

2.5.3 Label in Name

Partially Supports

Some controls have visible labels that do not match accessible names.

2.5.4 Motion Actuation

Supports

No motion-based activation required.

3.1.1 Language of Page

Partially Supports

Language is programmatically defined however translation was not tested properly by ADA requirements so that we could not define it as 100% supported

3.2.1 On Focus

Supports

No unexpected context changes on focus.

3.2.2 On Input

Supports

No unexpected context changes on input.

3.3.1 Error Identification

Supports

Errors are identified when present.

3.3.2 Labels or Instructions

Supports

Input fields and sliders lack sufficient instructions for screen readers

4.1.1 Parsing

Supports

Always supported per WCAG guidance.

4.1.2 Name, Role, Value

Partially Supports

Some custom components do not fully expose name, role, or value to assistive technologies.


First View Mobile App - Level AA

Criteria

Conformance

Remarks

1.2.4 Captions (Live)

Not Applicable

No live audio or video content.

1.2.5 Audio Description (Prerecorded)

Not Applicable

No prerecorded video content.

1.3.4 Orientation

Do not Support

Landscape Orientation is fully disabled for now

1.3.5 Identify Input Purpose

Supports

Input purposes are generally identifiable.

1.4.3 Contrast (Minimum)

Supports

Contrast requirements are met.

1.4.4 Resize Text

Partially Supports

Text resizing issues identified in bottom sheets and notification flows.

1.4.5 Images of Text

Supports

Images of text are avoided.

1.4.10 Reflow

Partially Supports

Some views do not reflow optimally when text is resized.

1.4.11 Non-text Contrast

Supports

Non-text contrast requirements are met.

1.4.12 Text Spacing

Partially Supports

Spacing adjustments impact readability in some iOS views.

1.4.13 Content on Hover or Focus

Not Applicable

No hover-dependent content.

2.4.5 Multiple Ways

Not Applicable

Mobile navigation patterns apply.

2.4.6 Headings and Labels

Supports

Headings and labels are generally descriptive.

2.4.7 Focus Visible

Supports

Focus indicators are visible.

4.1.3 Status Messages

Supports

Dynamic updates (e.g., notifications, map status) are consistently announced.


 VPAT® – First View District Dashboard

WCAG Edition: WCAG 2.1 A & AA

Name of Product/Version: First View Mobile App (iOS and Android)

Report Date: February 2026

This ACR is a living report and accurate at the date of publishing. Changes may be made to the document as updates are made to our product.

Product Description: 

First View is a desktop application designed for districts, schools, and operations to track student transportation, send notifications, and view bus location and trip-related information.

This Voluntary Product Accessibility Template (VPAT®) documents the accessibility conformance of the First View District Dashboard against WCAG 2.1 Levels A and AA. The District Dashboard is a web-based application used by district and transportation staff and is evaluated separately from the First View Parent App due to different users, functionality, and interaction patterns.

Evaluation Methods Used:

  • Automated testing using Lighthouse
Applicable Standards/Guidelines: WCAG 2.1 Level A and AA


Criteria

Conformance

Remarks

1.1.1 Non-text Content (A)

Partially Supports

Not all images contain alternative text.  Decorative images are ignored by assistive technologies.

1.3.1 Info and Relationships (A)

Partially Supports

Some form controls and custom interactive elements lack programmatic labels, which may impact screen reader interpretation.

1.3.2 Meaningful Sequence (A)

Supports

Content is presented in a logical order that preserves meaning when read by assistive technologies.

1.3.3 Sensory Characteristics (A)

Supports

Instructions do not rely solely on shape, size, or visual location.

1.4.1 Use of Color (A)

Supports

Color is not used as the sole means of conveying information.

1.4.3 Contrast (Minimum) (AA)

Supports

Text and interactive elements meet minimum color contrast requirements.

2.1.1 Keyboard (A)

Partially Supports

Core functions can be performed using the keyboard. This option is available in several places, but is generally unavailable.

2.1.2 No Keyboard Trap (A)

Partially Supports

The keyboard focus can be moved and displayed. Not all elements have this capability; in some elements, this capability has been deliberately removed for technical reasons.

2.4.1 Bypass Blocks (A)

Partially Supports

The application includes landmarks; however, skip links are not consistently implemented.

2.4.3 Focus Order (A)

Partially Supports

The focus order usually corresponds to the visual layout of the page. The focus order is not specified on the elements; in some cities it is specified, but this is due to technical nuances rather than accessibility considerations.

2.4.4 Link Purpose (In Context) (A)

Partially Supports

Some icon-only buttons and links lack discernible accessible names.

2.4.6 Headings and Labels (AA)

Partially Supports

Headings and labels are present but not always programmatically associated with their controls.

3.2.1 On Focus (A)

Supports

Elements do not initiate unexpected changes when receiving focus.

3.2.2 On Input (A)

Supports

User input does not automatically trigger significant context changes without warning.

4.1.1 Parsing (A)

Partially Supports

Almost all of the HTML markings here are structurally correct, but there are places where this has been neglected for technical reasons.

4.1.2 Name, Role, Value (A)

Partially Supports

Some custom buttons and controls do not expose an accessible name, role, or value to assistive technologies.


 Notes

  • Items marked Partially Supports represent known gaps identified through a combination of automated testing and limited manual review. Testing was performed using commonly available accessibility tools and manual techniques; however, results may vary based on the specific tools, assistive technologies, browsers, operating systems, and user configurations used.
  • Due to these variables, additional unidentified accessibility gaps may exist that were not detected during this assessment.
  • WCAG standards, accessibility guidance, and assistive technologies continue to evolve over time. As a result, interpretations of conformance and applicable best practices may change.
  • The First View product suite is under continuous development and improvement. Ongoing enhancements, bug fixes, and feature updates may introduce changes that impact accessibility over time.
  • This VPAT reflects the product state at the time of evaluation and is provided for transparency and informational purposes only.
Terms

The terms used in the Conformance Level information are defined as follows:

  • Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
  • Partially Supports: Some functionality of the product does not meet the criterion.
  • Not Applicable: The criterion is not relevant to the product.
Legal Disclaimer

This document is provided “as is” and for informational purposes only, and the contents are subject to change without notice. Although the information in this document is true and correct to the best of First Student’s knowledge at the time of publication, First Student does not warrant or guarantee the accuracy, completeness, or ongoing applicability of this report. First Student specifically disclaims any liability with respect to this document, and no contractual obligations are formed either directly or indirectly by this document. Please contact us to report any accessibility errors or issues so that they can be proactively evaluated and addressed.