Oracle Accessibility Conformance Report

The product does not use CAPTCHAs.

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
• The information shown in complex images such as charts is also available in an alternative textual form (e.g. a data table)

Exceptions:

• VoiceOver reads part of dropdown element as separate element (WP-6360)

The product was tested for:

• User interface component labels are associated with the fields they are labeling.
• Headings are encoded with HTML heading tags.
• Table markup is used for marking up data tables including row and column headers and table captions/summaries where appropriate.

Exceptions:

• Time Period and Format are header level 3 elements. User can be confused and doesn't understand that these texts were assigned to following groups (WP-6356)
• Widget doesn't contain a heading level and as result, a user can't navigate by the heading menu on the page with several widgets (WP-6864)
• Non-inline configured view selector does not have a label but has a title (WP-7048)
• Broken Heading Level numbering sequence can mislead the user when working with a deeply structured document (WP-6652)

The product was tested for:

• The sequence of elements in the Document Object Model (DOM) matches a logical reading sequence

Exceptions:

• NVDA focuses on the "cancel" button instead of the "export" button. User must switch to focus mode and press tab to select the "export" button. Otherwise, the next read element will be a list of footer links (WP-6363)
• If we only compare neighbor for the most recent year in the neighbor view, the left arrow and right arrow should be hidden. Otherwise, it would be read in the screenreader and does not serve a meaningful sequence (WP-7049)

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

Exceptions:

• Left/Right arrows shape are served as the only indications for browsing old and new energy/cost usages (WP-7050)

The product was tested for:

• Information conveyed by color is available in alternative formats, such as shape, text, and font weight
• Information conveyed by color has a contrast ratio of at least 3:1

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:

• Low contrast in 'Count of therms for row YOU; Link text See your energy bill details; Who are your neighbors?' (WP-6479)
• Low contrast between the bar color and temperature value color when the temperature value happens to appear inside the bar and the bar read is estimated, and low contrast for texts on solar banner (WP-7051)
• Low contrast in dimmed 'save' button (WP-8006)
• Low contrast in dimmed 'sign in' button (WP-7970)
• Low contrast in dimmed 'send link' button (WP-7955)
• Low contrast in dimmed 'next'/'create login' buttons (WP-7950)
• Low contrast in dimmed 'reset password' button (WP-7944)

The product was tested for:

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

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 product was tested for:

• Ability to perform functions from keyboard only.

Exceptions:

• The "Show" button in the password input field is not accessible using keyboard (WP-7951)
• Redirect to energy-use-details by keyboard is not working (WP-7973)
• Unable to tab to CTA in Neighbor view in Firefox/Safari/Edge (WP-7052)
• Unable to tab to empty bars with values read (WP-7053)

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.

There are no time limits set by the content.

The product was tested for:

• There is no moving, blinking or scrolling content

The product was tested for:

• No portion of the screen flickers or flashes with a frequency between 2 Hz and 55 Hz.

The product was tested for:

• 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 product was tested for:

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

The product was tested for:

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

Exceptions:

• Instead of focus placed on the next element, focus is placed on an empty area (WP-7975)
• User can't skip input fields for inactive time period (WP-6344)
• Focusable components are not in a meaningful order when navigating (e.g., using a mouse click or a keyboard tab). The focus stays on the hidden element (WP-6354)
• System: Win10+NVDA+Firefox(52ESR)    NVDA reads link cancel button export with focus on Cancel. Reproduced in browser mode. For select Export button user should switch to focus mode and press tab. Otherwise, next read element will be list of footer links (WP-6363)
• If the number of columns are smaller, the "EXPLORE IN DETAIL" button is focused first followed by the columns. In opposite, if we have 13 columns, the columns are tabbed first followed by the CTA button (Widget content looks like a two columns content. We have focus ordering issue, when link from right column selected before link from left column. This issue does not affect meaning (If the number of columns are smaller, the "EXPLORE IN DETAIL" button is focused first followed by the columns. In opposite, if we have 13 columns, the columns are tabbed first followed by the CTA button (Focus is placed on "." after login link (WP-7979)

The product 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.

The product was tested for:

• Pages are fully inter-linked to each other
• Page contains controls that enable reaching all pages

The product was tested for:

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

Exceptions:

• Page content on one page only is not defined with semantic markup (WP-8008)
• NVDA reads one complex element as three separate elements; i.e., Green button and Download my data are read as 3 elements: "Button, Button Green Button, Button Download my data" (WP-6362)
• Non-inline configured view selector does not have a label but has a title. (Energy Costs, Energy Use, Neighbors) (WP-7048)
• Heading starts from level 4. Other widgets on the dashboard use aria-level=1 for header (WP-8142)

The product was tested for:

• Visual indication of the location of the focus.

Exceptions:

• Hidden links are given focus. VoiceOver reads a list of links related to highest energy use days instead of focusing on the "Top 5 energy use days" text. (WP-7977)
• Keyboard only and screen reader users go into content inside collapsed accordion on the Neighbor Comparison page (WP-6482)

The product was tested for:

• Properly set lang attribute for each page

• There are no passages with different languages than that of the page

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.
• On moving focus to the next/previous element -  page content is not changed.

The product was tested for:

• Changes in the value of user interface components does not result in a substantial change in the page, an additional change of keyboard focus or the spawning of a pop-up window.

Exceptions:

• User should be notified about UI changes before they click on the following buttons: "Green Button Download my data", "Cancel" and "Close" (WP-6361)

The product 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.

The product was tested for:

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

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.

Exceptions:

• Focus is not moved automatically to the field that has input errors (WP-6648)
• When an invalid date (e.g. a from date that falls after a to date) is typed into the from and to fields for range of days export, the widget auto-corrects the date field value completely changing it without adequately informing the user (WP-7854)

The product was tested for:

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

Exceptions:

• Input fields do not have instructions for what information to enter in them: Account Number and Full Name (WP-7980), Account Number and Email (WP-7952), Email & Password (WP-7954), Email & Password (WP-7971)

The product was tested for:

• Where suggestions for fixing an input error are known, they are provided to the user.

Exceptions:

• Input error is not detected on initial page load (WP-8004, WP-8005, WP-8007, WP-7959) 

The product was tested for:

• Data is checked for input errors with an opportunity for the user to correct them

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

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 role attribute.

Exceptions:

• It is possible to set focus to hidden element (WP-8053)
• VoiceOver mistakenly determines the number of items in Navigation Landmark - 1 instead of 2 (WP-6619)
• Hidden elements are available for Assitive Technologies (WP-6620)
• VoiceOver reads content of all fields under "Edit recipient details" section every time the focus is moved to one of the input fields: Name, Email, SMS or Voice Message (WP-6645)
• NVDA+Firefox specific issue. SAVE and CANCEL buttons are considered as one element therefore second button is not available for NVDA. Accessible via keyboard (WP-6650)

The application does not include specific features for accessibility.

Product documentation is in electronic format.