- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Thu, 5 Sep 2019 10:44:17 +0200
- To: Shawn Henry <shawn@w3.org>
- Cc: wai-eo-editors <wai-eo-editors@w3.org>
Hi Shawn, Thanks for addressing my comments. Just to be clear, I think this resource is great and happy for it to get published as-is! Some more responses inline: On 04/09/2019 22:58, Eric Eggert wrote: > > > Sent from my iPad > >> On 4. Sep 2019, at 22:38, Shawn Henry <shawn@w3.org> wrote: >> >> Hi Shadi, >> >> Thank you for squeezing this in right after your vacation! >> >> Replies below >> >> On 9/3/2019 12:00 PM, Shadi Abou-Zahra via WBS Mailer wrote: >> ... >>> Comments: >>> This resource is great and has much improved since I last reviewed it! I >>> look forward to it getting published. >>> As I have not been able to review this any earlier, all my comments are >>> strictly for editor's discretion: >>> [ED-med] Intro page: "Some cannot, and prefer sign language" -> "Some are >>> more comfortable with sign language". Rationale: you explain the reading >>> aspects well in the "Captions/Subtitles" page but I feel that it is here >>> too abbreviated, and I recall some sensitivities in the community around >>> this topic. >> >> Thanks. Definitely want to avoid sensitivities. >> >> Content around it: "Many people who are Deaf can read text well. They get the audio information from transcripts or captions. Some cannot, and prefer sign language." >> >> "more comfortable" seems too wimpy. >> >> I considered: "Some people need sign language." >> >> Changed to: "Many people who are Deaf can read text well. They get the audio information from transcripts or captions. Some people prefer sign language." >> >> OK? Great! >>> [ED-med] Intro page, How to Make Audio and Video Accessible: I would prefer >>> the page links for "Planning", "Audio and Video Content", and "Media >>> Players" to be at the front of the text rather than at the end (as in the >>> next four page links later on). >> >> Early on, EOWG said that section was heavy and dense. We cut some text. Having some before and some after helps break up the density. More importantly, it helps communicate the things are different. >> >> Also, we've had this layout since June (with images since July) and there were not comments on this previously. > > Just for the record, I did remark on this, and I think the distinction between the first three and the latter four links is not clear to readers. I personally find the jump distracting. > > But I also had realized that there would be no consensus to aligning all icons to the left, and so I let it go. > >> >> I did a quick pass to see it: https://deploy-preview-111--wai-media-guide.netlify.com/design-develop/media/#how-to-make-audio-and-video-accessible >> >> Indeed, I think the usability is better as we have it. We would like readers to read those paragraphs. Whereas, the aspects in the list, readers can just go to those pages without reading the description if they don't need it. > > That is kind of an intentional decision. I guess my underlying issue is that it took me a while to realize that this section is actually an annotated table of contents. I think having the links (and only the links, not the images) at the beginning of the paragraph (especially with the mdash'es) helps me realize that this is description of the page/link. I like the images on the right for pages that are more meta or process-oriented. I think it would be just better to recognize this section as a table of contents more easily. I wonder if the section heading is also playing a role here? >>> [ED-med] Intro page, How to Make Audio and Video Accessible: I would prefer >>> the paragraph on "Media Players" to be last, so that the page links are in >>> order of the navigation. >> >> We did have Media Players last in an iteration many weeks ago, and it made the section more complex. ([new preview so you can see it](https://deploy-preview-113--wai-media-guide.netlify.com/design-develop/media/#how-to-make-audio-and-video-accessible)) >> >> done: re-ordered navigation - moved media player up and transcribing down. rationale: media player is essential for accessibility, matching order of How to Make Audio and Video Accessible <https://wai-media-guide.netlify.com/design-develop/media/#how-to-make-audio-and-video-accessible> and Checklists <https://wai-media-guide.netlify.com/design-develop/media/planning/#checklist> > > +1 I like this matching order between the navigation and this section. Now that I see it I also prefer the media player up rather than at the end. This is a key decision that needs to be made early in the process. >>> [ED-low] Captions, Introduction: image seems overly large and the text to >>> the right is in a very narrow column that is hard to read. >> >> yeah, it's just that the captions are so small! I changed settings in the player and am re-doing the image. made it smaller. Reads much better now! >>> [ED-high] Captions, Captions and Subtitles: "Captions for the same >>> language." -- same language as what? Think need to emphasize that captions >>> (for accessibility) must be in the same language as the spoken audio. >> >> Changed to: "Captions for the same language as the spoken audio" Works for me given how you addressed my next comment. >>> [ED-high] Captions, Captions and Subtitles: suggest a >>> clarification/reminder that captions are necessary for accessibility while >>> subtitles are not an accessibility accommodation (it seems kind of >>> implicit). >> >> OK. I think some people might disagree somewhat -- based on some of the other comments that we've gotten. >> >> I'm trying: "Captions are needed for accessibility, whereas subtitles in other languages are not directly an accessibility accommodation." >> >> Other ideas? Or, let's see how that flies? Works well for me. Not sure what the controversy is, though. Thanks, Shadi >> Best, >> ~Shawn >> > -- Shadi Abou-Zahra - http://www.w3.org/People/shadi/ Accessibility Strategy and Technology Specialist Web Accessibility Initiative (WAI) World Wide Web Consortium (W3C)
Received on Thursday, 5 September 2019 08:44:22 UTC