VPAT - Tomahawk Technologies & OperationsCommander Accessibility Conformance Report

Revised Section 508 Edition - (Based on VPAT® Version 2.5Rev) 

 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. 

 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 

 

 

 

 

 

 Date of Change 

 

 

 Notes 

 

 

 

 

 August 13, 2024 

 

 

 Final Draft - SJ 

 

 

 

 May 13, 2025 

 Review for Accuracy - SJ 

 

 

 March 17, 2026 

 Review for Accuracy - SJ 

 

 

 April 8, 2026 

 Update to WCAG 2.1 Level AA - CB 

 

 

 

 

 

 

 

 

 

 

 

 

 

 Name of Product/Version: 

 

 

 OperationsCommander - User Portal 

 

 

 

 

 Platform: 

 

 

 Web 

 

 

 

 

 Report Date: 

 

 

 March 2026 

 

 

 

 

 Product Description: 

 

 

 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. 

 

 

 

 

 Contact Information: 

 

 

 support@ops-com.com 

 

 

 

 

 Evaluation Methods Used: 

 

 

 Testing is based on knowledge of general product functionality 

 

 

 

 

 

 Applicable Standards/Guidelines 

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

 

 

 

 

 

 Standard/Guideline 

 

 

 Included In Report 

 

 

 

 

 

 

 Web Content Accessibility Guidelines 2.0 

 

 

 Level A (Yes) 

 Level AA (Yes) 

 Level AAA (Yes) 

 

 

 

 

 Web Content Accessibility Guidelines 2.1 

 

 

 Level A (Yes) 

 Level AA (Yes) 

 Level AAA (Yes) 

 

 

 

 

 Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 

 

 

 (Yes) 

 

 

 

 

 

 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.1 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.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.1 Conformance Requirements . 

 Table 1: Success Criteria, Level A 

 

 

 

 

 

 Criteria 

 

 

 Conformance Level 

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 1.1.1 Non-text Content (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: No audio or video media is used on the website 

 

 

 

 

 1.2.2 Captions (Prerecorded) (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software)  

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: No audio or video media is used on the website 

 

 

 

 

 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software)  

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: No audio or video media is used on the website 

 

 

 

 

 1.3.1 Info and Relationships (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Semantic structure and labeling complies. ARIA roles are explicitly defined to enhance accessibility. 

 

 

 

 

 1.3.2 Meaningful Sequence (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Logical order is followed on all pages 

 

 

 

 

 1.3.3 Sensory Characteristics  (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: There are no instructions that rely solely on sensory characteristics 

 

 

 

 

 1.4.1 Use of Color (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Links, buttons, and other interactive elements are not identified solely by color. information conveyed through color is also available through text 

 

 

 

 

 1.4.2 Audio Control (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Website does not play any audio or video media 

 

 

 

 

 2.1.1 Keyboard (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: All pages and functionality can be accessed using a keyboard 

 

 

 

 

 2.1.2 No Keyboard Trap (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Pages that can be accessed using a keyboard can also be exited using the keyboard 

 

 

 

 

 2.1.4 Character Key Shortcuts (Level A) 

 

 

 Web: Not applicable 

 

 

 Web: No single-character shortcuts exist. All keydown bindings use .enter or .space. 

 

 

 

 

 2.2.1 Timing Adjustable (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: In app notifications (success or failure messages) have a timer with a button to dismiss before the timer ends. Prior warning is given when the user’s session times out. 

 

 

 

 

 2.2.2 Pause, Stop, Hide (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

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

 

 

 

 

 2.3.1 Three Flashes or Below Threshold (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Website does not contain any flashing content 

 

 

 

 

 2.4.1 Bypass Blocks (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 

 

 

 

 

 Web: Supports 

 

 

 Web: A “skip to main content” link is provided as the first focusable element on the page, allowing keyboard users to bypass repeated navigation (e.g., the side menu with multiple items) and move directly to the primary onboarding content. 

 

 

 

 

 2.4.2 Page Titled (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: All pages are titled appropriately  

 

 

 

 

 2.4.3 Focus Order (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Interactive elements in anis in an order that follows sequences and relationships within the content 

 

 

 

 

 2.4.4 Link Purpose (In Context) (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 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 

 

 

 

 

 2.5.1 Pointer Gestures (Level A) 

 

 

 Web: Supports 

 

 

 Swipers (touch) are hidden on desktop; stacked grid shows instead. Welcome/subscriptions pages have explicit Next/Prev/Skip buttons. 

 

 

 

 

 2.5.2 Pointer Cancellation (Level A) 

 

 

 Web: Supports 

 

 

 All actions fire on (click) (up event). Only mousedown found is non-destructive (markFieldTouched). 

 

 

 

 

 2.5.3 Label in Name (Level A) 

 

 

 Web: Supports 

 

 

 Visible button text matches aria-label values across the app. 

 

 

 

 

 2.5.4 Motion Actuation (Level A) 

 

 

 Web: Not applicable 

 

 

 No device motion, accelerometer, gyroscope, or shake detection found. 

 

 

 

 

 3.1.1 Language of Page (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Default browser language is used 

 

 

 

 

 3.2.1 On Focus (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Focus on input fields does not change context 

 

 

 

 

 3.2.2 On Input (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Submit buttons or dialogues are provided in areas where change of context may be initiated 

 

 

 

 

 3.3.1 Error Identification (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Fully complies 

 

 

 

 

 3.3.2 Labels or Instructions (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Placeholders and/or labels are used to describe input fields 

 

 

 

 

 4.1.1 Parsing (Level A) 

 Also applies to: 

 WCAG 2.1 – Always answer ‘Supports’ 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 For WCAG 2.0, WCAG 2.1, and the 508 standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata . 

 

 

 

 

 4.1.2 Name, Role, Value (Level A) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Form controls elements have label elements associated to them 

 

 

 

 

 

 Table 2: Success Criteria, Level AA 

 Notes: WebAIM Contrast Checker was used to test contrast ratios 

 

 

 

 

 

 Criteria 

 

 

 Conformance Level 

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 1.2.4 Captions (Live) (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: No audio or video content is used on website 

 

 

 

 

 1.2.5 Audio Description (Prerecorded) (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: No audio or video content is used on website 

 

 

 

 

 1.3.4 Orientation (Level AA) 

 

 

 Web: Supports 

 

 

 No CSS orientation locks found. 

 

 

 

 

 1.3.5 Identity Input Purpose (Level AA) 

 

 

 Web: Partially Supports 

 

 

 Web: Any input collecting personal info (e.g., name, email, address) needs autocomplete so browsers/assistive tech can auto-fill. 

   

 Will be supported by May 31, 2026 

 

 

 

 

 1.4.3 Contrast (Minimum) (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 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 

 

 

 

 

 1.4.4 Resize text (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Text and components are responsive to different screen sizes and zoom levels 

 

 

 

 

 1.4.5 Images of Text (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 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) 

 

 

 

 

 1.4.10 Reflow (Level AA) 

 

 

 Web: Supports 

 

 

 Responsive grid with breakpoint sizing. Content reflows at 320px. 

 

 

 

 

 1.4.11 Non-text Contrast (Level AA) 

 

 

 Web: Supports 

 

 

 Focus outlines are 3px #1a73e8 on white (high contrast). Ionic toggle/button borders meet 3:1. 

 

 

 

 

 1.4.12 Text Spacing (Level AA) 

 

 

 Web: Supports 

 

 

 No fixed heights or overflow: hidden that would clip adjusted text. Uses rem/em units. 

 

 

 

 

 1.4.13 Content on Hover or Focus (Level AA) 

 

 

 Web: Supports 

 

 

 Popovers triggered by click/keyboard (not hover), dismissible, and persistent until closed. 

 

 

 

 

 2.4.5 Multiple Ways (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 

 

 

 

 

 Web: Supports 

 

 

 Web: Search functionality on pages and linking to all of the pages on the site from the home page 

 

 

 

 

 2.4.6 Headings and Labels (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Content is described in headings and labels 

 

 

 

 

 2.4.7 Focus Visible (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Elements do visibility show that they have received focus  

 

 

 

 

 3.1.2 Language of Parts (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: The language of each passage or phrase in the content can be programmatically determined when it differs from the default language of the page. 

 

 

 

 

 3.2.3 Consistent Navigation (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 

 

 

 

 

 Web: Supports 

 

 

 Web: Side navigation bar is consistent on all pages 

 

 

 

 

 3.2.4 Consistent Identification (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 

 

 

 

 

 Web: Supports 

 

 

 Web: Using consistent identification for components with similar functionality. 

 

 

 

 

 3.3.3 Error Suggestion (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Form validation is provided with DOM text 

 

 

 

 

 

 

 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) 

 Also applies to: 

 Revised Section 508 

 

 

 501 (Web)(Software) 

 

 

 504.2 (Authoring Tool) 

 

 

 602.3 (Support Docs) 

 

 

 

 

 Web: Supports 

 

 

 Web: Financial transactions have a mechanism for reviewing, confirming, and correcting information before finalizing the submission. 

 

 

 

 

 4.1.3 Status Messages (Level AA) 

 

 

 Web: Partially Supports 

 

 

 Web: Success toasts, loading states, and cart updates are currently invisible to screen readers. 

   

 Will be supported by May 31, 2026 

 

 

 

 

 

 Table 3: Success Criteria, Level AAA 

 

 

 

 

 

 Criteria 

 

 

 Conformance Level 

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 1.2.6 Sign Language (Prerecorded) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: No media content is used 

 

 

 

 

 1.2.7 Extended Audio Description (Prerecorded) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: No media content is used 

 

 

 

 

 1.2.8 Media Alternative (Prerecorded) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: No media content is used 

 

 

 

 

 1.2.9 Audio-only (Live) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: No media content is used 

 

 

 

 

 1.3.6 Identify Purpose (Level AAA) 

 

 

 Web: Partially Supports 

 

 

 <nav>, role="alert", role="button" exist. Ionic shadow DOM provides implicit ARIA roles but no explicit <main>/<header>/<footer> landmarks. 

 

 

 

 

 1.4.6 Contrast (Enhanced )  (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 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: 7:1 

 

 

 

 

 

 

 1.4.7 Low or No Background Audio (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: No audio or video media content is used 

 

 

 

 

 1.4.8 Visual Presentation (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Does Not Support 

 

 

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

 

 

 Foreground and background colors. 

 

 

 Width of blocks of text. 

 

 

 Text alignment. 

 

 

 Line spacing. 

 

 

 Text size. 

 

 

 

 

 

 

 1.4.9 Images of Text (No Exception) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: Images of text are only used for pure decoration (client or OPSCOM logo) 

 

 

 

 

 2.1.3 Keyboard (No Exception) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Does Not Support 

 

 

 Web: Not all functionality of the content is operable through a keyboard interface 

 

 

 

 

 2.2.3 No Timing (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Does Not Support 

 

 

 Web: Users get logged out after inactivity without the ability to extend session 

 

 

 

 

 2.2.4 Interruptions (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: Pages do not automatically update while they are active. 

 

 

 

 

 2.2.5 Re-authenticating (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Does Not Support 

 

 

 Web: When a session expires, forms are not restored 

 

 

 

 

 2.2.6 Timeouts (Level AAA) 

 

 

 Web: Supports 

 

 

 SessionTimeoutService shows a persistent warning toast 5 minutes before session expiry. Timer resets on API activity. 

 

 

 

 

 2.3.2 Three Flashes (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: Website has no flashing content 

 

 

 

 

 2.3.3 Animation from Interactions (Level AAA) 

 

 

 Web: Partially Supports 

 

 

 No prefers-reduced-motion media query found. Ionic's built-in page transitions would still play for users who prefer reduced motion. 

 

 

 

 

 2.4.8 Location (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: Navigation bars and page titles show where the user currently is on the website 

 

 

 

 

 2.4.9 Link Purpose (Link Only) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 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 

 

 

 

 

 2.4.10 Section Headings (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: Pages are organized using headings 

 

 

 

 

 2.5.5 Target Size (Level AAA) 

 

 

 Web: Partially Supports 

 

 

 Ionic defaults buttons/items to 44px+. Some inline icons (help, edit) may be smaller — needs visual audit . 

 

 

 

 

 2.5.6 Concurrent Input Mechanisms (Level AAA) 

 

 

 Web: Supports 

 

 

 No input restriction. Users can freely switch between touch, mouse, and keyboard. 

 

 

 

 

 3.1.3 Unusual Words (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 3.1.4 Abbreviations (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 3.1.5 Reading Level (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 3.1.6 Pronunciation (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Does Not Support 

 

 

 Web: No mechanism is available for identifying specific pronunciation of words 

 

 

 

 

 3.2.5 Change on Request (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 3.3.5 Help (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

 Web: For forms, the client can add instructions for each field to describe necessary input 

 

 

 

 

 3.3.6 Error Prevention (All) (Level AAA) 

 Revised Section 508 – Does not apply 

 

 

 Web: Supports 

 

 

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

 

 

 

 

 

 

 

 Revised Section 508 Report 

 Notes: WebAIM Contrast Checker was used to test contrast ratios 

 Chapter 3: Functional Performance Criteria (FPC) 

 

 

 

 

 

 Criteria 

 

 

 Conformance Level  

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 302.1 Without Vision 

 

 

 Web: Supports 

 

 

 Web: Website can fully used with keyboard only 

 

 

 

 

 302.2 With Limited Vision 

 

 

 Web: Supports 

 

 

 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 

 

 

 

 

 302.3 Without Perception of Color 

 

 

 Web: Supports 

 

 

 Web: Information conveyed with color is also available without color 

 

 

 

 

 302.4 Without Hearing 

 

 

 Web: Supports 

 

 

 Web: No audio is played on the website 

 

 

 

 

 302.5 With Limited Hearing 

 

 

 Web: Supports 

 

 

 Web: No audio is played on the website 

 

 

 

 

 302.6 Without Speech 

 

 

 Web: Supports 

 

 

 Web: No speech is needed for any functionality 

 

 

 

 

 302.7 With Limited Manipulation 

 

 

 Web: Supports 

 

 

 Web: Fully functional with a keyboard, controls are operated with a single action, avoiding the need for simultaneous pressing or holding of multiple keys/buttons. 

 

 

 

 

 302.8 With Limited Reach and Strength 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 302.9 With Limited Language, Cognitive, and Learning Abilities 

 

 

 Web: Supports 

 

 

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

 

 

 

 

 

 Chapter 4: Hardware 

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

 

 

 

 

 

 Criteria 

 

 

 Conformance Level  

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 402 Closed Functionality 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 402.1 General 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 402.2 Speech-Output Enabled 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 402.2.1 Information Displayed On-Screen 

 

 

 Web: Supports 

 

 

 Web: Screen reader not built in, but using a screen reader extension allows all labels and fields to have speech output 

 

 

 

 

 402.2.2 Transactional Outputs 

 

 

 Web: Partially supports 

 

 

 Web: Not all transactions show messages. successful login doesn’t get announced, user is only redirected to home page on successful login 

 

 

 

 

 402.2.3 Speech Delivery Type and Coordination 

 

 

 Web: Supports 

 

 

 Web: The application does not utilize or provide speech output features 

 

 

 

 

 402.2.4 User Control 

 

 

 Web: Supports 

 

 

 Web: The application does not provide or require speech output features 

 

 

 

 

 402.2.5 Braille Instructions 

 

 

 Web: Supports 

 

 

 Web: The application does not support or require Braille output features 

 

 

 

 

 402.3 Volume 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 402.3.1 Private Listening 

 

 

 Web: Supports 

 

 

 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 

 

 

 

 

 402.3.2 Non-private Listening 

 

 

 Web: Supports 

 

 

 Web: The application does not feature non-private listening capabilities 

 

 

 

 

 402.4 Characters on Display Screens 

 

 

 Web: Supports 

 

 

 Web: The application uses the sans-serif font Roboto, meeting the requirements for character display. 

 

 

 

 

 402.5 Characters on Variable Message Signs 

 

 

 Web: Supports 

 

 

 Web: The application is a web application, which does not include or utilize variable message signs. 

 

 

 

 

 403 Biometrics 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 403.1 General 

 

 

 Web: Supports 

 

 

 Web: The application does not utilize biometric technology for user authentication or interaction 

 

 

 

 

 404 Preservation of Information Provided for Accessibility 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 404.1 General 

 

 

 Web: Supports 

 

 

 Web: The application preserves all accessibility information during data transmission and conversion 

 

 

 

 

 405 Privacy 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 405.1 General 

 

 

 Web: Supports 

 

 

 Web: The application ensures equal privacy for input and output for all users. 

 

 

 

 

 406 Standard Connections 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 406.1 General 

 

 

 Web: Supports 

 

 

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

 

 

 

 

 407 Operable Parts 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 407.2 Contrast 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 407.3 Input Controls 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 407.3.1 Tactilely Discernible 

 

 

 Web: Supports 

 

 

 Web: Since the application is entirely software-based and does not include any physical input controls, this criterion is not applicable. 

 

 

 

 

 407.3.2 Alphabetic Keys 

 

 

 Web: Supports 

 

 

 Web: Since the application is entirely software-based and does not include any physical keyboards, this criterion is not applicable. 

 

 

 

 

 407.3.3 Numeric Keys 

 

 

 Web: Supports 

 

 

 Web: Since the application is software-based and does not include any physical numeric keypads, this criterion is not applicable. 

 

 

 

 

 407.4 Key Repeat 

 

 

 Web: Supports 

 

 

 Web:. Since the application is software-based and does not provide or control physical keyboards, this criterion is not applicable. 

 

 

 

 

 407.5 Timed Response 

 

 

 Web: Partially supports 

 

 

 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. 

 

 

 

 

 407.6 Operation 

 

 

 Web: Supports 

 

 

 Web: The application is web-based and does not have any physical operable parts. 

 

 

 

 

 407.7 Tickets, Fare Cards, and Keycards 

 

 

 Web: Supports 

 

 

 Web: All interactions and transactions are handled digitally within the application, making this requirement irrelevant. 

 

 

 

 

 407.8 Reach Height and Depth 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 407.8.1 Vertical Reference Plane 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.1.1 Vertical Plane for Side Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.1.2 Vertical Plane for Forward Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.2 Side Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.2.1 Unobstructed Side Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.2.2 Obstructed Side Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.3 Forward Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.3.1 Unobstructed Forward Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.3.2 Obstructed Forward Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.3.2.1 Operable Part Height for ICT with Obstructed Forward Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 407.8.3.2.2 Knee and Toe Space under ICT with Obstructed Forward Reach 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 408 Display Screens 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 408.2 Visibility 

 

 

 Web: Supports 

 

 

 Web: The application is purely software-based and does not require specialized physical hardware beyond standard input devices 

 

 

 

 

 408.3 Flashing 

 

 

 Web: Supports 

 

 

 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 

 

 

 

 

 409 Status Indicators 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 409.1 General 

 

 

 Web: Supports 

 

 

 Web: The application does not include physical status indicators; status information is provided visually through the user interface 

 

 

 

 

 410 Color Coding 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 410.1 General 

 

 

 Web: Supports 

 

 

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

 

 

 

 

 411 Audible Signals 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 411.1 General 

 

 

 Web: Supports 

 

 

 Web: The application does not utilize audible signals or cues to convey information, indicate actions, or prompt responses 

 

 

 

 

 412 ICT with Two-Way Voice Communication 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 412.2 Volume Gain 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 412.2.1 Volume Gain for Wireline Telephones 

 

 

 Web: Supports 

 

 

 Web: The application does not involve wireline telephones 

 

 

 

 

 412.2.2 Volume Gain for Non-Wireline ICT 

 

 

 Web: Supports 

 

 

 Web: The application does not involve non-wireline ICT devices that require volume control 

 

 

 

 

 412.3 Interference Reduction and Magnetic Coupling 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 412.3.1 Wireless Handsets 

 

 

 Web: Supports 

 

 

 Web: The application does not involve the use of wireless handsets 

 

 

 

 

 412.3.2 Wireline Handsets 

 

 

 Web: Supports 

 

 

 Web: The application does not involve the use of wireline handsets 

 

 

 

 

 412.4 Digital Encoding of Speech 

 

 

 Web: Supports 

 

 

 Web: The application does not involve the digital encoding of speech 

 

 

 

 

 412.5 Real-Time Text Functionality 

 

 

 Reserved for future 

 

 

 Reserved for future 

 

 

 

 

 412.6 Caller ID 

 

 

 Web: Supports 

 

 

 Web : The application does not provide or require caller ID functionality 

 

 

 

 

 412.7 Video Communication 

 

 

 Web: Supports 

 

 

 Web: The application does not provide or require video communication functionality 

 

 

 

 

 412.8 Legacy TTY Support 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 412.8.1 TTY Connectability 

 

 

 Web: Supports 

 

 

 Web: The application does not support or require TTY connectability 

 

 

 

 

 412.8.2 Voice and Hearing Carry Over 

 

 

 Web: Supports 

 

 

 Web: The application does not include or require voice and hearing carry over features 

 

 

 

 

 412.8.3 Signal Compatibility 

 

 

 Web: Supports 

 

 

 Web: The application does not include or require TTY or signal compatibility features 

 

 

 

 

 412.8.4 Voice Mail and Other Messaging Systems 

 

 

 Web: Supports 

 

 

 Web: The application does not provide voice mail or other messaging systems 

 

 

 

 

 413 Closed Caption Processing Technologies 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 413.1.1 Decoding and Display of Closed Captions 

 

 

 Web: Supports 

 

 

 Web: The application does not include video content or media that requires closed captions 

 

 

 

 

 413.1.2 Pass-Through of Closed Caption Data 

 

 

 Web: Supports 

 

 

 Web: The application does not include video content or media that requires closed captions 

 

 

 

 

 414 Audio Description Processing Technologies 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 414.1.1 Digital Television Tuners 

 

 

 Web: Supports 

 

 

 Web: The application does not include or interface with digital television tuners 

 

 

 

 

 414.1.2 Other ICT 

 

 

 Web: Supports 

 

 

 Web: The application does not include or interface with other ICT related to digital television tuners 

 

 

 

 

 415 User Controls for Captions and Audio Descriptions 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 415.1.1 Caption Controls 

 

 

 Web: Supports 

 

 

 Web: The application does not include video content or media that requires closed captions 

 

 

 

 

 415.1.2 Audio Description Controls 

 

 

 Web: Supports 

 

 

 Web: The application does not include video content requiring audio descriptions 

 

 

 

 

 

 Chapter 5:  Software 

 

 

 

 

 

 Criteria 

 

 

 Conformance Level  

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 501.1 Scope – Incorporation of WCAG 2.1 AA 

 

 

 See WCAG 2.x section 

 

 

 See information in WCAG 2.x section 

 

 

 

 

 502 Interoperability with Assistive Technology 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 502.2.1 User Control of Accessibility Features 

 

 

 Web: Does Not Support 

 

 

 Web: no in app controls and documentation for accessibility settings 

 

 

 

 

 502.2.2 No Disruption of Accessibility Features 

 

 

 Web: Does Not Support 

 

 

 Web: The application does not interfere with or disrupt any built-in accessibility features of the platform 

 

 

 

 

 502.3 Accessibility Services 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 502.3.1 Object Information 

 

 

 Web: Partially supports 

 

 

 Web: not all UI elements have a ARIA labels, roles and IDs 

 

 

 

 

 502.3.2 Modification of Object Information 

 

 

 Web: Partially supports 

 

 

 Web: some UI elements (toggles, checkboxes, etc.) can be modified using keyboard 

 

 

 

 

 502.3.3 Row, Column, and Headers 

 

 

 Web: Supports 

 

 

 Web: no tables are used 

 

 

 

 

 502.3.4 Values 

 

 

 Web: Partially supports 

 

 

 Web: some values are accessible programmatically 

 

 

 

 

 502.3.5 Modification of Values 

 

 

 Web: Partially supports 

 

 

 Web: some values can be modified programmatically 

 

 

 

 

 502.3.6 Label Relationships 

 

 

 Web: Partially supports 

 

 

 Web: attributes that define a relationship with labels aren’t explicitly defined 

 

 

 

 

 502.3.7 Hierarchical Relationships 

 

 

 Web: Partially supports 

 

 

 Web: attributes that define a relationships within elements aren’t explicitly defined 

 

 

 

 

 502.3.8 Text 

 

 

 Web: Partially supports 

 

 

 Web: text can have better accessibility if ARIA labels were defined 

 

 

 

 

 502.3.9 Modification of Text 

 

 

 Web: Supports 

 

 

 Web: text input fields can be programmatically controlled  

 

 

 

 

 502.3.10 List of Actions 

 

 

 Web: Partially supports 

 

 

 Web: accessibility can be improved by adding appropriate ARIA roles and properties to interactive elements. 

 

 

 

 

 502.3.11 Actions on Objects 

 

 

 Web: Partially supports 

 

 

 Web: accessibility can be improved by adding appropriate ARIA roles and properties to interactive elements. 

 

 

 

 

 502.3.12 Focus Cursor 

 

 

 Web: Partially supports 

 

 

 Web: most interactive elements correctly manage focus 

 

 

 

 

 502.3.13 Modification of Focus Cursor 

 

 

 Web: Partially supports 

 

 

 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 

 

 

 

 

 502.3.14 Event Notification 

 

 

 Web: Does Not Support 

 

 

 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. 

 

 

 

 

 502.4 Platform Accessibility Features 

 

 

 Web: Supports 

 

 

 Web: The application is a web-based platform and does not provide platform-level accessibility features.  

 

 

 

 

 503 Applications 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 503.2 User Preferences 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 503.3 Alternative User Interfaces 

 

 

 Web: Supports 

 

 

 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. 

 

 

 

 

 503.4 User Controls for Captions and Audio Description 

 

 

 Web: Not applicable 

 

 

 Web: the website does not display video with synchronized audio. Section removed 

 

 

 

 

 504 Authoring Tools 

 

 

 Web: Not applicable 

 

 

 The application in question is not an authoring tool. Section removed 

 

 

 

 

 

 Chapter 6:  Support Documentation and Services 

 

 

 

 

 

 Criteria 

 

 

 Conformance Level  

 

 

 Remarks and Explanations 

 

 

 

 

 

 

 601.1 Scope 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 602 Support Documentation 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 602.2 Accessibility and Compatibility Features 

 

 

 Web: Does Not Support 

 

 

 Web: The application currently does not have specific documentation detailing accessibility and compatibility features. 

 

 

 

 

 602.3 Electronic Support Documentation 

 

 

 See WCAG 2.x section 

 

 

 See information in WCAG 2.x section 

 

 

 

 

 602.4 Alternate Formats for Non-Electronic Support Documentation 

 

 

 Web: Does Not Support 

 

 

 Web: The application currently does not have specific documentation detailing accessibility and compatibility features. 

 

 

 

 

 603 Support Services 

 

 

 Heading cell – no response required 

 

 

 Heading cell – no response required 

 

 

 

 

 603.2 Information on Accessibility and Compatibility Features 

 

 

 Web: Does Not Support 

 

 

 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. 

 

 

 

 

 603.3 Accommodation of Communication Needs 

 

 

 Web: Does Not Support 

 

 

 Web: Current support services do not accommodate the communication needs of individuals with disabilities