Make aria-relevant and ariaRelevant reflect

[sideshowbarker]

The ariaRelevant IDL attribute seems to have been intentionally commented out from the ARIAMixin interface in 646f093 — without any explanation that I could find, including not in the related issue at #1058.

But since at https://w3c.github.io/aria/#idl-reflection-attribute-values the spec says:

All ARIA attributes reflect in IDL as nullable DOMString attributes.

…and since there’s a test case included in http://wpt.live/html/dom/aria-attribute-reflection.html, and WebKit, Gecko, and Blink all pass that test — then it seems ariaRelevant needs to be included in ARIAMixin in the spec.

• "author MUST" tests: N/A
• "user agent MUST" tests: http://wpt.live/html/dom/aria-attribute-reflection.html
• Browser implementations (link to issue or commit):
  • WebKit: Already implemented to reflect
  • Gecko: Already implemented to reflect
  • Blink: Already implemented to reflect
• Does this need AT implementations?
• Related APG Issue/PR:
• MDN Issue/PR:

---

Preview | Diff

[netlify]

✅ Deploy Preview for wai-aria ready!

Name	Link
🔨 Latest commit	5b9e38d
🔍 Latest deploy log	https://app.netlify.com/sites/wai-aria/deploys/67495ecf626b3e0008abfe2a
😎 Deploy Preview	https://deploy-preview-2326--wai-aria.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[rahimabdi]

Thank you for raising this, @sideshowbarker!

In addition to the WPT test confirming reflection, I am indeed seeing ariaRelevant in the accessibility WebIDL definition files for the 3 major browsers:

• WebKit
• Gecko
• Chromium

@cookiecrook had raised a newer related issue describing the general challenges with reflecting this attribute which was why it was removed: #1267.

I'll assign this one to myself to discuss at a future ARIA WG meeting.

[spectranaut]

Discussed today's aria working group meeting during triage: https://www.w3.org/2024/09/05-aria-minutes#t02

[cookiecrook]

I am indeed seeing ariaRelevant in the accessibility WebIDL definition files for the 3 major browsers

Yes, since this reflects the current reality, let's approve it.... In the meeting this morning I suggested, "revisit after the ongoing IDL discussions resolve," (so @spectranaut added the Do Not Merge label) but since all 3 engines are already shipping it, this is okay to merge as-is, IMO.

[rahimabdi]

I think the table in Section 10.2 ARIA Attribute Correspondence also needs updating.

[spectranaut]

Hi @sideshowbarker -- thanks for this, can you update the table here too: https://w3c.github.io/aria/#accessibilityroleandproperties-correspondence

[sideshowbarker]

Hi @sideshowbarker -- thanks for this, can you update the table here too: w3c.github.io/aria#accessibilityroleandproperties-correspondence

Yep, will do tomorrow or later this week. (I’m in the midst of finishing up implementation of accessible-name computation in Ladybird. But I expect to get the last patch/PR for that pushed for review today.)

[sideshowbarker]

I think the table in Section 10.2 ARIA Attribute Correspondence also needs updating.
…
can you update the table here too: w3c.github.io/aria#accessibilityroleandproperties-correspondence

Now updated. Sorry for having taken so ridiculously long to get around to it

[spectranaut]

thanks! :)

[spectranaut]

@rahim can we get one more +1 on this, then we will land?

[rahim]

@rahim can we get one more +1 on this, then we will land?

I think you meant @rahimabdi 😄