Java Tooling for IntelliJ, Eclipse
Accessibility Conformance Report published by Microsoft
Conformance by level
Reported by the vendor. WCAG Level AA is the benchmark referenced by ADA Title II, Section 508 and the European Accessibility Act; Level AAA is optional and often left unevaluated.
Level A — 30 criteria
- Supports
- 14
- Partially supports
- 4
- Does not support
- 0
- Not applicable
- 12
- Not evaluated
- 0
Level AA — 20 criteria
- Supports
- 9
- Partially supports
- 5
- Does not support
- 0
- Not applicable
- 6
- Not evaluated
- 0
Level AAA — 28 criteria
- Supports
- 0
- Partially supports
- 0
- Does not support
- 0
- Not applicable
- 0
- Not evaluated
- 28
Source: Download the original report from Microsoft (Word document). Or browse all of Microsoft's reports on Microsoft's own site.
These figures are extracted from that document. They are the vendor's own statements, not an independent assessment, and automated extraction can misread a table.
All reported criteria (78)
| Criterion | Name | Level | Conformance | Remarks from vendor |
|---|---|---|---|---|
| 1.1.1 | Non-text Content | A | Supports | |
| 1.2.1 | Audio-only and Video-only (Prerecorded) | A | Not Applicable | |
| 1.2.2 | Captions (Prerecorded) | A | Not Applicable | |
| 1.2.3 | Audio Description or Media Alternative (Prerecorded) | A | Not Applicable | |
| 1.3.1 | Info and Relationships | A | Partially Supports | - Eclipse: Sometimes text label and radio button is blurred in Eclipse dark theme, for instance, the auth method radio buttons and correspond labels in sign-in window. - Eclipse: Sometimes screen readers like NVDA can't read the focused hyperlink in UI components, such as the hyperlink in device login window. - Eclipse: Sometimes NVDA will regard message label as text editor, such as the error message label in Eclipse error dialog. This may confuse screen reader users. - Eclipse: Sometimes screen readers will read items in the dropdown list twice, such as the dynamic web module version drop list in the New Dynamic Web Project wizard. - Eclipse: Narrator could not read the subscription select status correctly in subscription selection dialog. - Eclipse: The difference of selected and unselected items in the table is not obvious in Eclipse dark theme. - Eclipse: Narrator can't read the title message in Eclipse TitleAreaDialog.- IntelliJ: JAWS can't read the search result of IntelliJ plugin marketplace once user finished the typing. - IntelliJ: JAWS can't read the first item in a sub menu automatically; it will read the item only if user switches to other item and switches back. - Eclipse: Narrator can't read the presence status of list table when navigating to corresponding items in Eclipse.- Eclipse: NVDA will read the select status of table. For instance, it will read the row number of item in web app table of web app deployment panel, but will not tell the user whether the item is currently selected. - Eclipse: Narrator will not read the "Review the items to be installed" label in Eclipse software installation panel. - Eclipse: Screen readers like NVDA will not read the search result count link in Eclipse marketplace dialog automatically; it will report the result only if users hover on the link or focus on the link by tab. - Eclipse: Screen readers like NVDA will not read the "Find" Label in Eclipse marketplace. - Eclipse: Keyboard focus is going to non-interactive text content after users search plugins in Eclipse marketplace. -Eclipse: Screen readers like NVDA can't read the information in Eclipse progress bar. -NVDA is not reading about More link in Install Details dialog- Eclipse: "Detail" label in Eclipse software install page can't be detected by screen reader nor access using keyboard TAB. - Eclipse: Screen readers like NVDA can't read the error message provided by "work with" label in Eclipse software installation page. - Eclipse: Screen readers like Narrator are reading the status of the Azure toolkit checkbox as ‘Checked’ instead of reading ‘Expanded’ or ‘Collapsed in Eclipse marketplace dialog. - Eclipse: Screen readers like Narrator can't read the title when switch to specified panel in Eclipse tool window.- IntelliJ: JAWS is not reading the result that is displayed on the interactive console window. The screen reader user could not know the execution result of a script. One way to work around this for low vision users is to copy the output to Word in which the screen reader could read the content.- Jaws is not reading the selected data present in the dropdown “Use classpath of module”- IntelliJ: In "Link A Cluster" dialog, JAWS is not notifying the user about the "Authentication Error Details" error message automatically. One way to work around this is to use "Up" arrow to move the cursor to the first character then JAWS will start reading the error message.- Eclipse: Screen reader like NVDA can't read the label "Wizards" in Project creation wizard. The label is not accessible by keyboard either.- Screen readers like Narrator are reading the status of the Azure toolkit checkbox as ‘Checked’ instead of reading ‘Expanded’ or ‘Collapsed in Your Subscriptions dialog. - On T key press in Scan/Browse mode, screen reader focus is not shifting to the table- When the focus is on "Details" menu button, Narrator is not reading anything in New HD Insights Scale Project Dialog.- On changing the tab selection, Narrator is not reading the selected tab details in New HD Insights Scale Project Dialog.- Narrator/NVDA is not reading the label for "Kind" and "Source Folder" fields in New File Wizard dialog- Narrator is reading the "Kind" drop-down as table- IntelliJ: Screen readers such as NVDA could not read the list item when navigating with an arrow. For example, in the "Select Main Class" dialog, screen readers like NVDA will read items in classes list as "blank".- IntelliJ: Screen readers might not read the status of some components; for example, the status of "Before launch" panel will not be read by screen readers.- IntelliJ: Some screen readers such as JAWS could not read the list item of combobox when navigating with an arrow, but NVDA works fine.- IntelliJ: JAWS could not read the status of the checkbox in the list, but NVDA works fine. |
| 1.3.2 | Meaningful Sequence | A | Supports | |
| 1.3.3 | Sensory Characteristics | A | Supports | |
| 1.4.1 | Use of Color | A | Partially Supports | Eclipse: Some UI dialog is not adaptive in Eclipse, for instance, the New project wizard, the wizard content is hidden in low display resolution with high scaling size. |
| 1.4.2 | Audio Control | A | Not Applicable | |
| 2.1.1 | Keyboard | A | Partially Supports | - IntelliJ: Buttons in the tool window title bar such as the sign out button of Azure Explorer are not accessible by keyboard.- IntelliJ: Radio buttons such as the auth method buttons in login dialog are not auto-selected when receiving focus by keyboard.- IntelliJ: Some components in IntelliJ dialog like HideableDecorator and the HyperlinkLabel are not accessible by keyboard.- IntelliJ: ActionButton such as the refresh button in subscription select dialog is not accessible by keyboard.- IntelliJ: Some browser buttons in IntelliJ New Project wizard are not accessible by keyboard.- Eclipse: Marketplace links such as the "Obeo Marketplace" and "Red Hat" are not accessible by keyboard in Eclipse Marketplace dialog.- Eclipse: Tooltips such as the tips for Share button in Eclipse Marketplace dialog are not accessible by keyboard.- Eclipse: Some hyperlinks such as "More info" in Eclipse marketplace dialog are not accessible by keyboard.- IntelliJ: At times, the keyboard user can not access controls. For example, in "Run/Debug configuration" window, keyboard users can not access the "Before launch" panel. One way to work around this is manually execute these tasks before running the configurations.- IntelliJ: At times, the keyboard user could not access controls. For example, in debug tool window, keyboard users could not access the following buttons: Restore Default Layout, Pin Tab, Soft wrap, Scroll to End, Print, Settings controls. These actions are helpful for debugging but not necessary.- Eclipse: At times, the tooltips are not visible on keyboard focus. For example, the text field in "Link New HDInsight Cluster" dialog. Keyboard users will not be able to know the meaning if tooltips are not visible.- IntelliJ: Action button like Insert Macros in text input of Spark run configuration is not accessible through keyboard. |
| 2.1.2 | No Keyboard Trap | A | Supports | |
| 2.1.4 | Character Key Shortcuts | A | Not Applicable | |
| 2.2.1 | Timing Adjustable | A | Not Applicable | |
| 2.2.2 | Pause, Stop, Hide | A | Supports | |
| 2.3.1 | Three Flashes or Below Threshold | A | Supports | |
| 2.4.1 | Bypass Blocks | A | Not Applicable | |
| 2.4.2 | Page Titled | A | Not Applicable | |
| 2.4.3 | Focus Order | A | Supports | |
| 2.4.4 | Link Purpose (In Context) | A | Supports | |
| 2.5.1 | Pointer Gestures | A | Not Applicable | |
| 2.5.2 | Pointer Cancellation | A | Not Applicable | |
| 2.5.3 | Label in Name | A | Supports | |
| 2.5.4 | Motion Actuation | A | Not Applicable | |
| 3.1.1 | Language of Page | A | Not Applicable | |
| 3.2.1 | On Focus | A | Supports | |
| 3.2.2 | On Input | A | Supports | |
| 3.3.1 | Error Identification | A | Supports | |
| 3.3.2 | Labels or Instructions | A | Supports | |
| 4.1.1 | Parsing | A | Supports | |
| 4.1.2 | Name, Role, Value | A | Partially Supports | Eclipse: At times, screen reader has the wrong role for UI component; for instance, description in Azure sign in dialog will be read as document. |
| 1.2.4 | Captions (Live) | AA | Not Applicable | |
| 1.2.5 | Audio Description (Prerecorded) | AA | Not Applicable | |
| 1.3.4 | Orientation | AA | Supports | |
| 1.3.5 | Identify Input Purpose | AA | Supports | |
| 1.4.3 | Contrast (Minimum) | AA | Partially Supports | - Eclipse: Color contrast ratio for message label and dialog title is less than 4.5:1 in specified color theme.- Eclipse: Color contrast ratio for title of tool window is less than 4.5:1 in specified color theme.- Eclipse: Color contrast ratio for hyperlink in Eclipse dialog is less than 4.5:1 in specified color theme.- Eclipse: Color contrast ratio for list items in tree view is less than 4.5:1 in specified color theme.- Eclipse: Color contrast ratio for error messages in Eclipse console window is less than 4.5:1 in specified color theme.- IntelliJ: Color contrast ratio for text in some buttons is less than 4.5:1 in specified color theme.- IntelliJ: The color contrast ratio for the selected text (white text on blue background) is less than 4.5:1 in specified theme.- IntelliJ: Color contrast ratio for buttons in project creation wizard is less than 4.5:1 in specified theme.- IntelliJ: At times, the color contrast fails for placeholder text. For example, the placeholder text of name field in "Create New Scala Class" dialog, the placeholder text of "Cluster name/URL" field in "Link A Cluster" dialog. The hint text is hard to see. One way to work around this is to use a High Contrast theme to avoid low color contrast.- Eclipse: At times, the color contrast is not high enough. For example, the console window after submitting an application. It is difficult to read the content. One way to work around this is to use a light theme, which has clearer fonts for error messages.- Eclipse: At times, the color contrast is low within some themes in Eclipse, such as the error dialog for sign in. |
| 1.4.4 | Resize text | AA | Partially Supports | - Eclipse: At times, controls are not visible after resizing. For example, in the "New HDInsight Scala Project" dialog, some buttons such as "Add External Class Folder" are not visible once custom scaling to 200%. One way to work around this is to use Narrator to read the button and use the keyboard to perform further action.- Eclipse: At times, some elements in the screen are not visible\truncated after zooming, for instance, some components is not visible in project creation wizard after zooming to 200% in 1280*768 display, one workaround is to use Narrator to read the component focus and perform further action.- IntelliJ: At times, some elements in the screen are not visible\truncated after zooming, for instance, some components are not visible in function run configuration after zooming to 200% in 1280*768 display. One workaround is to use Narrator to read the component focus and perform further action. |
| 1.4.5 | Images of Text | AA | Supports | |
| 1.4.10 | Reflow | AA | Supports | |
| 1.4.11 | Non-text Contrast | AA | Partially Supports | IntelliJ: Non text contrast for some icons like the file icon in local repository text field in New project wizard is lower than 3:1. |
| 1.4.12 | Text Spacing | AA | Not Applicable | |
| 1.4.13 | Content on Hover or Focus | AA | Supports | |
| 2.4.5 | Multiple Ways | AA | Not Applicable | |
| 2.4.6 | Headings and Labels | AA | Supports | |
| 2.4.7 | Focus Visible | AA | Partially Supports | - IntelliJ: Keyboard focus is not visible on list items in specified color themes such as "High Contrast".- IntelliJ: Keyboard focus is not visible on “Maven” menu item in IntelliJ new project wizard in specified theme.- IntelliJ: At times, the focused item does not show the highlighted border. For example, in "Link A cluster" dialog, the "Authentication Error Details" field will not show a highlighted border. One way to work around this is the blinking cursor will indicate the console view is currently in focus.- IntelliJ: At times, focus is not visible. For example, in "Link A Cluster" dialog, focus is not visible on "Help" control in IntelliJ theme. One way to work around this is to use High Contrast theme in which focus is visible.- IntelliJ: At times, the focus is not visible. For example, the "X" (close) button in "New Project" dialog, keyboard users will find difficulty in navigating on controls. One way to work around this is to tab once more, where the focus is visible.- IntelliJ: At times, the focus is not visible. For example, in the "Run/Debug Configuration" dialog, focus on the Close button is not visible. Keyboard users will face difficulty in knowing where the focus is pointing. One way to work around this is to tab once more, where the focus is visible.- IntelliJ: At times, the focus is not visible. For example, in the "Run/Debug Configuration" dialog, focus on before launch configuration is not visible and will be read as a list by screen readers like NVDA. |
| 3.1.2 | Language of Parts | AA | Not Applicable | |
| 3.2.3 | Consistent Navigation | AA | Supports | |
| 3.2.4 | Consistent Identification | AA | Supports | |
| 3.3.3 | Error Suggestion | AA | Supports | |
| 3.3.4 | Error Prevention (Legal, Financial, Data) | AA | Not Applicable | |
| 4.1.3 | Status Messages | AA | Partially Supports | - Eclipse: At times, the output and status of operation could not be read by the screen reader automatically, but the message could be read correctly when focus is on them with keyboard or mouse. |
| 1.2.6 | Sign Language (Prerecorded) | AAA | Not Evaluated | |
| 1.2.7 | Extended Audio Description (Prerecorded) | AAA | Not Evaluated | |
| 1.2.8 | Media Alternative (Prerecorded) | AAA | Not Evaluated | |
| 1.2.9 | Audio-only (Live) | AAA | Not Evaluated | |
| 1.3.6 | Identify Purpose | AAA | Not Evaluated | |
| 1.4.6 | Contrast (Enhanced) | AAA | Not Evaluated | |
| 1.4.7 | Low or No Background Audio | AAA | Not Evaluated | |
| 1.4.8 | Visual Presentation | AAA | Not Evaluated | |
| 1.4.9 | Images of Text (No Exception) | AAA | Not Evaluated | |
| 2.1.3 | Keyboard (No Exception) | AAA | Not Evaluated | |
| 2.2.3 | No Timing | AAA | Not Evaluated | |
| 2.2.4 | Interruptions | AAA | Not Evaluated | |
| 2.2.5 | Re-authenticating | AAA | Not Evaluated | |
| 2.2.6 | Timeouts | AAA | Not Evaluated | |
| 2.3.2 | Three Flashes | AAA | Not Evaluated | |
| 2.3.3 | Animation from Interactions | AAA | Not Evaluated | |
| 2.4.8 | Location | AAA | Not Evaluated | |
| 2.4.9 | Link Purpose (Link Only) | AAA | Not Evaluated | |
| 2.4.10 | Section Headings | AAA | Not Evaluated | |
| 2.5.5 | Target Size | AAA | Not Evaluated | |
| 2.5.6 | Concurrent Input Mechanisms | AAA | Not Evaluated | |
| 3.1.3 | Unusual Words | AAA | Not Evaluated | |
| 3.1.4 | Abbreviations | AAA | Not Evaluated | |
| 3.1.5 | Reading Level | AAA | Not Evaluated | |
| 3.1.6 | Pronunciation | AAA | Not Evaluated | |
| 3.2.5 | Change on Request | AAA | Not Evaluated | |
| 3.3.5 | Help | AAA | Not Evaluated | |
| 3.3.6 | Error Prevention (All) | AAA | Not Evaluated |
Is this your product? If this report is out of date or misrepresented, we will correct or remove it. Contact us to claim this listing.
Get told when this changes
This report is dated October 28, 2024. An ACR can be quietly replaced at any time, and the published date is the only signal a buyer gets. We will email you when this one is updated.
Double opt-in — we email you once to confirm, and send nothing until you do. One-click unsubscribe on every message. We store your address and what you are watching, nothing else. Privacy.