VPAT® Version 2.3 - April 2019
The OCI Data Labeling service (DLS) is an OCI native service that allows customers to create and browse datasets, view data records (text, images) and apply labels for the purposes of building AI/ML models. The service also provides interactive user interfaces designed to aide in the labeling process. Once records are labeled, the dataset can be exported as line-delimited JSON for use in machine learning model development. The OCI Data Labeling service will provide a platform for customers to assemble data into data sets, grant access to labelers, provide interactive UIs and instructions to labelers, store data labels and collate this labeled data which can then be used to build custom AI/ML models
This ACR does not cover APIs nor backend services
This product interacts with or is built with the other Oracle products listedin this section. Click below to view information about the accessibility ofthese dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersedethese versions.
Oracle's policy is to design, develop and test both products and documentation to be accessible. The recommended styles of testing for accessibility include: (i) algorithmic automated tests, (ii) human judgement tests such as tool-assisted tests, visual inspection and manual operation, and (iii) testing with assistive technology by people with and without disabilities. Additional information about Oracle's accessibility program is available on http://www.oracle.com/corporate/accessibility/index.html
This report covers the degree of conformance for the following accessibility standard/guideline:
Standard/Guideline | Included In Report |
---|---|
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 |
The terms used in the Conformance Level information are defined as follows:
Table 1 also documents conformance with:
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.1 Conformance Requirements.
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
1.1.1 Non-text Content (Level A) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3282 For different screens and components listed below, there is a missing label for control:
DLS-3382 Alternative text for following SVG images is missing:
|
1.2.1 Audio-only and Video-only (Prerecorded) (Level A) | Not Applicable | The product has no multimedia. |
1.2.2 Captions (Prerecorded) (Level A) | Not Applicable | The product has no multimedia. |
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A) | Not Applicable | The product has no multimedia. |
1.2.4 Captions (Live) (Level AA) | Not Applicable | The product has no multimedia. |
1.2.5 Audio Description (Prerecorded) (Level AA) | Not Applicable | The product has no multimedia. |
1.3.1 Info and Relationships (Level A) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3280 For different screens listed below, the tables present don't have accessible text:
DLS-3284 On the labeling screen, lists are not structured correctly for carousel. DLS-3314 On the overview page, the headers are incorrectly used for links like Image Labeling, Document Labeling and Text Labeling. DLS-3809 With screen readers enabled, whenever the focus comes to rows in tables present on list datasets and dataset details page, screen readers announce row id (which is a hidden field). Row id is the programatic row identifier which has no meaning for the user. |
1.3.2 Meaningful Sequence(Level A) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3268 On the labeling screen, when we try to navigate using tab key, after the toolbar, focus goes to carousel and then comes to Tools, Adjust image, Labels. The order is not maintained as the DOM contains Carousel before the draggable panels. |
1.3.3 Sensory Characteristics(Level A) | Supports | The product was tested for:
|
1.3.4 Orientation (Level AA) | Supports | The product was tested for :
|
1.3.5 Identify Input Purpose (Level AA) | Supports | The product was tested for:
|
1.4.1 Use of Color(Level A) | Supports | The product was tested for:
|
1.4.2 Audio Control(Level A) | Not Applicable | The product has no multimedia. |
1.4.3 Contrast (Minimum) (Level AA) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3281 For different screens and components listed below, there is an issue with contrast between foreground and background colors. The contrast ratio should be at least 4.5:1.
|
1.4.4 Resize text(Level AA) | Supports | The product was tested for:
|
1.4.5 Images of Text(Level AA) | Supports | The product was tested for:
|
1.4.10 Reflow (Level AA) | Partially Supports | The product was tested for :
The following tickets track the identified errors in DLS Jira: DLS-3285 For the labeling screen, functionality becomes unusable if the zoom level is 400%. |
1.4.11 Non-text Contrast (Level AA) | Supports | The product was tested for:
|
1.4.12 Text Spacing (Level AA) | Supports | The product was tested for:
|
1.4.13 Content on Hover or Focus (Level AA) | Supports | The product was tested for:
|
2.1.1 Keyboard(Level A) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3266 On the labeling screen, toolbar buttons - Move, zoom in/out, etc don't respond to "Enter" key. Carousel images don't respond to "Enter" key Toolbar buttons and Carousel images, receive the focus using tab key but intended operations do not take place once "Enter" key is pressed. DLS-3277 For the Labels set field (Step 2 of create dataset flow) and Add labels dialog on dataset details screen and labeling screen, labels can't be deleted with "enter" key when "X" icon is highlighted. Workaround - Selected values can be cleared by hitting the delete/backspace key. DLS-3320 When screen reader is enabled, while creating the dataset, the bucket can't be selected in step no 2 (Add files and labels). Screen reader treats the field as text and list of buckets don't show up. DLS-3810 While screen reader is enabled, navigation doesn't work for below mentioned links by hitting "Enter" key on keyboard:
|
2.1.2 No Keyboard Trap (Level A) | Supports | The product was tested for:
|
2.1.4 Character Key Shortcuts (Level A) | Supports | The product was tested for:
|
2.2.1 Timing Adjustable(Level A) | Supports | The product was tested for:
|
2.2.2 Pause, Stop, Hide (Level A) | Supports | The product was tested for:
|
2.3.1 Three Flashes or Below Threshold(Level A) | Supports | The product was tested for:
|
2.4.1 Bypass Blocks(Level A) | Supports | The product was tested for:
|
2.4.2 Page Titled(Level A) | Supports | The product was tested for:
|
2.4.3 Focus Order(Level A) | Partially Supports | The product was tested for:
The following ticket tracks the identified error in DLS Jira: DLS-3263 For the create dataset flow, while navigating the workflow steps on the left, inactive steps dont' get focus in forward direction. DLS-3264 On the dataset details screen, while navigating using keyboard, focus gets lost after "More Actions" button. After pressing tab 3 times, it becomes visible DLS-3267 On the labeling screen, while traversing using tab key, carousel header, "Records (1 of 10 labelled)" also receives focus which is not desirable as this text is not actionable. DLS-3268 On the labeling screen, when we try to navigate using tab key, after the toolbar, focus goes to carousel and then comes to Tools, Adjust image, Labels. The order is not maintained as the DOM contains Carousel before the draggable panels. DLS-3270 On the labeling screen, using tab key if we try to select labels for single/multiple label type datasets, as soon as selection is made, the focus goes to first element on the page. DLS-3276 On the labeling screen, for Object Detection type datasets, inside the Tools panel, focus is not coming on the actionable items - Bounding box and remove box. |
2.4.4 Link Purpose (In Context)(Level A) | Supports | The product was tested for:
|
2.4.5 Multiple Ways(Level AA) | Supports | The product was tested for:
|
2.4.6 Headings and Labels(Level AA) | Supports | The product was tested for:
|
2.4.7 Focus Visible(Level AA) | Partially Supports | The product was tested for:
The following ticket tracks the identified error in DLS Jira: DLS-3269 On the labeling screen, while trying to navigate the adjust image panel using tab key, the controls receive focus but the border is missing. As a result visual representation is missing. If we press up/down arrow, the value changes indicating the focus. |
2.5.1 Pointer Gestures (Level A) | Supports | The product was tested for:
|
2.5.2 Pointer Cancellation (Level A) | Supports | The product was tested for:
|
2.5.3 Label in Name (Level A) | Supports | The product has been tested for:
|
2.5.4 Motion Actuation (Level A) | Supports | The product was tested for:
|
3.1.1 Language of Page(Level A) | Supports | The product was tested for:
|
3.1.2 Language of Parts(Level AA) | Supports | The product was tested for:
|
3.2.1 On Focus(Level A) | Supports | The product was tested for:
|
3.2.2 On Input(Level A) | Supports | The product was tested for:
|
3.2.3 Consistent Navigation(Level AA) | Supports | The product was tested for:
|
3.2.4 Consistent Identification(Level AA) | Supports | The product was tested for:
|
3.3.1 Error Identification(Level A) | Supports | The product was tested for:
|
3.3.2 Labels or Instructions (Level A) | Partially Supports | The product was tested for:
The following ticket tracks the identified error in DLS Jira: DLS-3282 For different screens and components listed below, there is a missing label for the form control:
|
3.3.3 Error Suggestion (Level AA) | Supports | The product was tested for:
|
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA) | Supports | The product was tested for:
|
4.1.1 Parsing(Level A) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3279 For different screens and components listed below, the landmarks are not unique:
DLS-3283 In Create dataset flow Step No 1 --> Add dataset details --> Tags fieldset, the ids for fields are not unique |
4.1.2 Name, Role, Value (Level A) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3316 For the list datasets, dataset details and work request list screens where we have tables, screen reader is not announcing number of results in table. DLS-3317 For the following fields, screen reader is not announcing labels:
DLS-3369 On the labeling screen, screen reader is not announcing the canvas. For images and documents, the screen reader does not read out the record name for single/multiple label text type datasets. |
4.1.3 Status Messages (Level AA) | Partially Supports | The product was tested for:
The following tickets track the identified errors in DLS Jira: DLS-3318 For List datasets screen, screen reader starts announcing the status like active, needs attention, labeled, unlabeled, etc in random. This is not done against a particular table row entry. Only the status names on the page are announced as soon as user lands on the screen. DLS-3321 The screen reader is not reading the status when the datataset is in "needs attention" state. DLS-3322 When the records are being generated or the dataset is being exported (Updating state), screen reader doesn't announce the progress of the operation on the dataset details screen. DLS-3323 For the operations which take time like Add labels, delete, loading icon is visible on screen for a long time. Screen readers must announce the ongoing operation like "Creating labels", Deleting labels", etc. Below are some of the operations:
DLS-3324 On the dataset details screen, once the delete tag operation completes, screen reader is not able to announce the same. DLS-3808 Screen readers are not announcing toast notifications on the dataset details page. |
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
302.1 Without Vision | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.2 With Limited Vision | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.3 Without Perception of Color | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.4 Without Hearing | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.5 With Limited Hearing | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.6 Without Speech | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.7 With Limited Manipulation | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.8 With Limited Reach and Strength | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
302.9 With Limited Language, Cognitive, and Learning Abilities | Not Applicable | The product does not rely on equivalent functionality, and all aspects are addressed by the technical standards. |
These criteria are all Not Applicable because the product is not Hardware
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
501.1 Scope - Incorporation of WCAG 2.0 AA | Supports | See the responses in the WCAG 2.0 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 | The product is not a platform or does not have access to platform accessibility features. |
502.2.2 No Disruption of Accessibility Features | Not Applicable | The product is designed to be isolated from the underlying platform. |
 502.3 Accessibility Services | Heading cell - no response required | Heading cell - no response required |
502.3.1 Object Information | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.2 Modification of Object Information | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.3 Row, Column, and Headers | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.4 Values | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.5 Modification of Values | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.6 Label Relationships | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.7 Hierarchical Relationships | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.8 Text | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.9 Modification of Text | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.10 List of Actions | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.11 Actions on Objects | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.12 Focus Cursor | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.13 Modification of Focus Cursor | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.3.14 Event Notification | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
502.4 Platform Accessibility Features | Not Applicable | The product is not a platform or does not have access to platform accessibility features. |
 503 Applications | Heading cell - no response required | Heading cell - no response required |
503.2 User Preferences | Not Applicable | The product is designed to be isolated from the underlying platform. |
503.3 Alternative User Interfaces | Not Applicable | The product does not have assistive technology features. |
 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 | The product has no multimedia. |
503.4.2 Audio Description Controls | Not Applicable | The product has no multimedia. |
 504 Authoring Tools | Heading cell - no response required | Heading cell - no response required |
504.2 Content Creation or Editing | Not Applicable | The product is not an authoring tool. |
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion | Not Applicable | The product is not an authoring tool. |
504.2.2 PDF Export | Not Applicable | The product is not an authoring tool. |
504.3 Prompts | Not Applicable | The product is not an authoring tool. |
504.4 Templates | Not Applicable | The product is not an authoring tool. |
Criteria | Conformance Level | Remarks and Explanations |
---|---|---|
 602 Support Documentation | Heading cell - no response required | Heading cell - no response required |
602.2 Accessibility and Compatibility Features | Not Applicable | There are no accessibility or compatibility features to document. Product uses standard HTML specifications to support accessibility |
602.3 Scope - Incorporation of WCAG 2.0 AA | Supports | See the responses in the WCAG 2.0 section of this report. |
602.4 Alternate Formats for Non-Electronic Support Documentation | Not Applicable | Product documentation is in electronic format. |
 603 Support Services | Heading cell - no response required | Heading cell - no response required |
603.2 Information on Accessibility and Compatibility Features | Supports | Oracle Global Customer Support can provide information about accessibility features of the product. |
603.3 Accommodation of Communication Needs | Supports | Oracle customers have access to electronic support through My Oracle Support or by calling Oracle Support at 1.800.223.1711. Hearing-impaired customers in the U.S. who wish to speak to an Oracle Support representative may use a telecommunications relay service (TRS). Information about the TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of telephone numbers is available at https://www.fcc.gov/general/telecommunications-relay-services-directory. International hearing-impaired customers should use the TRS at +1.605.224.1837. An Oracle Support engineer will respond to technical issues according to the standard service request process. |
The information above describes this product's ability to support the applicableStandards/Guidelines, subject to Oracle's interpretation of those standards(available at https://www.oracle.com/corporate/accessibility/policy.html#standards-tab) and the remarks in this document. For more information regarding the accessibility status of this product or other Oracle products, see http://www.oracle.com/corporate/accessibility or contact: accessible_ww@oracle.com.
This document is provided for information purposes only and the contents hereof are subject to change without notice. Oracle Corporation does not warrant that this document is error free, nor does it provide any other warranties or conditions, whether expressed orally or implied in law, including implied warranties and conditions of merchantability or fitness for a particular purpose. Oracle Corporation specifically disclaims any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document. Oracle further makes no representation concerning the ability of assistive technologies or other products to interoperate with Oracle products. This document addresses the named product(s) only and not prerequisite products for which Oracle supplies restricted use licenses.