# VPAT - Tomahawk Technologies & OperationsCommander Accessibility Conformance Report

<p class="callout info">**Revised Section 508 Edition - (Based on VPAT® Version 2.5)**</p>

<p class="callout warning">**Legal Disclaimer -** This Voluntary Product Accessibility Template (VPAT) is provided for informational purposes only and does not constitute a legal binding claim of compliance. The information reflects the product as of the date of this report and does not cover subsequent changes or updates. While we strive for accuracy and compliance with applicable accessibility standards, we acknowledge that there may be instances of non-conformity. We encourage users to report any such instances to OperationsCommander so we can address them promptly. No liability is assumed for the accuracy of this document or the decisions made based on its content. This VPAT does not imply endorsement by any federal agency.</p>

#### Purpose

The VPAT is a template used to document a product's conformance with accessibility standards and guidelines. The purpose of the Accessibility Conformance Report is to assist customers and buyers in making preliminary assessments regarding the availability of commercial "Electronic and Information Technology," also referred to as “Information and Communication Technology” (ICT) products and services with features that support accessibility.

#### Legal Disclaimer 

This Voluntary Product Accessibility Template (VPAT) is provided for informational purposes only and does not constitute a legal binding claim of compliance. The information reflects the product as of the date of this report and does not cover subsequent changes or updates. While we strive for accuracy and compliance with applicable accessibility standards, we acknowledge that there may be instances of non-conformity. We encourage users to report any such instances to OperationsCommander so we can address them promptly. No liability is assumed for the accuracy of this document or the decisions made based on its content. This VPAT does not imply endorsement by any federal agency.

#### Revision History

<div align="center" dir="ltr" id="bkmrk-date-of-change-notes"><table><colgroup><col width="163"></col><col width="461"></col></colgroup><tbody><tr><td>Date of Change

</td><td>Notes

</td></tr><tr><td>August 13, 2024

</td><td>Final Draft - Shannon Jones

</td></tr><tr><td>May 13, 2025</td><td>Review for Accuracy - Shannon Jones</td></tr><tr><td>  
</td><td>  
</td></tr><tr><td>  
</td><td>  
</td></tr></tbody></table>

  
</div><div align="left" dir="ltr" id="bkmrk-name-of-product%2Fvers"><table border="1" style="border-collapse: collapse; border-color: rgb(53, 152, 219); border-style: solid;"><colgroup><col width="263"></col><col width="697"></col></colgroup><tbody><tr><td style="border-color: rgb(53, 152, 219);">Name of Product/Version:

</td><td style="border-color: rgb(53, 152, 219);">OperationsCommander - User Portal

</td></tr><tr><td style="border-color: rgb(53, 152, 219);">Platform:

</td><td style="border-color: rgb(53, 152, 219);">Web

</td></tr><tr><td style="border-color: rgb(53, 152, 219);">Report Date:

</td><td style="border-color: rgb(53, 152, 219);">May 2025

</td></tr><tr><td style="border-color: rgb(53, 152, 219);">Product Description:

</td><td style="border-color: rgb(53, 152, 219);">OperationsCommander provides a cloud-based parking and enforcement management system. The online portal allows users access to manage their account, personal information, and vehicles. They can also appeal and pay violations and purchase permits.

</td></tr><tr><td style="border-color: rgb(53, 152, 219);">Contact Information:

</td><td style="border-color: rgb(53, 152, 219);">support@ops-com.com

</td></tr><tr><td style="border-color: rgb(53, 152, 219);">Evaluation Methods Used:

</td><td style="border-color: rgb(53, 152, 219);">Testing is based on knowledge of general product functionality

</td></tr></tbody></table>

</div>#### Applicable Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guidelines:

<div align="left" dir="ltr" id="bkmrk-standard%2Fguideline-i"><table><colgroup><col width="608"></col><col width="355"></col></colgroup><thead><tr><th scope="col">Standard/Guideline

</th><th scope="col">Included In Report

</th></tr></thead><tbody><tr><td>[Web Content Accessibility Guidelines 2.0](http://www.w3.org/TR/2008/REC-WCAG20-20081211)

</td><td>Level A (Yes)

Level AA (Yes)

Level AAA (Yes)

</td></tr><tr><td>[Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018](https://www.access-board.gov/ict/)

</td><td>(Yes)

</td></tr></tbody></table>

</div>#### 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.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can only be used in WCAG Level AAA criteria.

#### WCAG 2.0 Report

Tables 1 and 2 also document conformance with Revised Section 508:

- Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
- Chapter 6 – 602.3 Electronic Support Documentation

Note: When reporting on conformance with the WCAG 2.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the [WCAG 2.0 Conformance Requirements](https://www.w3.org/TR/WCAG20/#conformance-reqs).

#### Table 1: Success Criteria, Level A

<div align="left" dir="ltr" id="bkmrk-criteria-conformance"><table><colgroup><col width="7"></col><col width="440"></col><col width="7"></col><col width="169"></col><col width="347"></col></colgroup><thead><tr><th colspan="2" scope="col">Criteria

</th><th colspan="2" scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td colspan="2">[1.1.1 Non-text Content](http://www.w3.org/TR/WCAG20/#text-equiv-all) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)
- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: Most of the content is text. Images that are used are decorative (e.g., brand/client logos). Images presenting the vehicle type are decorative and are placed next to the text description (including the vehicle type) of the vehicle. The real-time map parking doesn’t require the map as the interface to get a permit is text-based (appears next to the map; the map is only to see where the lots are). Content mostly complies except for:

- The chart on the real-time map page showing the percentage of available permits has no text alternative
- QR Code scanning does not have a text alternative

Note: The primary users for QR code scanning and real-time permit availability are drivers who are expected to be visually interactive, an accessible alternative method is provided as users can access the same page to obtain the permit directly through the app.

</td></tr><tr><td colspan="2">[1.2.1 Audio-only and Video-only (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-av-only-alt) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: no audio or video media is used on the website

</td></tr><tr><td colspan="2">[1.2.2 Captions (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-captions) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: no audio or video media is used on the website

</td></tr><tr><td colspan="2">[1.2.3 Audio Description or Media Alternative (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-audio-desc) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: no audio or video media is used on the website

</td></tr><tr><td colspan="2">[1.3.1 Info and Relationships](http://www.w3.org/TR/WCAG20/#content-structure-separation-programmatic) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Partially supports

</td><td>Web: semantic structure and labeling complies. However, ARIA roles need to be explicitly defined to enhance accessibility.

  
This is on the development roadmap for winter 2024. Improvement number AC1-T3

</td></tr><tr><td colspan="2">[1.3.2 Meaningful Sequence](http://www.w3.org/TR/WCAG20/#content-structure-separation-sequence) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: logical order is followed on all pages

</td></tr><tr><td colspan="2">[1.3.3 Sensory Characteristics](http://www.w3.org/TR/WCAG20/#content-structure-separation-understanding) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: there are no instructions that rely solely on sensory characteristics

</td></tr><tr><td colspan="2">[1.4.1 Use of Color](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-without-color) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: links, buttons, and other interactive elements are not identified solely by color. information conveyed through color is also available through text

</td></tr><tr><td colspan="2">[1.4.2 Audio Control](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-dis-audio) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: website does not play any audio or video media

</td></tr><tr><td colspan="2">[2.1.1 Keyboard](http://www.w3.org/TR/WCAG20/#keyboard-operation-keyboard-operable) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Partially supports

</td><td>Web: not all pages and functionality can be accessed using a keyboard

Improvement number AC1-T4

</td></tr><tr><td colspan="2">[2.1.2 No Keyboard Trap](http://www.w3.org/TR/WCAG20/#keyboard-operation-trapping) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: pages that can be accessed using a keyboard can also be exited using the keyboard

</td></tr><tr><td colspan="2">[2.2.1 Timing Adjustable](http://www.w3.org/TR/WCAG20/#time-limits-required-behaviors) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Does not support

</td><td>Web: in app notifications (success or failure messages) have a timer with no button to dismiss before the timer ends. Also ,no prior warning is given when the user’s session times out.

  
This is on the development roadmap for winter 2024

Improvement number AC1-T5

</td></tr><tr><td colspan="2">[2.2.2 Pause, Stop, Hide](http://www.w3.org/TR/WCAG20/#time-limits-pause) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: The application does not include moving or blinking content that needs to be paused,stopped or hidden

</td></tr><tr><td colspan="2">[2.3.1 Three Flashes or Below Threshold](http://www.w3.org/TR/WCAG20/#seizure-does-not-violate) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: website does not contain any flashing content

</td></tr><tr><td colspan="2">[2.4.1 Bypass Blocks](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-skip) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)

- 602.3 (Support Docs) – Does not apply to non-web docs

</td><td colspan="2">Web: Supports

</td><td>Web: the only page with content, the onboarding page, can be skipped.

</td></tr><tr><td colspan="2">[2.4.2 Page Titled](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-title) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: All pages are titled appropriately

</td></tr><tr><td colspan="2">[2.4.3 Focus Order](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-focus-order) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: interactive elements in anis in an order that follows sequences and relationships within the content

</td></tr><tr><td colspan="2">[2.4.4 Link Purpose (In Context)](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-refs) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: links are only used in news items that are sent by the admins to the users. The admins choose the link description that will be displayed to describe the purpose of this link

</td></tr><tr><td colspan="2">[3.1.1 Language of Page](http://www.w3.org/TR/WCAG20/#meaning-doc-lang-id) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: Default browser language is used

</td></tr><tr><td colspan="2">[3.2.1 On Focus](http://www.w3.org/TR/WCAG20/#consistent-behavior-receive-focus) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: focus on input fields does not change context

</td></tr><tr><td colspan="2">[3.2.2 On Input](http://www.w3.org/TR/WCAG20/#consistent-behavior-unpredictable-change) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: submit buttons or dialogues are provided in areas where change of context may be initiated

</td></tr><tr><td colspan="2">[3.3.1 Error Identification](http://www.w3.org/TR/WCAG20/#minimize-error-identified) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Partially supports

</td><td>Web: mostly complies, some form input fields do not present a message when the are empty, they just get a red outline

  
Improvement number AC1-T6

</td></tr><tr><td colspan="2">[3.3.2 Labels or Instructions](http://www.w3.org/TR/WCAG20/#minimize-error-cues) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: placeholders and/or labels are used to describe input fields

</td></tr><tr><td colspan="2">[4.1.1 Parsing](http://www.w3.org/TR/WCAG20/#ensure-compat-parses) (Level A)

Also applies to:

WCAG 2.0 – Always answer ‘Supports’

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>For WCAG 2.0 and the 508 standards, the September 2023 errata update indicates this criterion is always supported. See the [WCAG 2.0 Editorial Errata](https://www.w3.org/WAI/WCAG20/errata/#editorial).

  
</td></tr><tr><td colspan="2">[4.1.2 Name, Role, Value](http://www.w3.org/TR/WCAG20/#ensure-compat-rsv) (Level A)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: form controls elements have label elements associated to them

</td></tr></tbody></table>

</div>#### Table 2: Success Criteria, Level AA

Notes: WebAIM Contrast Checker was used to test contrast ratios

<div align="left" dir="ltr" id="bkmrk-criteria-conformance-1"><table><colgroup><col width="1"></col><col width="440"></col><col width="2"></col><col width="177"></col><col width="339"></col></colgroup><thead><tr><th colspan="2" scope="col">Criteria

</th><th colspan="2" scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td colspan="2">[1.2.4 Captions (Live)](http://www.w3.org/TR/WCAG20/#media-equiv-real-time-captions) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: no audio or video content is used on website

</td></tr><tr><td colspan="2">[1.2.5 Audio Description (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-audio-desc-only) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: no audio or video content is used on website

  
</td></tr><tr><td colspan="2">[1.4.3 Contrast (Minimum)](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-contrast) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>web : The website uses more than one color combination across different pages.  
The measured contrast ratios are as follows:  
page text: 17.74:1  
buttons: 7.71:1  
displaying active pages on navigation bar: 6.88:1

</td></tr><tr><td colspan="2">[1.4.4 Resize text](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-scale) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: text and components are responsive to different screen sizes and zoom levels

</td></tr><tr><td colspan="2">[1.4.5 Images of Text](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-text-presentation) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: on the manage credit card page, text is used to display credit card info instead of an image, which allows accessibility tools to be used. Only images that might contain text are just decorative (brand/client logos)

</td></tr><tr><td colspan="2">[2.4.5 Multiple Ways](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-mult-loc) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)

- 602.3 (Support Docs) – Does not apply to non-web docs

</td><td colspan="2">Web: Supports

</td><td>Web: search functionality on pages and linking to all of the pages on the site from the home page

</td></tr><tr><td colspan="2">[2.4.6 Headings and Labels](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-descriptive) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: content is described in headings and labels

</td></tr><tr><td colspan="2">[2.4.7 Focus Visible](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-focus-visible) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Partially supports

</td><td>Web: most elements do visibility show that they have received focus but some don’t

  
Improvement number - AC1-T7

</td></tr><tr><td colspan="2">[3.1.2 Language of Parts](http://www.w3.org/TR/WCAG20/#meaning-other-lang-id) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: each passage or phrase in the content can be programmatically determined

</td></tr><tr><td colspan="2">[3.2.3 Consistent Navigation](http://www.w3.org/TR/WCAG20/#consistent-behavior-consistent-locations) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)

- 602.3 (Support Docs) – Does not apply to non-web docs

</td><td colspan="2">Web: Supports

</td><td>Web: side navigation bar is consistent on all pages

</td></tr><tr><td colspan="2">[3.2.4 Consistent Identification](http://www.w3.org/TR/WCAG20/#consistent-behavior-consistent-functionality) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software) – Does not apply to non-web software
- 504.2 (Authoring Tool)

- 602.3 (Support Docs) – Does not apply to non-web docs

</td><td colspan="2">Web: Supports

</td><td>Web: using consistent identification for components with similar functionality.

</td></tr><tr><td colspan="2">[3.3.3 Error Suggestion](http://www.w3.org/TR/WCAG20/#minimize-error-suggestions) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Partially supports

</td><td>Web: form validation is provided but in some forms when a required field is left empty it is only highlighted in red with no DOM text

  
Improvement number: AC1-T6

</td></tr><tr><td colspan="2">[3.3.4 Error Prevention (Legal, Financial, Data)](http://www.w3.org/TR/WCAG20/#minimize-error-reversible) (Level AA)

Also applies to:

Revised Section 508

- 501 (Web)(Software)
- 504.2 (Authoring Tool)

- 602.3 (Support Docs)

</td><td colspan="2">Web: Supports

</td><td>Web: financial transactions have a mechanism for reviewing, confirming, and correcting information before finalizing the submission.

</td></tr></tbody></table>

</div>#### Table 3: Success Criteria, Level AAA

<div align="left" dir="ltr" id="bkmrk-criteria-conformance-2"><table><colgroup><col width="1"></col><col width="440"></col><col width="2"></col><col width="177"></col><col width="339"></col></colgroup><thead><tr><th colspan="2" scope="col">Criteria

</th><th colspan="2" scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td colspan="2">[1.2.6 Sign Language (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-sign) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web:no media content is used

</td></tr><tr><td colspan="2">[1.2.7 Extended Audio Description (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-extended-ad) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: no media content is used

</td></tr><tr><td colspan="2">[1.2.8 Media Alternative (Prerecorded)](http://www.w3.org/TR/WCAG20/#media-equiv-text-doc) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: no media content is used

</td></tr><tr><td colspan="2">[1.2.9 Audio-only (Live)](http://www.w3.org/TR/WCAG20/#media-equiv-live-audio-only) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: no media content is used

</td></tr><tr><td colspan="2">[1.4.6 Contrast (Enhanced](http://www.w3.org/TR/WCAG20/#visual-audio-contrast7)) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Partially supports

</td><td>Web: The website employs various color combinations across different pages. The measured contrast ratios for different elements are as follows:

- Page text: 17.74:1
- Buttons: 7.71:1
- Displaying active pages on the navigation bar: 6.88:1

While most elements meet the required contrast ratio of at least 7:1 for enhanced contrast, the active pages on the navigation bar fall slightly short with a ratio of 6.88:1. Therefore, the website partially supports this criterion.

  
</td></tr><tr><td colspan="2">[1.4.7 Low or No Background Audio](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-noaudio) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: no audio or video media content is used

</td></tr><tr><td colspan="2">[1.4.8 Visual Presentation](http://www.w3.org/TR/WCAG20/#visual-audio-contrast-visual-presentation) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: does not support

</td><td>Web: The website does not provide user controls to change the following aspects of the visual presentation:

1. Foreground and background colors.
2. Width of blocks of text.
3. Text alignment.
4. Line spacing.
5. Text size.

  
</td></tr><tr><td colspan="2">[1.4.9 Images of Text (No Exception)](http://www.w3.org/TR/WCAG20/#http://www.w3.org/TR/WCAG20/) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: Images of text are only used for pure decoration (client or ops-com logo)

</td></tr><tr><td colspan="2">[2.1.3 Keyboard (No Exception)](http://www.w3.org/TR/WCAG20/#keyboard-operation-all-funcs) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: does not support

</td><td>Web: not all functionality of the content is operable through a keyboard interface

</td></tr><tr><td colspan="2">[2.2.3 No Timing](http://www.w3.org/TR/WCAG20/#time-limits-no-exceptions) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: does not support

</td><td>Web: users get logged out after inactivity without the ability to extend session

</td></tr><tr><td colspan="2">[2.2.4 Interruptions](http://www.w3.org/TR/WCAG20/#time-limits-postponed) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: pages do not automatically update while they are active.

</td></tr><tr><td colspan="2">[2.2.5 Re-authenticating](http://www.w3.org/TR/WCAG20/#time-limits-server-timeout) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: does not support

</td><td>Web: when a session expires, forms are not restored

</td></tr><tr><td colspan="2">[2.3.2 Three Flashes](http://www.w3.org/TR/WCAG20/#seizure-three-times) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: website has no flashing content

</td></tr><tr><td colspan="2">[2.4.8 Location](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-location) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: navigation bars and page titles show where the user currently is on the website

</td></tr><tr><td colspan="2">[2.4.9 Link Purpose (Link Only)](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-link) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: links are only used in news items that are sent by the admins to the users. The admins choose the link description that will be displayed to describe the purpose of this link

</td></tr><tr><td colspan="2">[2.4.10 Section Headings](http://www.w3.org/TR/WCAG20/#navigation-mechanisms-headings) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: pages are organized using headings

</td></tr><tr><td colspan="2">[3.1.3 Unusual Words](http://www.w3.org/TR/WCAG20/#meaning-idioms) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: The website does not include a mechanism for adding definitions and does not inherently use unusual words. However, the client controls almost all the text (headers, fields, etc.) on the website.

</td></tr><tr><td colspan="2">[3.1.4 Abbreviations](http://www.w3.org/TR/WCAG20/#meaning-located) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web:The website does not include a mechanism for adding definitions and does not inherently use abbreviations. However, the client controls almost all the text (headers, fields, etc.) on the website.

</td></tr><tr><td colspan="2">[3.1.5 Reading Level](http://www.w3.org/TR/WCAG20/#meaning-supplements) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: The website does not include a mechanism for adding definitions and does not inherently use complex text. However, the client controls almost all the text (headers, fields, etc.) on the website.

</td></tr><tr><td colspan="2">[3.1.6 Pronunciation](http://www.w3.org/TR/WCAG20/#meaning-pronunciation) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: does not support

</td><td>Web: no mechanism is available for identifying specific pronunciation of words

</td></tr><tr><td colspan="2">[3.2.5 Change on Request](http://www.w3.org/TR/WCAG20/#consistent-behavior-no-extreme-changes-context) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: The website ensures that all changes of context are initiated by explicit user actions. For example, form submissions, navigation actions, and opening of modals are all triggered by user inputs or clicks.

</td></tr><tr><td colspan="2">[3.3.5 Help](http://www.w3.org/TR/WCAG20/#minimize-error-context-help) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: for forms, the client can add instructions for each field to describe necessary input

</td></tr><tr><td colspan="2">[3.3.6 Error Prevention (All)](http://www.w3.org/TR/WCAG20/#minimize-error-reversible-all) (Level AAA)

Revised Section 508 – Does not apply

</td><td colspan="2">Web: Supports

</td><td>Web: The website provides error checking and validation for all forms, with confirmation dialogs for critical actions.

</td></tr></tbody></table>

</div>#### Revised Section 508 Report

Notes: WebAIM Contrast Checker was used to test contrast ratios

#### Chapter 3: [Functional Performance Criteria](https://www.access-board.gov/ict/#chapter-3-functional-performance-criteria) (FPC)

<div align="left" dir="ltr" id="bkmrk-criteria-conformance-3"><table><colgroup><col width="442"></col><col width="259"></col><col width="258"></col></colgroup><thead><tr><th scope="col">Criteria

</th><th scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td>302.1 Without Vision

</td><td>Web: does not support

</td><td>web: website cannot be fully used with keyboard only

</td></tr><tr><td>302.2 With Limited Vision

</td><td>Web: Supports

</td><td>web : The website uses more than one color combination across different pages.  
The measured contrast ratios are as follows:  
page text: 17.74:1  
buttons: 7.71:1  
displaying active pages on navigation bar: 6.88:1

</td></tr><tr><td>302.3 Without Perception of Color

</td><td>Web: Supports

</td><td>web: information conveyed with color is also available without color

</td></tr><tr><td>302.4 Without Hearing

</td><td>Web: Supports

</td><td>web: no audio is played on the website

</td></tr><tr><td>302.5 With Limited Hearing

</td><td>Web: Supports

</td><td>web: no audio is played on the website

</td></tr><tr><td>302.6 Without Speech

</td><td>Web: Supports

</td><td>web: no speech is needed for any functionality

</td></tr><tr><td>302.7 With Limited Manipulation

</td><td>Web: Partially supports

</td><td>web: even though the website is not fully functional with a keyboard, controls are operated with a single action, avoiding the need for simultaneous pressing or holding of multiple keys/buttons.

</td></tr><tr><td>302.8 With Limited Reach and Strength

</td><td>Web: Supports

</td><td>web: The application is operable using standard web interactions (keyboard, mouse, touch screen), accommodating users with limited reach and strength. Standard web components ensure compatibility with assistive technologies.

</td></tr><tr><td>302.9 With Limited Language, Cognitive, and Learning Abilities

</td><td>Web: Supports

</td><td>web: Consistent navigation, error prevention and visual Cues are used.   
language: The client controls almost all the text (headers, fields, etc.) on the website.

</td></tr></tbody></table>

</div>#### Chapter 4: [Hardware](https://www.access-board.gov/ict/#chapter-4-hardware)

Notes: screen reader on the google web store was used for testing

<div align="left" dir="ltr" id="bkmrk-criteria-conformance-4"><table><colgroup><col width="444"></col><col width="257"></col><col width="258"></col></colgroup><thead><tr><th scope="col">Criteria

</th><th scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td>[402 Closed Functionality](https://www.access-board.gov/ict/#402-closed-functionality)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>402.1 General

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>402.2 Speech-Output Enabled

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>402.2.1 Information Displayed On-Screen

</td><td>Web: Supports

</td><td>web: screen reader not built in, but using a screen reader extension allows all labels and fields to have speech output

</td></tr><tr><td>402.2.2 Transactional Outputs

</td><td>Web: Partially supports

</td><td>web: not all transactions show messages. successful login doesn’t get announced, user is only redirected to home page on successful login

</td></tr><tr><td>402.2.3 Speech Delivery Type and Coordination

</td><td>Web: Supports

</td><td>web: The application does not utilize or provide speech output features

</td></tr><tr><td>402.2.4 User Control

</td><td>Web: Supports

</td><td>web: The application does not provide or require speech output features

</td></tr><tr><td>402.2.5 Braille Instructions

</td><td>Web: Supports

</td><td>web: the application does not support or require Braille output features

</td></tr><tr><td>402.3 Volume

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>402.3.1 Private Listening

</td><td>Web: Supports

</td><td>web: The application does not deliver audio output through private listening devices such as headphones or earphones, nor does it provide any functionality that requires magnetic wireless coupling to hearing technologies

</td></tr><tr><td>402.3.2 Non-private Listening

</td><td>Web: Supports

</td><td>web: The application does not feature non-private listening capabilities

</td></tr><tr><td>402.4 Characters on Display Screens

</td><td>Web: Supports

</td><td>web: The application uses the sans-serif font Roboto, meeting the requirements for character display.

</td></tr><tr><td>402.5 Characters on Variable Message Signs

</td><td>Web: Supports

</td><td>web: the application is a web application, which does not include or utilize variable message signs.

</td></tr><tr><td>[403 Biometrics](https://www.access-board.gov/ict/#403-biometrics)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>403.1 General

</td><td>Web: Supports

</td><td>web: The application does not utilize biometric technology for user authentication or interaction

</td></tr><tr><td>[404 Preservation of Information Provided for Accessibility](https://www.access-board.gov/ict/#404-preservation-information)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>404.1 General

</td><td>Web: Supports

</td><td>web: The application preserves all accessibility information during data transmission and conversion

</td></tr><tr><td>[405 Privacy](https://www.access-board.gov/ict/#405-privacy)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>405.1 General

</td><td>Web: Supports

</td><td>web: The application ensures equal privacy for input and output for all users.

</td></tr><tr><td>[406 Standard Connections](https://www.access-board.gov/ict/#406-standard-connections)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>406.1 General

</td><td>Web: Supports

</td><td>web: The application does not use or require specific data connections for input or output, ensuring conformity with industry standards for non-proprietary formats.

</td></tr><tr><td>[407 Operable Parts](https://www.access-board.gov/ict/#407-operable-parts)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>407.2 Contrast

</td><td>Web: Supports

</td><td>The requirement pertains to physical operable parts such as keys and controls on devices. Since the application does not involve any physical operable parts and is entirely software-based, this criterion is not applicable.

</td></tr><tr><td>407.3 Input Controls

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>407.3.1 Tactilely Discernible

</td><td>Web: Supports

</td><td>web: Since the application is entirely software-based and does not include any physical input controls, this criterion is not applicable.

</td></tr><tr><td>407.3.2 Alphabetic Keys

</td><td>Web: Supports

</td><td>web: Since the application is entirely software-based and does not include any physical keyboards, this criterion is not applicable.

</td></tr><tr><td>407.3.3 Numeric Keys

</td><td>Web: Supports

</td><td>web: Since the application is software-based and does not include any physical numeric keypads, this criterion is not applicable.

</td></tr><tr><td>407.4 Key Repeat

</td><td>Web: Supports

</td><td>web:. Since the application is software-based and does not provide or control physical keyboards, this criterion is not applicable.

</td></tr><tr><td>407.5 Timed Response

</td><td>Web: Partially supports

</td><td>web: The application provides visual alerts for timed responses, such as session timeouts. However, the application does not offer a way for users to request additional time.

</td></tr><tr><td>407.6 Operation

</td><td>Web: Supports

</td><td>web: The application is web-based and does not have any physical operable parts.

</td></tr><tr><td>407.7 Tickets, Fare Cards, and Keycards

</td><td>Web: Supports

</td><td>web: All interactions and transactions are handled digitally within the application, making this requirement irrelevant.

</td></tr><tr><td>407.8 Reach Height and Depth

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>407.8.1 Vertical Reference Plane

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.1.1 Vertical Plane for Side Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.1.2 Vertical Plane for Forward Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.2 Side Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.2.1 Unobstructed Side Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.2.2 Obstructed Side Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.3 Forward Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.3.1 Unobstructed Forward Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.3.2 Obstructed Forward Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>[408 Display Screens](https://www.access-board.gov/ict/#408-display-screens)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>408.2 Visibility

</td><td>Web: Supports

</td><td>web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices

</td></tr><tr><td>408.3 Flashing

</td><td>Web: Supports

</td><td>web: This section pertains to hardware components that might have flashing lights or indicators. The application is purely software-based and does not interact with or require any physical hardware components for its operation

</td></tr><tr><td>[409 Status Indicators](https://www.access-board.gov/ict/#409-status-indicators)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>409.1 General

</td><td>Web: Supports

</td><td>web: The application does not include physical status indicators; status information is provided visually through the user interface

</td></tr><tr><td>[410 Color Coding](https://www.access-board.gov/ict/#410-color-coding)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>410.1 General

</td><td>Web: Supports

</td><td>web: links, buttons, and other interactive elements are not identified solely by color. information conveyed through color is also available through text

</td></tr><tr><td>[411 Audible Signals](https://www.access-board.gov/ict/#411-audible-signals)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>411.1 General

</td><td>Web: Supports

</td><td>web: The application does not utilize audible signals or cues to convey information, indicate actions, or prompt responses

</td></tr><tr><td>[412 ICT with Two-Way Voice Communication](https://www.access-board.gov/ict/#412-two-way-communication)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>412.2 Volume Gain

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>412.2.1 Volume Gain for Wireline Telephones

</td><td>Web: Supports

</td><td>web: The application does not involve wireline telephones

</td></tr><tr><td>412.2.2 Volume Gain for Non-Wireline ICT

</td><td>Web: Supports

</td><td>web: The application does not involve non-wireline ICT devices that require volume control

</td></tr><tr><td>412.3 Interference Reduction and Magnetic Coupling

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>412.3.1 Wireless Handsets

</td><td>Web: Supports

</td><td>web: The application does not involve the use of wireless handsets

</td></tr><tr><td>412.3.2 Wireline Handsets

</td><td>Web: Supports

</td><td>web: The application does not involve the use of wireline handsets

</td></tr><tr><td>412.4 Digital Encoding of Speech

</td><td>Web: Supports

</td><td>web: The application does not involve the digital encoding of speech

</td></tr><tr><td>412.5 Real-Time Text Functionality

</td><td>Reserved for future

</td><td>Reserved for future

</td></tr><tr><td>412.6 Caller ID

</td><td>Web: Supports

</td><td>web : The application does not provide or require caller ID functionality

</td></tr><tr><td>412.7 Video Communication

</td><td>Web: Supports

</td><td>web: The application does not provide or require video communication functionality

</td></tr><tr><td>412.8 Legacy TTY Support

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>412.8.1 TTY Connectability

</td><td>Web: Supports

</td><td>web: The application does not support or require TTY connectability

</td></tr><tr><td>412.8.2 Voice and Hearing Carry Over

</td><td>Web: Supports

</td><td>web: The application does not include or require voice and hearing carry over features

</td></tr><tr><td>412.8.3 Signal Compatibility

</td><td>Web: Supports

</td><td>web: The application does not include or require TTY or signal compatibility features

</td></tr><tr><td>412.8.4 Voice Mail and Other Messaging Systems

</td><td>Web: Supports

</td><td>web: The application does not provide voice mail or other messaging systems

</td></tr><tr><td>[413 Closed Caption Processing Technologies](https://www.access-board.gov/ict/#413-closed-caption)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>413.1.1 Decoding and Display of Closed Captions

</td><td>Web: Supports

</td><td>web: The application does not include video content or media that requires closed captions

</td></tr><tr><td>413.1.2 Pass-Through of Closed Caption Data

</td><td>Web: Supports

</td><td>web: The application does not include video content or media that requires closed captions

</td></tr><tr><td>[414 Audio Description Processing Technologies](https://www.access-board.gov/ict/#414-audio-description)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>414.1.1 Digital Television Tuners

</td><td>Web: Supports

</td><td>web: The application does not include or interface with digital television tuners

</td></tr><tr><td>414.1.2 Other ICT

</td><td>Web: Supports

</td><td>web: The application does not include or interface with other ICT related to digital television tuners

</td></tr><tr><td>[415 User Controls for Captions and Audio Descriptions](https://www.access-board.gov/ict/#415-user-controls-captions-audio-descriptions)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>415.1.1 Caption Controls

</td><td>Web: Supports

</td><td>web: The application does not include video content or media that requires closed captions

</td></tr><tr><td>415.1.2 Audio Description Controls

</td><td>Web: Supports

</td><td>web: The application does not include video content requiring audio descriptions

</td></tr></tbody></table>

</div>#### Chapter 5: [Software](https://www.access-board.gov/ict/#chapter-5-software)

<div align="left" dir="ltr" id="bkmrk-criteria-conformance-5"><table><colgroup><col width="442"></col><col width="259"></col><col width="258"></col></colgroup><thead><tr><th scope="col">Criteria

</th><th scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td>501.1 Scope – Incorporation of WCAG 2.0 AA

</td><td>See WCAG 2.x section

</td><td>See information in WCAG 2.x section

</td></tr><tr><td>[502 Interoperability with Assistive Technology](https://www.access-board.gov/ict/#502-interoperability-assistive-technology)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>502.2.1 User Control of Accessibility Features

</td><td>Web: does not support

</td><td>web: no in app controls and documentation for accessibility settings

</td></tr><tr><td>502.2.2 No Disruption of Accessibility Features

</td><td>Web: does not support

</td><td>web: The application does not interfere with or disrupt any built-in accessibility features of the platform

</td></tr><tr><td>502.3 Accessibility Services

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>502.3.1 Object Information

</td><td>Web: Partially supports

</td><td>web: not all UI elements have a ARIA labels, roles and IDs

</td></tr><tr><td>502.3.2 Modification of Object Information

</td><td>Web: Partially supports

</td><td>web: some UI elements (toggles, checkboxes, etc) can be modified using keyboard

</td></tr><tr><td>502.3.3 Row, Column, and Headers

</td><td>Web: Supports

</td><td>web: no tables are used

</td></tr><tr><td>502.3.4 Values

</td><td>Web: Partially supports

</td><td>web: some values are accessible programmatically

</td></tr><tr><td>502.3.5 Modification of Values

</td><td>Web: Partially supports

</td><td>web: some values can be modified programmatically

</td></tr><tr><td>502.3.6 Label Relationships

</td><td>Web: Partially supports

</td><td>web: attributes that define a relationship with labels aren’t explicitly defined

</td></tr><tr><td>502.3.7 Hierarchical Relationships

</td><td>Web: Partially supports

</td><td>web: attributes that define a relationships within elements aren’t explicitly defined

</td></tr><tr><td>502.3.8 Text

</td><td>Web: Partially supports

</td><td>web: text can have better accessibility if ARIA labels were defined

</td></tr><tr><td>502.3.9 Modification of Text

</td><td>Web: Supports

</td><td>web: text input fields can be programmatically controlled

</td></tr><tr><td>502.3.10 List of Actions

</td><td>Web: Partially supports

</td><td>web: accessibility can be improved by adding appropriate ARIA roles and properties to interactive elements.

</td></tr><tr><td>502.3.11 Actions on Objects

</td><td>Web: Partially supports

</td><td>web: accessibility can be improved by adding appropriate ARIA roles and properties to interactive elements.

</td></tr><tr><td>502.3.12 Focus Cursor

</td><td>Web: Partially supports

</td><td>web: most interactive elements correctly manage focus

</td></tr><tr><td>502.3.13 Modification of Focus Cursor

</td><td>Web: Partially supports

</td><td>web The application allows focus and cursor positions to be controlled programmatically, supporting assistive technologies. accessibility can be improved by adding appropriate ARIA roles and properties

</td></tr><tr><td>502.3.14 Event Notification

</td><td>Web: does not support

</td><td>The application currently lacks the implementation of ARIA attributes or other mechanisms to notify assistive technology about changes in component states, values, names, descriptions, or boundaries. Without these notifications, assistive technology users may not be aware of these changes.

</td></tr><tr><td>502.4 Platform Accessibility Features

</td><td>Web: Supports

</td><td>web: The application is a web-based platform and does not provide platform-level accessibility features.

</td></tr><tr><td>[503 Applications](https://www.access-board.gov/ict/#503-applications)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>503.2 User Preferences

</td><td>Web: Supports

</td><td>web: The application is designed to be isolated from the underlying platform software. Therefore, it is not required to conform to the 503.2 User Preferences guideline. This exemption applies because the application is a web application, and web applications are generally considered isolated from the platform software.

</td></tr><tr><td>503.3 Alternative User Interfaces

</td><td>Web: Supports

</td><td>web: The application does not provide an alternative user interface that functions as assistive technology. Instead, it relies on standard web accessibility practices and compatibility with browser-based assistive technologies to ensure accessibility.

</td></tr><tr><td>503.4 User Controls for Captions and Audio Description

</td><td>web: Not applicable

</td><td>web: the website does not display video with synchronized audio. Section removed

</td></tr><tr><td>[504 Authoring Tools](https://www.access-board.gov/ict/#504-authoring-tools)

</td><td>web: Not applicable

</td><td>The application in question is not an authoring tool. Section removed

</td></tr></tbody></table>

</div>#### Chapter 6: [Support Documentation and Services](https://www.access-board.gov/ict/#chapter-6-support-documentation-and-services)

<div align="left" dir="ltr" id="bkmrk-criteria-conformance-6"><table><colgroup><col width="442"></col><col width="259"></col><col width="258"></col></colgroup><thead><tr><th scope="col">Criteria

</th><th scope="col">Conformance Level

</th><th scope="col">Remarks and Explanations

</th></tr></thead><tbody><tr><td>601.1 Scope

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>[602 Support Documentation](https://www.access-board.gov/ict/#602-support-documentation)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>602.2 Accessibility and Compatibility Features

</td><td>Web: does not support

</td><td>web: The application currently does not have specific documentation detailing accessibility and compatibility features.

</td></tr><tr><td>602.3 Electronic Support Documentation

</td><td>See [WCAG 2.x](https://docs.google.com/document/d/11W8e2TPEN5a2z4WU3q2mAO7VaEks7hje/edit#heading=h.qsh70q) section

</td><td>See information in WCAG 2.x section

</td></tr><tr><td>602.4 Alternate Formats for Non-Electronic Support Documentation

</td><td>Web: does not support

</td><td>web: The application currently does not have specific documentation detailing accessibility and compatibility features.

</td></tr><tr><td>[603 Support Services](https://www.access-board.gov/ict/#603-support-services)

</td><td>Heading cell – no response required

</td><td>Heading cell – no response required

</td></tr><tr><td>603.2 Information on Accessibility and Compatibility Features

</td><td>Web: does not support

</td><td>web: ICT support services do not currently include information on the accessibility and compatibility features as required by 602.2. Without this information, users with disabilities may not be able to fully understand or utilize the accessibility features of the application.

</td></tr><tr><td>603.3 Accommodation of Communication Needs

</td><td>Web: does not support

</td><td>web: Current support services do not accommodate the communication needs of individuals with disabilities

</td></tr></tbody></table>

</div>---