W3C home > Mailing lists > Public > w3c-wai-au@w3.org > July to September 2005

Proposed change to: A.?.4

From: Jan Richards <jan.richards@utoronto.ca>
Date: Mon, 11 Jul 2005 14:37:54 -0400
Message-ID: <42D2BC82.6070904@utoronto.ca>
To: "List (WAI-AUWG)" <w3c-wai-au@w3.org>

PROPOSED:

[1]

Def’n: Preview: A non-editable, rendered view that is intended to 
emulate a browser or class of browsers

[2]

A.?.4 Ensure previews emulate accessible rendering features of browsers 
[Priority ?]

Rationale: The workflow of many authoring tools includes periodically 
checking a preview of how content will appear in a browser. When this 
functionality is not provided by an external browser, the authoring tool 
should ensure the same level of accessibility to the content as a 
browser would provide.

Note: The *authoring tool user interface* for built-in preview windows 
must meet the accessibility requirements in this document. It is only 
the preview content window that this checkpoint applies to.

Techniques: ???

Success Criteria:

1. Preview functions must provide the accessible rendering features 
(e.g. keyboard accessibility, API support, etc.) of the browser or class 
of browsers being emulated (identified in the conformance profile) 
and/or allow the author to choose an alternative browser to perform the 
preview.


CURRENT:

A.?.4 Ensure previews emulate accessible rendering features of browsers 
[Priority ?] @@JR@@

Rationale: The workflow of many authoring tools includes periodically 
checking a preview of how content will appear in a browser. When this 
functionality is not provided by an external browser, the authoring tool 
should ensure the same level of accessibility to the content as a 
browser would provide. @@+ changes req'd to "user interface"@@

Note: The authoring tool user interface for built-in preview windows 
must meet the accessibility requirements in this document. It is only 
the preview content window that this checkpoint applies to. @@def'n of 
preview: A non-editable, rendered view that is intended to emulate a 
browser or class of browsers.@@

Techniques: ???

Success Criteria:

1. Preview functions must provide the accessible rendering features of 
the browser or class of browsers being emulated @@identified in the 
conformance profile@@ and/or allow the author to choose an alternative 
browser to perform the preview.

--------
Cheers,
Jan
Received on Monday, 11 July 2005 18:38:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 22 September 2008 15:53:05 GMT