RE: Support as an SC prefix?



Steve


-----Original Message-----
From: Alastair Campbell [mailto:acampbell@nomensa.com] 
Sent: Wednesday, March 08, 2017 11:44 AM
To: Repsher, Stephen J <stephen.j.repsher@boeing.com>
Cc: WCAG <w3c-wai-gl@w3.org>
Subject: Re: Support as an SC prefix?

Repsher, Stephen J wrote:
> "mechanism" may not be the absolute best word, but it is well-established throughout 2.0 with a clear definition that the author is not necessarily fully liable and links to several other definitions.

That is true, but we still had umpteen comments along the lines of: You can’t require people to put a widget on the page!

People assumed that is what it meant (and this is from experts in WCAG).
[Steve] Agreed.  Time to understand may be the best solution though.

> ultimately the word "support" should not be added as all other criteria have names which are nouns, not command sentences.
    
I don’t think it is that clear cut, resize text, use of color, and pause/stop/hide come to mind.
[Steve] Touche :)

All I’m suggesting (as per the commenter) is an indicator at the start of some SCs, so linearize is currently:
Linearization: A mechanism is available to view content as a single column, except for parts of the content where the spatial layout is essential to the function and understanding of the content.

That would become:
Support linearization: Content can be viewed as a single column, except for parts of the content where the spatial layout is essential to the function and understanding of the content.
[Steve] My point is just that you would also have to be willing to change 2.4.1 to "Bypass Blocks: Blocks of content that are repeated on multiple web pages can be bypassed." (i.e. remove any mention of a mechanism)

There are 3 or 4 other SCs that would apply to currently.

Cheers,

-Alastair

Received on Wednesday, 8 March 2017 17:15:11 UTC