-
Notifications
You must be signed in to change notification settings - Fork 320
2.4.6-headings-and-labels-descriptive-icons #4147
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
Changes from 14 commits
9b47bec
150f22b
ddde778
9f86757
cb6f62d
36cceff
99a9d42
c8c0d9c
047cc48
a9e2ef7
c768199
f0296bf
436e537
9f1f34b
0e3250e
a63907e
9bd0b4c
73c9310
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,6 +30,9 @@ <h2>Intent of Headings and Labels</h2> | |
<p>Labels and headings do not need to be lengthy. A word, or even a single character, | ||
may suffice if it provides an appropriate cue to finding and navigating content. | ||
</p> | ||
<p>Labels of form controls are usually text-based. In some cases, images can serve as descriptive labels without additional text. In these cases, authors should ensure that the image and its use as a label (in context) are widely understood. | ||
alastc marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
<p>Note that the same image can be interpreted differently in different contexts. However, it can still be considered descriptive if its use is commonly understood in each context. For example, when accompanying a text field, a loupe or magnifying glass icon with text alternative of "Search" is commonly interpreted as indicating the field is for entering and submitting a search query.</p> | ||
Placed on or near another image, a loupe or magnifying glass icon is commonly interpreted as a means to view a magnified version of the image (for instance, acting as a mechanism to zoom into the image, or opening a full-sized image in a new window).</p> | ||
alastc marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
<p>This Success Criterion does not require headings or labels. This Success Criterion | ||
requires that if headings or labels are provided, they be descriptive. This Success Criterion also | ||
|
@@ -93,6 +96,9 @@ <h2>Examples of Headings and Labels</h2> | |
<dt>A form asking for the name of the user</dt> | ||
<dd>A form asks for the name of the user. It consists of two input fields to ask for the first | ||
and last name. The first field is labeled <q>First name</q>, the second is labeled <q>Last name</q>.</dd> | ||
<dt>A search field labeled by a magnifying glass icon</dt> | ||
<dd>A search text input is followed by a button containing a magnifying glass icon that activates the search function. | ||
The icon has the string "search" as programmatically determinable label.</dd> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. A visible text alternative is also needed. Can we please add an according sentence? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. isn't this the whole point of this PR? clarifying that if an icon is "descriptive" enough, it doesn't need text? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That is explicity stated: "In some cases, images can serve as descriptive labels without additional text." Such an image needs a text alternative, but the author does not need to make the alternative visible, just programmatically available (which can be exposed to users in a number of ways, including visibly, through user agents and AT) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @patrickhlauke does this work? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This addition would make it seem like all instances of images directly need to have alt text, when in reality the image could have no alt text because the form field’s accname is clear enough. Eg having a search icon with alt=search next to a text field with an accname of search is not what anyone should think they need to do in this situation. To put it bluntly, this just seems to make this more complicated, and to provide the appropriate nuance, it’d submit more verbiage is necessary. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's the text input that needs an accessible name, not the icon/image used as visual label, basically. (which would cross-reference 4.1.2 and, depending how you look at it, 1.1.1) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good point, sorry I missed that. In that case, its basically only 4.1.2 that is needed not 1.1.1. |
||
</dl> | ||
|
||
</section> | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.