Oracle Accessibility Conformance Report

VPAT® Version 2.0 - October 2017

Name of Product:

Oracle Public Sector Community Development (January 2019) 11.13.19.01.0

Product Description:

Oracle Fusion Applications are a suite of web-based enterprise software business products. Oracle Public Sector Community Development targets the needs of state and local officials responsible for regulating building development and business operation within their jurisdictions.The responses to many of the technical standards are based on functionality provided by underlying technologies; please see the Oracle Fusion Applications Common Dependencies VPAT listed in the Product Dependencies section for more information.

Date:

06-Feb-2019

Archive Note:

This VPAT applies to only versions 11.13.19.01.0 through 11.13.19.10.0. It does not apply to any versions of Oracle Public Sector Community Development after this. This VPAT has been superseded by Oracle Public Sector Community Development (January 2020) 11.13.20.01.0.

Contact Information:

accessible_ww@oracle.com

Notes:

This VPAT does not cover the following product areas:

The product contains an authoring tool that allows the author to design a form for permits. While the content produced from the authoring tool is accessible, the content designer itself is excluded.
The product integrates to a third party rendering tool, ESRI, to display maps.
BI Publisher reports are intended for printing purposes only.
Product Documentation in PDF format.
The product utilizes process automation in Oracle Integration Cloud.

Oracle Public Sector Community Development has a single run time mode for the user interface. The single run time mode ensures a more consistent approach to the user interface regardless of whether the user is utilizing a screen reader, keyboard, high contrast, or large fonts mode. There are specific keystrokes for a number of operations within the application. For information for keystrokes and on accessibility in the product, review Chapter 10, Using Accessibility Features in the Oracle Public Sector Community Development documentation.

Dependent Products

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.

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/Guideline	Included In Report
Web Content Accessibility Guidelines 2.0, at https://www.w3.org/TR/2008/REC-WCAG20-20081211/	Level A - Yes Level AA - Yes Level AAA - No
Section 508 as published in 2017, at https://www.Section508.gov	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 criteria without known defects or meets with equivalent facilitation.
Supports with Exceptions: 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.0 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.0 Success Criteria, they are scoped for full pages, complete processes, and accessibility-supported ways of using technology as documented in the WCAG 2.0 Conformance Requirements.

Table 1: WCAG Conformance Criteria

Criteria	Conformance Level	Remarks and Explanations
1.1.1 Non-text Content (Level A)	Supports with Exceptions	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. CAPTCHAs are not used. During testing, the following issue was discovered: Help and lock icon are not read by the assistive technology. Bug 28071894.
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)	Supports with Exceptions	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. During testing, the following issues were discovered: Column sort for a table which appears as a button is marked up in the HTML as a link. Bug 28525815. Table summaries have not been identified for data tables. Bug 28527556. Tables are not marked up correctly so that columns and headers can be read by the assistive technology. Bug 28436677, Bug 28435563, Bug 28527556, and Bug 28435457. Process monitor marked up as a button but displayed as a link. Bug 28587166.
1.3.2 Meaningful Sequence(Level A)	Supports	The product was tested for: The sequence of elements in the DOM matches a 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 include a reference to the text alternative of the graphic.
1.4.1 Use of Color(Level A)	Supports	The product was tested for: Information is not conveyed only using color.
1.4.2 Audio Control(Level A)	Not Applicable	The 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. 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	The product 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.
2.1.1 Keyboard(Level A)	Supports with Exceptions	The product 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). During testing, the following issues were discovered: Toggle buttons cannot be operated via the keyboard when using an assistive techology in conjunction with Firefox. Bug 28526002. Button bar values in Group Tasks cannot be selected when using only the keyboard, however, the tasks are individually navigable via alternative accessible means. Bug 28525844. ESRI map toolbar and buttons are not operable using the keyboard. Bug 28412539. Controls within the row of the payment cart are not operable using the keyboard. Bug 28528700. Task list on the homepage are not operable with the keyboard, however, the tasks are available via other alternative accessible transactions. Bug 28428949. Unable to sign-out of the application when using keyboard with VoiceOver. Bug 28413612. Conditions has multiple hot spots within the field which are not operable with the keyboard. Bug 28587181. Increment and Decrement buttons are not operable with the keyboard. Bug 28278296.
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.
2.2.1 Timing Adjustable(Level A)	Supports	The product was tested for: Time limits in the product can be turned off before they are encountered. Time limits in the product can be extended with at least 20 seconds warning up to 10 times. Time limits are longer than 20 hours.
2.2.2 Pause, Stop, Hide (Level A)	Supports	The product was tested for: There is no moving, blinking or scrolling content.
2.3.1 Three Flashes or Below Threshold(Level A)	Supports	The product 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.
2.4.2 Page Titled(Level A)	Supports	The product was tested for: Pages have a meaningful title specified in the TITLE element.
2.4.3 Focus Order(Level A)	Supports with Exceptions	The product was tested for: Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence. During testing, an issue was discovered where focus does not preserve a logical focus order after returning from a modal dialog. Bug 28369778.
2.4.4 Link Purpose (In Context)(Level A)	Supports	The product was tested for: The text of links and their surrounding paragraph, list,or between list, and 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 can be found using the provided "search" function Pages are fully inter-linked to each other.
2.4.6 Headings and Labels(Level AA)	Supports with Exceptions	The product was tested for: Headers describe the topic or purpose of the content below them. Labels describe the purpose of the associated field. During testing a number of issues were discovered: Button to enable and disable multiple selection of rows is not labeled appropriately. Bug 28525888. Increment and decrement buttons are not labeled to understand context for which it is utilized. Bug 28525896. Radio buttons and checkboxes do not include an additional fieldset label that help describe purpose. Bug 28300564. Label for Number of rows to show in associated table not sufficient. Bug 28525603. Label when navigating account tree not appropriate. Bug 28282856.
2.4.7 Focus Visible(Level AA)	Supports	The product was tested for: Visual indication of the location of the focus.
3.1.1 Language of Page(Level A)	Supports	The product was tested for: Properly set lang attribute for each page.
3.1.2 Language of Parts(Level AA)	Supports	The product 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.
3.2.2 On Input(Level A)	Supports	The product 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 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
3.2.3 Consistent Navigation(Level AA)	Supports	The product was tested for: There are no navigational mechanisms that are repeated.
3.2.4 Consistent Identification(Level AA)	Supports with Exceptions	The product was tested for: Images and controls are used and identified consistently throughout the product. During testing, the following issues were discovered: Labeling of the search mechanism across transactions is not consistent. Bug 28522578. Sorting of table contents across tables in different transactions is not implemented consistently. Bug 28525798. Implementation of tables across different transactions is not implemented consistently. Bug 28525590. Modals are not implemented consistently from a keyboard or an assistive technology perspective. Bug 28587781.
3.3.1 Error Identification(Level A)	Supports with Exceptions	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. During testing an issue was discovered with the search input field where the error message does not describe the error condition appropriately. Bug 28522582.
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.
3.3.3 Error Suggestion (Level AA)	Supports	The product was tested for: Where suggestions for fixing an input error are known, they are provided to the user.
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.
4.1.1 Parsing(Level A)	Supports with Exceptions	The 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. Pages validate to the HTML specification. During testing, the following issues were discovered: Heading level 2 exists without Heading level 1. Bug 28587764. Invalid ID was found in the HTML. Bug 28587771.
4.1.2 Name, Role, Value (Level A)	Supports with Exceptions	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’. Frames have a meaningful title specified in the title attribute. During testing, a number of issues were discovered: Collapse/expand buttons do not expose the state of the button to the assistive technology. Bug 28528449. Number of results in a table are not read by the assistive technology. Bug 28442406. Display only combo boxes and toggle values not read by the assistive technology. Bug 28526084. Table pagination controls difficult to understand and utilize using an assistive technology. Bug 28528553. Recommended permits not read to the user after completing questionnaire. Bug 28428677. Map View has two frames with the same title. Bug 28587195.

2017 Section 508 Report

Chapter 3: Functional Performance Criteria (FPC)

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.

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 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	Supports	The product was tested for: Does not disrupt platform accessibility features such as Sticky Keys, High Contrast and Large Fonts.
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	Supports	The product was tested for: Responds to platform settings for color, contrast, font type, font size, and focus cursor.
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	Supports	See WCAG 2.0 Section.
504.2.1 Preservation of Information Provided for Accessibility in Format Conversion	Not Applicable	The product does not include authoring tools that provide format conversions or saving content in multiple formats.
504.2.2 PDF Export	Not Applicable	The product does not provide export of PDF files.
504.3 Prompts	Not Supported	The product does not prompt authors to create accessible content. Bug 28586849.
504.4 Templates	Not Applicable	The product does not provide templates.

Chapter 6: Support Documentation and Services

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	Supports	The product documentation describes: accessibility modes, either at installation or runtime special keystrokes needed to operate controls workarounds Accessibility-related documentation can be found at Oracle Applications Cloud Using Common Features, Chapter 13 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	Support documentation is provided 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.

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.