W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > April to June 2004

Re: 506 definition of structure

From: Sailesh Panchang <sailesh.panchang@deque.com>
Date: Mon, 7 Jun 2004 17:25:02 -0400
Message-ID: <014201c44cd5$e5636d20$a401a8c0@deque.local>
To: <w3c-wai-gl@w3.org>
Message
  ----- Original Message ----- 
  From: John M Slatin 
  <current guideline 1.3>
  Ensure that information, functionality, and structure are separable from presentation.
  </current guideline 1.3>
  John writes:
  > So it's not that these things "are separable >from presentation": we're really saying that >the presentation must always include all the >parts of the resource, including functionality >and structure.

  Sailesh writes:
  My understanding is that presentational and styling elements  or markup  are not embedded or built-into markup that 
  - convey structure of different parts of the resource, or 
  - do things (functionality).

  An example from another context might help clarify my thought. When designing say, employee ID# for an org., one normally prefers not to build intelligence into the ID#. If the ID# were to convey employee's department and be the employee's unique identifier, he/she would have to be assigned a new ID# everytime  the individual's department changed.   Likewise "intelligence"or in our context, code that conveys presentational effects should be independent of code that conveys structure / functionality.
  Perhaps the last sentence  is the wording for the guideline 1.3...?
  Sailesh Panchang
  Senior Accessibility Engineer 
  Deque Systems,11180  Sunrise Valley Drive, 
  4th Floor, Reston VA 20191
  Tel: 703-225-0380 Extension 105 
  E-mail: sailesh.panchang@deque.com
  Fax: 703-225-0387
  * Look up <http://www.deque.com> *
Received on Monday, 7 June 2004 17:25:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:30 GMT