Accessibility statement for Queue-it’s default waiting room pages
This accessibility statement applies to Queue-it’s default waiting room pages (here called “Queue-it Queue Front”) which are provided to all Queue-it customers.
At Queue-it, we want to ensure our waiting rooms align with our customer’s accessibility standards. For our customers’ online visitors, this could mean they can for example:
- zoom in up to 300% without the text spilling off the screen
- navigate most of the waiting room page using just a keyboard
- navigate most of the waiting room page using speech recognition software
- listen to most of the waiting room page using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the waiting room page text as simple as possible to understand.
How accessible is Queue-it Queue Front?
Queue-it’s Queue Front is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard.
We know some parts of Queue-it Queue Front are not fully accessible:
- The option to change languages is unlabelled.
- The option to change languages has a low level of contrast for between the drop-down menu and background.
- Some error messages are not descriptive and do not let users know how to resolve the error. For example, if users enter their email address incorrectly.
- Not all elements on the page have accessible names.
These non-compliances are described in further detail below.
How do I report accessibility problems with Queue-it Queue Front?
We’re always looking to improve the accessibility of our default waiting room pages.
If you find any problems not listed on this page or think we’re not meeting accessibility requirements, contact: info@queue-it.com.
Enforcement procedure
The Equality and Human Rights Commission (EHRC) is responsible for enforcing the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018 (the ‘accessibility regulations’). If you’re not happy with how we respond to your complaint, contact the Equality Advisory and Support Service (EASS).
Technical information about Queue-it Queue Front accessibility
Queue-it is committed to making its default waiting room pages accessible, in accordance with the Public Sector Bodies (Websites and Mobile Applications) (No. 2) Accessibility Regulations 2018.
Compliance status
Queue-it Queue Front is partially compliant with the Web Content Accessibility Guidelines version 2.1 AA standard, due to the non-compliances listed below.
Non-accessible content
The content listed below is non-accessible for the following reasons.
Non-compliance with the accessibility regulations
- Not all user interface elements have labels or instructions. This may make some features difficult to understand or use. For example, the language drop down menu does not have any instructions. This fails WCAG 2.1. success criterion 3.3.2 (labels or instructions).
- When using the language drop down menu, a language is selected and the page re-loaded without confirmation from the user. This could be confusing or present challenges for some users and fails WCAG 2.1. success criterion 3.2.5 (change on request).
- Some HTML elements are incorrectly nested. For example, an H1 element contains an image element. This fails WCAG 2.1 success criterion 4.1.1 (parsing).
- When users incorrectly enter their email address there are no suggestions made to help solve the issue. This could include incorrectly formatted email addresses such as a missing ‘@’ symbol or domain name. This fails WCAG 2.1. success criterion 3.3.3 and 3.3.6 (error suggestion and error prevention)
- Some user interface elements do not have accessible names. This could present issues when using the website with assistive technologies. This fails to meet WCAG 2.1. success criterion 4.1.2 (name, role, value)
- The contrast of some non-text user interface elements do not meet minimum contrast requirements. This fails to meet WCAG 2.1. success criterion 1.4.11 (non-text contrast)
What we’re doing to improve accessibility
We are continuing to audit Queue-it Queue Front to make regular accessibility improvements to make sure that the default waiting room pages are both compliant and usable. These accessibility improvements are integrated into Queue-it’s product roadmap.
Preparation of this accessibility statement
This statement was prepared on 12 January 2023.
This website was last tested in December 2022. The test was carried out by Accessible by Design.
Queue-it Accessibility Conformance Report
International Edition
(Based on VPAT® Version 2.4Rev)
Name of Product/Version: Queue-it Queue Front, version: 4.4.746.0
Report Date: January 2023
Product Description:
Queue-it is a virtual waiting room platform that protects websites from exceeding their capacity. In high-demand situations, online visitors are redirected to a waiting room on Queue-it's infrastructure and then throttled back to the website or app in a controlled order. When online visitors are in the waiting room, they see a waiting room web page. Queue-it provides default, out-of-the-box pages for our customers (henceforth “Queue-it Queue Front”) which are the focus of this accessibility report. Customers can brand and customize their waiting room pages as desired but should be aware of the accessibility implications of any changes they may make.
Contact Information: info@queue-it.com
Notes: This report covers the customer facing aspect of Queue-it and does not cover the administration tools. An updated version of the report will be produced following an audit of the administration tools.
Evaluation Methods Used:
The Queue-it Queue Front has been evaluated using Chrome, Firefox and Safari on a Mac running MacOS Monterey as well as iPhone and iPad. Assistive technologies used include Voiceover on MacOS and iOS, magnification and testing using only a keyboard to navigate. The assessment involved using a combination of automated and manual assessment against each of the WCAG 2.1 success criterion.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|
Level A (Yes) Level AA (Yes) Level AAA (Yes) |
|
|
Level A (Yes) Level AA (Yes) Level AAA (Yes) |
|
|
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 |
(No) |
|
EN 301 549 Accessibility requirements for ICT products and services - V3.1.1 (2019-11) AND EN 301 549 Accessibility requirements for ICT products and services - V3.2.1 (2021-03) |
(No) |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.1 Report
Tables 1 and 2 also document conformance with:
- EN 301 549: Chapter 9 - Web, Sections 10.1-10.4 of Chapter 10 - Non-Web documents, and Sections 11.1-11.4 and 11.8.2 of Chapter 11 - Non-Web Software (open and closed functionality), and Sections 12.1.2 and 12.2.4 of Chapter 12 – Documentation
- Revised Section 508: Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing, and Chapter 6 – 602.3 Electronic Support Documentation.
Note: When reporting on conformance with the WCAG 2.1 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.
Table 1: Success Criteria, Level A
Notes:
|
Criteria |
Conformance Level |
Remarks and explanations |
|
1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports |
Web: Organisations using the Queue-it platform can set appropriate alternative text within the admin panel. |
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not Applicable |
Web: The platform does not contain audio-only or video-only content. However, this content can be uploaded by organisations through the content editing tools in the administration of the platform. |
|
1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not Applicable |
Web: The platform does not contain any video content requiring captions. However, this content can be uploaded by organisations through the content editing tools in the administration of the platform. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not Applicable |
Web: The platform does not contain any video content requiring audio description. However, this content can be uploaded by organisations through the content editing tools in the administration of the platform. |
|
1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports |
Web: |
|
1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports |
Web: The site is presented in a meaningful sequence |
|
1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Information presented visually is also available to users of assistive technology through accessible names or labels.
|
|
1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Alternative formats are available to information conveyed through the use of color.
|
|
1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not Applicable
|
Web: The platform does not play audio automatically for more than three seconds.
|
|
2.1.1 Keyboard (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: The platform can be navigated using only a keyboard.
|
|
2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: There are no keyboard traps within the application
|
|
2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Not applicable
|
Web: The platform does not use custom keyboard shortcuts
|
|
2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: The Queue-it platform has a time limit imposed by which users must enter the website having waited in the queue. This time limit is required due to the nature of the queuing system and to manage load on the website it is protecting. This is a real-time exception. |
|
2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Blinking and moving content can be avoided through the use of ‘prefers-reduced-motion’.
|
|
2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable
|
Web: None of the content in the platform contains flashing content. However, this can be uploaded through the administration. Organisations using Queue-it should check their content for this before uploading video content.
|
|
2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially supports
|
Web: Headings are used to break up content, however, only one landmark is used within the page. Footer content is not split into a separate landmark. As a single page application there is less of a need to bypass repeated content.
|
|
2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially Supports
|
Web: Page titles are used within the platform, however, the titles for all pages and states. This means it is not clear from the Title tag whether users are in the before queue page, queue page, after queue page or error page. |
|
2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: The focus order within Queue-it is logical and easy to follow.
|
|
2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Link text makes sense within the context of the surrounding content.
|
|
2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: The platform does not use multipoint or path based gestures. All functionality can be accessed using a single pointer without path-based gestures.
|
|
2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: The platform supports pointer cancellation
|
|
2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Partially Supports
|
Web: The language selector does not have an accessible label.
|
|
2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Not applicable
|
Web: The platform does not have any functionality that Is operated by device motion. |
|
3.1.1 Language of Page (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: The selected language of the platform is declared within the HTML.
|
|
3.2.1 On Focus (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: When an element receives focus, it does not result in a change of context. |
|
3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Changes to settings of any user interface components do not result in an automatic change of context.
|
|
3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially supports
|
Web: When entering incomplete or incorrectly formatted email addresses users are presented with an error. However, a single, generic error message is used for any input error and this does not provide a full description of why the error is presented or what needs to be done to resolve the error.
|
|
3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially supports
|
Web: The language selector is currently unlabeled. A visual label will be added for this in Q3 2023.
|
|
4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially supports
|
Web: Some HTML elements contain disallowed child elements. This includes an image contained within an H1 element.
|
|
4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Partially supports |
Web: The name and role for most user interface components can be programmatically determined. However, the progress bar does not have an accessible name.
|
Table 2: Success Criteria, Level AA
Notes:
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable |
Web: The platform contains no live video content and does not require live captions. |
|
1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable |
Web: The platform does not contain any content that requires audio description. However, organisations using Queue It can upload this content via the administration and should check their content when doing so. |
|
1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: The platform can be used in landscape and portrait orientations.
|
|
1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: Purpose of input fields can be programmatically determined
|
|
1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: The contrast used throughout the platform meets minimum contrast requirements.
|
|
1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Users can resize text to a minimum of 200%.
|
|
1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: The platform does not use images of text. It is possible to upload images of text through the administration panel and business users of Queue-it should avoid doing this.
|
|
1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: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.
|
|
1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Partially supports
|
Web: Sufficient contrast is used for user interface components throughout the platform by default. However, the language selector has a contrast of 1.32:1 |
|
1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: No loss of content or functionality occurs when adjusting line height, paragraph spacing, letter spacing or word spacing to the required levels.
|
|
1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: Content is not triggered on hover or focus
|
|
2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable
|
Web: The Queue It Queue Page is not a navigable website and as such users cannot choose to navigate through pages. Users are automatically progressed based on their position within the queue. Instructions are given to indicate where users are within this process.
|
|
2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Headings and labels are used throughout the platform
|
|
2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Links, input fields and buttons are given visible focus when given focus.
|
|
3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable
|
Web: The Queue Page uses one language at a time throughout the content. This is set for the document as a whole.
|
|
3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable.
|
Web: There are not multiple pages to navigate, users are automatically progressed through the application from the before queue page through to the destination website.
|
|
3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Supports
|
Web: Consistent identification is used throughout.
|
|
3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Does not support
|
Web: When users make errors inputting their email address, no suggestions are made for resolving these errors.
|
|
3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria
Revised Section 508
|
Web: Not applicable
|
Web: No legal or financial transactions are made through the submission of user data.
|
|
4.1.3 Status Messages (Level AA 2.1 only) Also applies to: EN 301 549 Criteria
Revised Section 508 – Does not apply |
Web: Supports
|
Web: Status messages are included in the platform.
|
Table 3: Success Criteria, Level AAA
Notes:
|
Criteria |
Conformance Level |
Remarks and Explanations |
|
1.2.6 Sign Language (Prerecorded) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Not Applicable |
Web: No pre-recorded audio content is included in the platform. However, it is possible for business users of Queue-it to upload pre-recorded audio content. |
|
1.2.7 Extended Audio Description (Prerecorded) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Not applicable |
Web: No video content is included within the platform. However, it is possible for business users of Queue-it to upload video content and audio description should be added when doing so. |
|
1.2.8 Media Alternative (Prerecorded) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Not applicable |
Web: No pre recorded media is included within the platform. However, it is possible for business users of Queue-it to upload pre recorded media and media alternatives should be added when doing so. |
|
1.2.9 Audio-only (Live) (Level AAA) EN 301 549 Criteria– Does not apply Revised Section 508 – Does not apply |
Web: Not applicable |
Web: No live content is included within the platform. |
|
1.3.6 Identify Purpose (Level AAA 2.1 only) EN 301 549 Criteria– Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: User interface components, icons and regions can be programmatically determined. |
|
1.4.6 Contrast (Enhanced) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Colour contrasts are sufficient for the font sizes used. |
|
1.4.7 Low or No Background Audio (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: No low or background audio is used in the platform. |
|
1.4.8 Visual Presentation (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Does not support |
Web: Users cannot adjust the background or foreground colours. |
|
1.4.9 Images of Text (No Exception) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Images of text are not used with the exception of the Queue-it logo which is considered essential. Business users of Queue-it can upload images through the administration and should ensure that images of text are not included unless purely decorative. |
|
2.1.3 Keyboard (No Exception) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes. |
|
2.2.3 No Timing (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Does not support |
Web: Users are given a time limit by which they must enter the website they have been queuing for. |
|
2.2.4 Interruptions (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Interruptions can be postponed or suppressed by the user |
|
2.2.5 Re-authenticating (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating. However, if a session position is lost, users must take a new position within the queue. |
|
2.2.6 Timeouts (Level AAA 2.1 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Users are notified of timeouts |
|
2.3.2 Three Flashes (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Platform does not contain flashing content, however, organisations can upload flashing content through the administration and need to test their content for this. |
|
2.3.3 Animation from Interactions (Level AAA 2.1 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: The platform does not contain animations triggered by user interactions. |
|
2.4.8 Location (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Users do not have the option to navigate through multiple pages. Users are given an indication of where they are in the queueing process on the before queue page and queue page. |
|
2.4.9 Link Purpose (Link Only) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Does not support |
Web: The link text ‘What is this’ could be improved to offer a better understanding as to what it relates to and what will happen when clicking the link. |
|
2.4.10 Section Headings (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Headings are used to semantically group nested content. |
|
2.5.5 Target Size (Level AAA 2.1 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Partially supports |
Web: The Queue ID button and close buttons do not meet minimum target size requirements |
|
2.5.6 Concurrent Input Mechanisms (Level AAA 2.1 only) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Web content does not restrict use of input modalities. |
|
3.1.3 Unusual Words (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: The platform allows organisations to include definitions of any unusual words used within the content. |
|
3.1.4 Abbreviations (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: The platform allows organisations to include definitions of any abbreviations used within the content. |
|
3.1.5 Reading Level (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Business users of the platform should review any content being input through the admin panel to ensure that it does not require a reading ability more advanced than the lower secondary education level. |
|
3.1.6 Pronunciation (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Not applicable |
Web: The platform does not contain words that would be ambiguous without knowing the pronunciation. |
|
3.2.5 Change on Request (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Content does not significantly change or redirect unexpectedly. |
|
3.3.5 Help (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Supports |
Web: Context sensitive help is available. Additional instructional information can be added by business users through the administration. |
|
3.3.6 Error Prevention (All) (Level AAA) EN 301 549 Criteria – Does not apply Revised Section 508 – Does not apply |
Web: Does not support |
Web: Email addresses can be submitted by users without the ability to check, confirm or reverse submissions. |