How can we help?
A Focus on Accessibility
Watchman is committed to accessibility as part of mission to provide the highest quality and most usable software and services to the Higher Education community. This includes creating and maintaining digital products and services that are accessible regardless of ability.
Voluntary Product Accessibility Template (VPAT) v2.5
The Voluntary Product Accessibility Template, or VPAT is meant to report the capabilities of vendors like Watchman to offer “Electronic and Information Technology” products and services that support accessibility.
The purpose of the tables below is to show Watchman’s performance to important criteria (see: WCAG 2.0 Level A to AAA Success Criteria to Section 508 Functional Performance Criteria) The tables, below, include all criteria from WCAG 2.0, 2.1, and 2.2 – aligning with “VPAT 2.5 WCAG” – in a format that is easy to read and evaluate.
Watchman’s STEP Platform
This assessment first covers the STEP Platform which is made up of middleware software that we refer to as the API. This interface handles all transactions between Campus Systems, including POS systems, SIS’s and other important systems. As middleware, much of the important VPAT criteria does not apply as it would for user-facing software.
The assessment also covers the back-office UX components, referred to as the UI, which are used for customer configuration and initial system configuration, to monitor performance and occasional manual queries.
The results are presented in two sections, the API and the UI below.
Summary Results
| Total Standards | Total Applicable Standards | Supports | Partially Supports | Does Not Support | Total Exceptions | Supported WCAG Level | |
|---|---|---|---|---|---|---|---|
| API | 84 | 26 | 26 | 0 | 0 | 0 | AAA |
| User Interface (UI) | 84 | 69 | 65 | 1 | 3 | 0 | AA |
Watchman STEP API results
As mentioned above, the Watchman STEP platform API is a middleware interface between systems and therefore many of the VPAT requirements are not applicable.
| Standard | Level | Standard Description | Result | Summary |
|---|---|---|---|---|
| 1.1.1 Non-text Content | A | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. | Not Applicable | No non-text content. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Provide alternatives for time-based media. | Not Applicable | No media content is utilized. |
| 1.2.2 Captions (Prerecorded) | A | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | No media content is utilized. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | No media content is utilized. |
| 1.2.4 Captions (Live) | AA | Captions are provided for all live audio content in synchronized media. | Not Applicable | No media content is utilized. |
| 1.2.5 Audio Description (Prerecorded) | AA | Audio description is provided for all prerecorded video content in synchronized media. | Not Applicable | No media content is utilized. |
| 1.2.6 Sign Language (Prerecorded) | AAA | Sign language interpretation is provided for all prerecorded audio content in synchronized media. | Not Applicable | No media content is utilized. |
| 1.2.7 Extended Audio Description (Prerecorded) | AAA | Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. | Not Applicable | No media content is utilized. |
| 1.2.8 Media Alternative (Prerecorded) | AAA | An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. | Not Applicable | No media content is utilized. |
| 1.2.9 Audio-only (Live) | AAA | An alternative for time-based media that presents equivalent information for live audio-only content is provided. | Not Applicable | No media content is utilized. |
| 1.3.1 Info and Relationships | A | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Supports | All content is returned via standard JSON format, including labels. |
| 1.3.2 Meaningful Sequence | A | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | Supports | All content is returned via standard JSON format, including labels. |
| 1.3.3 Sensory Characteristics | A | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. | Supports | All content is returned via standard JSON format, including labels. |
| 1.3.4 Orientation | AA (2.1/2.2) | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. | Not Applicable | Content is not orientation specific |
| 1.3.5 Identify Input Purpose | AA (2.1/2.2) | UI: Supports API: N/A UI: Theme and font contrast meets standard API: Content is not returned via a UI. | Not Applicable | Content is not returned via a UI. |
| 1.4.1 Use of Color | A | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Not Applicable | No color is returned. |
| 1.4.2 Audio Control | A | If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | Not Applicable | No media content is utilized. |
| 1.4.3 Contrast (Minimum) | AA | Not Applicable | Content is not returned via a UI. | |
| 1.4.4 Resize text | AA | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | Not Applicable | No media content is utilized. |
| 1.4.5 Images of Text | AA | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable: The image of text can be visually customized to the user's requirements; Essential: A particular presentation of text is essential to the information being conveyed. Note: Logotypes (text that is part of a logo or brand name) are considered essential. | Not Applicable | Information is returned as text only. |
| 1.4.6 Contrast Enhanced | AAA | Not Applicable | Content is not returned via a UI. | |
| 1.4.7 Low or No Background Audio | AAA | For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background: The audio does not contain background sounds. Turn Off: The background sounds can be turned off. 20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds. Note: Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content. | Not Applicable | No media content is utilized. |
| 1.4.8 Visual Presentation | AAA | For the visual presentation of blocks of text, a mechanism is available to achieve the following: Foreground and background colors can be selected by the user. Width is no more than 80 characters or glyphs (40 if CJK). Text is not justified (aligned to both the left and the right margins). Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. | Supports | no restrictions on how info can be displayed as API results are returned programmatically and can be presented as preferred |
| 1.4.9 Images of Text (No Exception) Control | AAA | Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. Note: Logotypes (text that is part of a logo or brand name) are considered essential. | Not Applicable | No images of text. |
| 1.4.10 Reflow | AA (2.1/2.2) | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. | Not Applicable | All content is returned via standard JSON format, including labels. |
| 1.4.11 Non-text Contrast | AA (2.1/2.2) | The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. | Not Applicable | All content is returned via standard JSON format, including labels. |
| 1.4.12 Text Spacing | AA (2.1/2.2) | In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script. | Not Applicable | All content is returned via standard JSON format, including labels. |
| 1.4.13 Content on Hover or Focus | AA (2.1/2.2) | Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissible A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; Hoverable If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; Persistent The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. | Not Applicable | All content is returned via standard JSON format, including labels. |
| 2.1.1 Keyboard | A | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. | Supports | The API information is available as a Swagger setup, which is not timing dependent and can be fully utilized using a keyboard only. |
| 2.1.2 No Keyboard Trap | A | If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. | Supports | The API information is available as a Swagger setup, which is not timing dependent and can be fully utilized using a keyboard only. |
| 2.1.3 Keyboard (No Exception) | AAA | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA) | Supports | The API information is available as a Swagger setup, which is not timing dependent and can be fully utilized using a keyboard only. |
| 2.1.4 Character Key Shortcuts | A (2.1/2.2) | If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: Turn off A mechanism is available to turn the shortcut off; Remap A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt); Active only on focus The keyboard shortcut for a user interface component is only active when that component has focus. | Not Applicable | API endpoints do not function as a standalone web page and there are no keyboard shortcuts |
| 2.2.1 Timing Adjustable | A | For each time limit that is set by the content, at least one of the following is true: Turn off: The user is allowed to turn off the time limit before encountering it; or Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or Essential Exception: The time limit is essential and extending it would invalidate the activity; or 20 Hour Exception: The time limit is longer than 20 hours. Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action. | Not Applicable | The API calls do not have a required time for entry. |
| 2.2.2 Pause, Stop, Hide | A | For moving, blinking, scrolling, or auto-updating information, all of the following are true: Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3. Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. | Not Applicable | No autoupdating, blinking, or scrolling information presented using an API call. |
| 2.2.3 No Timing | AAA | Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. | Supports | Specific timing is not required for any endpoints. |
| 2.2.4 Interruptions | AAA | Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. | Supports | The API calls do not involve interruptions. |
| 2.2.5 Re -authenticating | AAA | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. | Supports | If the token expires, the user can resubmit the same data. |
| 2.3.1 Three Flashes or Below Threshold | A | Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Supports | No endpoints flash |
| 2.3.2 Three Flashes | AAA | Web pages do not contain anything that flashes more than three times in any one second period. | Supports | No endpoints flash |
| 2.3.3 Animation from Interactions | AAA (2.1/2.2) | Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. | Supports | No animations are used |
| 2.4.1 Bypass Blocks | A | A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | Not Applicable | There is no critically repeated content. |
| 2.4.2 Page Titled | A | Web pages have titles that describe topic or purpose. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.3 Focus Order | A | If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.4 Link Purpose (In Context) | A | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | Not Applicable | Links are not present in the returned content. |
| 2.4.5 Multiple Ways | AA | More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.6 Headings and Labels | AA | Headings and labels describe topic or purpose. | Supports | Endpoints are clearly named to correspond to their purpose. |
| 2.4.7 Focus Visible | AA | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | Not Applicable | API endpoints do not include UI. |
| 2.4.8 Location | AAA | Information about the user's location within a set of Web pages is available. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.9 Link Purpose (Link Only) | AAA | A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. | Not Applicable | Links are not present in the returned content. |
| 2.4.10 Section Headings | AAA | Section headings are used to organize the content. Note 1: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content. Note 2: This success criterion covers sections within writing, not user interface components. User Interface components are covered under Success Criterion 4.1.2. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.11 Focus Not Obscured (Minimum) | AA (2.2) | When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. NOTE 1 Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion. NOTE 2 Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA (2.2) | When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.4.13 Focus Appearance | AAA (2.2) | When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states. Exceptions: The focus indicator is determined by the user agent and cannot be adjusted by the author, or The focus indicator and the indicator's background color are not modified by the author. NOTE 1 What is perceived as the user interface component or sub-component (to determine enclosure or size) depends on its visual presentation. The visual presentation includes the component's visible content, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border. NOTE 2 Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid. NOTE 3 Contrast calculations can be based on colors defined within the technology (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 2.5.1 Pointer Gestures | A (2.1/2.2) | All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. | Not Applicable | Pointer is not used for API |
| 2.5.2 Pointer Cancellation | A (2.1/2.2) | For functionality that can be operated using a single pointer, at least one of the following is true: No Down-Event The down-event of the pointer is not used to execute any part of the function; Abort or Undo Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal The up-event reverses any outcome of the preceding down-event; Essential Completing the function on the down-event is essential. | Not Applicable | Pointer is not used for API |
| 2.5.3 Label in Name | A (2.1/2.2) | For user interface components with labels that include text or images of text, the name contains the text that is presented visually. | Not Applicable | There are no components of this type in the API |
| 2.5.4 Motion Actuation | A (2.1/2.2) | Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Supported Interface The motion is used to operate functionality through an accessibility supported interface; Essential The motion is essential for the function and doing so would invalidate the activity. | Not Applicable | No motion-based functionality |
| 2.5.5 Target Size (Enhanced) | AAA (2.1/2.2) | The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed. | Not Applicable | Pointer is not used for API |
| 2.5.6 Concurrent Input Mechanisms | AAA (2.1/2.2) | Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. | Supported | No restrictions are imposed by the software |
| 2.5.7 Dragging Movements | AA (2.2) | All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. NOTE This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). | Not Applicable | Pointer is not used for API |
| 2.5.8 Target Size (Minimum) | AA (2.2) | The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where: Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target; Equivalent: The function can be achieved through a different control on the same page that meets this criterion; Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text; User agent control: The size of the target is determined by the user agent and is not modified by the author; Essential: A particular presentation of the target is essential or is legally required for the information being conveyed. NOTE 1 Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor. NOTE 2 For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal. | Not Applicable | Pointer is not used for API |
| 3.1.1 Language of Page | A | The default human language of each Web page can be programmatically determined. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.1.2 Language of Parts | AA | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.1.3 Unusual Words | AAA | A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. | Supports | The API is fully documented using Swagger. |
| 3.1.4 Abbreviations | AAA | A mechanism for identifying the expanded form or meaning of abbreviations is available. | Supports | All word meanings used are standard. |
| 3.1.5 Reading Level | AAA | When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. | Supports | No long form text is returned from the API. |
| 3.1.6 Pronunciation | AAA | A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. | Not Applicable | No pronunciation-specific words are used in the endpoints. |
| 3.2.1 On Focus | A | When any component receives focus, it does not initiate a change of context. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.2.2 On Input | A | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.2.3 Consistent Navigation | AA | Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.2.4 Consistent Identification | AA | Components that have the same functionality within a set of Web pages are identified consistently. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.2.5 Change on Request | AAA | Changes of context are initiated only by user request or a mechanism is available to turn off such changes. | Supports | API endpoints only return information when called by a user. |
| 3.2.6 Consistent Help | A (2.2) | If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
| 3.3.1 Error Identification | A | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | Supports | API endpoints return useful and appropriate error messages. |
| 3.3.2 Labels or Instructions | A | Labels or instructions are provided when content requires user input. | Supports | All content is returned via standard JSON format, including labels. |
| 3.3.3 Error Suggestion | AA | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | Supports | API endpoints return useful and appropriate error messages. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Supports | All submissions are reversible, either by deletion or by a balancing negative/positive transaction. The Authorize endpoint is used to confirm the Capture endpoint. |
| 3.3.5 Help | AAA | Context-sensitive help is available. | Supports | The API is fully documented using Swagger. |
| 3.3.6 Error Prevention (All) | AAA | For Web pages that require the user to submit information, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Supports | All submissions are reversible, either by deletion or by a balancing negative/positive transaction. The Authorize endpoint is used to confirm the Capture endpoint. |
| 3.3.7 Redundant Entry | A (2.2) | Information previously entered by or provided to the user that is required to be entered again in the same process is either: auto-populated, or available for the user to select. Except when: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid. | Not Applicable | API endpoints are not expected to have data entered by a human in actual operation |
| 3.3.8 Accessible Authentication (Minimum) | AA (2.2) | A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test. Object Recognition The cognitive function test is to recognize objects. Personal Content The cognitive function test is to identify non-text content the user provided to the Web site. NOTE 1 "Object recognition" and "Personal content" may be represented by images, video, or audio. NOTE 2 Examples of mechanisms that satisfy this criterion include: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing. | Not Applicable | API authentication is for machine/software authorization |
| 3.3.9 Accessible Authentication (Enhanced) | AAA (2.2) | A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test. | Not Applicable | API authentication is for machine/software authorization |
| 4.1.1 Parsing | A | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. | Supported | For WCAG 2.0 and 2.1, 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 | A | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. | Not Applicable | API endpoints do not function as a standalone web page and are clearly labeled. |
Watchman UI results
The Watchman STEP User Interface supports administrative and reporting functions to support the STEP middleware interface a middleware interface.
| Standard | Level | Standard Description | Result | Summary |
|---|---|---|---|---|
| 1.1.1 Non-text Content | A | All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below. | Supports | All non-text content contains text alternative. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | A | Provide alternatives for time-based media. | Not Applicable | There is no audio or video content on the site. |
| 1.2.2 Captions (Prerecorded) | A | Captions are provided for all prerecorded audio content in synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | There is no audio or video content on the site. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | A | An alternative for time-based media or audio description of the prerecorded video content is provided for synchronized media, except when the media is a media alternative for text and is clearly labeled as such. | Not Applicable | There is no audio or video content on the site. |
| 1.2.4 Captions (Live) | AA | Captions are provided for all live audio content in synchronized media. | Not Applicable | There is no audio or video content on the site. |
| 1.2.5 Audio Description (Prerecorded) | AA | Audio description is provided for all prerecorded video content in synchronized media. | Not Applicable | There is no audio or video content on the site. |
| 1.2.6 Sign Language (Prerecorded) | AAA | Sign language interpretation is provided for all prerecorded audio content in synchronized media. | Not Applicable | There is no audio or video content on the site. |
| 1.2.7 Extended Audio Description (Prerecorded) | AAA | Where pauses in foreground audio are insufficient to allow audio descriptions to convey the sense of the video, extended audio description is provided for all prerecorded video content in synchronized media. | Not Applicable | There is no audio or video content on the site. |
| 1.2.8 Media Alternative (Prerecorded) | AAA | An alternative for time-based media is provided for all prerecorded synchronized media and for all prerecorded video-only media. | Not Applicable | There is no audio or video content on the site. |
| 1.2.9 Audio-only (Live) | AAA | An alternative for time-based media that presents equivalent information for live audio-only content is provided. | Not Applicable | There is no audio or video content on the site. |
| 1.3.1 Info and Relationships | A | Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Supports | Information, structure, and relationships can be programmatically determined or are available in text. |
| 1.3.2 Meaningful Sequence | A | When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined. | Supports | Order can be programmatically determined. |
| 1.3.3 Sensory Characteristics | A | Instructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, size, visual location, orientation, or sound. | Supports | All buttons have an associated text label field or alt text and hover text. |
| 1.3.4 Orientation | AA (2.1/2.2) | Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. | Supports | Content manages orientation changes without loss |
| 1.3.5 Identify Input Purpose | AA (2.1/2.2) | UI: Supports API: N/A UI: Theme and font contrast meets standard API: Content is not returned via a UI. | Supports | UI doesn't collect information about the user with the exception of login credentials, which identify themselves according to this requirement |
| 1.4.1 Use of Color | A | Color is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Supports | Color is not used to convey information. Text is presented to convey meaning |
| 1.4.2 Audio Control | A | If any audio on a Web page plays automatically for more than 3 seconds, either a mechanism is available to pause or stop the audio, or a mechanism is available to control audio volume independently from the overall system volume level. | Not Applicable | There is no audio or video content on the site. |
| 1.4.3 Contrast (Minimum) | AA | The visual presentation of text and images of text has a contrast ratio of at least 4.5:1, except for the following: Large Text: Large-scale text and images of large-scale text have a contrast ratio of at least 3:1; Incidental: Text or images of text that are part of an inactive user interface component, that are pure decoration, that are not visible to anyone, or that are part of a picture that contains significant other visual content, have no contrast requirement. Logotypes: Text that is part of a logo or brand name has no contrast requirement. | Supports | Theme and font contrast meets standard |
| 1.4.4 Resize text | AA | Except for captions and images of text, text can be resized without assistive technology up to 200 percent without loss of content or functionality. | Supports | No loss of content or functionality when page resized |
| 1.4.5 Images of Text | AA | If the technologies being used can achieve the visual presentation, text is used to convey information rather than images of text except for the following: Customizable: The image of text can be visually customized to the user's requirements; Essential: A particular presentation of text is essential to the information being conveyed. Note: Logotypes (text that is part of a logo or brand name) are considered essential. | Supports | No images of text are used outside of Logotypes. |
| 1.4.6 Contrast Enhanced | AAA | Not Supported | Only level AA contrast is supported | |
| 1.4.7 Low or No Background Audio | AAA | For prerecorded audio-only content that (1) contains primarily speech in the foreground, (2) is not an audio CAPTCHA or audio logo, and (3) is not vocalization intended to be primarily musical expression such as singing or rapping, at least one of the following is true: No Background: The audio does not contain background sounds. Turn Off: The background sounds can be turned off. 20 dB: The background sounds are at least 20 decibels lower than the foreground speech content, with the exception of occasional sounds that last for only one or two seconds. Note: Per the definition of "decibel," background sound that meets this requirement will be approximately four times quieter than the foreground speech content. | Not Applicable | There is no audio or video content on the site. |
| 1.4.8 Visual Presentation | AAA | For the visual presentation of blocks of text, a mechanism is available to achieve the following: Foreground and background colors can be selected by the user. Width is no more than 80 characters or glyphs (40 if CJK). Text is not justified (aligned to both the left and the right margins). Line spacing (leading) is at least space-and-a-half within paragraphs, and paragraph spacing is at least 1.5 times larger than the line spacing. Text can be resized without assistive technology up to 200 percent in a way that does not require the user to scroll horizontally to read a line of text on a full-screen window. | Partially Supports | Only meets subpoint 5 (Resizing of text to 200%). May meet some others depending on content entered by user, but does not enforce. Does not meet subpoint 1 about user controllable colors. |
| 1.4.9 Images of Text (No Exception) Control | AAA | Images of text are only used for pure decoration or where a particular presentation of text is essential to the information being conveyed. Note: Logotypes (text that is part of a logo or brand name) are considered essential. | Supports | No images of text are used outside of Logotypes. |
| 1.4.10 Reflow | AA (2.1/2.2) | Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for: Vertical scrolling content at a width equivalent to 320 CSS pixels; Horizontal scrolling content at a height equivalent to 256 CSS pixels. Except for parts of the content which require two-dimensional layout for usage or meaning. NOTE 1 320 CSS pixels is equivalent to a starting viewport width of 1280 CSS pixels wide at 400% zoom. For web content which is designed to scroll horizontally (e.g., with vertical text), 256 CSS pixels is equivalent to a starting viewport height of 1024 CSS pixels at 400% zoom. NOTE 2 Examples of content which requires two-dimensional layout are images required for understanding (such as maps and diagrams), video, games, presentations, data tables (not individual cells), and interfaces where it is necessary to keep toolbars in view while manipulating content. It is acceptable to provide two-dimensional scrolling for such parts of the content. | Supports | The UI meets this requirement assuming evaluation against Note 2 in the WCAG 2.2 documentation |
| 1.4.11 Non-text Contrast | AA (2.1/2.2) | The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s): User Interface Components Visual information required to identify user interface components and states, except for inactive components or where the appearance of the component is determined by the user agent and not modified by the author; Graphical Objects Parts of graphics required to understand the content, except when a particular presentation of graphics is essential to the information being conveyed. | Supports | Theme and font contrast meets standard |
| 1.4.12 Text Spacing | AA (2.1/2.2) | In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property: Line height (line spacing) to at least 1.5 times the font size; Spacing following paragraphs to at least 2 times the font size; Letter spacing (tracking) to at least 0.12 times the font size; Word spacing to at least 0.16 times the font size. Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script. | Supports | Content and Functionality is not lost in the UI with these settings in place |
| 1.4.13 Content on Hover or Focus | AA (2.1/2.2) | Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true: Dismissible A mechanism is available to dismiss the additional content without moving pointer hover or keyboard focus, unless the additional content communicates an input error or does not obscure or replace other content; Hoverable If pointer hover can trigger the additional content, then the pointer can be moved over the additional content without the additional content disappearing; Persistent The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid. Exception: The visual presentation of the additional content is controlled by the user agent and is not modified by the author. | Supports | This is supported by all fields |
| 2.1.1 Keyboard | A | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints. | Supports | All fields pass. |
| 2.1.2 No Keyboard Trap | A | If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. | Supports | All fields pass. |
| 2.1.3 Keyboard (No Exception) | AAA | All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. (Level AAA) | Supports | All fields pass. |
| 2.1.4 Character Key Shortcuts | A (2.1/2.2) | If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true: Turn off A mechanism is available to turn the shortcut off; Remap A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt); Active only on focus The keyboard shortcut for a user interface component is only active when that component has focus. | Supports | Shortcuts meet "active only on focus" |
| 2.2.1 Timing Adjustable | A | For each time limit that is set by the content, at least one of the following is true: Turn off: The user is allowed to turn off the time limit before encountering it; or Adjust: The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or Extend: The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, "press the space bar"), and the user is allowed to extend the time limit at least ten times; or Real-time Exception: The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or Essential Exception: The time limit is essential and extending it would invalidate the activity; or 20 Hour Exception: The time limit is longer than 20 hours. Note: This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action. | Supports | All time limits that are set by the content meet this standard. |
| 2.2.2 Pause, Stop, Hide | A | For moving, blinking, scrolling, or auto-updating information, all of the following are true: Moving, blinking, scrolling: For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and Auto-updating: For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential. Note 1: For requirements related to flickering or flashing content, refer to Guideline 2.3. Note 2: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. Note 3: Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so. Note 4: An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken. | Supports | All loading animations occur as part of a preload phase and are to standard |
| 2.2.3 No Timing | AAA | Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events. | Supports | All time limits that are set by the content meet this standard. |
| 2.2.4 Interruptions | AAA | Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency. | Supports | All updates to pages require an action on the part of the user (typically click on a Save button) |
| 2.2.5 Re -authenticating | AAA | When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. | Not Supported | Unsaved changes to a form are not available on re-authentication. |
| 2.3.1 Three Flashes or Below Threshold | A | Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. Note: Since any content that does not meet this success criterion can interfere with a user's ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference. | Supports | |
| 2.3.2 Three Flashes | AAA | Web pages do not contain anything that flashes more than three times in any one second period. | Supports | |
| 2.3.3 Animation from Interactions | AAA (2.1/2.2) | Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed. | Supports | No animations are used |
| 2.4.1 Bypass Blocks | A | A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. | Not Applicable | Blocks of text are not repeated on multiple pages. |
| 2.4.2 Page Titled | A | Web pages have titles that describe topic or purpose. | Supports | Interface includes both title and breadcrumb. |
| 2.4.3 Focus Order | A | If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. | Supports | Focus order is sequential on pages. |
| 2.4.4 Link Purpose (In Context) | A | The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. | Supports | |
| 2.4.5 Multiple Ways | AA | More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process. | Supports | More than one path exists to locate page |
| 2.4.6 Headings and Labels | AA | Headings and labels describe topic or purpose. | Supports | |
| 2.4.7 Focus Visible | AA | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | Supports | All text fields and buttons highlight when focused on. |
| 2.4.8 Location | AAA | Information about the user's location within a set of Web pages is available. | Supports | Naviagation is either 1) only one-level deep, or 2) tree-based without leaving the screen, or 3) wizard-based and full breadcrumbing is available |
| 2.4.9 Link Purpose (Link Only) | AAA | A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general. | Supports | |
| 2.4.10 Section Headings | AAA | Section headings are used to organize the content. Note 1: "Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content. Note 2: This success criterion covers sections within writing, not user interface components. User Interface components are covered under Success Criterion 4.1.2. | Supports | Headings meet this requirement |
| 2.4.11 Focus Not Obscured (Minimum) | AA (2.2) | When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content. NOTE 1 Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion. NOTE 2 Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content. | Supports | All text fields and buttons highlight when focused on. They aren't obscured. |
| 2.4.12 Focus Not Obscured (Enhanced) | AAA (2.2) | When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. | Supports | All text fields and buttons highlight when focused on. They aren't obscured. |
| 2.4.13 Focus Appearance | AAA (2.2) | When the keyboard focus indicator is visible, an area of the focus indicator meets all the following: is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states. Exceptions: The focus indicator is determined by the user agent and cannot be adjusted by the author, or The focus indicator and the indicator's background color are not modified by the author. NOTE 1 What is perceived as the user interface component or sub-component (to determine enclosure or size) depends on its visual presentation. The visual presentation includes the component's visible content, border, and component-specific background. It does not include shadow and glow effects outside the component's content, background, or border. NOTE 2 Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid. NOTE 3 Contrast calculations can be based on colors defined within the technology (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored. | Supports | All text fields and buttons highlight when focused on and meet this requirement. |
| 2.5.1 Pointer Gestures | A (2.1/2.2) | All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. | Supports | |
| 2.5.2 Pointer Cancellation | A (2.1/2.2) | For functionality that can be operated using a single pointer, at least one of the following is true: No Down-Event The down-event of the pointer is not used to execute any part of the function; Abort or Undo Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion; Up Reversal The up-event reverses any outcome of the preceding down-event; Essential Completing the function on the down-event is essential. | Supports | Meets criteria "No Down-Event" |
| 2.5.3 Label in Name | A (2.1/2.2) | For user interface components with labels that include text or images of text, the name contains the text that is presented visually. | Supports | Label components meet this requirement |
| 2.5.4 Motion Actuation | A (2.1/2.2) | Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when: Supported Interface The motion is used to operate functionality through an accessibility supported interface; Essential The motion is essential for the function and doing so would invalidate the activity. | Not Applicable | No motion-based functionality |
| 2.5.5 Target Size (Enhanced) | AAA (2.1/2.2) | The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when: Equivalent The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels; Inline The target is in a sentence or block of text; User Agent Control The size of the target is determined by the user agent and is not modified by the author; Essential A particular presentation of the target is essential to the information being conveyed. | Supported | |
| 2.5.6 Concurrent Input Mechanisms | AAA (2.1/2.2) | Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings. | Supported | No restrictions are imposed by the software |
| 2.5.7 Dragging Movements | AA (2.2) | All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. NOTE This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology). | Supports | Dragging is not required to operate the UI |
| 2.5.8 Target Size (Minimum) | AA (2.2) | The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where: Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target; Equivalent: The function can be achieved through a different control on the same page that meets this criterion; Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text; User agent control: The size of the target is determined by the user agent and is not modified by the author; Essential: A particular presentation of the target is essential or is legally required for the information being conveyed. NOTE 1 Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor. NOTE 2 For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal. | Supports | |
| 3.1.1 Language of Page | A | The default human language of each Web page can be programmatically determined. | Supports | |
| 3.1.2 Language of Parts | AA | The human language of each passage or phrase in the content can be programmatically determined except for proper names, technical terms, words of indeterminate language, and words or phrases that have become part of the vernacular of the immediately surrounding text. | Supports | |
| 3.1.3 Unusual Words | AAA | A mechanism is available for identifying specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon. | Supports | No specific definitions of words or phrases are used in an unusual or restricted way, including idioms and jargon. |
| 3.1.4 Abbreviations | AAA | A mechanism for identifying the expanded form or meaning of abbreviations is available. | Supports | Use of abbreviations are very limited and only to industry-known terms |
| 3.1.5 Reading Level | AAA | When text requires reading ability more advanced than the lower secondary education level after removal of proper names and titles, supplemental content, or a version that does not require reading ability more advanced than the lower secondary education level, is available. | Supports | Text is minimal and easy to read. |
| 3.1.6 Pronunciation | AAA | A mechanism is available for identifying specific pronunciation of words where meaning of the words, in context, is ambiguous without knowing the pronunciation. | Not Applicable | No found instances of areas where meaning is ambiguous without pronounciation. |
| 3.2.1 On Focus | A | When any component receives focus, it does not initiate a change of context. | Supports | Change of focus does not change context |
| 3.2.2 On Input | A | Changing the setting of any user interface component does not automatically cause a change of context unless the user has been advised of the behavior before using the component. | Supports | Changes to settings do not cause a change of context on any page. |
| 3.2.3 Consistent Navigation | AA | Navigational mechanisms that are repeated on multiple Web pages within a set of Web pages occur in the same relative order each time they are repeated, unless a change is initiated by the user. | Supports | |
| 3.2.4 Consistent Identification | AA | Components that have the same functionality within a set of Web pages are identified consistently. | Supports | No exceptions found. Icon usage (such as +/Add button or Save) is consistent across all pages. |
| 3.2.5 Change on Request | AAA | Changes of context are initiated only by user request or a mechanism is available to turn off such changes. | Supports | Changes to settings do not cause a change of context on any page. |
| 3.2.6 Consistent Help | A (2.2) | If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user: Human contact details; Human contact mechanism; Self-help option; A fully automated contact mechanism. | Supports | Help mechanisms are situated in identical locations with reference to the fields they refer to. Other help links are positioned statically in header and/or footer positions. |
| 3.3.1 Error Identification | A | If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. | Supports | Errors appear in text |
| 3.3.2 Labels or Instructions | A | Labels or instructions are provided when content requires user input. | Supports | All text fields and buttons have hover over hints. |
| 3.3.3 Error Suggestion | AA | If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. | Not Applicable | Data validity is checked, but correct suggestions cannot be known. (For example, if an invalid student ID is entered, it is not possible for the system to suggest a correct student ID for security purposes.) |
| 3.3.4 Error Prevention (Legal, Financial, Data) | AA | For Web pages that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Supports | Submissions are confirmed by using a submit button, and can be reversed in all cases (either with an edit, or with a corresponding reversal transaction.) |
| 3.3.5 Help | AAA | Context-sensitive help is available. | Supports | All fields have hover over help hints. |
| 3.3.6 Error Prevention (All) | AAA | For Web pages that require the user to submit information, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. | Supports | |
| 3.3.7 Redundant Entry | A (2.2) | Information previously entered by or provided to the user that is required to be entered again in the same process is either: auto-populated, or available for the user to select. Except when: re-entering the information is essential, the information is required to ensure the security of the content, or previously entered information is no longer valid. | Supports | |
| 3.3.8 Accessible Authentication (Minimum) | AA (2.2) | A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test. Object Recognition The cognitive function test is to recognize objects. Personal Content The cognitive function test is to identify non-text content the user provided to the Web site. NOTE 1 "Object recognition" and "Personal content" may be represented by images, video, or audio. NOTE 2 Examples of mechanisms that satisfy this criterion include: support for password entry by password managers to reduce memory need, and copy and paste to reduce the cognitive burden of re-typing. | Supports | Password managers are supported |
| 3.3.9 Accessible Authentication (Enhanced) | AAA (2.2) | A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following: Alternative Another authentication method that does not rely on a cognitive function test. Mechanism A mechanism is available to assist the user in completing the cognitive function test. | Not Supported | |
| 4.1.1 Parsing | A | In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features. | Supports | For WCAG 2.0 and 2.1, 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 | A | For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies. Note: This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification. | Supports | All components not provided by HTML5 are supplied by PrimeNG which meets this requirements |