Digital Science & Research Solutions, Inc. Accessibility Conformance Report International Edition
Based on VPAT® Version 2.4
Name of Product: ReadCube
Product Description: Linked research information system.
Report Date: Aug 24, 2023
Contact Information: support@readcube.com
Notes: This report covers accessibility conformance for ReadCube web application and does not discuss documentation or support services.
Evaluation Methods Used: SortSite website testing tool.
Applicable Standards/Guidelines
This report covers the degree of conformance for the following accessibility standard/guidelines:
| Standard/Guideline | Included In Report |
|---|---|
| Web Content Accessibility Guidelines 2.0 | Level A: Yes Level AA: Yes Level AAA: No |
| Web Content Accessibility Guidelines 2.1 | 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.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
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) Also applies to: EN 301 549 Criteria 9.1.1.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | ReadCube is only using a limited set of images which all have a text equivalent in the alt attribute. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria 9.1.2.1 (Web) Revised Section 508 501 (Web)(Software) | Not Applicable | ReadCube itself does not use video or audio. Nevertheless, supplemental material related to the documents we provide could use these formats without providing equivalent information. |
| 1.2.2 Captions (Prerecorded) (Level A) Also applies to: EN 301 549 Criteria 9.1.2.2 (Web) Revised Section 508 501 (Web)(Software) | Not Applicable | ReadCube itself does not use video or audio. Nevertheless, supplemental material related to the documents we provide could use these formats without providing captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded)(Level A) Also applies to: EN 301 549 Criteria 9.1.2.3 (Web) Revised Section 508 501 (Web)(Software) | Not Applicable | ReadCube itself does not use video or audio. Nevertheless, supplemental material related to the documents we provide could use these formats without providing an alternative. |
| 1.3.1 Info and Relationships (Level A) Also applies to: EN 301 549 Criteria 9.1.3.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | Information, structure, and relationships are available in text. E.g., the content is readable if the user switches off CSS. |
| 1.3.2 Meaningful Sequence (Level A) Also applies to: EN 301 549 Criteria 9.1.3.2 (Web) Revised Section 508 501 (Web)(Software) | Supports | Contents of sequences are structured, meaningful and can be programmatically determined. |
| 1.3.3 Sensory Characteristics (Level A) Also applies to: EN 301 549 Criteria 9.1.3.3 (Web) Revised Section 508 501 (Web)(Software) | Supports | Information is not solely provided by shape, size, location or orientation but always also available e.g., as alt text. |
| 1.4.1 Use of Color (Level A) Also applies to: EN 301 549 Criteria 9.1.4.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | For those elements in ReadCube where information is conveyed using color, the same information is also available by markup. |
| 1.4.2 Audio Control (Level A) Also applies to: EN 301 549 Criteria 9.1.4.2 (Web) Revised Section 508 501 (Web)(Software) | Not Applicable | ReadCube does not use audio. |
| 2.1.1 Keyboard (Level A)
Also applies to: EN 301 549 Criteria 9.2.1.1 (Web) Revised Section 508 501 (Web)(Software) | Partial Support | ReadCube provides support to execute most core functions using the keyboard. |
| 2.1.2 No Keyboard Trap (Level A) Also applies to: EN 301 549 Criteria 9.2.1.2 (Web) Revised Section 508 501 (Web)(Software) | Supports | Keyboard focus can be moved away from all components using only the keyboard interface. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EN 301 549 Criteria 9.2.1.4 (Web) Revised Section 508 - Does not apply | Not applicable | |
| 2.1.4 Character Key Shortcuts (Level A 2.1 only) Also applies to: EN 301 549 Criteria 9.2.1.4 (Web) Revised Section 508 - Does not apply | Not Applicable | |
| 2.2.1 Timing Adjustable (Level A) Also applies to: EN 301 549 Criteria 9.2.2.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | ReadCube product functionality is not restricted by time limits. Only downloads are available for a restricted time (Above the 20-hour limit). |
| 2.2.2 Pause, Stop, Hide (Level A) Also applies to: EN 301 549 Criteria 9.2.2.2 (Web) Revised Section 508 501 (Web)(Software) | Not applicable | |
| 2.3.1 Three Flashes or Below Threshold(Level A) Also applies to: EN 301 549 Criteria 9.2.3.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | The ReadCube application does not use flashing elements. Nevertheless, supplemental material related to the documents we provide could contain flashes or flickering e.g., in videos. |
| 2.4.1 Bypass Blocks (Level A) Also applies to: EN 301 549 Criteria 9.2.4.1 (Web) Revised Section 508 501 (Web)(Software) - Does not apply to non-web software | Supports | ReadCube does provide support to bypass repeated elements like navigation links. |
| 2.4.2 Page Titled (Level A) Also applies to: EN 301 549 Criteria 9.2.4.2 (Web) Revised Section 508 501 (Web)(Software) | Supports | All pages in ReadCube have titles describing the purpose. |
| 2.4.3 Focus Order (Level A) Also applies to: EN 301 549 Criteria 9.2.4.3 (Web) Revised Section 508 501 (Web)(Software) | Supports | ReadCube can be navigated sequentially in a meaningful and operable manner. |
| 2.4.4 Link Purpose (In Context) (Level A) Also applies to: EN 301 549 Criteria 9.2.4.4 (Web) Revised Section 508 501 (Web)(Software) | Supports | Link's purpose can be determined by link text and context. |
| 2.5.1 Pointer Gestures (Level A 2.1 only) Also applies to: EN 301 549 Criteria 9.2.5.1 (Web) Revised Section 508 - Does not apply | Not applicable | |
| 2.5.2 Pointer Cancellation (Level A 2.1 only) Also applies to: EN 301 549 Criteria 9.2.5.2 (Web) Revised Section 508 - Does not apply | Supports | The pointer down-event is not used to execute functions. |
| 2.5.3 Label in Name (Level A 2.1 only) Also applies to: EN 301 549 Criteria 9.2.5.3 (Web) Revised Section 508 - Does not apply | Supports | The components with labels have the visually shown text in name attribute. |
| 2.5.4 Motion Actuation (Level A 2.1 only) Also applies to: EN 301 549 Criteria 9.2.5.4 (Web) Revised Section 508 - Does not apply | Not applicable | |
| 3.1.1 Language of Page (Level A)
Also applies to: EN 301 549 Criteria 9.3.1.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | The language of pages in ReadCube is provided by the 'lang' attribute. |
| 3.2.1 On Focus(Level A) Also applies to: EN 301 549 Criteria 9.3.2.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | No actions are performed when components get focus. |
| 3.2.2 On Input (Level A) Also applies to: EN 301 549 Criteria 9.3.2.2 (Web) Revised Section 508 501 (Web)(Software) | Supports | Changing settings of user interface components does not automatically cause a change of context. |
| 3.3.1 Error Identification (Level A) Also applies to: EN 301 549 Criteria 9.3.3.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | Error messages in ReadCube are clearly visible and as specific as possible. |
| 3.3.2 Labels or Instructions (Level A) Also applies to: EN 301 549 Criteria 9.3.3.2 (Web)Revised Section 508 501 (Web)(Software) | Supports | Labels are provided when content requires user input. |
| 4.1.1 Parsing (Level A) Also applies to: EN 301 549 Criteria 9.4.1.1 (Web) Revised Section 508 501 (Web)(Software) | Supports | The markup of ReadCube has complete start and end tags, attributes and IDs are unique. |
| 4.1.2 Name, Role, Value (Level A) Also applies to: EN 301 549 Criteria 9.4.1.2 (Web) Revised Section 508 501 (Web)(Software) | Supports | Role, state, and value information are provided on all user interface components. |
Table 2: Success Criteria, Level AA
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) Also applies to: EN 301 549 Criteria 9.1.2.4 (Web) Revised Section 508 501 (Web)(Software) | Not Applicable | ReadCube does not use audio media. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: EN 301 549 Criteria 9.1.2.5 (Web) Revised Section 508 501 (Web)(Software) | Not applicable | |
| 1.3.4 Orientation (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.1.3.4 (Web) Revised Section 508 - Does not apply | Supports | ReadCube content can be viewed and operated in portrait and landscape display orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.1.3.5 (Web) Revised Section 508 - Does not apply | Supports | Input collecting information about the user is implemented with support to identify the meaning for the form input data. |
| 1.4.3 Contrast (Minimum) (Level AA) Also applies to: EN 301 549 Criteria 9.1.4.3 (Web) Revised Section 508 501 (Web)(Software) | Supports | Visual presentation of information, match level AA contrast ratio requirements. (At least 4.5:1 for small text and 3:1 for large texts). |
| 1.4.4 Resize text (Level AA) Also applies to: EN 301 549 Criteria 9.1.4.4 (Web) Revised Section 508 501 (Web)(Software) | Supports | Text can be resized without assistive technology up to 200 percent without loss of content or functionality. |
| 1.4.5 Images of Text (Level AA) Also applies to: EN 301 549 Criteria 9.1.4.5 (Web) Revised Section 508 501 (Web)(Software) | Supports | Text is the primary way to convey information in ReadCube. |
| 1.4.10 Reflow (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.1.4.10 (Web) Revised Section 508 - Does not apply | Supports | Only data tables, images or PDFs require two-way scrolling. |
| 1.4.11 Non-text Contrast (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.1.4.11 (Web) Revised Section 508 - Does not apply | Supports | Parts of the ReadCube user interface that are needed to understand the content have a contrast ratio of at least 3:1. |
| 1.4.12 Text Spacing (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.1.4.12 (Web) Revised Section 508 - Does not apply | Supports | No loss of content or functionality occurs by changing text styles to required settings. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.1.4.13 (Web) Revised Section 508 - Does not apply | Supports | Additional content is dismissible, hoverable, and persistent. |
| 2.4.5 Multiple Ways (Level AA) Also applies to: EN 301 549 Criteria 9.2.4.5 (Web) Revised Section 508 501 (Web)(Software) - Does not apply to non-web software | Supports | Contents in ReadCube can be searched, browsed, and navigated in different ways. |
| 2.4.6 Headings and Labels (Level AA) Also applies to: EN 301 549 Criteria 9.2.4.6 (Web) Revised Section 508 501 (Web)(Software) | Supports | Headings and labels are designed to be clear, descriptive, and logically organized. |
| 2.4.7 Focus Visible (Level AA) Also applies to: EN 301 549 Criteria 9.2.4.7 (Web) Revised Section 508 501 (Web)(Software) | Supports | Keyboard focus is always visible in ReadCube. |
| 3.1.2 Language of Parts (Level AA) Also applies to: EN 301 549 Criteria 9.3.1.2 (Web) Revised Section 508 501 (Web)(Software) | Supports | When parts of a page are presented in a different language than the page itself, the language can be programmatically determined. |
| 3.2.3 Consistent Navigation (Level AA) Also applies to: EN 301 549 Criteria 9.3.2.3 (Web) Revised Section 508 501 (Web)(Software) - Does not apply to non-web software | Supports | Navigation areas shown on multiple pages are presented in a consistent way. |
| 3.2.4 Consistent Identification (Level AA) Also applies to: EN 301 549 Criteria 9.3.2.4 (Web) Revised Section 508 501 (Web)(Software) - Does not apply to non-web software | Supports | UI components with same functionality are identified consistently. |
| 3.3.3 Error Suggestion (Level AA) Also applies to: EN 301 549 Criteria 9.3.3.3 (Web) Revised Section 508 501 (Web)(Software) | Supports | Error feedback in ReadCube is designed to give the best possible suggestions to users. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: EN 301 549 Criteria 9.3.3.4 (Web) Revised Section 508 501 (Web)(Software) | Supports | For all data that can be modified or deleted by users in ReadCube functionalities are provided that need confirmation or can be reversed. |
| 4.1.3 Status Messages (Level AA 2.1 only) Also applies to: EN 301 549 Criteria 9.4.1.3 (Web) Revised Section 508 - Does not apply | Supports | Status messages can be programmatically determined through role or properties. |
Table 3: Success Criteria, Level AAA
Notes: ReadCube has not been evaluated for WCAG 2.1 Level AAA conformance.
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | ReadCube uses standard HTML attributes to describe identity, operation, and state of user interface elements to assistive technologies. |
| 302.2 With Limited Vision | Supports | ReadCube supports standard browser magnification and contrast adjustments. |
| 302.3 Without Perception of Color | Supports | Color is only used as a supplemental attribute of user interface elements. |
| 302.4 Without Hearing | Not Applicable | ReadCube does not use features that require hearing. |
| 302.5 With Limited Hearing | Not Applicable | ReadCube does not use features that require hearing. |
| 302.6 Without Speech | Not Applicable | ReadCube does not use features that require speech input. |
| 302.7 With Limited Manipulation | Supports | ReadCube supports standard input mechanisms such as keyboards and pointing devices. Fine motor controls nor simultaneous actions are not required. |
| 302.8 With Limited Reach and Strength | Supports | Use of ReadCube is not restricted by limited reach or strength. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Partially Supports | ReadCube is a complex product and needs training and technical experience. We strive to support users in the best possible ways. |
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope - Incorporation of WCAG 2.0 AA | See WCAG 2.1 section | See information in WCAG 2.1 section |
| 502 Interoperability with Assistive Technology | ||
| 502.2.1 User Control of Accessibility Features | Not applicable | ReadCube is not platform software. |
| 502.2.2 No Disruption of Accessibility Features | Supports | ReadCube has not been found to disrupt accessibility features of the user's system. |
| 502.3 Accessibility Services | ||
| 502.3.1 Object Information | Supports | ReadCube uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
| 502.3.2 Modification of Object Information | Supports | ReadCube uses standard HTML or ARIA object roles for maximum compatibility with assistive technologies. |
| 502.3.3 Row, Column, and Headers | Supports | ReadCube uses standard HTML attributes to define table structure and relationships. |
| 502.3.4 Values | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.5 Modification of Values | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.6 Label Relationships | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.7 Hierarchical Relationships | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 502.3.8 Text | Supports | ReadCube renders strings as plain text values in HTML for maximum compatibility with assistive technologies. |
| 502.3.9 Modification of Text | Supports | ReadCube renders strings as plain text values in HTML for maximum compatibility with assistive technologies. |
| 502.3.10 List of Actions | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.11 Actions on Objects | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.3.12 Focus Cursor | Supports | ReadCube uses standard HTML elements with standard cursor controls for user input. |
| 502.3.13 Modification of Focus Cursor | Supports | ReadCube uses standard HTML elements with standard cursor controls for user input. |
| 502.3.14 Event Notification | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 502.4 Platform Accessibility Features | Not Applicable | ReadCube is not platform software. |
| 503 Applications | ||
| 503.2 User Preferences | Supports | ReadCube respects user preferences from platform or browser. |
| 503.3 Alternative User Interfaces | Not Applicable | ReadCube does not offer alternative user interfaces. |
| 503.4 User Controls for Captions and Audio Description | ||
| 503.4.1 Caption Controls | Not Applicable | |
| 503.4.2 Audio Description Controls | Not Applicable | |
| 504 Authoring Tools | ||
| 504.2 Content Creation or Editing (if not authoring tool, enter "not applicable") | See WCAG 2.1 section | See information in WCAG 2.1 section |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | |
| 504.2.2 PDF Export | Not Applicable | |
| 504.3 Prompts | Not Applicable | |
| 504.4 Templates | Not Applicable |
Chapter 6: Support Documentation and Services
Notes: This report covers accessibility conformance for ReadCube product and does not discuss support documentation or services. Support documentation and services are not fully accessible, but support is available via email.
EN 301 549 Report
Chapter 4: Functional Performance Statements (FPS)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 4.2.1 Usage without vision | Supports | ReadCube uses standard HTML and WAI-ARIA attributes to describe the identity, operation, and state of user interface elements to Assistive Technologies |
| 4.2.2 Usage with limited vision | Supports | ReadCube supports standard browser magnification and contrast adjustments |
| 4.2.3 Usage without perception of color | Supports | Color is only used as a decorative or supplemental attribute of user interface elements. |
| 4.2.4 Usage without hearing | Not Applicable | |
| 4.2.5 Usage with limited hearing | Not Applicable | |
| 4.2.6 Usage without vocal capability | Not Applicable | |
| 4.2.7 Usage with limited manipulation or strength | Supports | ReadCube supports standard input mechanisms such as keyboards and pointing devices. Fine motor controls nor simultaneous actions are not required. |
| 4.2.8 Usage with limited reach | Supports | Use of ReadCube is not restricted by limited reach or strength. |
| 4.2.9 Minimize photosensitive seizure triggers | Supports | ReadCube does not include visual features with flashing that could trigger seizures. |
| 4.2.10 Usage with limited cognition | Partially Supports | ReadCube is a complex product and needs training and technical experience. We strive to support users in the best possible ways. |
| 4.2.11 Privacy | Supports | ReadCube does not impede usage of standard privacy controls alongside assistive technologies. For example, users can connect a headset for private listening to screen reader announcements. |
Chapter 5: Generic Requirements
Notes: ReadCube supports standard assistive technologies and is therefore not subject to the Closed Functionality criteria described in this Chapter.
Chapter 6: ICT with Two-Way Voice Communication
Notes: ReadCube does not offer two-way voice communication and is therefore not subject to the requirements of this section.
Chapter 7: ICT with Video Capabilities
Notes: ReadCube does not include video content and is therefore not subject to the requirements of this section.
Chapter 8: Hardware
Notes: ReadCube is a web software application and is not subject to the requirements of this section.
Chapter 9: Web (see WCAG 2.1 section)
Chapter 10: Non-Web Software
Notes: ReadCube does not include non-web documents and is therefore not subject to the requirements of this section.
Chapter 11: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 11.0 General | ||
| 11.1.1.1 through 11.4.1.3 | See WCAG 2.1 section | See information in WCAG 2.1 section |
| 11.5 Interoperability with assistive technology | ||
| 11.5.1 Closed functionality (informative) | ||
| 11.5.2 Accessibility services | ||
| 11.5.2.1 Platform accessibility service support for software that provides a user interface | See 11.5.2.5 through 11.5.2.17 | See 11.5.2.5 through 11.5.2.17 |
| 11.5.2.2 Platform accessibility service support for assistive technologies | See 11.5.2.5 through 11.5.2.17 | See 11.5.2.5 through 11.5.2.17 |
| 11.5.2.3 Use of accessibility services | Supports | ReadCube uses standard platform accessibility services. |
| 11.5.2.4 Assistive technology | Not Applicable | ReadCube is not itself an assistive technology. |
| 11.5.2.5 Object information | Supports | ReadCube uses WAI-ARIA attributes to describe the role, state, and description of user interface elements to Assistive Technologies. This includes the use of "role", "aria-invalid", and "aria-required" attributes. |
| 11.5.2.6 Row, column, and headers | Supports | ReadCube uses standard HTML attributes to define table structure and relationships, including column and row headers, to Assistive Technologies. |
| 11.5.2.7 Values | Supports | ReadCube uses standard HTML or ARIA object attributes for maximum compatibility with assistive technologies. |
| 11.5.2.8 Label relationships | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.9 Parent-child relationships | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.10 Text | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.11 List of available actions | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.12 Execution of available actions | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.13 Tracking of focus and selection attributes | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.14 Modification of focus and selection attributes | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.15 Change notification | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.16 Modifications of states and properties | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.5.2.17 Modifications of values and text | Supports | ReadCube uses standard HTML markup for maximum compatibility with assistive technologies. |
| 11.6 Documented accessibility usage | ||
| 11.6.1 User control of accessibility features | Not Applicable | ReadCube is not platform software |
| 11.6.2 No disruption of accessibility features | Supports | |
| 11.7 User preferences | Supports | ReadCube respects user preferences from platform or browser. |
| 11.8 Authoring tools | ||
| 11.8.1 Content technology | ||
| 11.8.2 Accessible content creation (if not authoring tool, enter "not applicable") | See information in WCAG 2.1 section | See information in WCAG 2.1 section |
| 11.8.3 Preservation of accessibility information in transformations | Not Applicable | |
| 11.8.4 Repair assistance | Not Applicable | |
| 11.8.5 Templates | Not Applicable |
Chapter 12: Documentation and Support Services
Notes: This report covers accessibility conformance for the ReadCube web app and does not discuss support documentation or services. Support documentation and services are not fully accessible, but support is available via email.
Chapter 13: ICT Providing Relay or Emergency Service Access
Notes: Not applicable to ReadCube
Legal Disclaimer
This document seeks to describe ReadCube's ability to support the applicable standards, subject to our interpretation of those standards and the comments in this document. It is provided "AS IS" for information purposes only and is subject to change without notice. This document is not intended to (nor does it) create, impose or supplement any duty or obligation, contractual or otherwise. Without prejudice to the generality of the foregoing, no warranty is given that this document is correct, complete, up to date, or fit for any particular purpose and no liability shall arise for any loss, damage or expense whatsoever, whether direct or indirect, howsoever arising, whether in contract, tort (including negligence) or otherwise, in connection with document, including (without limitation) any course of action taken on the basis of its content.