Oracle Accessibility Conformance Report

VPAT® Version 2.5

Name of Product:

 Oracle Permitting and Licensing 26C

Product Description:

 

Oracle Fusion Applications are a suite of web-based enterprise software business products. Oracle Permitting and Licensing 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 ACRs listed in the Dependent Products section for more information.

Report Date:

 3-Aug-2026

Contact Information:

 accessible_ww@oracle.com

Notes:

 

This ACR does not cover the following product areas:

  • The product contains an authoring tool that allows the author to design forms such as for permits or business licenses.  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.
  • The product provides Chatbot/Digital Assistants which are an alternative to the UI.
  • BI Publisher reports are intended for printing purposes only.
  • Product Documentation in PDF format.
  • The product utilizes process automation in Oracle Integration Cloud.
  • Deprecated features and transactions 

Oracle Permitting and Licensing 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, zoom, voice activation, or  large fonts mode. There are specific keystrokes for a number of operations within the application. For information on keystrokes and on accessibility in the product, review the Using Accessibility Features chapters in the Oracle Permitting and Licensing documentation.

Dependent Products


This product interacts with or is built with the other Oracle products listed in this section. Click below to view information about the accessibility of these dependent products. Products listed are the versions available at thetime of publication of this document; newer documents may be available that supersede these 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/

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.1 Level A - Yes
Level AA - Yes
Level AAA - No
Revised Section 508 standards published January 18, 2017 and corrected January 22, 2018 Yes
Web Content Accessibility Guidelines 2.0 Level A - Yes
Level AA - Yes
Level AAA - No
Web Content Accessibility Guidelines 2.2 Level A - Yes
Level AA - Yes
Level AAA - No

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.2 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.2 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) Partially 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).
  • Non-text characters have meaningful alternative text.
  • Titles for Objects and Applets are provided.
  • Controls have an associated name.
  • CAPTCHAs are not used.

Exceptions:

  • Bug 38800068 - Image on Inspection Details page does not have alternative text.
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:

  • 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 34815718 - Tab groups on Worklist not marked up as Tabs which results in the wrong number of tabs read by Screen Reader.
  • Bug 37955846 - Screen reader reads irrelevant text when focus arrives in a button on owners tab of the business license details page.
  • Bug 37955863 - When focus moves to the Owners table on the Record Details page, incorrect or unrelated information is read instead of the table content and button labels.
  • Bug 37962041 - In responsive mode the User is unable to blank out the Country value in applicant fragment.
  • Bug 37962786 - On the Parcel and Address list pages, screen reader announces “collapsed” and placeholder text even when the suggestions list for the search field is open.
  • Bug 38022824 - Screen reader is not able to focus and read incident id and district information in schedule inspection drawer of incident details page.
  • Bug 38136066 - Screen reader reads zero rows even when there is 1 row in the Calculate late fee drawer on Case.
  • Bug 38616932 - The screen reader does not read active badge and business name while reading header information on contractor details page.
  • Bug 38625311 - AI planner assignment is not announcing progress information when AI is loading in planning application detail page. 
  • Bug 38627155 - On the Contractor License Comments page, screen reader reads table and row count even when empty state message is displayed with no rows and columns are displayed.
  • Bug 38630362 - AI assignment disclaimer note is not getting read by screen reader in AI planner assignment section of the planning application detail page.
  • Bug 38679895 - On the Select billing contact drawer, screen reader reads the “Business Name” table column’s label as “Title”.
  • Bug 38679966 - When the Select Billing Contact drawer is opened on the Billing Account page, screen reader announces all the content of the billing account page before announcing the drawer content.
  • Bug 38689590 - On District type drawer, the screen reader not reading the number of items in the district type Category dropdown when revisiting the field, though it works on first interaction.
  • Bug 38811454 - While searching for property address for a permit, the screen reader starts reading the page from the top instead of reading the matching suggested addresses.
  • Bug 39194255 - Screen reader reads irrelevant text when focus moves on planner name with down arrow key on assign planner drawer.

     

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 38344121 - The screen reader reads the message banner contents first ignoring the other fields in sequence though that appears at the bottom part of the agency options page.
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.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.
1.3.5 Identify Input Purpose (Level AA) Partially Supports

The product was tested for:

  • Text fields which collect information about the user contain the appropriate autocomplete content attribute.

Exceptions:

  • Bug 36004035 - Name, Phone, and Address fields on Manage Account page does not have autocomplete content attributes.

  • Bug 37531153 - Phone field on the Request Access to Your Case page does not have autocomplete content attribute.

  • Bug 37549378 - Name, Phone, and Address fields on Register User page does not have autocomplete content attributes.

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) Partially 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.

Exceptions

  • Bug 38824100 - Text for filter chips on Project List page does not have a contrast 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.
1.4.10 Reflow (Level AA) Partially Supports

The product was tested for:

  • Text information reflows so that only one direction of scrolling is required while at 400% zoom.
  • Content that requires two-dimensional layout only presents scroll bars in the component used to present the two-dimensional content.

Exceptions:

  • Bug 37521925 - Text overlaps on the Reassign Task modal page when resized to 400%.
  • Bug 37938656 - On Business License details, the contact page is not usable when zoomed to 400%.
  • Bug 37986356 - Selecting Industrial Classification not usable when resized to 400%.
  • Bug 38157112 - On Preapplication Outcome page, the header and footer obscure the main content, rendering page unusable when resized to 400%.
  • Bug 38706567 - User cannot switch to tabs beyond languages tab, when agency details page is zoomed 400%.
  • Bug 38807909 - Parcel details content shows up on each tab making page unusable when resized to 400%.
  • Bug 38800019 - On Inspection List page, the filter chip dropdown not getting displayed when zoomed to 400%.
  • Bug 38800038 - The Inspector application page is not usable when zoomed to 400%.
  • Bug 38807902 - Business Details tab does not show any information for Business Details when resized to 400%.
  • Bug 38824124 - Project Details page shows up empty when resized to 400%.
  • Bug 39322509 - On the New Attachment drawer on the Communication Webform page, the Description field goes out of viewport when zoom is set to 400%.
1.4.11 Non-text Contrast (Level AA) Partially Supports

The product was tested for:

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

Exceptions:

  • Bug 34815740 - Worklist tab focus color has a contrast ratio less than 3:1.
1.4.12 Text Spacing (Level AA) Supports

The product 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) Supports

The product was tested for:

  • Dismissable -The content can be dismissed without moving the pointer or keyboard focus
  • Hoverable - When pointer hover triggers additional content, the pointer can be moved over the additional content without the additional content disappearing
  • Persistent - The additional content remains visible until the hover or focus trigger is removed, the user dismisses it, or its information is no longer valid
2.1.1 Keyboard (Level A) Partially Supports

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).

Exceptions:

  • Bug 33402202 - Deleting conditions on Sync Card Status not operable with the keyboard.
  • Bug 34815764 - Worklist Tab selector menu not operable with keyboard when resized to 200%.
  • Bug 34815753 - Worklist back button tab that displays all tabs not operable with the keyboard.
  • Bug 37248817 - Reference Entity hyperlink cannot be activated with keyboard on the New Reference Entity drawer page.
  • Bug 37731287 - User cannot activate the row action menu items using keyboard on the inspection list page.
  • Bug 37871227 - Menu options are not getting listed by pressing space key when run through screen reader on case list page.
  • Bug 38030290. - Case Inspections grid's action menu not operable with the keyboard.
  • Bug 38664154 - The screen reader suggests using arrow keys to move between toolbar’s Download and Personalization options while only Tab key works on Refund History page.
  • Bug 38510525 - On Contractor list page, the grid's action menu is not operable with the keyboard.
  • Bug 38804986 - Hyperlink in the License Period column cannot be activated with keyboard on the Business License Activity.
  • Bug 38850176 - Menu options are not getting listed by pressing space key when run through screen reader for inspection list on incident detail page.
  • Bug 38805896 - On a Permit’s assign reviewer drawer, the plan reviewer assignment grid is not fully traversable with keyboard.
  • Bug 38969391 - On Communication Center page user is not able to delete the filter chip in search box by pressing delete key though screen reader prompts to do so.
  • Bug 38974196 - The screen reader announces multi select check box only after second keyboard interaction on project attachments page.
  • Bug 39182785 - The action menu of the incoming tasks list is not getting activated using keyboard for the first time on planner worklist page.
  • Bug 39355242 - The action menu of the cases list is not getting activated only keyboard for the first time on code enforcement worklist page.
  • Bug 39347707 - The action menu of the inspections list is not getting activated via keyboard when accessed for the first time on code enforcement worklist page.
  • Bug 39349333 - The action menu of the incidents list is not getting activated via keyboard when accessed for the first time on code enforcement worklist page.
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.1.4 Character Key Shortcuts (Level A) Supports

The product was tested for:

  • There are no single character keyboard shortcuts.
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 automatic scrolling content that is greater than or equal to 5 seconds.
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) Partially Supports

The product was tested for:

  • Pages have a meaningful title specified in the TITLE element.

Exceptions:

  • Bug 38969780 - Browser tab name is not meaningful for the inspections page.
  • Bug 39320248 - Browser tab name is not meaningful for the worklist page.
2.4.3 Focus Order (Level A) Partially Supports

The product was tested for:

  • Logical movement through the focusable components using only the keyboard, in an order that follows a meaningful sequence.

Exceptions:

  • Bug 35926870 - Focus gets lost on the case list page after showing or hiding a column using column personalization options.
  • Bug 37530090 - After closing the drawer that allows adding or updating information, the keyboard focus moves to the top of the page instead of the element that opened the drawer, on multiple pages across the application including Plan Review, Case Details, Business License.
  • Bug 37963527 - Tab navigation skips header fields and moves focus directly to the “Go to Addresses” link on the Address Details page.
  • Bug 37974776 - While creating a case, hitting tab key after selecting the issue sub-type resets the focus to browser control instead of Continue button.
  • Bug 38470915 - Focus order is lost while creating new billing contact after City and Postal Code field values are selected.
  • Bug 38471136 - Focus order is lost while creating new billing account after City and Postal Code field values are selected.
  • Bug 38641101 - Initial focus is set to a field in the middle of the form while adding Responsible Party on the Case Notice Details page.
  • Bug 38603661 - On the Business Details page, the focus is lost on selecting a value for the fields Fiscal Year Month, City, State, and Postal Code.
  • Bug 38674750 - Focus order is lost after selecting a value from the Country/Region dropdown in the Physical or Mailing Address section on the New Owner or Corporate Officer drawer.
  • Bug 38855011 - On the Incident attachment page, the focus order is getting lost when the user tries to activate the action menu of the attachment list for the first time.
  • Bug 38923888 - On the Cashier and Reconcile cashier sessions, the Suggested Filter chips can be read by a screen reader, but keyboard focus does not move to the chips.
  • Bug 38953377 - Focus order is lost on returning from Complete Reconciliation confirmation.
  • Bug 38969562 - Focus order is lost when the user tries to navigate through the multiple applied search criteria filter chips on the Inspections page.
  • Bug 39171940 - Focus order is lost after activating the tool bar buttons such as Month, Week, Day, and List when there is no data available on planner calendar worklist page.
  • Bug 39264813 - Focus does not go to the first field when add responsible party drawer is opened on case worklist page.
  • Bug 39265017 - The focus order is lost when the user tries to activate the action menu of the responsible party list using keyboard on the  case notice details drawer of case worklist page.
  • Bug 39338669 - The focus order is getting lost when the user tries to activate the action menu of the unassigned license applications for the first time on business license worklist page.
2.4.4 Link Purpose (In Context) (Level A) Partially 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.

Exceptions:

  • Bug 35950403 - Worklist conditions dialog has an unlabeled link.
  • Bug 38582599 - On the Select Industry Classification drawer, the hyperlink in the Description column is not read as an interactive control by the screen reader.
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) Partially Supports

The product was tested for:

  • Headers describe the topic or purpose of the content below them.
  • Labels describe the purpose of the associated field.

Exceptions:

  • Bug 35950694 - Labels for Search and Actions in Worklist do not describe purpose.
  • Bug 38469989 - Labels for Account Name and Party Site Name on the Billing Accounts tab for Business License Details page do not describe purpose.
  • Bug 39320346 - On edit page layout of worklist, the screen reader wrongly announces the panel section title as undefined.
2.4.7 Focus Visible (Level AA) Partially Supports

The product was tested for:

  • Visual indication of the location of the focus.

Exceptions:

  • Bug 37938183 - In the "Apply for multiple applications drawer" on the Apply page, the Delete icon does not show a visible highlight when it receives keyboard focus.
2.4.11 Focus Not Obscured (Level AA) Partially Supports

The product was tested for:

  • The initial position of user interface components receiving keyboard focus is not hidden entirely by author-created content.

Exceptions:

  • Bug 37514587 - On Manage Accounts, when a user activates Delete, a delete confirmation dialog opens but an additional drawer also opens unexpectedly and covers the dialog.
  • Bug 37520912 - Search header stays visible at the top of the viewport on the Permits page for the public user and it is tall enough to completely cover some of the cards in focus as a user tabs up the page.
  • Bug 37952199 - On Industry Classification fragment, the footer stays visible at the bottom of the viewport, and it is tall enough to completely cover some elements in focus when tabbing down the page.
  • Bug 37530068 - On the Manage Account drawers, the footer covers some elements in focus when tabbing down the page.
  • Bug 37737667 - When using the keyboard to delete a time record, the delete confirmation pop-up opens at the same time as the Time Details drawer.
  • Bug 37952735 - On the Apply for multiple applications drawer, the rows do not scroll to the view port while scrolling using keyboard.
  • Bug 37961292 - On the Business Licenses intake, the footer covers some elements in focus when tabbing down the page.
  • Bug 38347580 - On the Business License Audit History page, the rows do not scroll to the view port while scrolling using keyboard.
  • Bug 38414872 - On the Business Audit History page, the rows do not scroll to the view port while scrolling using keyboard.
  • Bug 38603621 - On Business License Details, the footer on Business Details tab completely covers some elements in focus when tabbing down the page.
  • Bug 38639959 - On Case Inspection page, the attachments foldout panel is only partially visible when focused on initially.
  • Bug 38706503 - On the Agency Details page, few elements are obscured by the header when navigating to the top of the Agency Information section.
  • Bug 38827459 - On Business Details edit page, the footer completely covers some elements in focus when tabbing down the page.
  • Bug 38794623 - On the Communication Center tabs, the footer completely covers the rows while scrolling down using keyboard.
  • Bug 39194050 - On the planner worklist page, some column headers and values do not scroll to the view port and remains obscured on the right side of the view port while accessing through keyboard.
2.5.1 Pointer Gestures (Level A) Supports

The product was tested for:

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

The product was tested for:

  • When an operation uses a single pointer, the down-event of the pointer is not used to execute any part of the function.
  • 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.
  • When an operation uses a single pointer, the up-event reverses any outcome of the preceding down-event.
2.5.3 Label in Name (Level A) Partially Supports

The product has been tested for:

  • User interface components that include text or images of text and have a label, have a name that contains the text that is presented visually.

Exceptions:

  • Bug 36008809 - Visual label for login and account avatar is not included in the accessible name.
2.5.4 Motion Actuation (Level A) Supports

The product was tested for:

  • There are no functions that require motion of the device.
2.5.7 Dragging Movements (Level AA) Supports

The product was tested for:

  • All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging.
2.5.8 Target Size (Minimum) (Level AA) Supports

The product was tested for:

  • Interactive targets take up at least 24×24 CSS pixels of space, including white space around the target, and the space is not shared with another target.

  • The function can be achieved through a different control in the same software that meets this criterion.

  • The target is in a sentence or its size is otherwise constrained by the line-height of non-target text.

  • A particular presentation of the target is essential or is legally required for the information being conveyed.

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) Partially Supports

The product was tested for:

  • Images and controls are used and identified consistently throughout the product.

Exceptions:

  • Bug 28525590 - Implementation of tables and sorting of table columns across different transactions is not consistent.
  • Bug 30109779 - Header icons and colors are not consistent throughout the elements of the application.
3.2.6 Consistent Help (Level A) Supports

The product was tested for:

  • Help mechanisms (or a link to different software containing help mechanisms) occur in the same order relative to other software content.
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.
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.
3.3.7 Redundant Entry (Level A) Supports

The product was tested for:

  • Information previously entered by or provided to the user that is required to be entered again in the same process is auto-populated by the application.
  • Information previously entered by or provided to the user that is required to be entered again in the same process is available for the user to select.
  • Re-entering information previously entered by or provided to the user is essential.
  • Re-entering information previously entered by or provided to the user is required to ensure the security of content.
3.3.8 Accessible Authentication (Minimum) (Level AA) Supports

The product was tested for:

  • A mechanism is available to assist the user with any authentication step that utilizes a cognitive functional test.

  • The product supports password entry by password managers.

  • The product supports copy and paste while authenticating.

4.1.1 Parsing (Level A) Not Applicable This criterion is considered as always satisfied for any content using HTML or XML.
4.1.2 Name, Role, Value (Level A) Partially 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’.
  • Frames have a meaningful title specified in the title attribute.

Exceptions

  • Bug 37532155 - On the Workflow Details, process information page, the screen reader starts reading each word from the second letter instead of the first letter.
  • Bug 37732209 - Screen reader is unable to read the correct field labels for some fields on the public user setup page. It reads field labels of the prior field.
  • Bug 37870981 - Screen reader reads the applied search filter chip text multiple times on case list page.
  • Bug 37938151 - Checkboxes for row selection not read by screen reader while selecting Business License applications on Apply page.
  • Bug 37962818 - On the Parcel List page, when the suggested filter chip below the search field receives focus, its content is announced multiple times.
  • Bug 37997707 - Screen reader is not reading the field label for Legal Name and only reads its value on Business details page.
  • Bug 38138733 - On Case page, Fee summary drawer, data from the previous row is read before reading the current row’s content.
  • Bug 38165919 - Aria attributes not supported by role elements on Planning application’s Reapplication outcome page.
  • Bug 38680858 - On the Contractors list page, screen reader announces return to home link even when the link is hidden.
  • Bug 38706520 - On Agency Details page, screen reader reads the 1st row’s content again even when accessing 2nd row.
  • Bug 38706556 - On Agency Details Business license options drawer, screen reader is not reading name of the section Configure business license search.
  • Bug 38404432 - In the Billing Account's New Account drawer, turning off the “Same as Business Mailing Address” switch causes the address fields to be announced multiple times.
  • Bug 38554255 - Screen reader reads "Title" instead of "Business name" column heading on the Billing Account's billing contacts grid.
  • Bug 38689529 - On the Parcel value details page, screen reader reads the Effective Date dropdown as a single continuous row instead of announcing each row/column individually like a table.
  • Bug 38713494 - In the “View Details” drawer, screen reader announces bulleted list items as “black square” instead of properly conveying list semantics.
  • Bug 38800920 - Aria dialog element missing accessible name on Case Inspections page.
  • Bug 38807869 - Aria attributes not supported by role element for suggested filter on Business list page.
  • Bug 38923905 - Screen reader is not announcing Show and Hide sections on the grid's Customize Columns modal.
  • Bug 38969709 - On inspections page, screen reader prompts table column label twice instead of prompting the label and value when focus arrives on some columns such as Unannounced, Classification, and Preferred date.
4.1.3 Status Messages (Level AA) Partially Supports

The product was tested for:

  • Status messages have role or properties set so information is conveyed to assistive technology without the component receiving focus.

Exceptions:

  • Bug 35950726 - Worklist search results not programmatically determined.
  • Bug 37522483 - On the Report an issue page, screen reader is not announcing the secondary text for the status message while using Firefox.
  • Bug 37379665 - Search status message for number of rows and results not programmatically determined for Apply page.
  • Bug 38969415 - On Communication Center page, screen reader reads incorrect number of applied search filters.
  • Bug 39186256 - On Planner Worklist Activities page, screen reader reads incorrect number of applied search filters.
  • Bug 39189015 - The screen reader reads some irrelevant save confirmation message text after adding a comment on the  Public Comments page.
  • Bug 39189128 - When focus moves to the actionable elements in submission confirmation page, incorrect or unrelated information is read instead of the button labels.
  • Bug 39189137 - In the Submission Confirmation page, screen reader does not announce about the presence of links even though page has links.
  • Bug 39190114 - The screen reader reads some irrelevant delete confirmation message text after deleting a comment on the public comment page.
  • Bug 39198769 - The screen reader reads some irrelevant save confirmation message text after adding a fee attribute on the Global Fee Attributes page.

back to top

2018 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.

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 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 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 Supports

The product was tested for:

  • Prompts authors to create content that conforms to WCAG 2.0 AA.
504.4 Templates Not Applicable

The product does not provide templates.

back to top

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:

  • Special keystrokes needed to operate controls.

Accessibility-related documentation can be found in the Oracle Permitting and Licensing documentation in the Using Accessibility Features Chapter.

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.

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.