- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Sat, 30 Oct 2010 17:10:10 +0100
- To: "w3c-wai-au@w3.org" <w3c-wai-au@w3.org>
One of my actions was to re-work the wording on A.2.2.1, originally: A.2.2.1 Purpose of Added Presentation: If an editing view modifies the presentation of web content to provide additional information to authors, then that additional information can be programmatically determined. The comment (MS6) was questioning what "additional information" could be construed as, and to make it objectively testable or revise the success criterion. I believe the typical scenario to cover is spelling/grammar checkers, but the principle is that if an editing program changes the view to indicate something to the author, that indication is programmatically determinable by assistive tech. Although I stumbled on the meaning initially, JR's proposal does make sense: A.2.2.1 Editing-View Messages: If an editing-view provides messages to authors by modifying the content renderings or adding temporary content, then those messages can be programmatically determined. An alternative could be: A.2.2.1 Editing-View Messages: If an editing-view provides highlighting or temporary content that will not be included in the published web content, then those additions can be programmatically determined. Another reply to the comment (specifically: "In order to determine what is considered additional information, one must know what is considered baseline information.") might be to add a definition: Additional content is an addition to the rendering of the editing-view that is not included with the published content. (E.g. highlighting by a spell checker, or making visible information about the underlying markup.) Kind regards, -Alastair -- Alastair Campbell | www.nomensa.com
Received on Saturday, 30 October 2010 16:10:46 UTC