On Sat, 25 Apr 2026 06:55:18 GMT, Jeremy Wood <[email protected]> wrote:
>> On Mac OS: a "heading" has a special semantic meaning for assistive >> technologies. It is a more accurate/useful role than "header" (which is a >> Java construct and doesn't directly map to a Mac OS feature) >> >> --------- >> - [x] I confirm that I make this contribution in accordance with the >> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai). > > Jeremy Wood has updated the pull request with a new target base due to a > merge or a rebase. The incremental webrev excludes the unrelated changes > brought in by the merge/rebase. The pull request contains five additional > commits since the last revision: > > - 8379953: use NSAccessibilityHeadingRole for "header" > - 8379953: use NSAccessibilityHeadingRole for "header" > - 8379953: reverting previous fix > - Merge branch 'master' into 8379953 > - 8377938: use NSAccessibilityHeadingRole for AccessibleRole.HEADER > > On Mac OS: a "heading" has a special semantic meaning for assistive > technologies. It is a more accurate/useful role than "header" (which is a > Java construct and doesn't directly map to a Mac OS feature) Using JavaAccessibilityUtilities is not recommended - it is a fallback place for a11y peers not properly implemented using the new API. The property based API is being deprecated and would go away at some point (Apple loves doing it suddenly) so unless you have a real issue not being able to implement native peer using the new API you need to do it properly as you did with the hyperlink implementation. ------------- PR Comment: https://git.openjdk.org/jdk/pull/30251#issuecomment-4321677253
