Re: Review points for Understanding and Techniques

Re FLASH15 technique -

Example 1, last sentence - it seems the link should be "source of Using
tabindex to navigate a column structure" since it links to a fla file and
the working version is already provided by the link in the previous
sentence.

Expected results - #4 is missing. Should be "Checks #2 and #4 are true".



On Mon, Sep 27, 2010 at 2:11 PM, Michael Cooper <cooper@w3.org> wrote:

>  The Understanding and Techniques documents have all the edits in place
> that are on my radar. I would like for us to approve publication this week,
> so you should review these documents before Thursday.
>
> Once again, the URLs are:
>
>    - http://www.w3.org/WAI/GL/2010/WD-UNDERSTANDING-WCAG20-20100923/
>    - http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/
>
> You can look at anything you like for your review, but here are a few
> points I'd particularly like the group's attention on:
>
>    - Technique F39<http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/F39>was substantially updated.
>    - Technique H93<http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/H93>is new.
>    - Technique H94<http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/H94>is new.
>    - Technique FLASH37 removed and content merged into FLASH15<http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/FLASH15>
>    .
>    - I've added styling to example images in techniques, so they are now
>    centered and have an "outset" border. The technique that triggered this was
>    G175 <http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/G175>though it affects around 15 or 20 techniques. I'm no designer so want to
>    know if this looks ok as I implemented, or concrete suggestions otherwise.
>    - In the first paragraph of the intro to sufficient and advisory
>    techniques<http://www.w3.org/WAI/GL/2010/WD-UNDERSTANDING-WCAG20-20100923/intro.html#introduction-layers-techs-head>I added excerpts from the Understanding, but without the links you would
>    expect because they were examples, not content people should necessarily
>    follow in that context. Want to make sure that's ok and that the paragraph
>    reads ok. This was for issue 2834<http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=2834>
>    .
>     - Edited description for G164<http://www.w3.org/WAI/GL/2010/WD-WCAG20-TECHS-20100923/G164>but wasn't sure if that was the intended edit for issue
>    2711 <http://trace.wisc.edu/bugzilla_wcag/show_bug.cgi?id=2711>.
>    - I previously sent a question about a random todo<http://lists.w3.org/Archives/Public/w3c-wai-gl/2010JulSep/0060.html>from Ben.
>    - I previously sent a question that I don't know what the intended edit
>    is<http://lists.w3.org/Archives/Public/w3c-wai-gl/2010JulSep/0061.html>for issue 2761.
>
> The recent changes are mostly reflected in the issues found at the
> following query URL:
>
>
> http://trace.wisc.edu/bugzilla_wcag/buglist.cgi?chfieldto=2010-09-27&chfieldfrom=2010-09-20
>
> You can look through those bugs if you want to check my work more
> thoroughly. Also, the diff markup in the documents includes all changes
> (except super-minor editorial things like typo fixes) made in the last year
> and a half.
>
> If you have edits that need to be made, please send them my way ASAP, I
> can't receive a whole bunch of edits late and be able to publish in a timely
> manner. Also for this review, changes should focus on perfecting edits that
> we already have committed to do, largely in response to public comments
> we've processed. New improvements, please hold off, we can process them
> after we get this next public version posted.
>
> Michael
> --
>
> Michael Cooper
> Web Accessibility Specialist
> World Wide Web Consortium, Web Accessibility Initiative
> E-mail cooper@w3.org <cooper@w3.org>
> Information Page <http://www.w3.org/People/cooper/>
>