Re: Not for Last Call Specifically But Comment on Summaries

One of the original goals of the summaries was to clarify for the reader the relationships between different success criteria, which might be very different but similarly worded, or may actually build on each other other despite being separated in the document because of their different priority levels. That's why they were not sorted numerically, but by topic.

The full explanation can be found at http://lists.w3.org/Archives/Public/w3c-wai-ua/2010OctDec/0007.html.

For example, from the original samples:

    Upshot: Let users see at a glance which pieces of content have alternatives like alt text or longdesc (3.1.1) and click on an item to see its available alternatives (3.3.3); they can choose at least one alternative like alt text to be always displayed (3.1.2), but it's recommended that they also be able to specify a cascade, like alt text if it's there, otherwise longdesc, otherwise, filename, etc. (3.1.4)


However, we have drifted away from the original goals to some extent as the summaries have been revised over time, adopting passive voice, technical terms, more detail, and so forth. In my opinion that greatly reduces their value and undercuts their reason for being.

     Greg

-------- Original Message --------
Subject: Not for Last Call Specifically But Comment on Summaries
From: Kelly Ford <Kelly.Ford@microsoft.com>
To: 'UAWG list' (w3c-wai-ua@w3.org) <w3c-wai-ua@w3.org>
Date: 9/11/2013 10:59 AM
>
> Hi,
>
> Looking at this summary, I'm prompted to ask what are reasoning is for having these items referenced in non-numeric order?  I'm sure we have thought on this but when I read it, I'm left wondering if I missed something because I have to jump around on my thinking of the numbers.  I recognize we are not listing all numbers here and that this is just a summary.
>
> I assuredly don't want to propose more work but would say we just might want to think about this a bit further outside the last call completion work.  I think the content itself is good.
>
> Summary:   Every viewport has a keyboard focus (2.1.2, Level A). Users can  operate all functions using just the keyboard (2.1.1, Level A), activate  important
>
> or common features with shortcut keys, (2.1.6, Level A),  escape keyboard traps (2.1.3, Level A), specify that selecting an item  in a dropdown list or
>
> menu not activate that item (2.1.4, Level A) and  use standard keys for its platform (2.1.5, Level A).
>