Re: Media Resource issue followup

Thanks Shawn! Totally trust your judgement!

Rachel Comerford | Senior Director of Content Standards and Accessibility |
T 212.576.9433

*Macmillan Learning*


On Tue, Jun 11, 2019 at 6:39 PM Shawn Henry <shawn@w3.org> wrote:

> Hi Rachel,
>
> Thanks for your input on the draft media resource!
>
> I have a couple followup comments related to the tables that are now under:
>
> https://deploy-preview-7--wai-media-guide.netlify.com/design-develop/media/planning/#standards
>
> > Rachel wrote: This is a minor design/organization comment but have you
> considered making the background color of the tables the same pale as the
> summary/page contents background? I wonder if it would make them more
> readable. The contrast is certainly helpful at the top of the page.
>
> Yes! We're planning to make the header backgrounds that pale gray instead
> of the teal.
>
> > Rachel wrote: my gut reaction is that the tables are going to be
> referenced frequently but be more useful if they contain a few words
> reminding the user what the section of WCAG covers. ie: 1.2.7 (Extended
> Audio Description - Prerecorded)
>
> I totally agree that generally including the "handle" (e.g., Extended
> Audio Description - Prerecorded) with the SC number increases usability.
>
> I took a pass at that in these tables. The results:
> * the handles are redundant with the column headers, row headers, and
> section headings
> * it significantly increased line wrapping within the cells (so much so
> that the table didn't fit on one desktop screen for me, and might cause
> horizontal scrolling on mobile or with larger fonts) and cluttered the
> tables
> * it was confusing with the parenthetical information that's in the table
> -- e.g., "(audio description *or* transcript)" and "(including auditory and
> visual content)"
>
> With those considerations, I'm thinking it's best in this one case to not
> include the handles within the tables.
> Let me know if you think differently and have other ideas for addressing
> the issues.
>
> ---
>
> > Rachel wrote: When we say accessible in this heading what are we
> defining accessible as? A, AA, or AAA? I feel as though we're starting out
> with a trick question...
>
> Accessible, that is, usable by people with disabilities! :-)
>
> In the final re-organization, we now have those checklists (e.g., "What
> does my video need to be accessible?") on the same page with the standards
> and information about A, AA, AAA:
>
> https://deploy-preview-7--wai-media-guide.netlify.com/design-develop/media/planning/#standards
>
> I'm hoping that's a comfortable approach for you. :-)
>
> Let me know if you have other ideas for addressing it.
>
> ---
>
> Thanks again for your comments. We'll have the complete draft updated for
> review later this month.
>
> Best,
> ~Shawn
>
>
>
>
>
>
>
>
>