8000 Addition: clarify when to expose a required element as invalid by scottaohara · Pull Request #429 · w3c/html-aam · GitHub
[go: up one dir, main page]
Skip to content

Addition: clarify when to expose a required element as invalid #429

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.

Sign up for GitHub

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

Merged
scottaohara merged 10 commits into from
Oct 3, 2023
Merged

Addition: clarify when to expose a required element as invalid #429

Changes from 5 commits
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
9bb3fbb
First draft of text for required elements' state
scottaohara Jul 13, 2022
8a7aaf4
Merge branch 'gh-pages' into initial-validity-state-required-elements
scottaohara Jul 14, 2022
4e306c6
Merge branch 'gh-pages' into initial-validity-state-required-elements
scottaohara Sep 1, 2022
2b6d85b
Merge branch 'gh-pages' into initial-validity-state-required-elements
scottaohara Dec 13, 2022
ac63dda
Update index.html
scottaohara Dec 13, 2022
06aabe6
Update index.html
scottaohara Mar 8, 2023
9d09c20
break paragraph into two
scottaohara Mar 8, 2023
06db679
Merge branch 'gh-pages' into initial-validity-state-required-elements
scottaohara Mar 8, 2023
69cb62f
Merge branch 'gh-pages' int 10BC0 o initial-validity-state-required-elements
scottaohara Oct 3, 2023
29f7805
closing tag typo
scottaohara Oct 3, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4973,6 +4973,14 @@ <h3>HTML Attribute State and Property Mappings</h3>
<td class="ax"><div class="general">Use WAI-ARIA mapping</div></td>
<td class="comments">
If the element includes both the `required` attribute and the `aria-required` attribute with a valid value, User Agents MUST expose only the `required` attribute value.
<p>
If an element is <a data-cite="html/input.html#concept-input-required">required</a>, user agents MUST NOT expose the
element with an intitial invalid state (<a class="core-mapping" href="#ariaInvalidTrue">`aria-invalid="true"`</a>).
Only after a user has purposefully interacted with a required element, or attempted to submit a form and the element, or elements, do not meet
<a data-cite="html/form-control-infrastructure.html#constraint-validation">constraint validation</a> would it be expected for
these required elements to be exposed in the invalid state. Until then, user agents MUST expose the elements as
(<a class="core-mapping" href="#ariaInvalidFalse">`aria-invalid="false"`</a>).
</p>
</td>
</tr>
<tr tabindex="-1" id="att-reversed">
Expand Down
0