Skip to content
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
wants to merge 249 commits into from
Closed

jnurthen/issue1598 #1608

wants to merge 249 commits into from

Conversation

jnurthen
Copy link
Member

@jnurthen jnurthen commented Sep 1, 2021

joanmarie and others added 30 commits December 6, 2017 19:48
* Remove unused references from biblio.js
* Use specref for references with identical entries
* Change to versioned refs for Core AAM and AccName
* 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
* 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.
#785)

* Clarify whether alt attribute is valid alternative text for role="img" #783
There was a typo in the description of aria-live="off";
"unless the used is..." should be "unless the user is...".
…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.
* New Accessibility Tree section needs intro #811
Michael Cooper and others added 28 commits October 6, 2020 13:38
* focusable->focused to resolve #1381
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
@jnurthen
Copy link
Member Author

jnurthen commented Sep 1, 2021

oops - created a PR on main - this was meant to be on the CR branch

@jnurthen jnurthen closed this Sep 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.