Skip to content
This repository has been archived by the owner on Jul 16, 2024. It is now read-only.

Commit

Permalink
Change to designing alternative text tip #297
Browse files Browse the repository at this point in the history
  • Loading branch information
@iadawn
iadawn committed Nov 19, 2015
1 parent 79fd784 commit 61a6cae
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion source/designing.html.erb.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -559,7 +559,7 @@ Consider how page information is presented in different sized viewports, such as
{:.attach_permalink}
## Provide alternative text for images

Provide text which describes the purpose of each image. Images might convey information, provide decoration, or support functionality. Alternative text is not needed for purely decorative images that don't add information to the page.
Consider how imagery, sound, or video will be accessed by users unable to perceive visual or audio content. The design should provide a way to access video or audio transcripts, captions, or audio descriptions. Imagery may be informational (for example, a chart), functional (for example, icons and image buttons), or decorative (for example, 'smiling person' photography). Communicate with writers and developers to convey those needs.

{::nomarkdown}
<%= example 'Alternative text indicates functional purpose' %>
Expand Down

1 comment on commit 61a6cae

@shawna-slh
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Tip is titled "Provide alternative text for images", but the new description talks about sound and video. Either the tip title needs to be broader, or the description should be more focused. I mildly think it is useful to make it broader, since when designing, one might need to provide links to alternatives.

So maybe do include something like "Design a way for users to access transcripts and video with audio descriptions, as needed." (Probably not include captions – since that's usually specific to a media player. For audio descriptions, sometimes there is an alternative video with them, so would need to include a link to it.)
And if broader, do we need additional For more info links, e.g., about multimedia alternatives?

The wording is too formal and convoluted for these Tips. For example, I think nowhere on the WAI website do we use "imagery". I suggest that it's not worth the extra complexity of info processing (especially for non-native speakers), and that we just use "images". I think the examples may add more complexity than they help.

"Consider how imagery, sound, or video will be accessed by users unable to perceive visual or audio content" -- we don't include this type of info in any of the other tips, afaik, so I don't think we want to do it here.
I'm not sure about "Communicate with writers and developers…"

(I won't spend time drafting specific suggested text until we decide whether this will just be images, or also other alternatives.)

Please sign in to comment.