Update aria-busy to reflect relaxed accessibility child constraints when true#2754
Open
giacomo-petri wants to merge 1 commit intomainfrom
Open
Update aria-busy to reflect relaxed accessibility child constraints when true#2754giacomo-petri wants to merge 1 commit intomainfrom
giacomo-petri wants to merge 1 commit intomainfrom
Conversation
✅ Deploy Preview for wai-aria ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
|
🚀 Deployed on https://deploy-preview-2754--wai-aria.netlify.app |
pkra
requested changes
Mar 20, 2026
| branches are modified. | ||
| If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a>accessibility children</a> during script | ||
| execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. While <code>aria-busy</code> is set to <code>true</code>, | ||
| the <rref>widget</rref> MAY temporarily contain invalid <a>accessibility children</a>. Authors MUST set <code>aria-busy</code> back to <code>false</code> once the update is complete. |
Member
There was a problem hiding this comment.
The new MUST statement seems problematic to me. It does not seem testable since "once the update is complete" is an author decision.
I think it's more important to explain what happens when authors do not do this (e.g. AT may ignore the content marked busy).
I think a note, possibly including a warning on potential WCAG failures.
Member
There was a problem hiding this comment.
In that case, I'd move the example into the note.
Contributor
There was a problem hiding this comment.
I agree that the author MUST is not testable with an automated static or generic test. However, I believe it is testable. I proposed some revisions to the wording that I believe could improve clarity and thus testability.
I think a clear, normative authoring requirement is of this nature is important.
mcking65
requested changes
Mar 26, 2026
| execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. For example, if a rendered tree grid required a set of | ||
| simultaneous updates to multiple discontiguous branches, an alternative to replacing the complete tree element with a single update would be to mark the tree busy while each of the | ||
| branches are modified. | ||
| If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a>accessibility children</a> during script |
Contributor
There was a problem hiding this comment.
Suggested change
| If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a>accessibility children</a> during script | |
| If a script needs to change multiple <a>accessibility children</a> of a rendered <rref>widget</rref>, |
| simultaneous updates to multiple discontiguous branches, an alternative to replacing the complete tree element with a single update would be to mark the tree busy while each of the | ||
| branches are modified. | ||
| If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a>accessibility children</a> during script | ||
| execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. While <code>aria-busy</code> is set to <code>true</code>, |
Contributor
There was a problem hiding this comment.
Suggested change
| execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. While <code>aria-busy</code> is set to <code>true</code>, | |
| authors MAY temporarily set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> before the first change | |
| and then set it to <code>false</code> when script execution completes. | |
| While <code>aria-busy</code> is set to <code>true</code>, |
| branches are modified. | ||
| If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a>accessibility children</a> during script | ||
| execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. While <code>aria-busy</code> is set to <code>true</code>, | ||
| the <rref>widget</rref> MAY temporarily contain invalid <a>accessibility children</a>. Authors MUST set <code>aria-busy</code> back to <code>false</code> once the update is complete. |
Contributor
There was a problem hiding this comment.
Suggested change
| the <rref>widget</rref> MAY temporarily contain invalid <a>accessibility children</a>. Authors MUST set <code>aria-busy</code> back to <code>false</code> once the update is complete. | |
| the <rref>widget</rref> MAY temporarily contain invalid <a>accessibility children</a>. | |
| Authors MUST ensure that <code>aria-busy</code> is set to <code>false</code> either when updates are complete or when error conditions prevent their completion. |
| branches are modified. | ||
| If changes to a rendered <rref>widget</rref> would create a state where the <rref>widget</rref> is modifying <a>accessibility children</a> during script | ||
| execution, authors MAY set <code>aria-busy</code> to <code>true</code> on the <rref>widget</rref> during the update process. While <code>aria-busy</code> is set to <code>true</code>, | ||
| the <rref>widget</rref> MAY temporarily contain invalid <a>accessibility children</a>. Authors MUST set <code>aria-busy</code> back to <code>false</code> once the update is complete. |
Contributor
There was a problem hiding this comment.
I agree that the author MUST is not testable with an automated static or generic test. However, I believe it is testable. I proposed some revisions to the wording that I believe could improve clarity and thus testability.
I think a clear, normative authoring requirement is of this nature is important.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 Netlify Preview:
🔄 this PR updates the following sspecs:
Closes #2737
This PR updates
aria-busycontent:aria-busyis set totrue, permitting a temporarily non-conformant accessibility child structure during the update process, as discussed in the ARIA WG meetingTest, 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.