Oracle Accessibility Conformance Report

VPAT® Version 2.3 - April 2019

Name of Product:

Oracle ADF Faces Rich Client Components VPAT (output of JDeveloper) (updated) 12.2.1.4.0

Product Description:

This ACR covers Application Development Framework (ADF) Faces Rich Client Components (tags), as output from Oracle JDeveloper 12.2.1.4.0, the Installer, and the Upgrade Assistant. It does not cover the issues when developing native mobile apps or that are built on ADF Mobile Browser framework that uses Apache MyFaces Trinidad components. For the JDeveloper user environment, refer to the Oracle JDeveloper (12.2.1.4.0) ACR. Refer to the ADF Mobile ACR for any application issues that were built on ADF Mobile Browser framework using Apache MyFaces Trinidad components and not on ADF Faces rich client components.

ADF renders accessible content to the extent listed in this ACR, when an application developer uses it according to guidance provided in the reference manual, and follows all other applicable accessibility standards and guidelines.

Date:

07-May-2021

Contact Information:

accessible_ww@oracle.com

Evaluation Methods Used:

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

Accessibility Standards/Guidelines

This report covers the degree of conformance for the following accessibility standard/guideline:

Standard/GuidelineIncluded In Report
Web Content Accessibility Guidelines 2.1Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018Yes

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 criteria without known defects or meets with equivalent facilitation.
Partially Supports
Some functionality of the product does not meet the criteria.
Does Not Support
Majority of functionality of the product does not meet the criteria.
Not Applicable
The criteria are not relevant to the product.

WCAG 2.1 Report

Table 1 also documents conformance with:

  • 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.1 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria
Conformance Level
Remarks and Explanations
1.1.1 Non-text Content (Level A)Supports

The product was tested for:

  • Images that convey information have meaningful alternative text using ALT
  • Images that are decorative are marked up using ALT=”” or CSS background images
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
  • Titles for Objects and Applets are provided
  • Controls have an associated name
  • Text summary or alternative is provided for time-based media
  • Client-side image maps specify the ALT attribute on each AREA element.

The documentation was tested for:

  • Images that convey information have meaningful alternative text using ALT
  • Images that are decorative are marked up using ALT=”” or CSS background images
  • Information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)
  • Controls have an associated name
  • Information not conveyed using time-based media
  • Non-text characters are not used or have meaningful alternative text
  • CAPTCHAs are not used
1.2.1 Audio-only and Video-only (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.2 Captions (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.3 Audio Description or Media Alternative (Prerecorded) (Level A)Not ApplicableThe product has no multimedia.
1.2.4 Captions (Live) (Level AA)Not ApplicableThe product has no multimedia.
1.2.5 Audio Description (Prerecorded) (Level AA)Not ApplicableThe product has no multimedia.
1.3.1 Info and Relationships (Level A)Partially Supports

The product was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
  • Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
  • Data tables specify SUMMARY or CAPTION
  • Layout tables use appropriate markup
  • Groups of components are marked up with their description
  • Style sheets are used only to change the layout and presentation on the screen

The documentation was tested for:

  • User interface component labels are associated with the fields they are labeling
  • Headings are encoded with HTML heading tags
  • List markup is used for marking up lists
  • Table markup is used for marking up data tables, including row and column headers and table captions/summaries where appropriate
  • Data tables specify SUMMARY or CAPTION
  • Layout tables use appropriate markup
  • Groups of components are marked up with their description
  • Style sheets are used only to change the layout and presentation on the screen

Exceptions :

    Bug 32044066 – The af:SelectOneListbox is missing a label value.

    Bug 31971977 – An af:SelectOneChoice with mode=compact is missing a label value.

1.3.2 Meaningful Sequence(Level A)Partially Supports

The product was tested for:

  • The sequence of elements in the DOM matches a logical reading sequence

Exceptions :

  • Bug 28630020 – Screen Reader is not reading the characters when navigating through keyboard on HTTP Analyzer.

The documentation was tested for:

  • HTML markup and coding of text that provides a correct and logical reading sequence
1.3.3 Sensory Characteristics(Level A)Supports

The product was tested for:

  • Instructions provided do not refer to things solely based on their sensory characteristics such as shape, size, visual location, orientation, color, or sound
  • Instructions provided which refer to graphics included a reference to the text alternative of the graphic

The documentation was tested for:

  • Instructions provided which refer to graphics include a reference to the text alternative of the graphic
1.3.4 Orientation (Level AA)Supports

The product was tested for:

  • Text is displayed in both device orientations without loss of functionality or visibility of the text.

The documentation was tested for:

  • Text displayed in both device orientations without loss of functionality or visibility of the text.
1.3.5 Identify Input Purpose (Level AA)Partially Supports

The product was tested for:

  • Inputs that define a matching purpose are properly identified
  • Framework inputs that could be set a matching purpose allow proper identification

The documentation was tested for:

  • There are no text fields that collect information about the user

Exceptions :

  • Bug  32002282 - An inputText created with secret=true does not allow the setting of an autocomplete value.
1.4.1 Use of Color(Level A)Supports

The product was tested for:

  • Information conveyed by color is available in alternative formats, such as shape, text, font weight

The documentation was tested for:

  • Information is not conveyed using color
1.4.2 Audio Control(Level A)Not ApplicableThe product has no multimedia.
1.4.3 Contrast (Minimum) (Level AA)Supports

The product was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • Other text and images of text have a contrast ratio of at least 4.5:1

The documentation was tested for:

  • Large-scale text and images of large-scale text have a contrast ratio of at least 3:1
  • All other text and images of text have a contrast ratio of at least 4.5:1
1.4.4 Resize text(Level AA)Supports

This product was tested for:

  • Text can be resized up to 200% without loss of content or functionality.

The documentation was tested for:

  • Text can be resized up to 200% without loss of content or functionality
1.4.5 Images of Text(Level AA)Supports

The product was tested for:

  • Images of text are only used when the technology can't create the desired visual presentation, the image can be customized or the particular image is essential

The documentation was tested for:

  • Images of text are not used
1.4.10 Reflow (Level AA)Partially Supports

The product was tested for:

  • applicable content does not have two dimensional scrolling at 320px width and 256px height

Exceptions :

  • Bug 30924364 - ADF application templates do not meet small screen reflow requirements.
  • Bug 30986098 - Longer calendar activity titles get cut off when the activity box is not wide enough to accommodate the user provided text.

The documentation was tested for:

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom
  • An alternative mobile user interface is not available
  • Content that requires two-dimensional layout only presents scroll bars in the component used
    to present the two-dimensional content
1.4.11 Non-text Contrast (Level AA)Partially Supports

The product was tested for:

  • applicable non-text content meets color contrast requirements

The documentation was tested for:

  • Non-text items have a contrast ratio of at least 3:1

Exceptions :

  • Bug 31043778 - Selected row and column indicators do not meet contrast requirements
  • Bug 31043753 - Column and row headers do not meet contrast requirements
  • Bug 32315276 - The af:InputColor drop down indicator does not meet contrast requirements.
  • Bug 32025490 - The af:QuickQuery drop down indicator does not meet contrast requirements.
1.4.12 Text Spacing (Level AA)Supports

The product was tested for:

  • Text spacing of line height (line spacing) can be adjusted to at least 1.5 times the font size
  • Text spacing of following paragraphs is can be adjusted to at least 2 times the font size
  • Letter spacing (tracking) can be adjusted to at least 0.12 times the font size
  • Word spacing can be adjusted to at least 0.16 times the font size

The documentation was tested for:

  • When the following attributes and no others are modified there is no loss in functionality or content:
    • Line height (line spacing) to at least 1.5 times the font size
    • Spacing following paragraphs to at least 2 times the font size
    • Letter spacing (tracking) to at least 0.12 times the font size
    • Word spacing to at least 0.16 times the font size
1.4.13 Content on Hover or Focus (Level AA)Partially Supports

The product was tested for:

  • Content on hover or focus being dismissable, hoverable, and persistent

Exceptions :

  • Bug 31301713 -  Input components popups should not be dismissed when scrolled up or down. Progress bar should have an option to dismiss the pop-up while the focus is still on the field.

The documentation was tested for:

  • There is no content that appears on hover or focus
2.1.1 Keyboard(Level A)Partially Supports

The product and documentation was tested for:

  • Ability to perform functions from the keyboard only, and without requiring specific timings for individual keystrokes
  • Proper operation of unique keystrokes and access keys, including those listed in the product documentation
  • The ability to use the product with OS keyboard aids: StickyKeys and FilterKeys (feature names may be different on different platforms)

Exceptions:

  • Bug 28573952   - Having problems using the keyboard to open and close tree nodes while using screen reader
2.1.2 No Keyboard Trap (Level A)Supports

The product was tested for:

  • Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control

The documentation was tested for:

  • Movement of focus through each control only using the keyboard, with no "keyboard trap" that prevents focus from moving away from any control
2.1.4 Character Key Shortcuts (Level A)Supports

The product and documentation was tested for:

  • keyboard shortcuts implemented using only a letter, punctuation, number, or symbol can be either turned off, remapped, or are active only on focus
2.2.1 Timing Adjustable(Level A)Supports

The product was tested for:

  • Any application timeouts can either be turned off, adjusted, extended, or have a proper exception

Note that an ADF application by default will display a session timeout warning after 60 minutes of no interaction. The warning allows 120 seconds for a response. Both the session timeout and the length the warning popup allows are  configurable for individual apps. Besides this, there are no other time sensitive content included in the product.

The documentation was tested for:

  • Time limits are not used
2.2.2 Pause, Stop, Hide (Level A)Not Applicable

There is no flashing or moving content included in the product or in the documentation.

2.3.1 Three Flashes or Below Threshold(Level A)Supports

The product and documentation was tested for:

  • No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz
2.4.1 Bypass Blocks(Level A)Supports

The product was tested for:

  • A ‘Skip to Main Content’ link is provided to skip repetitive navigation links at the top of the page.
  • Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
  • WAI-ARIA Landmark elements are used outside of repetitive navigation links

The documentation was tested for:

  • Structure and hierarchy is marked up with Header elements outside of repetitive navigation links
2.4.2 Page Titled(Level A)Partially Supports

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element

Exception:

  • Bug 28630020 – Screen Reader is not reading the characters when navigating through keyboard on HTTP Analyzer.

The documentation was tested for:

  • Pages have a meaningful title specified in the TITLE element
2.4.3 Focus Order(Level A)Supports

The product and documentation was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence
2.4.4 Link Purpose (In Context)(Level A)Supports

The product was tested for:

  • The text of links and their surrounding paragraph, list, table cell (with marked up table headers) is sufficient to describe their purpose

The documentation was tested for:

  • The text of links and their surrounding paragraph, list, or table cell (with marked up table headers) is sufficient to describe their purpose
2.4.5 Multiple Ways(Level AA)Supports

The product was tested for:

  • Pages are contained in a "site map"
  • Pages can be found using the provided "search" function
  • Pages are in a site table of contents
  • Pages are fully inter-linked to each other
  • Page contains controls that enable reaching all pages

The documentation was tested for:

  • Pages can be found using the provided "Search" function
  • Pages are fully inter-linked to each other
  • Pages contain controls that enable reaching other pages
2.4.6 Headings and Labels(Level AA)Supports

The product and documentation was tested for:

  • Headers describe the topic or purpose of the content below them
  • Labels describe the purpose of the associated field
2.4.7 Focus Visible(Level AA)Supports

The product and documentation was tested for:

  • Visual indication of the location of the focus
2.5.1 Pointer Gestures (Level A)Supports

The product was tested for:

  • Multipoint or path-based gesture actions can be completed using a different input modality

The documentation was tested for:

  • There are no multipoint or path-based gesture actions.
2.5.2 Pointer Cancellation (Level A)Supports

The product and documentation was tested for:

  • When an operation uses a single pointer, completion of the function is on the up-event, and a mechanism is available to abort the function before completion or undo the function after completion
2.5.3 Label in Name (Level A)Supports

The product was tested for:

  • assigned labels matching the visibly displayed label text

The documentation has been tested for:

  • There are no user interface components labeled with text or images of text.
2.5.4 Motion Actuation (Level A)Supports

The product and documentation was tested for:

  • functionality that can be operated by device motion or user motion can also be operated by user interface components
3.1.1 Language of Page(Level A)Supports

The product and documentation was tested for:

  • Properly set lang attribute for each page.
3.1.2 Language of Parts(Level AA)Supports

The product and documentation was tested for:

  • Proper use of lang attribute for text passages that are in a different language than that of the page
3.2.1 On Focus(Level A)Supports

The product was tested for:

  • When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window

The documentation was tested for:

  • When an element receives focus, it does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.2 On Input(Level A)Supports

The product was tested for:

  • In circumstances where changing the value of the components causes a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window, warning is given prior to the user interacting with those user-interface components

The documentation was tested for:

  • Changes in the value of user interface components does not result in a substantial change to the page, an additional change of keyboard focus, or the spawning of a pop-up window
3.2.3 Consistent Navigation(Level AA)Supports

The product and documentation was tested for:

  • Pages that are grouped together into sets with a common navigation mechanism utilize that navigation mechanism in the same fashion, with navigation elements appearing in the same relative order each time.
3.2.4 Consistent Identification(Level AA)Supports

The product and documentation was tested for:

  • Images and controls are used and identified consistently throughout the product
3.3.1 Error Identification(Level A)Supports

The product was tested for:

  • When input errors are detected, they are described to the user in text, including identifying the item where the error occurred.

The documentation was tested for:

  • The documentation does not have input fields, except for the Search field
3.3.2 Labels or Instructions (Level A)Supports

The product was tested for:

  • Labels or instructions are provided when the product requires user input

The documentation was tested for:

  • Content does not require user input
3.3.3 Error Suggestion (Level AA)Not Applicable

ADF does not provide suggestions for error correction.

The documentation was tested for:

  • Content does not require user input
3.3.4 Error Prevention (Legal, Financial, Data)(Level AA)Supports

The product was tested for:

  • Submissions can be reversed by the user
  • Data is checked for input errors with an opportunity for the user to correct them
  • Data can be reviewed, corrected, and confirmed by the user before they are finalized

The documentation was tested for:

  • The documentation does not require user input that modifies user controllable data
4.1.1 Parsing(Level A)Supports

This product was tested for:

  • Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs

The documentation was tested for:

  • Elements in HTML content have complete start and end tags, are properly nested, do not contain duplicate attributes, and have unique IDs
  • Pages validate to the HTML specification
4.1.2 Name, Role, Value (Level A)Supports

The product was tested for:

  • HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
  • Additional state information is programmatically exposed for HTML controls, such as whether a field is ‘required’.
  • Custom controls have appropriate roles specified using the role attribute
  • Custom controls have appropriate state and property information conveyed using the relevant WAI-ARIA or HTML5 attributes
  • Custom controls have a meaningful programatically exposed name
  • Frames have a meaningful title specified in the title attribute

The documentation was tested for:

  • HTML controls have a programmatically associated name, derived from the appropriate HTML elements and attributes including LABEL, TITLE, SUMMARY, CAPTION, etc.
  • Frames have a meaningful title specified in the title attribute
4.1.3 Status Messages (Level AA)Supports

The product was tested for:

  • status messages are coded to be presented to the user by assistive technologies without receiving focus

The documentation was tested for:

  • There are no status messages

back to top

2018 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

Criteria
Conformance Level
Remarks and Explanations
302.1 Without VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.2 With Limited VisionNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.3 Without Perception of ColorNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.4 Without HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.5 With Limited HearingNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.6 Without SpeechNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.7 With Limited ManipulationNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.8 With Limited Reach and StrengthNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.
302.9 With Limited Language, Cognitive, and Learning AbilitiesNot ApplicableThe product does not rely on equivalent functionality, and all aspects are addressed by the technical standards.

back to top

Chapter 4: Hardware

These criteria are all Not Applicable because the product is not Hardware

Chapter 5: Software

Criteria
Conformance Level
Remarks and Explanations
501.1 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
 502 Interoperability with Assistive TechnologyHeading cell - no response requiredHeading cell - no response required
502.2.1 User Control of Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.2.2 No Disruption of Accessibility FeaturesNot ApplicableThe product is designed to be isolated from the underlying platform.
 502.3 Accessibility ServicesHeading cell - no response requiredHeading cell - no response required
502.3.1 Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.2 Modification of Object InformationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.3 Row, Column, and HeadersNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.4 ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.5 Modification of ValuesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.6 Label RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.7 Hierarchical RelationshipsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.8 TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.9 Modification of TextNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.10 List of ActionsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.11 Actions on ObjectsNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.12 Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.13 Modification of Focus CursorNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.3.14 Event NotificationNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
502.4 Platform Accessibility FeaturesNot ApplicableThe product is not a platform or does not have access to platform accessibility features.
 503 ApplicationsHeading cell - no response requiredHeading cell - no response required
503.2 User PreferencesNot ApplicableThe product is designed to be isolated from the underlying platform.
503.3 Alternative User InterfacesNot ApplicableThe product does not have assistive technology features.
 503.4 User Controls for Captions and Audio DescriptionHeading cell - no response requiredHeading cell - no response required
503.4.1 Caption ControlsNot ApplicableThe product has no multimedia.
503.4.2 Audio Description ControlsNot ApplicableThe product has no multimedia.
 504 Authoring ToolsHeading cell - no response requiredHeading cell - no response required
504.2 Content Creation or EditingSupports

See the responses in the WCAG 2.1 section of this report.

504.2.1 Preservation of Information Provided for Accessibility in Format ConversionNot Applicable

Product does not perform format conversion

504.2.2 PDF ExportNot Applicable

Product does not export PDF files

504.3 PromptsSupports

Oracle JDeveloper provides Audit Rules functionality that provides users feedback on content to conform to Accessibility requirements.

504.4 TemplatesNot Supported

BUG 26193542 Product does not provide templates

back to top

Chapter 6: Support Documentation and Services

Criteria
Conformance Level
Remarks and Explanations
 602 Support DocumentationHeading cell - no response requiredHeading cell - no response required
602.2 Accessibility and Compatibility FeaturesSupports

ADF renders accessible content, when an application developer uses it according to guidance provided in the reference manual, and follows all other applicable accessibility standards and guidelines.

The ADF accessibility information is provided in the Oracle Fusion Middleware Accessibility Guide in the Accessibility Features and Tips for Oracle JDeveloper and Oracle ADF chapter.

602.3 Scope - Incorporation of WCAG 2.0 AASupportsSee the responses in the WCAG 2.0 section of this report.
602.4 Alternate Formats for Non-Electronic Support DocumentationNot Applicable

Product documentation is in electronic format.

 603 Support ServicesHeading cell - no response requiredHeading cell - no response required
603.2 Information on Accessibility and Compatibility FeaturesSupportsOracle Global Customer Support can provide information about accessibility features of the product.
603.3 Accommodation of Communication NeedsSupportsOracle 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.

back to top

Oracle Legal Disclaimer

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.