-
Notifications
You must be signed in to change notification settings - Fork 126
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.
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
jnurthen/issue1598 #1608
Closed
Closed
jnurthen/issue1598 #1608
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
* Remove unused references from biblio.js * Use specref for references with identical entries * Change to versioned refs for Core AAM and AccName
Fixes github issue #701
* When aria-errormessage is not pertinent, authors MUST either ensure the content is not rendered or remove the aria-errormessage attribute or its value. * User agents MUST NOT expose <code>aria-errormessage</code> for an object with an <sref>aria-invalid</sref> value of <code>false</code>. Also some editorial cleanup
Addresses github issue #454.
* Add blockquote, caption, and paragraph roles
…d paragraph We have a script which automatically generates the list of roles which support name from content. It turns out that script is merely looking for the presence of listitem elements. We need to make the script more robust. In the meantime, fix the immediate problem.
There was a typo in the description of aria-live="off"; "unless the used is..." should be "unless the user is...".
…ion computation" See w3c/accname#34
…th sibling steppers (#813) * Change prose to author SHOULD from author MUST specify value for aria-valuenow. * Change aria-valuemin and aria-valuemax from required to supported properties. * Revise prose of paragraph with normative statements. * Change description to clearly state that a text field with sibling buttons outside the spinbutton is permitted. * Make related editorial change to consolidate keyboard requirements into a single paragraph. * Make other related editorial revisions for clarity.
…n rules (#792) This content was taken from the Core-AAM because it is information which is platform independent and has nothing to do with accessibility API mappings.
This reverts commit 74b311c.
updates name calculation bullet 3 to state: “the element does not support name from author” rather than “the element has no name”
Co-authored-by: Michael Cooper <cooper@w3.org> Co-authored-by: Scott O'Hara <scottaohara@users.noreply.github.com>
…me-aam-1.2 (#1514) This fixes some broken links, like the one in this section (click "Accessible Name and Description Computation"): https://www.w3.org/TR/2021/CR-wai-aria-1.2-20210302/#textalternativecomputation
oops - created a PR on main - this was meant to be on the CR branch |
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.
Preview | Diff