VOLUNTARY PRODUCT ACCESSIBILITY (VPAT)
OUR COMMITMENT
Trimdata is committed to accessibility as part of providing an exceptional experience for our employees, customers, business partners and their families. This includes creating and maintaining digital products and services – including our websites that are accessible to the widest possible audience, regardless of ability.
ONGOING EFFORTS
We continue to listen to your feedback, partner with relevant organizations and conduct research to ensure we meet existing standards and identify areas of potential concern.
VOLUNTARY PRODUCT ACCESSIBILITY TEMPLATE (VPAT)
The purpose of the Voluntary Product Accessibility Template, or VPAT is to assist buyers in making preliminary assessments regarding the availability of commercial “Electronic and Information Technology” products and services with features that support accessibility. It is assumed and recommended that offerers will provide additional contact information to facilitate more detailed inquiries.
COMPONENTS
This assessment covers two components that make up the FA~Link system: The middleware, referred to as the API, which performs all of the transactions and communications between POS and the SIS, and a back-office UX components, referred to as the UI, used for initial system configuration, to monitor performance and occasional manual queries.
Please view the Voluntary Accessibility Template – Results Summary and Results Details below.
FOR FURTHER INFORMATION
We value your input. If you have any accessibility-related questions, comments or problems, please contact us.
Voluntary Product Accessibility Template Results Summary
| Total Standards | Total Applicable Standards | Supports | Supports with Exceptions | Partially Supports | Does Not Support | Total Exceptions | |
|---|---|---|---|---|---|---|---|
| API | 61 | 23 | 23 | 0 | 0 | 0 | 0 |
| User Interface (UI) | 61 | 46 | 31 | 3 | 9 | 3 | 15 |
FA~Link API/Middleware Results Details
| 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. |
| 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. |
| 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. |
| 1.2.4 Captions (Live) | AA | Captions are provided for all live audio content in synchronized media. | Not Applicable | No media content. |
| 1.2.5 Audio Description (Prerecorded) | AA | Audio description is provided for all prerecorded video content in synchronized media. | Not Applicable | No media content. |
| 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. |
| 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. |
| 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. |
| 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. |
| 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.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 used in information 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. |
| 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. |
| 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. |
| 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 | API results are returned programmatically, so there no restrictions on how it can be displayed. |
| 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. |
| 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 can be accessed via a standard Swagger setup, which is not timing dependent and can be fully utilized with 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 can be accessed via a standard Swagger setup, which is not timing dependent and can be fully utilized with 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 can be accessed via a standard Swagger setup, which is not timing dependent and can be fully utilized with a keyboard only. |
| 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, red or otherwise. |
| 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, red or otherwise. |
| 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 are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a web page. |
| 3.1.1 Language of Page | A | The default human language of each Web page can be programmatically determined. | Not Applicable | API endpoints are clearly labeled, but do not function as an standalone web page. |
| 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 are clearly labeled, but do not function as a web page. |
| 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 are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a standalone web 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. | Not Applicable | API endpoints are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a standalone web page. |
| 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.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 | JSON objects include labels for all fields. |
| 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 | All endpoints are fully documented via 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. |
| 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. | Not Applicable | API endpoints are clearly labeled, but do not function as a standalone web page. |
| 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 are clearly labeled, but do not function as a standalone web page. |
FA~Link User Interface (UI) Results Details
| 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. | Partially Supports | Exception: The logo image on the page has no alt attribute specified. |
| 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. | Partially Supports | Passing with two minor exceptions which are in PR review. |
| 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 | Only relevant on Account Query and Transaction Interface page, which is essentially a testing interface. Requires remediation, but not a daily use item. |
| 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. |
| 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 | Colors are used to enhance error messages, but meaning is conveyed via text. |
| 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 | Supports | Theme and font contrast is too low. | |
| 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. | Partially Supports | On the Live Meter page, the title on one gauge is slightly truncated at 200%. |
| 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 | Supports | Theme and font contrast is too low. | |
| 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. | Supports | Hover hints used throughout site do not meet this requirement and require remediatation. |
| 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. |
| 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.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 with exception | The sole exception is log out for inactivity, which does not warn the user. |
| 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 | The animation on the Account Query and Transaction Interface (a ‘processing’ status bubble) falls under note 4. The return time on querying is depending on the SIS, which may take significant time. |
| 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 with exception | The sole exception is log out for inactivity. |
| 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 or Submit button, or a tab out of field on Account Query and Transaction Interface. |
| 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 | Processing status dot on Account Query and Transaction Interface does not cycle three times per second or more. |
| 2.3.2 Three Flashes | AAA | Web pages do not contain anything that flashes more than three times in any one second period. | Supports | Processing status dot on Account Query and Transaction Interface does not cycle three times per second or more. |
| 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. | Not Supported | Unique title attribute is not used, however all pages display a 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. | Partially Supports | While +/Add buttons all have text describing the button’s purpose, this is not using the label or aria-label tag. |
| 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 | Home page lists all top level pages (which have child tabs). Links for further exploration of topics are not applicable. |
| 2.4.6 Headings and Labels | AA | Headings and labels describe topic or purpose. | Partially Supports | Heading tags, etc, are not used. Label tags are used on all text fields, but are not used on +/Add buttons. |
| 2.4.7 Focus Visible | AA | Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible. | Supports with exception | All text fields have a blue highlight around them when focused with the exception of the +/Add button. |
| 2.4.8 Location | AAA | Information about the user's location within a set of Web pages is available. | Supports | Breadcrumb trail is shown at the top of every page with the selected tenant and location. |
| 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 | Link descriptions describe purpose. |
| 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. | Partially Supports | While tabs are used to organize sections within pages, these do not use tags. |
| 3.1.1 Language of Page | A | The default human language of each Web page can be programmatically determined. | Partially Supports | The "lang" attribute is missing for the element "html" |
| 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 | No language changes in site, but would prefer to remediate with 3.1.1 above. |
| 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. | Partially Supports | Industry-specific terms and usages are not defined. |
| 3.1.4 Abbreviations | AAA | A mechanism for identifying the expanded form or meaning of abbreviations is available. | Not Applicable | No abbreviations found. |
| 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 | On the Account Query and Transaction Interface, loss of focus can cause the same behavior as directly clicking on the Query button. |
| 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 | Navigation is consistent, and general ordering of most general to most specific is used on all applicable pages. |
| 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.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. | Partially Supports | One noted exception, where a required field does not have the ‘required’ highlight. |
| 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 | 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.) |
| 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 | No exceptions found. |
| 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 Supported | Failed due to combination of fails on items above, remediate on specific items above. |