- From: William Loughborough <love26@gorge.net>
- Date: Sat, 28 Oct 2000 05:59:30 -0700
- To: Jason White <jasonw@ariel.ucs.unimelb.EDU.AU>, Web Content Accessibility Guidelines <w3c-wai-gl@w3.org>
At 03:35 PM 10/28/00 +1100, Jason White wrote:
>2.3 Use markup or a data model to specify the logical structure of content.
In addition to markup/data model we will also recommend "content choices"
for this purpose, e.g. topic sentences in paragraphs, header language
hierarchies, and list method choices (not just their use).
Although the discussion concerning "what is structure" in another document
concludes with an example that seems to show <hr /> is not "structure", any
blindless person gains a "skim advantage" by using this element as a target
point, therefore it (and possibly *every* [even "decorative"] markup
element) might logically be structural insofar as its effective deployment
goes. Even if such an attitude doesn't lead very far it certainly can't
hurt to consider all elements and many attributes (I believe leaping
amongst "captions" helps skimming) as structure. At the least it might help
educate authors into what structure is and how they are frequently
unconsciously using "decorative" elements as structure.
--
Love.
ACCESSIBILITY IS RIGHT - NOT PRIVILEGE
Received on Saturday, 28 October 2000 09:00:02 UTC