Arkose Labs Accessibility Conformance Report
based on VPAT® Version 2.5
Introduction
Product Information
Name of Product/Version: Arkose Labs Enforcement Challenge
Report Date: March 2024
Product Description: Arkose Bot Manager allows application development and security teams to protect their apps and users against bot-driven and related attacks. When suspicious signals are detected, web traffic can be sent through the proprietary challenge-response technology of Arkose Labs Enforcement Challenge, including Arkose MatchKey, to validate malicious intent. Targeted attack response allows good users to pass uninterrupted, while suspicious traffic is met with a game-like enforcement challenge that bots and fraudulent actors cannot effeciently solve.
Contact Information: [email protected]
Notes: This report covers the following Enforcement Challenge variants and versions:
- All current game types Match Key Game, Tile Game, and Audio Game
- On the current Enforcement Challenge UI 2.0
This report does not extend to legacy or fallback versions of our product, such as the legacy Enforcement Challenge UI 1.0, obsolete game types not listed above, or fallback mode render types.
WCAG compliance certificates as well as demo links for the covered game types are available to our customers upon request. Please reach out to your customer service representative.
Evaluation Methods Used: The following methods and technologies were used for evaluation:
- Screen readers, according to the matrix of supported screen reader/browser combinations, to evaluate the experience for users who are blind or have low vision.
- Keyboard access, to simulate the experience of a user with a mobility impairment, or who is blind.
- ZoomText and browser zoom, to test the experience of users with low vision who might magnify the screen.
- Color inversion, to identify issues for color blind, low vision or cognitively impaired users.
- Manual testing, supplemented with automated testing using ARC Toolkit and others
- User testing, conducted on a subset of challenge types and a subset of impairment types.
Evaluation, user testing, and WCAG certification was conducted by accessibility experts at me2 accessibility PTY LTD.
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) |
| Web Content Accessibility Guidelines 2.2 | 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.
WCAG 2.x Report
This WCAG 2.x Report table also documents conformance with Revised Section 508:
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.x 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.
Success Criteria, Level A
Note: The stated conformance level refers to the web aspect, as the Enforcement Challenge is a web only application. Other aspects (docs, software, closed, authoring tool) do not apply.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.1.1 Non-text Content (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge provides text alternatives for all non-text content. Exceptions: -Decorative images may have empty alt text attributes, to allow assistive technologies to ignore them. This is in line with WCAG best practices. -Challenge images provide only minimal information in alt text, to not invalidate their security purpose. Users have the option to switch to an audio challenge instead. This is an explicitly allowed “CAPTCHA” exception as per WCAG success criterion definitions. |
| 1.2.1 Audio-only and Video-only (Prerecorded) (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The audio challenge does not provide an alternative that presents equivalent information, to not invalidate their security purpose. However, an alternative for the audio challenge is provided via the visual challenge. |
| 1.2.2 Captions (Prerecorded) (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | Audio files used for audio challenges generally do not constitute of spoken words that would require captions. |
| 1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenges do not play any video content that would require audio description or a media alternative. |
| 1.3.1 Info and Relationships (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge user interface allows information and relationships to be programmatically determined. |
| 1.3.2 Meaningful Sequence (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge user interface presents elements in a logical and intuitive reading and navigation order. |
| 1.3.3 Sensory Characteristics (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge user interface does not rely on a single type of sensory characteristics alone to communicate information. Where specific sensory information is necessary to determine the correct answer to a challenge (e.g. to identify an image), there is always an alternative for the user to switch to (e.g. opting for the audio challenge instead of visual). |
| 1.4.1 Use of Color (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge does not use color as the only visual means of conveying information. |
| 1.4.2 Audio Control (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The audio challenge allows the user full control over the audio playback via play/pause button. |
| 2.1.1 Keyboard (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge is fully operable via keyboard. |
| 2.1.2 No Keyboard Trap (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge does not present instances where a keyboard user could not navigate away from an area with a keyboard. If the Enforcement Challenge is implemented as a modal dialog box, the dialog box traps the keyboard focus, but allows the user to dismiss the dialog via keyboard. |
| 2.1.4 Character Key Shortcuts (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Not Applicable | The Enforcement Challenge does not use printable key keyboard shortcuts. |
| 2.2.1 Timing Adjustable (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge generally does not set any time limits on user interactions. Exceptions: -Known fraudulent traffic may have time limits enforced for submitting answers to the challenge. As this is limited to a subset of known fraud traffic, ordinary users will not encounter these time limits. -Where content is displayed only temporarily, the same information can be obtained elsewhere on the challenge (e.g. progress indicator) or on the customer’s hosting page (e.g. success screen). -Both above cases constitute an explicitly allowed essential exception as per WCAG success criterion definitions, as these timings are an essential feature of our challenge technology and would otherwise invalidate the activity. |
| 2.2.2 Pause, Stop, Hide (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The visual challenge may use animated images on the retry screen, to illustrate the correct and incorrect example images. These animations stop automatically after a maximum of 5 seconds. |
| 2.3.1 Three Flashes or Below Threshold (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenge does not use any flashing effects in the user interface nor the challenge images. |
| 2.4.1 Bypass Blocks (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) – Does not apply to non-web software -504.2 (Authoring Tool) -602.3 (Support Docs) – Does not apply to non-web docs | Not Applicable | The Enforcement Challenge does not contain any repeated blocks of content. |
| 2.4.2 Page Titled (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenge is not a webpage, but an applet embedded within an iframe on the customer’s page. |
| 2.4.3 Focus Order (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge uses a focus order that is logical and preserves meaning and operability. |
| 2.4.4 Link Purpose (In Context) (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenge does not contain any hyperlinks. |
| 2.5.1 Pointer Gestures (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Not Applicable | The Enforcement Challenge does not use multipoint or path-based gestures for operation. |
| 2.5.2 Pointer Cancellation (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge does not use the down-event of the pointer to execute any function. |
| 2.5.3 Label in Name (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | Where the Enforcement Challenge uses icons with visible labels, those labels match the name of the same element. |
| 2.5.4 Motion Actuation (Level A 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Not Applicable | The Enforcement Challenge does not use motion actuation in any of their challenges or user interfaces. |
| 3.1.1 Language of Page (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge generally uses the browser's language setting to determine which language to present the user interface in. The selected language is specified in the document language in the HTML markup. |
| 3.2.1 On Focus (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge does not contain any elements that would cause a change of context when focused. |
| 3.2.2 On Input (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge does not contain any input elements that would cause a change of context when receiving input. |
| 3.2.6 Consistent Help (Level A 2.2 only) Also applies to: Revised Section 508 - Does not apply | Not Applicable | The Enforcement Challenge does not offer any of the mentioned help mechanisms (human contact details, human contact mechanism, self-help option, a fully automated contact mechanism). |
| 3.3.1 Error Identification (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The visual challenge provides a retry screen if the user submits an incorrect answer, informing the user of the incorrect answer, providing further text based and image based solve hints, and inviting them to retry. The audio challenge provides descriptive text based error messages if the user submits an incorrect answer or submits invalid characters. Both retry screens and error messages are automatically focused and announced by screen readers as expected. |
| 3.3.2 Labels or Instructions (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The audio challenge provides clear instructions and labels to guide the user towards entering the answer into the text input field. |
| 3.3.7 Redundant Entry (Level A 2.2 only) Also applies to: Revised Section 508 - Does not apply | Not Applicable | The Enforcement Challenge does not require the user to enter the exact same information multiple times. |
| 4.1.1 Parsing (Level A) Applies to: -WCAG 2.0 and 2.1 – Always answer ‘Supports’ -WCAG 2.2 (obsolete and removed) - Does not apply Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge’s markup content follows the language specification without significant validation errors. Further: For WCAG 2.0, 2.1, and Revised 508 Standards, the September 2023 errata update indicates this criterion is always supported. See the WCAG 2.0 Editorial Errata and the WCAG 2.1 Editorial Errata. |
| 4.1.2 Name, Role, Value (Level A) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge’s markup is used according to specification and is accessible. |
Success Criteria, Level AA
Note: The stated conformance level refers to the web aspect, as the Enforcement Challenge is a web only application. Other aspects (docs, software, closed, authoring tool) do not apply.
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 1.2.4 Captions (Live) (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenges do not use any live audio content. |
| 1.2.5 Audio Description (Prerecorded) (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenges do not play any video content that would require audio description or a media alternative. |
| 1.3.4 Orientation (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge is responsive and adapts its size and layout according to the viewport size and orientation of the user’s device. It works equally well in landscape and portrait orientation. |
| 1.3.5 Identify Input Purpose (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The purpose of each input field can be programmatically determined. |
| 1.4.3 Contrast (Minimum) (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge has sufficient color contrast between text and background in its default styling. Customers may chose to customize the Enforcement Challenge styling according to their own branding, in which case it is the customer’s responsibility to ensure sufficient color contrast. |
| 1.4.4 Resize text (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge allows users to resize text up to 200% without loss of content or functionality. |
| 1.4.5 Images of Text (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge does not contain images of text. |
| 1.4.10 Reflow (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge is able to accommodate zoom levels of up to 400% without loss of content or functionality or the need for scrolling in two dimensions. Content will reflow to the available viewport. Actual results are dependent on the customer’s implementation of the iframe which embeds the Enforcement Challenge into the customer’s web page, and, as such, are ultimately out of Arkose Labs' control. |
| 1.4.11 Non-text Contrast (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge has sufficient color contrast between non-text user interface components and their background in its default styling. Customers may chose to customize the Enforcement Challenge styling according to their own branding, in which case it is the customer’s responsibility to ensure sufficient color contrast. |
| 1.4.12 Text Spacing (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge allow users to adjust text spacing without loss of content or functionality. |
| 1.4.13 Content on Hover or Focus (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge does not contain content that appears on focus or hover. |
| 2.4.5 Multiple Ways (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) – Does not apply to non-web software -04.2 (Authoring Tool) -602.3 (Support Docs) – Does not apply to non-web docs | Not Applicable | The Enforcement Challenge is a single-page app. Individual screens within the app by design cannot be located or directly navigated to. |
| 2.4.6 Headings and Labels (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | Each screen of the Enforcement Challenge has appropriate headings and/or labels to describe its purpose. The Enforcement Challenge uses H2 headings only, not H1. This is to avoid user confusion when the challenge is embedded on a customer page which already has a H1 heading. |
| 2.4.7 Focus Visible (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge provides a visible keyboard focus. |
| 2.4.11 Focus Not Obscured (Minimum) (Level AA 2.2 only) Also applies to: Revised Section 508 – Does not apply | Supports | Any Enforcement Challenge element receiving keyboard focus is always visible in the user's viewport. |
| 2.5.7 Dragging Movements (Level AA 2.2 only) Also applies to: Revised Section 508 – Does not apply | Not Applicable | The Enforcement Challenge does not require dragging movements for any part of the user interaction. |
| 2.5.8 Target Size (Minimum) (Level AA 2.2 only) Also applies to: Revised Section 508 – Does not apply | Supports | The click targets throughout the Enforcement Challenge meet and exceed the minimum size requirements |
| 3.1.2 Language of Parts (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The Enforcement Challenge displays all phrases in the page’s native language, which is specified in the document language in the HTML markup. |
| 3.2.3 Consistent Navigation (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) – Does not apply to non-web software -504.2 (Authoring Tool) -602.3 (Support Docs) – Does not apply to non-web docs | Supports | The Enforcement Challenge uses consistent navigation throughout its different challenge types and games. |
| 3.2.4 Consistent Identification (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) – Does not apply to non-web software -504.2 (Authoring Tool) -602.3 (Support Docs) – Does not apply to non-web docs | Supports | Within the Enforcement Challenge, any components that have the same functionality are identified consistently across the different challenge types and games. |
| 3.3.3 Error Suggestion (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Supports | The audio challenge provides descriptive error messages, if the user submits invalid characters. |
| 3.3.4 Error Prevention (Legal, Financial, Data) (Level AA) Also applies to: Revised Section 508 -501 (Web)(Software) -504.2 (Authoring Tool) -602.3 (Support Docs) | Not Applicable | The Enforcement Challenge does not cause legal commitments or financial transactions for the user to occur. |
| 3.3.8 Accessible Authentication (Minimum) (Level AA 2.2 only) Also applies to: Revised Section 508 – Does not apply | Supports | The Enforcement Challenge provides the user with two alternatives for solving (visual or audio). At least one of those alternatives is generally an object recognition task, which therefore satisfies this criteria. |
| 4.1.3 Status Messages (Level AA 2.1 and 2.2) Also applies to: Revised Section 508 – Does not apply | Supports | Status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 302.1 Without Vision | Supports | The Enforcement Challenge offers an audio challenge alternative which does not require user vision. |
| 302.2 With Limited Vision | Supports | The Enforcement Challenge supports zoom methods and technologies such as browser zoom or screen magnifiers, to assist users with limited vision. It meets minimum contrast ratios, supports high contrast modes, and colour inversion. Additionally, the user can opt to use the audio challenge alternative. |
| 302.3 Without Perception of Color | Supports | The Enforcement Challenge does not rely on color vision to perceive or operate the user interface, nor to solve the visual challenge. |
| 302.4 Without Hearing | Supports | The Enforcement Challenge offers a visual challenge alternative which does not require user hearing. |
| 302.5 With Limited Hearing | Supports | The Enforcement Challenge offers a visual challenge alternative which does not require user hearing. |
| 302.6 Without Speech | Supports | The Enforcement Challenge does not require user speech. |
| 302.7 With Limited Manipulation | Supports | The Enforcement Challenge is fully operable (both visual and audio challenges) without pointing devices by keyboard alone. By extension, it can also be operated by any other input devices that emit the standard keyboard events. |
| 302.8 With Limited Reach and Strength | Supports | The Enforcement Challenge is fully operable (both visual and audio challenges) without pointing devices by keyboard alone. By extension, it can also be operated by any other input devices that emit the standard keyboard events. |
| 302.9 With Limited Language, Cognitive, and Learning Abilities | Supports | The Enforcement Challenge is designed to be inherently accessibility friendly: The challenges use familiar, everyday images or sounds, as well as plain language in instructions. It does not generally enforce a time limit on providing an answer (exceptions exist for known fraudulent traffic). The user is allowed unlimited attempts at solving, without increasing the challenge’s difficulty. Upon a failed attempt, the user is given further solve hints. At any point, the user can toggle between visual and audio challenges depending on ability and preference. |
Chapter 4: Hardware
Notes: Not applicable, the Enforcement Challenge is a web only application.
Chapter 5: Software
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 501.1 Scope – Incorporation of WCAG | See WCAG section | See information in WCAG section of this report |
| 502 Interoperability with Assistive Technology | Heading cell – no response required | Heading cell – no response required |
| 502.2.1 User Control of Accessibility Features | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.2.2 No Disruption of Accessibility Features | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3 Accessibility Services | Heading cell – no response required | Heading cell – no response required |
| 502.3.1 Object Information | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.2 Modification of Object Information | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.3 Row, Column, and Headers | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.4 Values | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.5 Modification of Values | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.6 Label Relationships | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.7 Hierarchical Relationships | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.8 Text | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.9 Modification of Text | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.10 List of Actions | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.11 Actions on Objects | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.12 Focus Cursor | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.13 Modification of Focus Cursor | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.3.14 Event Notification | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 502.4 Platform Accessibility Features | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 503 Applications | Heading cell – no response required | Heading cell – no response required |
| 503.2 User Preferences | Not Applicable | Not applicable, the Enforcement Challenge is a web only application. |
| 503.3 Alternative User Interfaces | Not Applicable | Not applicable, the Enforcement Challenge does not provide an alternative accessibility user interface. |
| 503.4 User Controls for Captions and Audio Description | Heading cell – no response required | Heading cell – no response required |
| 503.4.1 Caption Controls | Not Applicable | Not applicable, the Enforcement Challenge does not display video with synchronized audio. |
| 503.4.2 Audio Description Controls | Not Applicable | Not applicable, the Enforcement Challenge does not provide user controls for volume adjustment. |
| 504 Authoring Tools | Heading cell – no response required | Heading cell – no response required |
| 504.2 Content Creation or Editing (if not authoring tool, enter “not applicable”) | Not Applicable | Not applicable, the Enforcement Challenge is not an authoring tool. |
| 504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | Not applicable, the Enforcement Challenge is not an authoring tool. |
| 504.2.2 PDF Export | Not Applicable | Not applicable, the Enforcement Challenge is not an authoring tool. |
| 504.3 Prompts | Not Applicable | Not applicable, the Enforcement Challenge is not an authoring tool. |
| 504.4 Templates | Not Applicable | Not applicable, the Enforcement Challenge is not an authoring tool. |
Chapter 6: Support Documentation and Services
| Criteria | Conformance Level | Remarks and Explanations |
|---|---|---|
| 601.1 Scope | Heading cell – no response required | Heading cell – no response required |
| 602 Support Documentation | Heading cell – no response required | Heading cell – no response required |
| 602.2 Accessibility and Compatibility Features | Partially Supports | Arkose Labs does not provide any documentation aimed at the end user, as our products in general and the Enforcement Challenge in particular are embedded into the customers' web page or app. Arkose Labs' customer-facing documentation does however include an overview over the level of provided accessibility support. |
| 602.3 Electronic Support Documentation | See WCAG section | See information in WCAG section of this report |
| 602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | All documentation is provided electronically. |
| 603 Support Services | Heading cell – no response required | Heading cell – no response required |
| 603.2 Information on Accessibility and Compatibility Features | Not Applicable | Arkose Labs does not provide support services to end users. |
| 603.3 Accommodation of Communication Needs | Not Applicable | Arkose Labs does not provide support services to end users. |
Legal Disclaimer
© 2024 Arkose Labs. The information contained in this conformance report represents the current view of Arkose Labs on the issues discussed as of the date of publication, as stated in the Product Information section of this report. Arkose Labs cannot guarantee that any information in this Conformance Report will remain accurate after the date of publication. Any modification or customization of the product may render some or all of this Conformance Report to become inapplicable. This Conformance Report is provided “as is” and for informational purposes only.
Updated about 1 month ago