link to table version of issues list
Last updated on: $Date: 2000/11/08 07:48:50 $
http://www.w3.org/WAI/UA/WD-UAAG10-20000707/
Refer to Issue 303 http://server.rehab.uiuc.edu/ua-issues/issues-linear.html#303
Resolved editorial
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:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0135.html
Refer to proposal from Al:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0179.html
Refer to discussion 25 April:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0196.html
Refer to comments from Madeleine Rothberg and Geoff Freed
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0311.html
Refer also to issue 111.
http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#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.
http://www.w3.org/WAI/UA/2000/04/rfbd-20000411#issue-264
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:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0188.html
Refer to 20 April discussion
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0183.html
Refer to 27 April discussion
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0242.html
Refer to 2 May discussion
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0274.html
Refer to Proposal from Ian following joint UAAG/WCAG teleconf
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0287.html
Refer to Proposed from JG:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0356.html
Refer to discussion on 11 May:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0359.html
Resolved that no:
http://www.w3.org/WAI/UA/2000/04/rfbd-20000410#issue-223
Refer to proposed wording
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0106.html
Second proposal:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0164.html
[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
http://www.w3.org/WAI/UA/2000/04/rfbd-20000410#issue-212
Resolved at ftf that alt equivs only
http://www.w3.org/WAI/UA/2000/04/rfbd-20000410#issue-211
Refer to proposal:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0104.html
Refer to discussion in Princeton:
http://www.w3.org/WAI/UA/2000/04/rfbd-20000410#issue-208
Refer to Ian's proposal:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0074.html
Proposal adopted in 13 april teleconf:
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000AprJun/0088.html
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.
Option 1:
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
2:MAP element
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
CONs:
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
http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html