Skip to content

fix(standards): update aria-errormessage and aria-details to be idrefs #5157

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.

Sign up for GitHub

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
straker wants to merge 1 commit into
base: develop
Choose a base branch
from
+2 −2
Open

fix(standards): update aria-errormessage and aria-details to be idrefs #5157

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions lib/standards/aria-attrs.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -78,7 +78,7 @@ const ariaAttrs = {
global: true
},
'aria-details': {
type: 'idref',
type: 'idrefs',

@chutchins25 chutchins25 Jun 11, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Is there a test case for the aria-details side of this? Unlike aria-errormessage (skipped in aria-valid-attr-value + covered by its own check), aria-details flips behavior here — aria-details="a b" was a violation before and now passes if one id resolves — and I didn't see a multi-id case covering it.

prop: 'ariaDetailsElements',
allowEmpty: true,
global: true
Expand All @@ -94,7 +94,7 @@ const ariaAttrs = {
global: true
},
'aria-errormessage': {
type: 'idref',
type: 'idrefs',
prop: 'ariaErrorMessageElements',
allowEmpty: true,
global: true
Expand Down
Loading