Skip to content

Conversation

@smhigley
Copy link
Contributor

@smhigley smhigley commented Jan 26, 2023

Closes #1026

TL:DR; I believe the history of this is that it was added when the expandable listbox was proposed as an alternative to the ARIA 1.1 combobox pattern. Now that we have the updated combobox pattern, there doesn't seem to be any benefit to keeping aria-expanded supported on listbox.

I wasn't sure if the best approach was to remove the attribute entirely (as in this PR), or:

  • keep it in the table, but with "(deprecated)" after it, similar to the "(deprecated on this role in ARIA 1.2)" we have for former global attrs.
  • add a note in the listbox section about it being deprecated in ARIA 1.X
  • Related Core AAM Issue/PR: N/A
  • Related AccName Issue/PR: N/A
  • Related APG Issue/PR: N/A (expandable listbox example already removed)
  • Any other dependent changes? N/A

Implementation tracking


Preview | Diff

@smhigley smhigley added this to the ARIA 1.4 milestone Jan 26, 2023
@JAWS-test
Copy link
Contributor

I think for consistency with other removed attributes, it would be useful to explicitly state "deprecated" for aria-expanded as well

@spectranaut
Copy link
Contributor

Since this has approving reviews, and we talked about it in a meeting, I'm going to make issues on browsers and validators

@spectranaut spectranaut added the waiting for implementations Cannot be merged until there are two browser impls or one impl + impl commit label Feb 22, 2024
@spectranaut
Copy link
Contributor

spectranaut commented Apr 25, 2024

I'm trying to understand if this has browser implications, but I can't find in the spec anything that says user agents shouldn't expose aria attributes that are not list in the "supported states and properties" list. I wonder if I missing something...?

edit: nevermind, its in core-aam:
Some WAI-ARIA properties are not global, and are only supported on certain roles. If a non-global WAI-ARIA state or property is used where it is not supported, user agents SHOULD NOT map the given WAI-ARIA property to the platform accessibility API.

webkit-commit-queue pushed a commit to WebKit/WebKit that referenced this pull request Apr 27, 2024
…stbox

https://bugs.webkit.org/show_bug.cgi?id=273333
rdar://problem/127124652

Reviewed by Chris Fleizach.

aria-expanded was added as a supported attribute for the listbox ARIA role when the notion of an expandable listbox
was being explored. This is now unnecessary as combobox has become the canonical way to implement this pattern, and
thus the ARIA spec is removing listbox's support for aria-expanded.

w3c/aria#1862

* Source/WebCore/accessibility/AccessibilityNodeObject.cpp:
(WebCore::AccessibilityNodeObject::setNode): Deleted.
Drive-by fix to delete this unused function.
* Source/WebCore/accessibility/AccessibilityNodeObject.h:
* Source/WebCore/accessibility/AccessibilityObject.cpp:
(WebCore::AccessibilityObject::supportsExpanded const):
* LayoutTests/platform/mac/accessibility/aria-expanded-supported-roles-expected.txt:
* LayoutTests/platform/glib/accessibility/aria-expanded-supported-roles-expected.txt:

Canonical link: https://commits.webkit.org/278080@main
Copy link
Contributor

@WilcoFiers WilcoFiers left a comment

Choose a reason for hiding this comment

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

Instead of removing this, can it be listed as deprecated? There is nothing bad about people using this, even if there's no major benefit to it.

@spectranaut
Copy link
Contributor

Wilco's comment on the issue opened on axe: dequelabs/axe-core#4433 (comment)

@scottaohara
Copy link
Member

it's not consistently exposed now, and per the linked Webkit issue it seems support will go down.

fwiw, i'm not opposed to marking it as deprecated for 1.3 - but maybe this PR should then be the start of addressing some of the conversation of #1990 - calling out why something was deprecated / is slated for future removal.

@spectranaut
Copy link
Contributor

Discussed in https://www.w3.org/2024/05/02-aria-minutes.html#t05

The decision was to create a deprecation section in the spec, and list this attribute there.

@spectranaut
Copy link
Contributor

Further discussion of the deprecation issue: https://www.w3.org/2025/01/09-aria-minutes#5464

@spectranaut
Copy link
Contributor

@smhigley there are implementations, this just needs the conflicts resolved -- unfortunate conflicts just with prettier. I think it would be easiest if you fixed the conflicts, then we can merge?

@pkra pkra removed the waiting for implementations Cannot be merged until there are two browser impls or one impl + impl commit label Apr 2, 2025
@pkra pkra force-pushed the listbox-expanded branch from 119171b to 04fe797 Compare April 2, 2025 07:43
@pkra
Copy link
Member

pkra commented Apr 2, 2025

Rebased on main.

@netlify
Copy link

netlify bot commented Apr 2, 2025

Deploy Preview for wai-aria ready!

Name Link
🔨 Latest commit 04fe797
🔍 Latest deploy log https://app.netlify.com/sites/wai-aria/deploys/67eceac110314e0008f4df5d
😎 Deploy Preview https://deploy-preview-1862--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 merged commit 364c3a3 into main Apr 2, 2025
9 checks passed
github-actions bot added a commit that referenced this pull request Apr 2, 2025
SHA: 364c3a3
Reason: push, by spectranaut

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
pkra added a commit that referenced this pull request Sep 25, 2025
Updates roleInfo using the current manual process. Changes are due to #2076, #1662, #1945, #2581, #1931, #1991, #1862

Part of #2501

Also resolves #2234
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Revisit allowed roles for aria-expanded

9 participants