Re: Including content modes in 4.1

Yep, this makes sense to mme.

Charles McCN

On Fri, 18 May 2001, Adam Victor Reed wrote:

  I suggested the addition of content modes to Gudeline 4.1 as a
  possible way of dealing with the vowel mark problem in Hebrew and
  Arabic, which was brought to our attention by Lisa Seeman (vowel marks
  are required to support screen reading in user agents, and for
  accessibility to people with limited reading ability.) If there
  is no objection, I would like to see Gudeline 4.1 updated as follows:

  4.1 Choose content modes, languages, API's, and protocols that support
  the use of these guidelines.
  	Content modes (e.g. Hebrew with and without vowel marks,)
  	markup languages, multimedia formats, software interface
  	standards, etc., vary in their support of accessibility. When
  	choosing which technologies and content modes to use, consider
  	how easy it is apply these guidelines. Where feasible, favor
  	content modes and technologies that:
  	* support assistive technology in user agents;
  	* permit equivalents to be associated with or synchronized
  	  with auditory, graphical, and multimedia content;
  	* allow the logical structure of the content to be defined
  	  independently of presentation;
  	* support device-independence;
  	* are documented in published specifications and can be
  	  implemented by user agent and assistive technology
  	  developers.


-- 
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 Sunday, 20 May 2001 16:17:01 UTC