Javadoc Accessibility violations in OpenJDK development release
Pasam Soujanya1
psoujany at in.ibm.com
Thu Jun 8 07:05:42 UTC 2023
Hi,
We've generated API docs using OpenJDK17 and ran Accessibility checker on the generated docs for compliance. We see violations in the generated docs. Below are the violations see
1. aria_attribute_valid
Reason for failure: When elements are assigned a ARIA role, ARIA specifies which attributes are valid for that role. If invalid ARIA attributes are used, assistive technologies may not be able to interpret and operate the element accurately for users.
2. aria_widget_labelled
Reason for failure: Interactive UI components with certain implicit or explicit ARIA roles require an accessible name. Without proper labels or the programmatically associated name, assistive technologies may not be able to accurately present the component's name and purpose to the user. This affects the user's navigation and ability to interact with the content.
3. element_scrollable_tabbable
Reason for failure: The scrollable element <div> with non-interactive content is not tabbable.
We see same set of violations with OpenJDK dev release too. Please let us know if we can raise bugs.openjdk.org bugs.
Thanks & Regards,
Pasam Soujanya.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.openjdk.org/pipermail/javadoc-dev/attachments/20230608/5506451e/attachment-0001.htm>
More information about the javadoc-dev
mailing list