Skip to content

[Core-AAM] Update role=scrollbar AXAPI platform mappings #2533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

rahimabdi
Copy link
Contributor

@rahimabdi rahimabdi commented May 12, 2025

Closes w3c/core-aam#242

Update Core-AAM's role=scrollbar AXAPI mapping to use NSAccessibility scrollbar APIs where aria-controls is provided, e.g., https://developer.apple.com/documentation/appkit/nsaccessibility-swift.struct/attribute/verticalscrollbar?language=objc.

Test, Documentation and Implementation tracking

Once this PR has been reviewed and has consensus from the working group, tests should be written and issues should be opened on browsers. Add N/A and check when not applicable.

  • "author MUST" tests:
  • "user agent MUST" tests:
  • Browser implementations (link to issue or commit):
  • Does this need AT implementations? n/a
  • Related APG Issue/PR: n/a
  • MDN Issue/PR: n/a

Preview | Diff

@rahimabdi rahimabdi self-assigned this May 12, 2025
Copy link

netlify bot commented May 12, 2025

Deploy Preview for wai-aria ready!

Name Link
🔨 Latest commit 0eeeb9b
🔍 Latest deploy log https://app.netlify.com/sites/wai-aria/deploys/6821778582e996000863e48d
😎 Deploy Preview https://deploy-preview-2533--wai-aria.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@spectranaut spectranaut self-requested a review May 15, 2025 17:06
@spectranaut spectranaut moved this from All PRS to Needs Consensus/Review in ARIA Normative PR Tracking Jun 13, 2025
Copy link
Contributor

@spectranaut spectranaut left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Rahim! A couple of things.

<p>
<span class="property"
>Property: <code>NSAccessibilityVerticalScrollBarAttribute</code>: pointer to accessible node matching IDREF of author-provided <code>aria-controls</code> for an element that
represents a vertical scrollbar.</span
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey @rahimabdi, with my read of the attribute's documentation... this property is not exposed scrollbar element, but on the element that the scroll bar controls? If so then these two properties don't belong here, because they aren't properties surfaced on the scrollbar.

Or maybe we could still say something about these properties here... something like:

If aria-controls is set on this the scrollbar element and references a valid element, and the scrollbar has aria-orientation=vertical, property NSAccessibilityVerticalScrollBarAttribute should be exposed on the accessible node matching IDREF of author-provided aria-controls. If the scrollbar has aria-orientation=horizontal, property NSAccessibilityHorizontalScrollBarAttribute should be exposed on the accessible node matching IDREF of author-provided aria-controls.

<sref>aria-expanded</sref> is also a <rref>treeitem</rref> in a <rref>tree</rref> or a <rref>row</rref> in a <rref>treegrid</rref>, then it SHOULD also be the
<a>accessibility parent</a> of the content it expands and collapses. Otherwise, the element with <sref>aria-expanded</sref> SHOULD NOT be the <a>accessibility parent</a> of the content
that is expanding or collapsing. Rather, identify that relationship between the interactive element and the element being controlled using <pref>aria-controls</pref>.
</p>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this looks like formatting changes that snuck in because of prettier... :/ maybe try rebasing?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Needs Review
Development

Successfully merging this pull request may close these issues.

Should the NSAccessibility scroll-bar API be included in mapping for scrollbar role?
2 participants