link to table version of issues list
Last updated on: $Date: 2000/11/08 07:48:50 $
Refer to Issue 303 http://server.rehab.uiuc.edu/ua-issues/issues-linear.html#303
http://www.w3.org/WAI/UA/2000/04/rfbd-20000411#issue-273 Proposal: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0127.html
Refer to proposal:
Refer to proposal from Al:
Refer to discussion 25 April:
Refer to comments from Madeleine Rothberg and Geoff Freed
Refer also to issue 111.
Per action item of 11 April ftf meeting, Ian sent reviewer
a request for more information on 13 April. No reply as of 18 April.
Proposed: Use definition of "document object" from:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0132.html In the techniques, state that navigation may not be strictly according to the document object.
Refer to comments from AG:
Refer to 20 April discussion
Refer to 27 April discussion
Refer to 2 May discussion
Refer to Proposal from Ian following joint UAAG/WCAG teleconf
Refer to Proposed from JG:
Refer to discussion on 11 May:
Resolved that no:
Refer to proposed wording
[QUOTE] The added twist is that the platform might provide it's own speech synthesizer (and controls for it) plus the user can also plug in and control their own hardware based speech synthesizer. [/QUOTE]
Refer to resolution in minutes
Resolved at ftf that alt equivs only
Refer to proposal:
Refer to discussion in Princeton:
Refer to Ian's proposal:
Proposal adopted in 13 april teleconf:
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.
IJ: Ideas for next draft.
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 navigational barsCONs:
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: Depricated HTML element
Discussed 7 July