Voluntary Product Accessibility Template (VPAT)
VPAT® Version 2.3 (Revised)
QReserve Accessibility Conformance Report
| Name of Product/Version | QReserve - Version 2 |
|---|---|
| Platform | Web |
| Last Updated | March 29, 2023 |
| Contact Information | hello@qreserve.com |
| Product Description | Resource reservation and management software. |
| Evaluation Methods Used | Conformance to the listed accessibility standards has been evaluation by QReserve using a combination of static analysis tools, manual testing, and user feedback within a formal focus group setting. One component of the QReserve testing process is to use automated testing tools that programically interact directly with the web application to ensure elements are always programically accessible and identifible. QReserve staff are working towards increasing conformance as new feature are developed and are focused on ensuring evermore increasing conformance levels. While effort is made to confirm that a requirement is conformed to, some updates or portions of the application that were missed in error may not conform to the requirement 100% of the time. We are constantly updating and improving our software to meet and increase our conformation to the requirements outlined in this document. Users who provide feedback and raise issues or areas in need of improvement are listened to and responded to in a timely manner and, where possible, a timely and appropriate solution or update to the application. |
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 |
Level A: Yes
Level AA: Yes
Level AAA: No
|
| Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 | Yes |
Terms
The terms used in the Conformance Level information are defined as follows:
- Supports: The functionality of the product has at least one method that meets the criterion without known defects or meets with equivalent facilitation.
- Partially Supports: Some functionality of the product does not meet the criterion.
- Does Not Support: The majority of product functionality does not meet the criterion.
- Not Applicable: The criterion is not relevant to the product.
- Not Evaluated: The product has not been evaluated against the criterion. This can be used only in WCAG 2.0 Level AAA.
WCAG 2.0 Report
Tables 1 and 2 also document conformance with:
- Chapter 5 – 501.1 Scope, 504.2 Content Creation or Editing
- Chapter 6 – 602.3 Electronic Support Documentation
Note: When reporting on conformance with the WCAG 2.0 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
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) | User generated content, especially images, may fail to provide text content altenatives to non-text content. | |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Tutorial video content is accompanied by a detailed audio track delivering equivalent information. | |
| 1.2.2 Captions (Prerecorded) (Level A) | Closed captions are supported through automatic speech-to-text services.. | |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Alternative help text is available when recorded videos are available. | |
| 1.3.1 Info and Relationships (Level A) | ||
| 1.3.2 Meaningful Sequence (Level A) | In some areas of our application, focus group participants using screen readers noted that content could be delivered out of sequence; however, were able to use the context of the information to understand the intended sequence. For example, when making a reservation, the reservation input area is inserted below the calendar area when being read by screen readers despite it visually being shown above on the screen. | |
| 1.3.3 Sensory Characteristics (Level A) | When graphical icons are used, alternative text is provided so sensory characteristics are not relied upon. | |
| 1.4.1 Use of Color (Level A) | ||
| 1.4.2 Audio Control (Level A) | There is no automatically playing audio within the application. | |
| 2.1.1 Keyboard (Level A) | ||
| 2.1.2 No Keyboard Trap (Level A) | ||
| 2.2.1 Timing Adjustable (Level A) | There are no timing based actions within the application that would apply. | |
| 2.2.2 Pause, Stop, Hide (Level A) | ||
| 2.3.1 Three Flashes or Below Threshold (Level A) | ||
| 2.4.1 Bypass Blocks (Level A) | Within the application content is typiclly not repeated and aria attributes are implemented in a significant portion of the application. |
|
| 2.4.2 Page Titled (Level A) | ||
| 2.4.3 Focus Order (Level A) | Some aspects of the application may have focus order that differs from the visual order of elements. Focus group testing has provided evidence that this did not prevent application usage and this is an area of constant improvement. | |
| 2.4.4 Link Purpose (In Context) (Level A) | ||
| 3.1.1 Language of Page (Level A) | The language of the application is specified in the <html> tag via the lang attribute. |
|
| 3.2.1 On Focus (Level A) | ||
| 3.2.2 On Input (Level A) | ||
| 3.3.1 Error Identification (Level A) | When a minor error occurs the error text is typically placed within the context of the object that error is related to. When a major error occurs, the context of the error is usually communicated; however, there can be cases where serious errors occur in the application and the objects or components responsible for the error cannot be readily identified at the time of error notification. In these situations, a more generalized error message will be provided to the user. | |
| 3.3.2 Labels or Instructions (Level A) | ||
| 4.1.1 Parsing (Level A) | ||
| 4.1.2 Name, Role, Value (Level A) | Form elements built into the application typically conform to this requirement; however, user generated form elements may not have appropriate names or roles as the actual HTML name value will typically be a unique identifier. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) | Live video broadcasts are not a component of this application. | |
| 1.2.5 Audio Description (Prerecorded) (Level AA) | ||
| 1.4.3 Contrast (Minimum) (Level AA) | The majority of text used in the application for all major functions has a contrast ratio of at least 4.5:1. Text failing to meet this standard is queued to be corrected to improved contrasts in a future release. | |
| 1.4.4 Resize Text (Level AA) | At 200%, the application functions in mobile mode to continue providing functionality with design elements modified to support the decreased screen size to text size ratio. | |
| 1.4.5 Images of Text (Level AA) | ||
| 2.4.5 Multiple Ways (Level AA) | Given the nature of this application, most elements are accessible through a series of steps rather than being static content that would warrant a site map. | |
| 2.4.6 Headings and Labels (Level AA) | ||
| 2.4.7 Focus Visible (Level AA) | The focus of some elements is not immediately visible to the user. This is an area of improvement we are actively working to improve. | |
| 3.1.2 Language of Parts (Level AA) | While the core of our application is single language and specified in the code, user provided content may be in other languages that are not known to the application and those components do not specify the language of that content. For example, the description of a resource may be in French, provided by the user, and while the entire application is specified as lang="en", that description block would not be specified as French. |
|
| 3.2.3 Consistent Navigation (Level AA) | ||
| 3.2.4 Consistent Identification (Level AA) | ||
| 3.3.3 Error Suggestion (Level AA) | ||
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) | For mutable data fields, any incorrect values can be modified after the initial modification. For immutable items, such as reservations, those reservations can be cancelled, modified, or replaced provided the administrators wish to allow this functionality within the operational constraints of their facility. For example, a reservation may be unmodifiable within a certain time period before the start of the reservation in order to meet the operational requirements of that facility. In such cases, data is still mutable when appropriate permission or task deligation is perfomed. |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Focus group user analysis partially supports access without vision. While some elements could be improved, all tested functions were accessible with appropriate screen reader software. | |
| 302.2 With Limited Vision | Focus group user analysis partially supports access without vision. While some elements could be improved, all tested functions were accessible with appropriate screen reader software. | |
| 302.3 Without Perception of Color | The user interface does not rely on specific color perceptions. | |
| 302.4 Without Hearing | Audio output is not a required component of this application. | |
| 302.5 With Limited Hearing | Audio output is not a required component of this application. | |
| 302.6 Without Speech | Audible speech input is not a required component of this application. | |
| 302.7 With Limited Manipulation | Standard and assistive technology input devices are compatible with this application. | |
| 302.8 With Limited Reach and Strength | Standard and assistive technology input devices are compatible with this application. | |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Focus group user analysis supports access with limited language, cognitive, and leaning abilities.. |
Chapter 4: Hardware
Not applicable.
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope - Incorporation of WCAG 2.0.AA | See Table 2 above. | |
| 502 Interoperability with Assistive Technology | ||
| 502.2.1 User Control of Accessibility Features | Accessibility features are incorprated into the application as a whole. At .his time, there are no in-application accessibility features that must be enabled. | |
| 502.2.2 No Disruption of Accessibility Features | As per the comment in 502.2.1, accessibility features are not toggled on or off, and thus their availability is not disruptable. | |
| 502.3 Accessibility Services | ||
| 502.3.1 Object Information | Form elements built into the application typically conform to this requirement; however, user generated form elements may not have appropriate names or roles as the actual HTML name value will typically be a unique identifier. | |
| 502.3.2 Modification of Object Information | ||
| 502.3.3 Row, Column, and Headers | ||
| 502.3.4 Values | ||
| 502.3.5 Modification of Values | ||
| 502.3.6 Label Relationships | Focus group testing and internal testing suggest this requirement has conformation; however, we are pending a more complete static analysis to confirm 100% support. | |
| 502.3.7 Hierarchical Relationships | ||
| 502.3.8 Text | ||
| 502.3.9 Modification of Text | ||
| 502.3.10 List of Actions | ||
| 502.3.11 Actions on Objects | ||
| 502.3.12 Focus Cursor | In the context of programmatic access to focus information, the web browser being using to interact with the application does provide information about current focus even if the styling in the UI fails to. | |
| 502.3.13 Modification of Focus Cursor | ||
| 502.3.14 Event Notification | ||
| 502.4 Platform Accessibility Features | The application, in conjunction with assistive technologies used with web browsers, should support the requirements outlined in this section. Note that full compliance with this section does depend on the appropriate behaviour of the web browser and its interaction with other assistive technologies used that is outside the scope of this document that references the QReserve application specifically. | |
| 503 Applications | ||
| 503.2 User Preferences | Our application does not prevent changes to font size and style overrides initiated through the web browser running the application. | |
| 503.3 Alternative User Interfaces | Alternative user interfaces are not provided. | |
| 503.4 User Controls for Captions and Audio Description | ||
| 503.4.1 Caption Controls | ||
| 503.4.2 Audio Description Controls | Embedded tutorial videos support automatically generated audio closed captions and alternative textual information sources that convey the same content are available within our help documentation. | |
| 504 Authoring Tools | ||
| 504.2 Content Creation or Editing | Other than plain text input, this application does not have a content creation component. | |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Other than plain text input, this application does not have a content creation component. | |
| 504.2.2 PDF Export | Export of application content to PDF through browser print-to-pdf functionality or through in application PDF generation may not conform to all standards at this time. | |
| 504.3 Prompts | The application does not prompt users to create content that conforms to Level A or Level AA at this time. | |
| 504.4 Templates | Content creation templates are not provided. | |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | ||
| 602 Support Documentation | ||
| 602.2 Accessibility and Compatibility Features | ||
| 602.3 Electronic Support Documentation | ||
| 602.4 Alternative Formats for Non-Electronic Support Documentation | Non-electronic support documentation is not currently available directly from the organization. | |
| 603 Support Services | ||
| 603.2 Information on Accessibility and Compatibility Features | Support inquiries related to accessibility and compatibility features are welcome. | |
| 603.3 Accommodation of Communication Needs | Our support services are available in a variety of communication methods including email, voice, and video communication to meet the communication needs of our users. | |