Re: Reminder: Tue 13 Aug for comments on Media tutorial

On 8/14/2019 12:42 AM, Judy Brewer wrote:
>
> Shawn,
>
> Highlighting a few things that jumped out at me...
>
> * https://wai-media-guide.netlify.com/design-develop/media/
>
> "Sign language is not required by most policies." I think that this 
> statement is unclear, e.g., it is presented without context; and that 
> it could be easily misunderstood. I think what you may mean here is 
> that sign language may not be required in many web accessibility 
> policies. If so, then scope the statement that way. As stated, IMO it 
> could be misunderstood (depending on the country as for instance that 
> sign language is not required under the US ADA, or the CVAA."
>
> "This resource walks through" needs copyediting. Suggestion: "This 
> resource provides a walk-through..." But overall this intro sentence 
> could be stated more directly "This resource walks through 
> understanding what is needed to make media accessible" for instance 
> "This resource describes what is needed to make media accessible"
>
> Also, word missing "To *figure out what your specific audio or video 
> needs*," -- "... needs are..."
>
> "An example accessible video is on the Colors with Good Contrast page 
> <https://www.w3.org/WAI/perspective-videos/contrast/>" ... hard to 
> parse. Perhaps... "An example accessible video from the Colors with 
> Good Contrast page <https://www.w3.org/WAI/perspective-videos/contrast/>
>
> How about boxing off the "Example" on this page, to break up the long 
> run of text?
>
> * https://wai-media-guide.netlify.com/design-develop/media/planning/
>
> Description not needed: This visuals in this video only support -- 
> Typo. The visuals...
>
> Spell out acronyms like SEO the first time it's used, to be fair and 
> welcoming to diverse communities including people reading this in 
> translation.
>
> * https://wai-media-guide.netlify.com/design-develop/media/av-content/
>
> Particularly in the Audio section of this page, the guidance seems 
> very spread-out -- few words, and lots of space and scrolling to get 
> to the next interesting bits.
>
> The lower part of the page (Video) where the information density is 
> higher seems more readable.
>
> No specific comments otherwise.
>
> In general, I wish there were a way to get to the next or previous 
> page without having to scroll all the way to the end.
>
> * General
>
>   * I wasn't able to get any further in my revise tonight, but what
>     I'm seeing looks good overall.
>
s/revise/review...
>
>  *
>   * Most of the points I'm seeing are minor, and could get picked up
>     through a last copyediting pass.
>
> Good to see this coming together!
>
> - Judy
>
>
> On 8/10/2019 11:02 PM, Shawn Henry wrote:
>> Hi AG WG folks,
>>
>> Here is a reminder that we would like any comments you have on the 
>> EOWG resource "Making Audio and Video Media Accessible" by
>>     *Tuesday 13 August*
>>
>> A link to the draft and information for your review is in this GitHub 
>> issue:
>>     To AG Reviewers
>> https://github.com/w3c/wai-media-guide/issues/87
>>
>> Thanks much!
>> ~Shawn
>>
>>
>> On 7/24/2019 11:01 AM, Shawn Henry wrote:
>>> Dear Alastair, Andrew, Michael,
>>>
>>> EOWG has a new version of a resource on making "time-based media" 
>>> (as you AG folks call it :-) accessible.
>>>
>>> Draft:
>>>      Making Audio and Video Media Accessible
>>> https://wai-media-guide.netlify.com/design-develop/media/
>>>
>>> Status:
>>> * complete draft of all content ready for review (images still 
>>> drafty and in-progress)
>>> * a few open issues (e.g., 
>>> <https://github.com/w3c/wai-media-guide/issues?q=is%3Aissue+is%3Aopen+label%3A%22for+EOWG+comment%22>)
>>> * hope to go to wide-review/last call/thorough review in early 
>>> August -- *after getting review from people we expect comments from, 
>>> and addressing those*
>>>
>>> We would especially like AG to review the following information 
>>> directly related to WCAG requirements:
>>> * WCAG Standard 
>>> <https://wai-media-guide.netlify.com/design-develop/media/planning/#wcag-standard>
>>> * Checklists for Audio and Video 
>>> <https://wai-media-guide.netlify.com/design-develop/media/planning/#checklists-for-audio-and-video>
>>> * in description page 
>>> <https://wai-media-guide.netlify.com/design-develop/media/description/#checklist>
>>> * in captions page 
>>> <https://wai-media-guide.netlify.com/design-develop/media/captions/#checklist>
>>> * in transcripts page 
>>> <https://wai-media-guide.netlify.com/design-develop/media/transcripts/#checklist>
>>> * in media player page: 
>>> <https://wai-media-guide.netlify.com/design-develop/media/player/#player-accessibility-functionality>
>>> * some small sections of Accessible Audio Content and Video Content 
>>> <https://wai-media-guide.netlify.com/design-develop/media/av-content/>
>>>
>>> New GitHub issues go here: 
>>> <https://github.com/w3c/wai-media-guide/issues/new>
>>>
>>> Could heavy-commenters review this over the next week? And then AG 
>>> approve publication after we address the rest of the open comments 
>>> (early August)?
>>>
>>> Thanks much in advance for helping get this resource reviewed!
>>>
>>> ~ Shawn (editor), Sharron, Brent
>>
> -- 
> Judy Brewer
> Director, Web Accessibility Initiative
> at the World Wide Web Consortium (W3C)
> 32 Vassar St. Room 385, MIT/CSAIL
> Cambridge MA 02139 USA
> www.w3.org/WAI/

-- 
Judy Brewer
Director, Web Accessibility Initiative
at the World Wide Web Consortium (W3C)
32 Vassar St. Room 385, MIT/CSAIL
Cambridge MA 02139 USA
www.w3.org/WAI/