# Product & Support Info # Customer Support FAQ ### How do I launch a support ticket? The best way to launch a support ticket is to email . This email is monitored Monday to Friday from 9 a.m. to 5 p.m. EST. ### What after-hours support do you provide? After hours support is limited to [critical issues](https://opscom.wiki/books/product-support-info/page/launching-a-critical-support-ticket). Critical is defined as system outages or issues that threaten immediate work stoppage. This support is provided by email and is staffed by on-call personnel. Issues will be triaged within 15 minutes and a status notification will be sent to you within 1 hour for Critical issues. This notification will include an estimated time to resolution. The goal is to get you back up and running as quickly as possible with minimal impact on your organization. ### How are upgrades delivered? Upgrades, Hotfixes and new Releases will be assessed by our Project Management Team and rolled out to clients to ensure minimal impact. In most cases, rollouts will be transparent to clients. Release notes are always available on the Upcoming Release page. Typically OPSCOM provides a monthly release of fixes and features. The Upcoming Release page is updated as items are added. We only do rollouts on certain days to ensure that we have a maximum coverage available to support users if issues arise. In the case of a large feature release, we may decide to stage this release to our clients and work directly with them to bring them up quickly and efficiently. ### What provisions do you have for training? New customers get one-on-one system training as per their contract. Extra training hours can be negotiated with your Sales Rep. The wiki has a full complement of articles, FAQs and videos to help you going forward. The self-guided training agenda is also helpful for learning the system and each client gets a preview environment to use for testing and training. The preview spaces are secured in the same manner as our production/live systems, though they exist in a testing environment. ### How is your support team structured? The support team is staffed with front line and escalation agents. Front line support agents help all customers with support issues by email and Premium support customers by telephone. They also have the ability to do screen sharing if the issues requires it. Escalation points help push fixes through development and manage the customer experience as well as provide guidance to our front line agents. ### Do you have online resources, self-help tools? Yes, we have a public wiki available that contains articles, FAQs, videos and webinars. ### What hours is telephone support available? Telephone Support is available to our Premium customers Mon-Fri 9-5 EST. Standard Plus support clients have email support only during the same hours. ### How does your escalation process work? Issues are escalated when the front line staff has determined through working with the customer and testing that an item is a bug. The escalation manager will assess the bug's severity and the impact it is having on the client and enter the issue into JIRA. JIRA is the system we use to track development work. The issue will be linked through JIRA to the Help Desk conversation. The client will be advised on estimated time to resolution and the Development team will address the bug. Once addressed, it will be passed to the Quality Assurance team for testing. The client will be informed that the issue is addressed and available through the original Support ticket. Please note, depending on the severity of the bug and the availability of a workaround, fix times can range from one (1) day to many months. # Product Information Sheets ## Welcome to our Information Gallery Feel free to download our .pdf files to help you better understand the many features and abilities of the **OperationsCommander** platform.
[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/1M0image.png)](https://opscom.wiki/uploads/images/gallery/2024-06/1M0image.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/Ideimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/Ideimage.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/s2pimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/s2pimage.png)
## Why OPSCOM ## One System ## Handhelds
[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/ZdQimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/ZdQimage.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/8ksimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/8ksimage.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/N1Simage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/N1Simage.png)
## ParkAdmin ## ViolationAdmin ## IncidentAdmin
[![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/FD9image.png)](https://opscom.wiki/uploads/images/gallery/2024-06/FD9image.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/fvQimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/fvQimage.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2024-06/scaled-1680-/iDmimage.png)](https://opscom.wiki/uploads/images/gallery/2024-06/iDmimage.png)
## Text2ParkMe ## Temp Permits ## OPSCOM LPR
# OPSCOM Glossary of Terms ## Detailed Definitions
***Primary Driver***The designation of Primary Driver is put in place to identify the owner of a vehicle in most cases. A vehicle can be in the system under two user profiles however there should only be one primary driver. The Primary Driver will receive communication from the system such as violation notices. There is a nightly script that runs which will designate primary driver to any vehicle that has been added to the system. If there is no Primary Driver on a vehicle when an appeal is launched, the person launching the appeal will be automatically designated as the Primary Driver.
***DNTT***A DNTT Note (Do Not Ticket or Tow) information is used to notify enforcement officers that a particular vehicle should not receive any violations in a particular lot, during a particular date and time.
***Multiple Offences***An administrator can add multiple Offences to a single Violation (ticket).
***Spoiled*** This is used to cancel a manual ticket if an officer has started to write a manual violation and then VOIDS it. This could occur when an officer makes a mistake on the ticket or the person at fault comes back to their vehicle and moves it. The violation is marked "Spoiled" as paper violations are incrementally numbered and must be accounted for.
***User Profile icon***
![](https://OPSCOM.atlassian.net/wiki/download/attachments/756285/UserProfileIcon.png?version=1&modificationDate=1465912437000&cacheVersion=1&api=v2) This is the icon that is used to link back to the User Profile information
***Rollover***A rollover is an action taken at the end of a term/year, in which all assigned permits for a select group (I.e staff/faculty) are carried over to the next term/year. This means that a faculty member with Permit A1 for the fall term, will continue to have Permit A1 in the winter term, as the permit was part of a rollover. Rollovers may be applied to all permits (in this case: parking) or to a selected group of permits. Admins may choose to rollover permits (carry the permit to the next term) while automatically deducting the cost of the permit (or charging individuals – payroll deduction usually in the case of faculty) OR they can choose to not do any rollovers. Rollover is an optional function and does not HAVE to happen, but makes the assignment of permits much easier if a selected group of users (ex. Full time staff/faculty) continue to carry the same permit, rather that being reassigned a new permit every term.
**Merge Users**Merge Users is a process in OPSCOM that allows administrators to take two user profiles (usually one has been created in error) and merge (combine, blend) the two user profiles into one user. All user information including history with be merged to the new user.
**Merge Vehicles**Merge Vehicles is a process in OPSCOM that allows administrators to take two vehicles and merge them into one. This will correct vehicle duplicates that can be problematic for enforcement.
**Common Lot **A Common Lot is not defined by user type, for example, a Bicycle lot. It doesn't matter if you're staff/faculty or student - you can park there if you have a bike, therefore it is a common lot.
**Midnight List**The Midnight list shows all permits and lockers that are reserved but have not been paid for. These items will be released back to available stock each day at midnight.
**Lot Groups**A lot group is a method to group similar lots. A lot may **ONLY** belong to 1 group. Lot groups exists to allow similar lots to be seen as 1 single entity for enforcement. For example: Lot 1, Lot 3, and Lot 5 are all student parking lots. - - Lots 1, 3, & 5 may belong to **one lot group,** called "Student Lots". - This allows officers to see that they are all student parking lots, essentially as a single entity. - Individually, these lots may have their own zones applied to them, but they may only belong to one lot group.
**RBAC- Role-Based Access Control**Through RBAC, you can control what end-users can do at both broad and granular levels. You can designate whether the user is an administrator, a specialist user, or an end-user, and align roles and access permissions with your employees' positions in the organization. We utilize RBAC in OPSCOM to control access to functionality in the system.
**Mobility (New Parking Lexicon)**A term that is quickly growing more popular as a replacement to the Parking & Transportation Dept. Many are rebranding as Mobility departments or referring to their Mobility Plan.
**Curbside Management** **(New Parking Lexicon)** Curbside management in a new term cropping up in Parking and violations. Seems to be pushed by the Smart City, Internet of Things groups. It refers to street parking and management of the street real-estate.
# Security Whitepaper As do many, we take security very seriously! We understand that the data we have been entrusted with is data which our clients have also been entrusted with. We always ensure that we go well above and beyond the requirements and standards for safe secure storage and handling of all data. This white paper outlines in details some of the lengths which we go to ensure business continuity and respect for entrusted data. ## Executive Summary OperationsCommander (OPSCOM) is a cloud-based parking and security management platform. This platform has been developed in-house for over 15 years. Tomahawk Technologies Inc. is committed to maintaining a high level of information security, and its key priority is protecting customer information, and carefully maintaining the information security of OPSCOM. This Security Whitepaper gives an overview of the OPSCOM security features. ***OPSCOM is PCI SAQ D-SP 3.2.1 certified*** ![military medal](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/standard/caa27a19-fc09-4452-b2b4-a301552fd69c/32x32/1f396.png) and is audited quarterly by a third-party to maintain this certification. We are also ***TX-RAMP Level 2 certified*** ![military medal](https://pf-emoji-service--cdn.us-east-1.prod.public.atl-paas.net/standard/caa27a19-fc09-4452-b2b4-a301552fd69c/32x32/1f396.png) by the Texas Risk and Authorization Management Program (certificate ID TX1332619). The Texas Risk and Authorization Management Program provides a standardized approach for security assessment, certification, and continuous monitoring of cloud computing services that process the data of Texas state agencies. Risk analysis forms the foundation of our security program. Risk assessments are periodically performed and security is regularly discussed in weekly team meetings. Our security processes, roles, and responsibilities are clear and well defined. Everyone is aware of our responsibilities and obligations when protecting our clients data. We review our policies annually and ensure that all employees sign-off on them. OPSCOM is developed and maintained by inspired, skilled personnel who are committed to maintaining a high level of online security. OPSCOM has been designed to meet customers' strict security requirements and industry best practices. OPSCOM has a solid and secure foundation that is based on widely used security methods and protocols. It has been designed to protect data both in transit and at rest to ensure its confidentiality, integrity, and availability. Strict access control allows only authorized users to access the data. Operation and maintenance of OPSCOM follows documented processes. Continuous monitoring of information security and system performance ensures that all deviations and incidents can be responded to in a timely manner by trained and competent personnel in accordance with the incident response process. This document is designed to answer all your questions regarding the security and design of both OPSCOM and our supporting systems. #### *This information is now available by request from your Sales representative or from* ** # 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, 2025Review for Accuracy - SJ
March 17, 2026Review for Accuracy - SJ
April 8, 2026Update 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](https://www.w3.org/TR/WCAG20/) Level A (Yes) Level AA (Yes) Level AAA (Yes)
[Web Content Accessibility Guidelines 2.1](https://www.w3.org/TR/WCAG21/) Level A (Yes) Level AA (Yes) Level AAA (Yes)
[Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018](https://www.access-board.gov/ict/) (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](https://www.w3.org/TR/WCAG21/#conformance-reqs). #### Table 1: Success Criteria, Level A
Criteria Conformance Level Remarks and Explanations
[1.1.1 Non-text Content](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#label-in-name) (Level A) Web: Supports Visible button text matches aria-label values across the app.
[2.5.4 Motion Actuation](https://www.w3.org/TR/WCAG21/#motion-actuation) (Level A) Web: Not applicable No device motion, accelerometer, gyroscope, or shake detection found.
[3.1.1 Language of Page](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/WAI/WCAG20/errata/#editorial) and the [WCAG 2.1 Editorial Errata](https://www.w3.org/WAI/WCAG21/errata/).
[4.1.2 Name, Role, Value](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#orientation) (Level AA) Web: Supports No CSS orientation locks found.
[1.3.5 Identity Input Purpose](https://www.w3.org/TR/WCAG21/#identify-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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#reflow) (Level AA) Web: Supports Responsive grid with breakpoint sizing. Content reflows at 320px.
[1.4.11 Non-text Contrast](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#audio-only-live) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: No media content is used
[1.3.6 Identify Purpose](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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: 1. Foreground and background colors. 2. Width of blocks of text. 3. Text alignment. 4. Line spacing. 5. Text size.
[1.4.9 Images of Text (No Exception)](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#three-flashes) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: Website has no flashing content
[2.3.3 Animation from Interactions](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#section-headings) (Level AAA) Revised Section 508 – Does not apply Web: Supports Web: Pages are organized using headings
[2.5.5 Target Size](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#concurrent-input-mechanisms) (Level AAA) Web: Supports No input restriction. Users can freely switch between touch, mouse, and keyboard.
[3.1.3 Unusual Words](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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](https://www.w3.org/TR/WCAG21/#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)](https://www.w3.org/TR/WCAG21/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#chapter-4-hardware) Notes: screen reader on the google web store was used for testing
Criteria Conformance Level Remarks and Explanations
[402 Closed Functionality](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#404-preservation-information) 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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#412-two-way-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](https://www.access-board.gov/ict/#413-closed-caption) 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](https://www.access-board.gov/ict/#414-audio-description) 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](https://www.access-board.gov/ict/#415-user-controls-captions-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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#502-interoperability-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](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#504-authoring-tools) Web: Not applicable The application in question is not an authoring tool. Section removed
#### Chapter 6: [Support Documentation and Services](https://www.access-board.gov/ict/#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](https://www.access-board.gov/ict/#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](https://docs.google.com/document/d/11W8e2TPEN5a2z4WU3q2mAO7VaEks7hje/edit#heading=h.qsh70q) 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](https://www.access-board.gov/ict/#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
--- # Launching a Critical Support Ticket

Only tickets marked **Critical** will trigger the **after hours notification** process. Please note, **Critical** is defined as a system outage or impact that threatens immediate work stoppage or production is proceeding in a significantly impaired fashion. If your issue is not deemed critical by our support staff, because it does not meet the criteria, it will be downgraded and a reply will be sent during the next business day.

To launch a Critical ticket, please follow the steps below: - Visit [http://support.OPSCOM.com](http://support.OPSCOM.com/ "http://support.OPSCOM.com"). - Click on Tickets. - Sign In (or Sign Up if necessary). - Click Add Ticket. - Fill out Ticket Information. Make sure to complete Priority at bottom of the form. Click down arrow to choose Critical. - Add attachments, if required. - Click **Submit** to complete the process. [![image.png](https://opscom.wiki/uploads/images/gallery/2025-08/scaled-1680-/oPJimage.png)](https://opscom.wiki/uploads/images/gallery/2025-08/oPJimage.png) [![image.png](https://opscom.wiki/uploads/images/gallery/2025-08/scaled-1680-/ddeimage.png)](https://opscom.wiki/uploads/images/gallery/2025-08/ddeimage.png)