Re: Feedback on tips for getting started

Dear Jordan,

Thank you for your suggestion. Creating advice for designers on this topic is certainly challenging, and I think your approach adds important additional information and presents the task in a more realistic light.
I have taken the liberty of rewording your suggestion slightly to avoid the first person reference (a stylistic choice in all other tips) and to tighten up the delivery a little. I hope you are comfortable with the suggested edits.

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.

This resource is a deliverable for the Education and Outreach Working Group (EOWG.) The group has reviewed and approved the suggestion as edited and will implement the change once you have agreed that your concerns have been adequately addressed. WAI relies on community participation and we greatly appreciate your contribution. Please let us know if you are satisfied or if further consideration is required on this issue.

Regards,

Kevin

——
Kevin White
W3C Web Accessibility Initiative (WAI)
e-mail: kevin@w3.org <mailto:kevin@w3.org>
about: http://www.w3.org/People/#kevin <http://www.w3.org/People/#kevin>


> On 4 Oct 2015, at 05:07, Jordan Wilson <Jordan.Wilson@theprimacy.com> wrote:
> 
> First - thanks! This is a very useful resource:
> http://www.w3.org/WAI/gettingstarted/tips/
> 
> Second - a comment on the Design tips:
> 
> I don't find this to be a useful design tip:
> Provide alternative text for images
> SHARE<http://www.w3.org/WAI/gettingstarted/tips/designing.html#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.
> 
> I believe that's a very useful content (copywriter) tip and a very useful developer tip. I've found that for designers this just gets ignored because its not part of their job role. Instead I convey it differently:
> 
> Non-text content (imagery, sound, video) need an appropriate text-alternative
> When your design includes imagery, sound or video consider how it will be conveyed to a user unable to perceive visible or audible content. Video or sounds will need a transcript, captions or audio descriptions. The design should provide a way to access those resources. Consider if your visual assets are informational (ex. important imagery, images of text or a chart) or decorative (ex. a separator or 'smiling businessperson' photography). Communicate with writers and developers to convey those needs.
> 
> _
> 
> primacy
> 
> Jordan.Wilson@theprimacy.com
> Associate Director, Creative Technology
> 860.404.3343
> connecticut / new york / boston
> 
> digitalwithpurpose
> 
>