monorepo: add html-aria history #2185
Closed
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
Member
pkra
commented
May 20, 2024
•
pkra
commented
- add html-aria history
- remove extraneous files
- adjust links to aria-common
- consider whether or not we should move html-aria right now
… 1.1 Since this has been removed from the now renamed table, makes more sense to point to the spec
Before jumping straight into explaining what each column is, give some context first for the overall table.
removed content duplicated from aria spec
update results for `aria-required` from the html validator
html validator has updated implementation for svg. changes to this element are no longer at risk
* HTML Validator has implemented rule for `aria-multiselectable` on `select` element * HTML Validator has fixed exception to `dfn role=term` - now produces warning that `role=term` is not necessary on `dfn` element.
update the global aria-* attributes url from using the tr/wai-aria-1.1 url to instead use `data-cite=...` as with other ARIA references.
* HTML validator has implemented `placeholder`/`aria-placeholder` rule. * HTML validator has implemented updated rules for `br` role allowances. (removes at risk) * HTML validator has implemented updates role allowances for `figure` (removes at risk) * HTML validator has updated rules for `input type=radio / checkbox` removing the minor exceptions.
updated html validator results
remove instances of 'must' from non-normative section
html validator has implemented rules for `aria-rowspan` and `aria-colspan`. the associated rules are no longer at risk with 2 implementations.
adds meter role
closes #474 changes ref of section element without name from 'no corresponding role' to `role=generic`. other changes made in this PR: - remove duplicate instances of code elements from ARIA roles (mostly instances of role=generic). - clarification for section element allowed roles - role=region not recommended in general, not just if the element is named since using the role w/out naming would be useless. mention authors SHOULD NOT use role=generic on the element, per the change from no corresponding role.
the s element was remapped from generic to role=deletion in html aam. the only potential change here for conformance checkers is to signal a warning that use of the deletion role on the s element is unnecessary. this pr will close #466
* Update button and input button type allowances closes #444 closes #395 closes #298 This PR makes the allowances for button-elements (button, input type=button|image|submit|reset) more consistent with each other. Additionally, slider and gridcell are now listed under the allowed roles for these elements. the LOE to properly create the necessary UX for some of these roles when specified, especially on the `input` type buttons, is rather large _but_ possible. Any failures to not implement these properly would be caught by other WCAG rules and likely other automated checks. * add missing slider allowance for input type=image * add changelog
* add allowed role for aside element - related to, w3c/html-aria#411 but does not resolve the issue. * update change log
(In this instance, it doesn’t seem needed.)
merging with 1.5 reflections in checkers, and the fact this is an update to match HTML AAM. Update: naming prohibited changes for hgroup, address, rp hgroup, address have each been mapped to the group role, and thus no longer prohibit naming. rp is not an element that _should_ be exposed to users, and even when it is - if ruby content is not supported - then it really should not be given a name then, either.
Some aria-hidden links refer to WAI-ARIA 1.1, not 1.2. Co-authored-by: Scott O'Hara <scottaohara@users.noreply.github.com>
update some missing aria attributes for the specified roles, unrelated to the overall img role tests
closes #488 allows role=separator on elements exposed as a button. any other author requirements for appropriately setting that up / ensuring the correct information is communicated would still need to be evaluated, but separate from whether the role is allowed or not. * Addition: allow role=separator on button elements * update changelog
moves td and th elements into the correct alphabetical order in the elements table.
…ibute usage by HTML element" table (header element) (#502) Fixes typo / link for allowed implicit role --------- Co-authored-by: Scott O'Hara <scottaohara@users.noreply.github.com>
…s for "form" element (#500) Co-authored-by: Scott O'Hara <scottaohara@users.noreply.github.com>
Editorial: input type=image should match type=reset|submit The allowed roles were made consistent in an earlier PR, but the other accompanying 'not recommended' guidance was missed. closes #504 expand on the 'if possible' paragraph to call out that it'd be better for authors to use the button element instead of these legacy (though still valid) input button types.
Previous: "... if the parent list item does not ...." Corrected text: "... if the parent list element does not ..."
* Correction: add missing allowance for aria-* on meter element closes #517 adds missing allowance for any aria-* attributes applicable to the meter role.
* remove sticky column headers per style breaking * Update makeup.css don't know why the last publish failed. maybe if i remove the css instead of commenting it out? this is silly..
✅ Deploy Preview for ephemeral-daifuku-0dc7d7 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Do we actually own this document, yet? |
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.