OnceHub Accessibility Conformance Report
- Name of Product: The public facing elements of OnceHub Booking Pages and Master Pages (the "Application").
- Product Description: All public facing web pages of the Application used to schedule, reschedule, and cancel bookings.
- Report Date: 12th June 2023
- Contact Information: privacyoffice@oncehub.com
- VPAT® Version: 2.4
- Evaluation Method: Systematic product evaluation.
- Applicable Standards/Guidelines
- Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 – the U.S. Federal accessibility standard for ICT Products, published by the U.S. Access Board in the Federal Register on January 18, 2017 and corrected on January 22, 2018.
- Web Content Accessibility Guidelines 2.0 or WCAG 2.0 (ISO/IEC 40500), Levels A & AA.
- Notes: Technical support for the Application is fully accessible, as it is provided over email, phone, and PDF help articles. Information in this Accessibility Conformance Report (ACR) is relevant to the elements of the Application running in a standards-compliant web browser. Web browsers may have extensions, plugins, or other add-ons installed by end users that may impact performance of the Application. These optional modifications of browsers have not been tested. Additionally, browsers in mobile devices have native methods for some behaviors that cannot be overridden. OnceHub does its best to accommodate those behaviors but success depends on versions of mobile operating systems. All other OnceHub product offerings not included in the definition of the Application are expressly excluded from the scope of this ACR.
- 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:
- 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.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
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content | Web: Supports | OnceHub allows account holders to upload images as backgrounds or icons on their booking pages and master pages. These images are for decoration purposes only, and may be ignored by assistive technology. |
| 1.2.1 Audio-only and Video-only (Prerecorded) | Not Applicable | The Application does not have prerecorded audio-only or prerecorded video-only media. |
| 1.2.2 Captions (Prerecorded) | Not Applicable | The Application does not have prerecorded audio content. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) | Not Applicable | The Application does not have prerecorded video content. |
| 1.3.1 Info and Relationships | Web: Supports | Most of the Application content is presented as text, the remainder is programmatically determinable using html semantics and ARIA attributes. |
| 1.3.2 Meaningful Sequence | Web: Supports | The correct reading sequence is meaningful throughout the Application. |
| 1.3.3 Sensory Characteristics | Web: Supports | The Application does not rely on sensory characteristics for instructions. |
| 1.4.1 Use of Color | Web: Supports | The Application does not rely on color alone to convey information. |
| 1.4.2 Audio Control | Not Applicable | The Application does not have audio content. |
| 2.1.1 Keyboard | Web: Supports | All functionality is operable using the keyboard alone in the Application, with some exceptions: Some buttons are only operable using the ENTER key. |
| 2.1.2 No Keyboard Trap | Web: Supports | The Application does not cause a keyboard trap. |
| 2.2.1 Timing Adjustable | Not Applicable | The Application does not contain any forms that are time constrained. |
| 2.2.2 Pause, Stop, Hide | Not Applicable | The Application does not have content that blinks, scrolls, or updates regularly. |
| 2.3.1 Three Flashes or Below Threshold | Not Applicable | The Application does not have flashing content. |
| 2.4.1 Bypass Blocks | Web: Supports | The Application provides a skip link that allows keyboard users to skip to the main content of the user interface. |
| 2.4.2 Page Titled | Web: Supports | The Application uses the name of the booking page for the page title (specifically “[NAME] – Online scheduling”) to ensure a descriptive title is provided. |
| 2.4.3 Focus Order | Web: Supports | Tab orders are logical in the Application. |
| 2.4.4 Link Purpose (In Context) | Web: Supports | The Application has meaningful link phrases. |
| 3.1.1 Language of Page | Web: Supports | The default language is English and is programmatically determinable. |
| 3.2.1 On Focus | Web: Supports | The Application does not cause a change of context on focus. |
| 3.2.2 On Input | Web: Supports | The Application does not cause an unexpected change of context when interacting with elements. |
| 3.3.1 Error Identification | Web: Supports | All error messages are text. |
| 3.3.2 Labels or Instructions | Web: Supports | Labels or instructions are visible for content which requires user input. |
| 4.1.1 Parsing | Web: Supports | Elements are compliant with proper html structures and guidelines. |
| 4.1.2 Name, Role, Value | Web: Supports | The Application provides the correct name, role, state, and other important accessibility information. |
Table 2: Success Criteria, Level AA
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) | Not Applicable | The Application does not have live audio content. |
| 1.2.5 Audio Description (Prerecorded) | Not Applicable | |
| 1.4.3 Contrast (Minimum) | Web: Supports | The Application has sufficient contrast between the foreground and background colors. |
| 1.4.4 Resize text | Web: Supports | Text is resizable to “very large” throughout the Application without a loss of content or functionality. However, depending on the browser being used, text size inside dropdown lists may not change. |
| 1.4.5 Images of Text | Web: Supports | The only images that include text are logos. |
| 2.4.5 Multiple Ways | Not Applicable | The Application consists of one page. |
| 2.4.6 Headings and Labels | Web: Supports | All content is semantically arranged with proper headings, from page titles, to form fields. |
| 2.4.7 Focus Visible | Web: Supports | Focus indicator is operable through Tab navigation. |
| 3.1.2 Language of Parts | Web: Supports | Content presented by the Application out of the box is readable as American English and determinable as such. Text can be changed into British English, French, German, Spanish, Brazilian Portuguese, and Dutch. This is determinable programmatically. |
| 3.2.3 Consistent Navigation | Web: Supports | The Application has a consistent navigation mechanism. |
| 3.2.4 Consistent Identification | Web: Supports | The Application components are identified consistently. |
| 3.3.3 Error Suggestion | Web: Supports | The Application does indicate required fields. |
| 3.3.4 Error Prevention (Legal, Financial, Data) | Web: Supports | Booking forms allow account holders to collect customer information – OnceHub is the processor in this context. Payment processing is done via PayPal integration, and charges may be reversed in part or in full, depending on the account holder’s refund policy. |
Revised Section 508 Report
Notes:
Chapter 3: Functional Performance Criteria (FPC)
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | Operable using a screen reader – The Application provides the correct name, role, state, and other important accessibility information for most interface elements. |
| 302.2 With Limited Vision | Supports | The Application can be used with limited vision. We rely on the browser and the operating systems support methods to change this. |
| 302.3 Without Perception of Color | Supports | The Application can be used without color perception. |
| 302.4 Without Hearing | Supports | No information is presented via audio. |
| 302.5 With Limited Hearing | Supports | No information is presented via audio. |
| 302.6 Without Speech | Supports | Speech is never the primary method, nor the only input method available to users. |
| 302.7 With Limited Manipulation | Supports | Operable with keyboard only without the need for fine motor control or simultaneous manual operations. |
| 302.8 With Limited Reach and Strength | Supports | Operable with keyboard only. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Not Supported | No additional functionality is in place to improve usability by users with Limited Language, Cognitive, and Learning Abilities. |
Chapter 5: Software
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG 2.0 AA | See WCAG 2.0 section | See information in WCAG section |
| 502 Interoperability with Assistive Technology | ||
| 502.2.1 User Control of Accessibility Features | Supports | The Application is not considered platform software as defined by Section 508. |
| 502.2.2 No Disruption of Accessibility Features | Supports | The Application is compatible with operating system and browser accessibility features configured by the user. |
| 502.3 Accessibility Services | ||
| 502.3.1 Object Information | Supports | The Application uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to assistive technologies. |
| 502.3.2 Modification of Object Information | Supports | The Application uses standard HTML or ARIA object roles for compatibility with assistive technologies. |
| 502.3.3 Row, Column, and Headers | Supports | The Application uses standard HTML attributes to define table structure and relationships, including column and row headers, to assistive technologies. |
| 502.3.4 Values | Supports | The Application uses standard HTML or ARIA object attributes for compatibility with assistive technologies. |
| 502.3.5 Modification of Values | Supports | The Application uses standard HTML or ARIA object attributes for compatibility with assistive technologies. |
| 502.3.6 Label Relationships | Supports | The Application uses standard HTML and WAI-ARIA attributes to describe label relationships of user interface elements to assistive technologies. This includes the use of “<label>” and “aria-labelledby” attributes. |
| 502.3.7 Hierarchical Relationships | Supports | The Application uses standard HTML markup to express hierarchical relationships. |
| 502.3.8 Text | Supports | The Application renders strings as plain text values in HTML for compatibility with assistive technologies. |
| 502.3.9 Modification of Text | Supports | The Application renders strings as plain text values in HTML for compatibility with assistive technologies. |
| 502.3.10 List of Actions | Supports | The Application uses standard HTML or ARIA object attributes for compatibility with assistive technologies. |
| 502.3.11 Actions on Objects | Supports | The Application uses standard HTML or ARIA object attributes for compatibility with assistive technologies. |
| 502.3.12 Focus Cursor | Supports | The Application uses visual changes to elements to indicate the current position of focus. See also 2.4.7 of Table 2 |
| 502.3.13 Modification of Focus Cursor | Supports | The Application uses standard HTML elements with standard cursor controls for user input. |
| 502.3.14 Event Notification | Not Applicable | There are no timeout events present in the Application. |
| 502.4 Platform Accessibility Features | Supports | The Application is not considered platform software as defined by Section 508. |
| 503 Applications | ||
| 503.2 User Preferences | Supports | The Application respects user preferences from platform or OS settings. For example, if a user enables high contrast mode, The Application user interfaces will display with high contrast. |
| 503.3 Alternative User Interfaces | Not Applicable | The Application does not provide any alternative user interfaces that function as assistive technology. |
| 503.4 User Controls for Captions and Audio Description | ||
| 503.4.1 Caption Controls | Not Applicable | No information is presented via audio. |
| 503.4.2 Audio Description Controls | Not Applicable | No information is presented via audio. |
| 504 Authoring Tools | ||
| 504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | See WCAG 2.0 section | See information in WCAG section |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | The Application does not make use of format conversion |
| 504.2.2 PDF Export | Not Applicable | The Application is not considered an authoring tool as defined by Section 508. |
| 504.3 Prompts | Not Applicable | The Application is not considered an authoring tool as defined by Section 508. |
| 504.4 Templates | Not Applicable | The Application is not considered an authoring tool as defined by Section 508. |
Chapter 6: Support Documentation and Services
Notes:
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | ||
| 602 Support Documentation | ||
| 602.2 Accessibility and Compatibility Features | Not Supported | All accessibility and compatibility features are managed by browser/computer settings. There is nothing that is programmatically managed by the Application. |
| 602.3 Electronic Support Documentation | Supports | Documentation is provided in text in a pdf format help file. The documentation complies with WCAG 2.0 A/AA |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All documentation is provided in electronic format. |
| 603 Support Services | ||
| 603.2 Information on Accessibility and Compatibility Features | Not Supported | |
| 603.3 Accommodation of Communication Needs | Not Supported |
Legal Disclaimer OnceHub
The Application includes various settings with accessibility impact. Out of the box settings are accessible, but changes made by account holders may not adhere to accessibility best practices. In such cases, the responsibility for accessibility relies on the account holder.
This information is true and correct to the best of our knowledge as of the date printed on the front page of this document. OnceHub cannot guarantee that any information in this ACR will remain accurate after this date, however we work continuously to monitor the accessibility of our product offerings and provide updates from time to time. This ACR is supplied “as is”, for customer evaluation purposes only; and is subject to change without notice. The contents of this document do not constitute either legal advice, representation, warranty or guarantee regarding a person's ability to comply with applicable accessibility requirements. Such a determination is the sole responsibility of the customer and its users. However, should you notice any issues, please report these to us so that they can be proactively addressed.
