Explicitly state requirements in 3rd column of conformance table #436
Conversation
This file contains 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
sideshowbarker
force-pushed
the
sideshowbarker/3rd-column-conformance-table-be-explicit
branch
2 times, most recently
from
6ecddfe
to
8480106
Compare
|
sideshowbarker marked as non substantive for IPR from ash-nazg. |
For all elements that have implicit roles, this change makes the third column of the “Rules of ARIA attribute usage by HTML element” table explicitly state which role values are not recommended or should not be used — that is, the change makes that column explicitly state, for example, “No role other than presentation, which is NOT RECOMMENDED”, or “Any role, though figure is NOT RECOMMENDED”, or “img is also allowed, but NOT RECOMMENDED”.
sideshowbarker
force-pushed
the
sideshowbarker/3rd-column-conformance-table-be-explicit
branch
from
8480106
to
1ce2245
Compare
stevefaulkner
approved these changes
Nov 4, 2022
stevefaulkner
deleted the
sideshowbarker/3rd-column-conformance-table-be-explicit
branch
|
thanks @sideshowbarker unfortunately, i was in the middle of working on fixing exactly this per the validator issue where this topic had come up. But this is a good stop gap until I finish the updates I was doing. |
scottaohara
added a commit
that referenced
this pull request
Nov 4, 2022
related to validator/validator#1425 and #436 cc @stevefaulkner @sideshowbarker as per my comment in #436, here is part of the update I had planned to do to help address this. it is also related to #358, but does NOT close that issue completely. I'm leaving in place the updates that Mike made in the merged PR, but likely will need to revise that column later on as well, so those specific call outs may be moved or changed in the future. Any further changes we would like to see to this text to help here?
pkra
pushed a commit
to w3c/aria
that referenced
this pull request
May 20, 2024
related to validator/validator#1425 and w3c/html-aria#436 cc @stevefaulkner @sideshowbarker as per my comment in #436, here is part of the update I had planned to do to help address this. it is also related to w3c/html-aria#358, but does NOT close that issue completely. I'm leaving in place the updates that Mike made in the merged PR, but likely will need to revise that column later on as well, so those specific call outs may be moved or changed in the future. Any further changes we would like to see to this text to help here?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For all elements that have implicit roles, this change makes the third column of the “Rules of ARIA attribute usage by HTML element” table explicitly state which role values are not recommended or should not be used — that is, the change makes that column explicitly state, for example, “No role other than
presentation, which is NOT RECOMMENDED”, or “Any role, thoughfigureis NOT RECOMMENDED, or “imgis also allowed, but NOT RECOMMENDED”.💥 Error: 504 Gateway Timeout 💥
PR Preview failed to build. (Last tried on Nov 4, 2022, 8:38 AM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.