Re: AU2-1.1 (produce accessible content)

Proposal for the at minimum bit:
At minimum allow the author to add or edit any element or property supported
by the content type specification.

Note that this is close to the requirement of checkpoint 7.3 - is that
redundant? (the fact that that has to be in an accessible fashion is already
covered by 7.1)

cheers

Charles McCN

On Tue, 10 Apr 2001, Jan Richards wrote:

  PROPOSED:
  1.1 Ensure that the author can produce accessible content in the markup
  language(s) or content type(s) supported by the tool. [Priority 1]
  At minimum, provide a code editing view that will accept manually-coded
  accessibility content and ensure that this content is preserved as per
  Checkpoint 1.2.

  WL's point: We are suggesting a UI implementation without specifically
  saying that it should be accessible.

  JR, CMN: 7.1 already covers the accessibility of the tool. JR: Besides,
  we're not telling them to do a drag-and-drop solution for which
  accessibility would be a major concern - we're talking about text
  editing.

  CMN's point: At minimum is misleading. Tools don't have to do this. We
  might say "The simplest way to meet this is..."

  Cheers,
  Jan



-- 
Charles McCathieNevile    http://www.w3.org/People/Charles  phone: +61 409 134 136
W3C Web Accessibility Initiative     http://www.w3.org/WAI    fax: +1 617 258 5999
Location: 21 Mitchell street FOOTSCRAY Vic 3011, Australia
(or W3C INRIA, Route des Lucioles, BP 93, 06902 Sophia Antipolis Cedex, France)

Received on Tuesday, 10 April 2001 15:25:38 UTC