This is a snapshot of the issues list as of $Date: 2000/11/08 07:48:47 $. It is made available as a static document in preparation for going to Candidate Recommendation.
The active issues list is available in linear form and tabular form.
These are three options I am aware of for markup related to navigation bars or in general grouping of links. Please respond with your own ideas or comments. FOllowing the options is a list of some of the archived e-mail discussion on the issue.
Using the DIV element and some type of CLASS or NAME identifier:
PROs: Easy to implement and author
CONs: There is no mechanism to reserve class names in HTML, there could be conflicts if specific class names are usedOption
PROs: Currently used for image based navigation bars
1. More complex than DIV to author
2. What if authors did not want to use images in their navigation bars
Option 3: Schema
Schemas are a potential way to indicate the purpose of content or structure
PROs: Proclaimed as the right method for the job
1. New technology and still under development
2. Not currently supported by UAs,
3. Not clear how easy to author
4. Not clear how easy for AT to decode and use information
Option 4: MENU element
CON: Deprecated HTML element
Discussed 7 July
IJ: Ideas for next draft.
Furthermore, we should consider adding a checkpoint abstracted from Todd's techniques to the effect that there should be one control in the UI which accomplishes a general increase or decrease of the font sizes throughout the document, while preserving size ordering of different text fragments to the maximum extent with user directives.