update / expand input value mappings #396

scottaohara · 2022-04-15T14:24:24Z

This PR closes #314 and clarifies the value attribute mappings for other input types.
note: the value attribute only represents the initial value for the input elements that expose the attribute's value. If a user updates a form control the value attribute's value does not mutate to reflect the updated entry. The updates I provided for these inputs attempts to specifically call this out. if this is not clear, please suggest alternate wording.

Note that the input type=color value is far more complex than the other inputs and I would appreciate specific feedback on what would need to be updated here, if anything.

Additionally, the input type=color seems to make a strong case for allowing aria-valuetext on a button element – where the button should be named via a label or an aria-label/labelledby, but still needs to expose it's displayed value (subtree of the button element).

NOTE: due to the still broken table/details/summary script with respec, to view the updated table in the preview, you can add this style via devtools:

#html-attribute-state-and-property-mappings .table-container {
  display: block !important;
}

or find the .table-container that has the display: none on it, and turn that off.

fun...

Preview | Diff

This PR closes #314 and clarifies the `value` attribute mappings for other input types. note: the `value` attribute only represents *the initial value* for the input elements that expose the attribute's value. If a user updates a form control the `value` attribute's value does not mutate to reflect the updated entry. The updates I provided for these inputs attempts to specifically call this out. if this is not clear, please suggest alternate wording. Note that the `input type=color` `value` is far more complex than the other inputs and I would appreciate specific feedback on what would need to be updated here, if anything. Additionally, the `input type=color` seems to make a strong case for allowing `aria-valuetext` on a `button` element – where the button should be named via a `label` or an `aria-label/labelledby`, but still needs to expose it's displayed value (subtree of the button element).

spectranaut

Still trying to catch up and get all the context for this change, i have a few questions to start!

index.html

spectranaut · 2022-04-22T19:44:19Z

index.html

+              <td class="atk">See comments</td>
+              <td class="ax">See comments</td>
+              <td class="comments">
+                If specified, expose the value of the attribute as the initial value entry of the `input` element.


Specifically, what is the "value entry of the input element"?

Do we have the following specified somewhere: if, in one of these inputs, a user has entered text, how that text surfaced in the different accessibility APIs? If so we should link to it if not we should add it?

As we discussed, let's use the same language here as in the HTML spec: https://html.spec.whatwg.org/multipage/input.html#attr-input-value

which I think would be (but check my work):

If specified, expose the content value attribute as the default value entry of the `input` element.

Can we not say what these mappings are though? Do we know how the accessibility API for the different platforms surface the value of a input [type="email"] etc? Like AXValue for Mac?

spectranaut · 2022-04-22T19:55:02Z

index.html

+              <td class="ax">Use WAI-ARIA mapping</td>
+              <td class="comments">
+                <p>
+                  If specified, expose the value of the attribute as the initial value of the `input`. User Agents MUST expose the modified value of the input to the <a class="termref">accessibility tree</a>. User Agents MAY expose the initial or modified value as a human readable text alternative. E.g., `#ff0000` as a localized text alternative of "Red".


Do these user agents MUSTs apply to the other inputs as well?

After discussing, I think we agreed that "If specified, expose the value of the attribute as the initial value of the input. User Agents MUST expose the modified value of the input to the accessibility tree." belongs in it's own section about all inputs that have attributes (like value or checked) who's default value is set by the content attribute. See the spec: https://html.spec.whatwg.org/multipage/input.html#attr-input-value

This can happen here or in a follow up.

spectranaut

From our conversation!

spectranaut · 2022-04-27T20:40:57Z

index.html

+              <td class="atk">See comments</td>
+              <td class="ax">See comments</td>
+              <td class="comments">
+                If specified, expose the value of the attribute as the initial value entry of the `input` element.


As we discussed, let's use the same language here as in the HTML spec: https://html.spec.whatwg.org/multipage/input.html#attr-input-value

which I think would be (but check my work):

If specified, expose the content value attribute as the default value entry of the `input` element.

spectranaut · 2022-04-27T20:51:58Z

index.html

+              <td class="ax">Use WAI-ARIA mapping</td>
+              <td class="comments">
+                <p>
+                  If specified, expose the value of the attribute as the initial value of the `input`. User Agents MUST expose the modified value of the input to the <a class="termref">accessibility tree</a>. User Agents MAY expose the initial or modified value as a human readable text alternative. E.g., `#ff0000` as a localized text alternative of "Red".


After discussing, I think we agreed that "If specified, expose the value of the attribute as the initial value of the input. User Agents MUST expose the modified value of the input to the accessibility tree." belongs in it's own section about all inputs that have attributes (like value or checked) who's default value is set by the content attribute. See the spec: https://html.spec.whatwg.org/multipage/input.html#attr-input-value

This can happen here or in a follow up.

spectranaut · 2022-04-27T21:04:39Z

index.html

+              <td class="atk">See comments</td>
+              <td class="ax">See comments</td>
+              <td class="comments">
+                If specified, expose the value of the attribute as the initial value entry of the `input` element.


Can we not say what these mappings are though? Do we know how the accessibility API for the different platforms surface the value of a input [type="email"] etc? Like AXValue for Mac?

cookiecrook · 2022-04-27T21:03:03Z

index.html

+                  Either contributes to the <a data-cite="accname-1.2/#dfn-accessible-name">accessible name</a>, the
+                  <a data-cite="accname-1.2/#dfn-accessible-description">accessible description</a>, or is not mapped (see comments).


Editorial: I think this is phrased ambiguously:

Intention: "either it's:

mapped (to name or description) or

not mapped."

As phrased with the 3-part serial comma: "either it's mapped to:

name,

description, or

not mapped" (seems like ~"mapped to not mapped")

Substantive: I think there are scenarios where implementations may still wish to map it even if it's not used by name or description. Leaving that follow-on mapping optional before the final "is not mapped."

For example, I think once aria-description is implemented, browsers would still want to expose the title here as AXHelp in AX API.

<button aria-label="foo" aria-description="bar" title="bop">bif</button>

rahimabdi · 2024-09-19T23:49:27Z

@scottaohara I tried to migrate this one but it is indeed complex; it looks like there are several changes that have already been made in spec (e.g., specifying reset, button for type) so parts of this PR may no longer be needed. The spec formatting has also changed since 2022 so I was unsure if you wanted to keep what we currently have in spec (e.g., input type=reset, type=submit as separate items) vs. this original PR where all of these would be contained in a single table.

If it's OK, I'll leave this one to you to determine what actually needs to be migrated to the mono repo.

this covers some editorial fixes that were originally part of w3c/html-aam#396 - but don't need to be.

replacement for w3c/html-aam#396 closes w3c/html-aam#314

scottaohara · 2024-11-08T22:51:12Z

migrated to w3c/aria#2373. closing this pr

jnurthen requested review from spectranaut and cookiecrook April 21, 2022 17:21

spectranaut reviewed Apr 22, 2022

View reviewed changes

scottaohara mentioned this pull request Apr 27, 2022

Attributes that do not reflect updates from users #397

Open

spectranaut requested changes Apr 27, 2022

View reviewed changes

cookiecrook requested changes Apr 27, 2022

View reviewed changes

scottaohara mentioned this pull request Apr 28, 2022

[popup] Consider renaming initiallyopen openui/open-ui#500

Closed

scottaohara added 2 commits July 8, 2022 17:11

Merge branch 'gh-pages' into issue_314

bb58b78

Merge branch 'gh-pages' into issue_314

0e75d89

pkra mentioned this pull request May 28, 2024

[Monorepo] PR "move" and wrapping up #549

Open

21 tasks

scottaohara added a commit to w3c/aria that referenced this pull request Nov 8, 2024

Editorial: minor text updates to html aam

a35f33d

this covers some editorial fixes that were originally part of w3c/html-aam#396 - but don't need to be.

This was referenced Nov 8, 2024

Editorial: minor text updates to html aam w3c/aria#2372

Merged

Account for title attribute and other aria-* description attributes #569

Open

scottaohara added a commit to w3c/aria that referenced this pull request Nov 8, 2024

Update: clarify / expand value attribute mappings

3af3bae

replacement for w3c/html-aam#396 closes w3c/html-aam#314

scottaohara mentioned this pull request Nov 8, 2024

Update: clarify / expand value attribute mappings w3c/aria#2373

Open

scottaohara closed this Nov 8, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

update / expand input value mappings #396

update / expand input value mappings #396

scottaohara commented Apr 15, 2022 •

edited by pr-preview bot

Loading

spectranaut left a comment

spectranaut Apr 22, 2022

spectranaut Apr 27, 2022

spectranaut Apr 27, 2022

spectranaut Apr 22, 2022

spectranaut Apr 27, 2022

spectranaut left a comment

spectranaut Apr 27, 2022

spectranaut Apr 27, 2022

spectranaut Apr 27, 2022

cookiecrook Apr 27, 2022

cookiecrook Apr 27, 2022 •

edited

Loading

rahimabdi commented Sep 19, 2024

scottaohara commented Nov 8, 2024

		Either contributes to the <a data-cite="accname-1.2/#dfn-accessible-name">accessible name</a>, the
		<a data-cite="accname-1.2/#dfn-accessible-description">accessible description</a>, or is not mapped (see comments).

update / expand input value mappings #396

update / expand input value mappings #396

Conversation

scottaohara commented Apr 15, 2022 • edited by pr-preview bot Loading

spectranaut left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

spectranaut left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

cookiecrook Apr 27, 2022 • edited Loading

Choose a reason for hiding this comment

rahimabdi commented Sep 19, 2024

scottaohara commented Nov 8, 2024

scottaohara commented Apr 15, 2022 •

edited by pr-preview bot

Loading

cookiecrook Apr 27, 2022 •

edited

Loading