W3C WAI User Agent Issue List: Linear Version

link to table version of issues list

Last updated on: Tue Mar 7 12:35:40 2000

Indexes of issues available

• List of open issues
• List of resoloved issues
• Numerical list of issues
• Index of issues by category of issue
• Index of issues by name of person raising the issue
• Index of issues by type of issue

Key to Letters Before Issue Number

• WD: Issue raised before last call
• LC:Issue raised during last call
• CR: Issue raised during candidate recommendation
• PR: Issue raised during proposed recommendation

No Open Issues

List of 206 Resolved Issues

• CR#206: Precise specification of what parts of DOM are required
• CR#205: Timing issues related to AT missing or not being synchronized to document changes
• CR#204: Add collated text to Checkpoint 2.6 and 4.8 or create a new checkpoint at lower priority
• CR#203: Checkpoint for access to content for non-HTML or non-XML WWW documents (i.e. Shockwave)
• CR#202: User agent configuration to render NOFRAMES content
• CR#201: 5.5 "Ensure that programmatic exchanges proceed in a timely manner" should be a priority 1
• CR#200: Checkpoint 5.5, developers not unclear on how they know they have satisfied this checkpoint
• CR#199: Poor wording of checkpoint 10.8, it is not clear what the requirement is to improve accessibility
• CR#198: How much information needs to be provided to satisfy Checkpoint 8.4
• CR#197: Not clear with the scope of user preferences is in Checkpoint 10.7
• CR#196: It is unclear to developers how they know they conform to Checkpoint 6.2: Conform to W3C specifications when they are appropriate
• CR#195: Problems understanding checkpoint 1.5
• CR#194: In a timed presentation does checkpoint 7.2 mean return to the time that the user was at in a previous MM rendering
• CR#193: In the case of animations, does checkpoint 4.5 mean a requirement to step through or slow the speed as well as being able to turn it off?
• CR#192: Does hiding video satisfy checkpoint 3.3
• CR#191: Does a pause function satisfy checkpoint 2.2?
• CR#190: Reduce the scope of 5.1 to say "write access only for that which you can do through the UI."
• WD#189: Proposed change to checkpoint 2.3 (missing alt info)
• WD#188: Add definition of disability? (to CG)
• WD#187: Proposed change in wording to 1.6 (profiles)
• WD#186: Proposed removal of Note in 2.1
• WD#185: clarification of "single key" access
• WD#184: Proposed simplification to checkpoint 1.1 (device-independent access)
• WD#183: Proposed rewording to checkpoint 7.5 (search alt content)
• WD#182: Should searching equivalent text be an AT responsibility
• WD#181: Request for a wrapper note designed for AT developers explaining relation to guidelines
• WD#180: 10.8 should be priority 2
• WD#179: Priority of 5.8 should be 1
• WD#178: In 10.1 and 10.2 what does communicate through an API mean
• WD#177: User control of current focus change and notification.
• LC#176: Proposed change in priority (P3 to P2) for checkpoint 8.7 (link information)
• LC#175: Proposed raise (to P1) of checkpoint 4.18
• LC#174: Natural language identification issues.
• LC#173: Proposed revision of "native" to account for OS features
• LC#172: Some clarification required in 1.1
• LC#171: 3.4: What does natively rendering audio mean?
• LC#170: How can UAs "stay" accessible when there is a mass of inaccessible content?
• LC#169: What UI is required for turning on/off features that may impede accessibility?
• LC#168: Checkpoint 2.7: Add object name in addition to type.
• LC#167: Proposed checkpoint to allow users to turn on/off multilingual support.
• LC#166: Review priority of 10.5 (default configs that interfere with OS conventions)
• LC#165: Add information about system level flags to 5.2
• LC#164: Proposed change to wording of 4.8 in last call UAGL.
• LC#163: Proposed new checkpoint on "Favorites" functionality
• LC#162: Raise priority of 8.9 (consistency in configs) to P2.
• LC#161: Raise priority of 8.8 to P2 (highlighting and identifying selection/focus)
• LC#160: Delete checkpoints 7.3 and 8.2 (related to tables) since too vague
• LC#159: Propose raise priority of 4.13 to Priority 1
• LC#158: Propose priority change (1 to 2) for checkpoint 4.1 (control of font family)
• LC#157: Correct reference to XSL in checkpoint 6.2 since only a Working Draft.
• LC#156: Propose change in priority of 5.6 (P1 -> P2)
• LC#155: Propose change of priorities for checkpoints 5.3 (r/w access) and 10.3 (single key)
• LC#154: Proposed requirement that UAs give access to style sheet classes
• LC#153: Hold off on conformance until functional requirements between browsers/ATs more defined?
• LC#152: Proposed checkpoint: "Do not constrain the accessible output by constraints of the existingpresentation"
• LC#151: Proposed checkpoint: change audio rate without changing pitch
• LC#150: Do APIs apply when the software is accessible on its own?
• LC#149: 10.6: Wording (delete "and software") and Priority.
• LC#148: Checkpoint 9.6: Does RETURN count as explicit submit?
• LC#147: Need to review priority and wording of 5.8
• LC#146: Review priorities of 4.16, 5.2, 8.3, 8.5, 10.3, 10.6
• LC#145: Why is 3.7 Pri 1 and 3.10 Pri 3? (Re: blinking and flashing)
• LC#144: Editorial changes to some Guideline titles suggested
• LC#143: Proposed deletion of 2.6 since special case of 2.2
• LC#142: Checkpoint 1.5 (output device-independence) needs clarification.
• LC#141: Need to qualify checkpoint 1.4 in same was as 1.1 is qualified re: "every"
• LC#140: Clarification on 2.3 required: how do you satisfy it if you don't support a language?
• LC#139: Need clarification of 4.11 (audio playback speed)
• LC#138: "Synchronized equivalent" v. "Continuous Equivalent"/ Proposed split of 2.5
• LC#137: Use of terms for disabilities, impairment
• LC#136: Proposal for checklist delivery (part of conformance)
• LC#135: Add incremental forward/rewind for audio, video, speech?
• LC#134: Proposed modification of 10.3: "The controls mustbe user-selectable."
• LC#133: Priority of 10.1 compared to 10.3
• LC#132: Checkpoint 4.17 (Note): User should not be able to turn off default styles
• LC#131: Proposed change in wording of 10.8
• LC#130: Proposed rewording of 10.5: Avoid default> > input configurations that conflict with operating system navigation, control, and access conventions.
• LC#129: Need to clarify 10.3 ("Allow the user to change and control the inputconfiguration. Users should be able to activate a functionality with a single-stroke (e.g., single-key, single voicecommand, etc.).)
• LC#128: Extend definition of focus to include GUI control focus
• LC#127: How to verify 5.7 (Provide programmatic exchange of information in a timely manner.)?
• LC#126: Proposed change in wording to 5.5 (Provide programmatic notification of changes to content and user interfacecontrols (including selection and focus).)
• LC#125: To what APIs does 5.1 refer ( Provide accessible APIs to other technologies)
• LC#124: Should the Guidelines reference MSAA and JAAPI?
• LC#123: Proposed checkpoint to use standard UI components for the interface.
• LC#122: Proposed checkpoint related to input focus on controls
• LC#121: Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI)
• LC#120: The UAGL should pay more attention to UI accessibility
• LC#119: Proposed narrowing of scope in definition of "applicability" (ALSO: Put back in conformance section? -IJ)
• LC#118: User Interface for text size (font size) control
• LC#117: How are exception cases determined and by whom?
• LC#116: Non-editorial issues raised by Eric Hansen
• LC#115: Checkpoint to maintain relative font sizes?
• LC#114: How do requirements for APIs overlap (DOM? Platform standards? Provided by Tool)
• LC#113: Deletion of Guideline 2: Support the Keyboard
• LC#112: Split checkpoint 10.1 into two separate checkpoints for author and user agent input functionalities and mark as an issue during last call
• LC#111: Proposal to make Checkpoint 6.1 have a relative priority
• WD#110: Proposed changes to Guidelines 1, 2, and 11 re: keyboard
• WD#109: Proposed rewording of Checkpoints 1.1 and 1.6
• WD#108: Proposed checkpoint for table summary information
• WD#107: Proposed new checkpoint: 6.7 Support assistive technology accessibility standards defined for plug-in and virtual machine systems used by your browser. [priority 1]
• WD#106: Proposed Abstract revision
• WD#105: ACCESSKEY implementation issues
• WD#104: Proposed additions to conformance claim requirements
• WD#103: Proposed change to priority wording
• WD#102: List of problematic checkpoints.
• WD#101: Wording of checkpoint on document change notification
• WD#100: Proposed Note on verifiability of some checkpoints
• WD#99: Priority of control of GUI layout should not be priority 1
• WD#98: What does "appropriate" mean in "appropriate w3c recommendations"?
• WD#97: Questions about wording of document outline checkpoint
• WD#96: Issues related to Checkpoint 2.1: Mapping of user agent functions to control mechanisms and memory demands related to sequential/direct access to functionalities
• WD#95: Proposed checkpoint: Choose from among style sheets
• WD#94: Reenforcing the the use of standard keyboard APIs in guideline 2
• WD#93: Proposed modification to definition of "applicable checkpoint"
• WD#92: Proposed checkpoint about form orientation
• WD#91: Proposed reformulation of frames checkpoint
• WD#90: Development of a dependency list between UA and AU
• WD#89: Proposed changes in conformance based on interoperable UA and non-interoperable UA
• WD#88: Proposed wording change for checkpoint on access to selected content.
• WD#87: Proposed wording change about user-control of highlight rendering
• WD#86: Should Guideline about support for W3C technologies be broadened or narrowed?
• WD#85: Priority of checkpoint on language support
• WD#84: Checkpoint on natural language applies to all UAs
• WD#83: Split Checkpoint on voice characteristics?
• WD#82: How to rendering text links for images in links that have no alt?
• WD#81: Allow the user to turn on and off rendering of audio descriptions.
• WD#80: Make audio output available as text
• WD#79: How do specialized browsers like pwWebSpeak and IBM Homepage Reader conform to the guidelines
• WD#78: Review requirements for window spawning
• WD#77: Validate conformance categories
• WD#76: How to get to frames when the user turns off the rendering of frames
• WD#75: Does accessible doc checkpoint apply to non Web-based docs?
• WD#74: Value of checkpoint on volume control
• WD#73: Text rendering of client-side iamge maps
• WD#72: What should UAs do to support author-supplied metadata?
• WD#71: Titles for ABBR and ACRONYM elements
• WD#70: Recognizing paying links from micropayments markup
• WD#69: Proposed Guideline for software consistency
• WD#68: Must the user be able to do everything with the mouse that they can with keyboard?
• WD#67: Adding guideline related to keyboard support in user agents
• WD#66: Proposal to simplify check points in guidelines 7 (11 June WD)
• WD#65: Flicker frequencies of concern for photosensitive epilepsy
• WD#64: Keyboard mapping among assistive technology tools
• WD#63: Checkpoint proposal from Marja to freeze time-sensitive content.
• WD#62: Renumbering guidelines similar to Web Content Guidelines
• WD#61: Proposed removing redundant checkpoint
• WD#60: Need to give user final control over accesskey settings
• WD#59: Reorder guidelines to place more important guidelines at the beginning of the document
• WD#58: Keyboard access to select form controls when there is an ONCHANGE event handler attached to the control
• WD#57: Which attributes can be used to search for an element based on attribute values
• WD#56: Provide orientation to audio (or video) to length and/or position in the rendering of the information
• WD#55: Priority of 5.1.7 Allow the user to control animation rate, due to photosensitive epilepsy
• WD#54: User notification of document changes due to scripting and other events
• WD#53: Proposed priority change to 5.2.9 from 2 to 1
• WD#52: Combining 6.1.9 and 6.1.10 in 31 March Draft
• WD#51: Language support
• WD#50: Modify Guideline 7.1
• WD#49: Add a checkpoint that says that UAs should allow users to turn off flicker
• WD#48: Saving form information to a local file and restoring the information when form is retrieved
• WD#47: Include scripting events in checkpoint on access to active elements
• WD#46: Allow user to configure active elements to include scripting events
• WD#45: Include a specific checkpoint to allow user to simulate scripting events
• WD#44: Navigation of time dependent mult-mdeia elements rendered to the user (more than just stop, rewind and fast forward)
• WD#43: Navigation and activation of elements with ACCESSKEY attributes defined
• WD#42: How do users navigate documents with embedded list elements?
• WD#41: What types of navigation commands support a user with a visual impairment navigating a familar document?
• WD#40: What types of navigation commands support visually impaired users navigating a unfamilar document?
• WD#39: Server side formatting of XML and other documents using XFO
• WD#38: Search for a link based on its attribute value
• WD#37: Allow user to navigate bewteen tables
• WD#36: Allow the user to view summary structural information about a table
• WD#35: Allow the user to view the summary attribute of a table
• WD#34: Allow the user to view assumed headers associated with a cell
• WD#33: Allow the user to view header information associated with a cell
• WD#32: Allow the user to view one table cell at a time
• WD#31: Allow users to navigate between cells of a table
• WD#30: Move to the parent element of the current element in the document tree
• WD#29: Move to the next (or previous) sibling element in the document tree
• WD#28: Move to the child level element of the current element in the document tree
• WD#27: Move to the next element in the document tree as defined by DOM
• WD#26: Search for an element based on its text content
• WD#25: Sequentially navigate to all elements (block level)
• WD#24: Search for a form control based on its attribute values (i.e. label or control type)
• WD#23: Search for a form control based on text content
• WD#22: Sequentially navigate between forms in a document
• WD#21: Search for link based on its text content
• WD#20: Sequentially navigate header elements
• WD#19: Sequentially navigate to elements with explicit scripting event handlers
• WD#18: Sequentailly navigate to only elements with long descriptions (longdesc attribute or OBJECT content)
• WD#17: Sequentially navigate to only form controls in a document
• WD#16: Sequentially navigate to only link elements
• WD#15: Sequentially navigate between active elements
• WD#14: MathML objects should be included as part of the document tree
• WD#13: Provide keyboard access to MathML similar to forms
• WD#12: Recommend full implmentation of MathML
• WD#11: Move to the next element with the same attributes and element type
• WD#10: Use OS conventions and accessibility settings in interface design, configuration, product installation, and documentation.
• WD#9: Require timely exchange of information between user agents and AT for rendering synchronization
• WD#8: Provide a means for AT to simulate user interface (non-WWW content) controls
• WD#7: Provide a means for AT to simulate WWW document events
• WD#6: Provide a means for AT to change the DOM, selection, focus and/or system caret
• WD#5: User agents should provide information to AT on changes to the document object, selection, focus or system caret
• WD#4: Use accessibility API and OS conventions for compatibility with AT
• WD#3: What should UAs do with recognize navigation bars?
• WD#2: Recommend full implmentation of DOM level 1 for AT compatibility
• WD#1: Use subgrouping of checkpoints for conformance for assistive technology and desktop graphical user agents

Issue details listed in numerical order

Issue 1: Use subgrouping of checkpoints for conformance for assistive technology and desktop graphical user agents

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1998/12/wai-ua-f2f-19981211.html#post-rec

Date: Mon Apr 19 16:58:14 1999

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Use subgrouping of checkpoints for conformance

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0071.html

First working draft: No reference

Comments: none

Key References: none

Issue 2: Recommend full implmentation of DOM level 1 for AT compatibility

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1998/12/wai-ua-f2f-19981211.html#media

Date: Mon Apr 19 17:06:34 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: This is part of the long term solution to making more accessible user agents

Resolution URL: http://www.w3.org/WAI/UA/1998/12/wai-ua-f2f-19981211.html#media

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/

Comments: none

Key References: none

Issue 3: What should UAs do with recognize navigation bars?

Name: Al Gilman

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-gl/1999JanMar/0521.html

Date: Mon Apr 19 17:15:04 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Add navigation bar techniqes based on the MAP element to the techniques document

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-gl/1999JulSep/0307.html

First working draft: No reference

Comments:

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

Key Reference URLs:

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0197.html

Issue 4: Use accessibility API and OS conventions for compatibility with AT

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0041.html

Date: Mon Apr 19 17:38:40 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include a checkppint that requires support for accessibility APIs and OS accessibility conventions

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990210/

Comments: none

Key References: none

Issue 5: User agents should provide information to AT on changes to the document object, selection, focus or system caret

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0041.html

Date: Mon Apr 19 17:44:15 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include in checkpoint the ability of assistive technology to change the DOM, selection, focus and system caret

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: No reference

Comments: none

Key References: none

Issue 6: Provide a means for AT to change the DOM, selection, focus and/or system caret

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0041.html

Date: Mon Apr 19 17:47:57 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include a checkpoint that includes this functionality

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: No reference

Comments: none

Key References: none

Issue 7: Provide a means for AT to simulate WWW document events

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0041.html

Date: Mon Apr 19 17:49:05 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include a checkpoint that includes this functionality

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: No reference

Comments: none

Key References: none

Issue 8: Provide a means for AT to simulate user interface (non-WWW content) controls

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0041.html

Date: Mon Apr 19 17:50:02 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include a checkpoint that includes this functionality

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: No reference

Comments: none

Key References: none

Issue 9: Require timely exchange of information between user agents and AT for rendering synchronization

Name: Rich Schwerdtfeger

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0022.html

Date: Mon Apr 19 17:50:52 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include a checkpoint that includes this functionality in a checkpoint

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: No reference

Comments:
The user agent needs to use interface and techniques that provides for timely exchange of information between the user agent and assistive technology.

Key Reference URLs:

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0044.html>http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0044.html

Issue 10: Use OS conventions and accessibility settings in interface design, configuration, product installation, and documentation.

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0022.html

Date: Mon Apr 19 17:54:57 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Include a checkpoint that includes this functionality in a checkpoint

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0060.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19990309/

Comments:
User agents should inherit accessibility information all ready set by the user in the operating system.

Key References: none

Issue 11: Move to the next element with the same attributes and element type

Name: Denis Anson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0327.html

Date: Mon Apr 19 17:59:50 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Search for the next element with the same attributes as the current element, P3, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments: none

Key References: none

Issue 12: Recommend full implmentation of MathML

Name: Tom Wlodkowski

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0263.html

Date: Tue Apr 20 13:14:36 1999

Category of issue: MathML

Type of issue: Checkpoints

Resolution summary: Recommend use MathML as the prefered method to represent MathML in user agents that render Mathematical equations

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990519.html

First working draft: No reference

Comments: none

Key References: none

Issue 13: Provide keyboard access to MathML similar to forms

Name: Tom Wlodkowski

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0263.html

Date: Tue Apr 20 13:17:17 1999

Category of issue: MathML

Type of issue: Checkpoints

Resolution summary: Include examples of keyboard navigation of math equations in techniques document sections related to element navigation

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990519.html

First working draft: No reference

Comments: none

Key References: none

Issue 14: MathML objects should be included as part of the document tree

Name: Tom Wlodkowski

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0263.html

Date: Tue Apr 20 13:17:55 1999

Category of issue: MathML

Type of issue: Checkpoints

Resolution summary: XML dom tree of mathml needs to be exposed like HTML document tree

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990519.html

First working draft: No reference

Comments: none

Key References: none

Issue 15: Sequentially navigate between active elements

Name: Kathy Hewitt

Source URL: http://www.w3.org/WAI/UA/1998/12/wai-ua-f2f-19981211.html#gl54

Date: Tue Apr 20 13:22:40 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Include a navigation command for sequential navigation between active elements

Resolution URL: http://www.w3.org/WAI/UA/1998/12/wai-ua-f2f-19981211.html#gl54

First working draft: No reference

Comments:
Active elements include links, form controls, longdesc exposed to users

Key References: none

Issue 16: Sequentially navigate to only link elements

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 13:27:16 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Add checkpoint to next working draft: Allow the user to select a link from a list of links, P2, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981019/

Comments: none

Key References: none

Issue 17: Sequentially navigate to only form controls in a document

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 13:44:35 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Allow the user to move the focus to a form control from a list of form controls, P2, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/

Comments:
If there is more than one form in the document, the list of form controls should include information on both the form and the form controls.

Key References: none

Issue 18: Sequentailly navigate to only elements with long descriptions (longdesc attribute or OBJECT content)

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 13:52:08 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept modified proposed checkpoint: Allow the user to select a alternative content from a list of alternative content, P2, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/

Comments:
Lo

Key References: none

Issue 19: Sequentially navigate to elements with explicit scripting event handlers

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1998/10/wai-ua-f2f-19981025.html#dom

Date: Tue Apr 20 13:53:16 1999

Category of issue: Scripting events

Type of issue: Checkpoints

Resolution summary: Will be part of another checkpoint related to navigation of active elements

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990602.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/

Comments: none

Key References: none

Issue 20: Sequentially navigate header elements

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1998/10/wai-ua-f2f-19981025.html#dom

Date: Tue Apr 20 16:05:51 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Allow the user to move to a header from a list, P2, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/#gl-nav-sequential

Comments: none

Key References: none

Issue 21: Search for link based on its text content

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 16:12:48 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Search for a link based on its text content, P3, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/#gl-nav-sequential

Comments: none

Key References: none

Issue 22: Sequentially navigate between forms in a document

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 16:16:59 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Allow the use to move the focus to the first control of a form from a list of forms, P2, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments: none

Key References: none

Issue 23: Search for a form control based on text content

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 16:22:55 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Part of active elements

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/#gl-nav-sequential

Comments:
- Form controls are part of active elements - In 9 July draft, checkpoint 8.5 covers this.

Key References: none

Issue 24: Search for a form control based on its attribute values (i.e. label or control type)

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 16:24:25 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Attribute information can be part of the labels that are used in the list of form controls

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/#gl-nav-sequential

Comments:
The attributes for a form control include references to labels or as part of a collection that is defined by other HTML markup. The attribute values of label can be part of the list of form controls.

Key References: none

Issue 25: Sequentially navigate to all elements (block level)

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 16:25:13 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Sequential access to all elements, P2, subgroup: DUA

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments:
The definition of a block level element or what navigating a block at a time needs careful definition. There are many blocks like list and tables that would be useful to give summary information when the block is first encountered. Like saying a "list of 12 items" when the block is first encountered, and then the next block navigation command would read the first item in the list and so on....

Key References: none

Issue 26: Search for an element based on its text content

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Tue Apr 20 16:29:16 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Accept proposed checkpoint: Search for an element based on its text content, P1, subgroup: both

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19981030/#gl-nav-sequential

Comments: none

Key References: none

Issue 27: Move to the next element in the document tree as defined by DOM

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/04/wai-ua-telecon-19990407.html

Date: Tue Apr 20 16:35:23 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Would be part of the techniques document for a checkpoint relating to navigating the DOM

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments: none

Key References: none

Issue 28: Move to the child level element of the current element in the document tree

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/04/wai-ua-telecon-19990407.html

Date: Tue Apr 20 16:36:28 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Would be part of the techniques document on navigating the DOM

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments: none

Key References: none

Issue 29: Move to the next (or previous) sibling element in the document tree

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/04/wai-ua-telecon-19990407.html

Date: Tue Apr 20 16:37:50 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Would be part of the techniques document for the checkpoint relating to navigating the DOM

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments: none

Key References: none

Issue 30: Move to the parent element of the current element in the document tree

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/04/wai-ua-telecon-19990407.html

Date: Tue Apr 20 16:38:20 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Would be part of the techniques document on navigating the DOM

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments: none

Key References: none

Issue 31: Allow users to navigate between cells of a table

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 16:56:43 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Include as a checkpoint for AT

Resolution URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

First working draft: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

Comments: none

Key References: none

Issue 32: Allow the user to view one table cell at a time

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 17:14:12 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Include as a checkpoint for AT

Resolution URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

First working draft: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

Comments: none

Key References: none

Issue 33: Allow the user to view header information associated with a cell

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 17:16:20 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Include as a checkpoint for AT

Resolution URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

First working draft: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

Comments: none

Key References: none

Issue 34: Allow the user to view assumed headers associated with a cell

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 17:17:25 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Use MAP element in examples of navigating groups of links

Resolution URL: http://www.w3.org/WAI/GL/meetings/19990826.html

First working draft: No reference

Comments:
Some tables will be used to present tabular data, but will not have any markup to indicate whcih cells are data cells and which cells are headers. Need to add techniques

Key References: none

Issue 35: Allow the user to view the summary attribute of a table

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 17:27:48 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Covered in access to alternative content checkpoints

Resolution URL: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

First working draft: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

Comments: none

Key References: none

Issue 36: Allow the user to view summary structural information about a table

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 17:29:42 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Include in a checkpoint for AT

Resolution URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

First working draft: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

Comments: none

Key References: none

Issue 37: Allow user to navigate bewteen tables

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/02/wai-ua-telecon-19990203.html

Date: Tue Apr 20 17:45:21 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Resolved to include checkpoint and changes to select from list

Resolution URL: http://www.w3.org/wai/ua/1999/05/wai-ua-telecon-19990519.html

First working draft: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

Comments: none

Key References: none

Issue 38: Search for a link based on its attribute value

Name: Jon Gunderson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0350.html

Date: Wed Apr 21 10:43:37 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Add checkpoint: search for content based on attribute value [metadata information (class, etc.)], P3, subgroup:both

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

First working draft: No reference

Comments:
This is primary using HTML markup to indicate the function or purpose of a link for creating sub groups of links to let the user navigate. For example navigation bars, and other logical groupings of links in a document. It will be part of a more general checkpoint on searching based on attribute values

Key References: none

Issue 39: Server side formatting of XML and other documents using XFO

Name: William Loughborough

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ig/1999AprJun/0062.html

Date: Tue Apr 27 16:11:27 1999

Category of issue: Servers

Type of issue: Checkpoints

Resolution summary: This is issue is out of scope for our working group right now. PF is aware of the issue and made recoommendations to the XML working group reguarding this issue

Resolution URL: Not resolved

First working draft: No reference

Comments:
This issue cannot be resolved right now. The XML working group is currently dealing with the issue and the WAI UA group is also aware of the issue and may include recommendations. The most UA would do at this point is include recommendations on recognizing or retreiving XML markup to allow semantic information to be available locally.

Key Reference URLs:

   http://www.operasoftware.com/people/howcome/1999/foch.html

   http://www.w3.org/WAI/UA/1999/04/wai-ua-telecon-19990428.html

Issue 40: What types of navigation commands support visually impaired users navigating a unfamilar document?

Name: Denis Anson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0064.html

Date: Wed Apr 28 17:23:36 1999

Category of issue: Navigation

Type of issue: Issue

Resolution summary: Sequential, direct, hierarchical and search and these are mentioned in working draft

Resolution URL: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19991029/

First working draft: No reference

Comments: none

Key References: none

Issue 41: What types of navigation commands support a user with a visual impairment navigating a familar document?

Name: Denis Anson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0064.html

Date: Wed Apr 28 17:28:09 1999

Category of issue: Navigation

Type of issue: Issue

Resolution summary: sequential, direct, hierarchical and search and all these techniques are in current working draft

Resolution URL: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19991029/

First working draft: No reference

Comments: none

Key References: none

Issue 42: How do users navigate documents with embedded list elements?

Name: Denis Anson

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0064.html

Date: Wed Apr 28 17:29:12 1999

Category of issue: Navigation

Type of issue: Issue

Resolution summary: Orientation technique to relational information in the web content, need a technique in techniques document

Resolution URL: http://www.w3.org/WAI/UA/WD-WAI-USERAGENT-19991029/

First working draft: No reference

Comments: none

Key References: none

Issue 43: Navigation and activation of elements with ACCESSKEY attributes defined

Name: Harvey Bingham

Source URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

Date: Wed May 5 16:58:23 1999

Category of issue: Navigation

Type of issue: Issue

Resolution summary: This is part of active elements. Already covered.

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html

First working draft: No reference

Comments:

Key References: none

Issue 44: Navigation of time dependent mult-mdeia elements rendered to the user (more than just stop, rewind and fast forward)

Name: Marja Koivunen

Source URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990505.html

Date: Wed May 5 17:03:33 1999

Category of issue: Navigation

Type of issue: Issue

Resolution summary: Provide time-independent access to time-sensitive active elements. Priority 1. For all user agents.

Resolution URL: http://www.w3.org/WAI/UA/1999/08/wai-ua-telecon-19990818.html

First working draft: No reference

Comments:
MN took an action item to define a checkpoint on May 5th telecon

Key References: none

Issue 45: Include a specific checkpoint to allow user to simulate scripting events

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990526.html

Date: Mon May 24 08:27:40 1999

Category of issue: Scripting events

Type of issue: Checkpoints

Resolution summary: Users should be able to simulate scripting events

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990602.html

First working draft: No reference

Comments: none

Key References: none

Issue 46: Allow user to configure active elements to include scripting events

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990526.html

Date: Wed May 26 14:07:15 1999

Category of issue: Scripting events

Type of issue: Checkpoints

Resolution summary: Include a checkpoint related to configurability of what active elements are navigated

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990602.html

First working draft: No reference

Comments: none

Key References: none

Issue 47: Include scripting events in checkpoint on access to active elements

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990526.html

Date: Wed May 26 14:12:37 1999

Category of issue: Scripting events

Type of issue: Checkpoints

Resolution summary: Include scripting elements as part of active content, but allow user to configure

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990602.html

First working draft: No reference

Comments:
PRO: Allows user to know all elements that could potentially change content of document CON: Many elements may be included in the list of active elements that do not respond to events (event bubbling) and some events may be decorative and therefore not important for people to have access

Key References: none

Issue 48: Saving form information to a local file and restoring the information when form is retrieved

Name: Al Gilman

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0269.html

Date: Wed, 03 Mar 1999 15:39:58 -0500

Category of issue: Forms

Type of issue: Issue

Resolution summary: Not considered an accessibility issue

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990609.html

First working draft: No reference

Comments: none

Key References: none

Issue 49: Add a checkpoint that says that UAs should allow users to turn off flicker

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0150.html

Date: Fri, 21 May 1999 18:43:20 -0400

Category of issue: Animations

Type of issue: Checkpoints

Resolution summary: Covered under existing checkpoints

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990609.html

First working draft: No reference

Comments:
Add a checkpoint that says that UAs should allow users to turn off flicker. This is not the same as blinking (already covered by 4.4.6 and 4.4.7

Key References: none

Issue 50: Modify Guideline 7.1

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0150.html

Date: Fri, 21 May 1999 18:43:20 -0400

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: For flicker: add note to spec but no checkpoint. For 7.1: Yes. For language; Yes.

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0192.html

First working draft: No reference

Comments:
2) Modify Guideline 7.1 to include these checkpoints: a) Implement W3C specifications when they are available and appropriate for a task and implement the latest versions when supported. Note. Some W3C specifications are cumulative (e.g., HTML 4.0, CSS, DOM). b) Implement accessibility features defined by supoprted W3C Recommendations. [The techniques would provide links to documents where these are defined.] c) Support deprecated features of W3C Recommendations.

Key References: none

Issue 51: Language support

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0150.html

Date: Fri, 21 May 1999 18:43:20 -0400

Category of issue: Language

Type of issue: Checkpoints

Resolution summary: Include a checkpoint related to user agent detection and user notifications of language changes

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990609.html

First working draft: No reference

Comments:

• Allow users to configure UA support for preferred language/list of languages. [Techniques: HTTP Content-Language and "lang" in HTML, "xml:lang" in HTML for document root]
• Very important for Braille users
• Speech based output should switch voices if it supports the language
• User agent should announce language change

Key References: none

Issue 52: Combining 6.1.9 and 6.1.10 in 31 March Draft

Name: Charles McCathieNevile

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0284.html

Date: Sat, 06 Mar 1999 15:01:36 -0500

Category of issue: Orientation

Type of issue: Checkpoints

Resolution summary: Combine checkpoints

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990609.html

First working draft: No reference

Comments: none

Key References: none

Issue 53: Proposed priority change to 5.2.9 from 2 to 1

Name: Jim Allan

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0285.html

Date: Wed Jun 9 10:58:21 1999

Category of issue: Alternative content

Type of issue: Checkpoints

Resolution summary: Change priority, wording and combine checkpoints 5.2.8/5.2.9

Resolution URL: http://www.w3.org/WAI/UA/1999/06/wai-ua-telecon-19990609.html

First working draft: No reference

Comments:

1. Change priority of 5.2.9 to Priority 1. Change priority of 5.2.5 to Pri 1.
2. sound/rendered at the same time as/synchronized with the presentation (The one on audio as well).
3. Merge 5.2.8/5.2.9 (adjust wording)

Key References: none

Issue 54: User notification of document changes due to scripting and other events

Name: Charles McCathieNevile

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0197.html

Date: Sat, 06 Mar 1999 15:01:36 -0500

Category of issue: Scripting events

Type of issue: Checkpoints

Resolution summary: Not resolved

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0265.html

First working draft: No reference

Comments:
Resolved: Generalize 9.2 (drop part about scripts) to talk about changes to the document. Not just user-caused. For all user agents. Priority 1.

Key Reference URLs:

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0195.html

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0196.html

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0197.html

Issue 55: Priority of 5.1.7 Allow the user to control animation rate, due to photosensitive epilepsy

Name: Mark Novak

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0230.html

Date: Wed Jun 9 16:00:06 1999

Category of issue: Animations

Type of issue: Checkpoints

Resolution summary: Already have checkpoints to turn off flicker, animations or blinking

Resolution URL: http://www.w3.org/TR/1999/WAI-USERAGENT-19990331/

First working draft: No reference

Comments: none

Key References: none

Issue 56: Provide orientation to audio (or video) to length and/or position in the rendering of the information

Name: Mark Novak

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0230.html

Date: Wed Jun 9 16:03:12 1999

Category of issue: Multimedia

Type of issue: Issue

Resolution summary: a) Mention media objects as example in checkpoint 1.6.
b) List as example in checkpoint 9.6
c) Incorporate media objects into 10.5 and 10.6.

Resolution URL: http://www.w3.org/WAI/UA/1999/08/wai-ua-telecon-19990818.html

First working draft: No reference

Comments: none

Key References: none

Issue 57: Which attributes can be used to search for an element based on attribute values

Name: Mark Novak

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0230.html

Date: Wed, 24 Feb 1999 08:10:08 -0500

Category of issue: Navigation

Type of issue: Technique

Resolution summary: Talk about alt content instead

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/

First working draft: No reference

Comments:
Allow user to search rendered content. Content includes alt content, thus attribute values.

Key References: none

Issue 58: Keyboard access to select form controls when there is an ONCHANGE event handler attached to the control

Name: Chris Kreussling

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0276.html

Date: Wed Jun 9 16:08:22 1999

Category of issue: Forms

Type of issue: Problem

Resolution summary: Modify checkpoint 10.6

Resolution URL: http://www.w3.org/WAI/UA/WAI-USERAGENT-19990827/

First working draft: No reference

Comments:
Appears to be an authoring issue, since the author specified that the onchange event is triggered as the user selects different options using the keyboard

Key References: none

Issue 59: Reorder guidelines to place more important guidelines at the beginning of the document

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0185.html

Date: Wed Jun 9 16:11:10 1999

Category of issue: Editorial

Type of issue: Guidelines

Resolution summary: Ian will do for next working draft

Resolution URL: http://www.w3.org/WAI/UA/1999/08/wai-ua-telecon-19990825.html

First working draft: http://www.w3.org/WAI/UA/WAI-USERAGENT-19990827/

Comments:
This allows the numerical order of the guidelines to also indicate importance.

Key References: none

Issue 60: Need to give user final control over accesskey settings

Name: Harvey Bingham

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0084.html

Date: Wed, 05 May 1999 18:01:53 -0400

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Add checkpoint to allow user to override author-specified bindings

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0265.html

First working draft: No reference

Comments:
2 main issues: user configuration and user override of accesskey specifications

Key References: none

Issue 61: Proposed removing redundant checkpoint

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0185.html

Date: Mon, 07 Jun 1999 11:41:39 -0400

Category of issue: Installation

Type of issue: Checkpoints

Resolution summary: Leave installation as separate checkpoint

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0179.html

First working draft: No reference

Comments:
This was changed in 11 June draft. 1.4 Left separate from 1.1 to highlight it. http://www.w3.org/WAI/UA/WAI-USERAGENT-19990611/

Key References: none

Issue 62: Renumbering guidelines similar to Web Content Guidelines

Name: Ian Jacobs

Source URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990519.html

Date: Wed Jun 9 16:37:36 1999

Category of issue: Editorial

Type of issue: Guidelines

Resolution summary: Renumber to conform to web content

Resolution URL: http://www.w3.org/WAI/UA/1999/05/wai-ua-telecon-19990519.html

First working draft: No reference

Comments: none

Key References: none

Issue 63: Checkpoint proposal from Marja to freeze time-sensitive content.

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0159.html

Date: Fri Jun 11 15:00:36 1999

Category of issue: Multimedia

Type of issue: none specified

Resolution summary: Limit freezing to active elements (see SMIL specs)

Resolution URL: http://www.w3.org/WAI/UA/1999/08/wai-ua-telecon-19990825.html

First working draft: No reference

Comments: none

Key References: none

Issue 64: Keyboard mapping among assistive technology tools

Name: Harvey Bingham

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JanMar/0363.html

Date: Fri, 26 Mar 1999 11:11:31 -0500

Category of issue: Navigation

Type of issue: Problem

Resolution summary: No change to spec since follow os conventions exists as a checkpoint (and mentions keyboard bindings explicitly).

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html

First working draft: No reference

Comments: none

Key References: none

Issue 65: Flicker frequencies of concern for photosensitive epilepsy

Name: Harvey Bingham

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0204.html

Date: Fri Jun 18 09:29:28 1999

Category of issue: Animations

Type of issue: Checkpoints

Resolution summary: The most serious frequencies are 6-30 Hz for seizures. Visual flicker should be less that 3 Hz (i.e.warnings, cursors, etc...)

Resolution URL: http://www.trace.wisc.edu/docs/nprm/pt_37b6.html

First working draft: No reference

Comments: none

Key References: none

Issue 66: Proposal to simplify check points in guidelines 7 (11 June WD)

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0207.html

Date: Fri Jun 18 09:37:03 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Refer to 16 July draft

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0265.html

First working draft: http://www.w3.org/WAI/UA/WAI-USERAGENT-19990716/

Comments: none

Key References: none

Issue 67: Adding guideline related to keyboard support in user agents

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0208.html

Date: Fri Jun 18 11:50:25 1999

Category of issue: Keyboard

Type of issue: Guidelines

Resolution summary: Ok to add keyboard guideline and Ian's proposed checkpoint

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html

First working draft: No reference

Comments: none

Key Reference URLs:

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0240.html

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0228.html

Issue 68: Must the user be able to do everything with the mouse that they can with keyboard?

Name: Harvey Bingham

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0204.html

Date: Tue Jun 29 16:10:20 1999

Category of issue: Keyboard

Type of issue: Issue

Resolution summary: No, use OS APIs for input devices.

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0018.html

First working draft: No reference

Comments:
Resoved by considering that by using standard APIs for input devices, allow any tools (e.g., onscreen keyboards) to be used. Don't require UA to implement an onscreen keyboard

Key References: none

Issue 69: Proposed Guideline for software consistency

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0236.html

Date: Tue Jul 6 11:42:47 1999

Category of issue: Orientation

Type of issue: Guidelines

Resolution summary: Add checkpoint only

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0003.html

First working draft: No reference

Comments: none

Key References: none

Issue 70: Recognizing paying links from micropayments markup

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0258.html

Date: Tue Jul 6 11:44:11 1999

Category of issue: Orientation

Type of issue: none specified

Resolution summary: Issue has already been resolved by the WAI PF working group

Resolution URL: Not resolved

First working draft: No reference

Comments:
Micropayments draft includes markup for paying links. What should UAGL say about this? Note; Not yet a Rec.

Key References: none

Issue 71: Titles for ABBR and ACRONYM elements

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999AprJun/0233.html

Date: Fri Jul 9 14:14:06 1999

Category of issue: Language

Type of issue: none specified

Resolution summary: Harevy Bingham will propose techniques for techniques document

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990915.html#action

First working draft: No reference

Comments:
Need to have a technique for the techniques document

Key References: none

Issue 72: What should UAs do to support author-supplied metadata?

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0090.html

Date: Sat Aug 7 17:40:37 1999

Category of issue: Metadata

Type of issue: Issue

Resolution summary: Include in techniques known meta data that is important for accessibility and recommend full implementation of W3C specs

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990915.html#action

First working draft: No reference

Comments:
Currently compiling a list of meta data and make sure we have appropriate examples in techniques document. Conference call with gl at: http://www.w3.org/WAI/GL/meetings/19990909.html#agenda The had no general ideas

Key References: none

Issue 73: Text rendering of client-side iamge maps

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0090.html

Date: Sat Aug 7 18:01:47 1999

Category of issue: Alternative content

Type of issue: Checkpoints

Resolution summary: Include technique in the techniques document

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990915.html

First working draft: No reference

Comments:
Should we have a checkpoint explicitly for text renderings of client-side image maps (e.g., using "title" in HTML) to match with WCAG 1.0 checkpoint 1.5? OR should this be a technique for checkpoint 1.2? Need a technique for technique document

Key References: none

Issue 74: Value of checkpoint on volume control

Name: Jon Gunderson/Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0063.html

Date: Sun Aug 8 16:03:33 1999

Category of issue: Multimedia

Type of issue: Checkpoints

Resolution summary: Volume control for user agents that render audio natively

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0153.html

First working draft: No reference

Comments:
Should checkpoint 6.12 (in 16 July draft) about control of volume be priority 1? Or dropped entirely since volume control done as OS level?

Key References: none

Issue 75: Does accessible doc checkpoint apply to non Web-based docs?

Name: David Poehlman

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0063.html

Date: Sun Aug 8 17:09:17 1999

Category of issue: Documentation

Type of issue: Checkpoints

Resolution summary: Ensure that there is an electronic version of the product documentation that conforms to WCAG 1.0

Resolution URL: http://www.w3.org/WAI/UA/1999/08/wai-ua-telecon-19990825.html

First working draft: No reference

Comments:
Refers to 3.1 in 16 July draft

Key References: none

Issue 76: How to get to frames when the user turns off the rendering of frames

Name: David Poehlman

Source URL: http://www.w3.org/WAI/UA/WAI-USERAGENT-19990716/#gl-feature-on-off

Date: Sun Aug 8 17:17:09 1999

Category of issue: Frames

Type of issue: Checkpoints

Resolution summary: Ian Jacons will proposed new wording for the checkpoint

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990915.html#action

First working draft: No reference

Comments:

• a) Ensure that alt content available when turned off.
• b) Important for screen reader users and some users with some cognitive impairments.

IJ: Ideas for next draft.

• a) For Guideline 4, add reminder to render alt content.
• b) Add rationale for frames.
• c) Add definition of "turn off a frame" to the document to distinguish from alternative renderings or navigation.

Key References: none

Issue 77: Validate conformance categories

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0093.html

Date: Sun Aug 8 18:28:18 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Consensus on only one type of user agent. There was a minority that felt that there should be a conformance means for "assistive technology" agents.

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0447.html

First working draft: No reference

Comments:
Proposed: Create a map of graphical desktop browsers and dependent UAs to test conformance division.

Key References: none

Issue 78: Review requirements for window spawning

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0212.html

Date: Tue Aug 10 12:38:08 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Provide better definition of spawned and allow user to control

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Checkpoint 5.11 in 9 August draft talks about turning on/off support for spawned windows. I propose that we rephrase this as "Ensure that users know when new windows are spawned or allow them to turn them off." The goal is to prevent disorienting behavior. This may be achieved by a number of mechanisms, such as a history mechanism, a warning mechanism, or turning off spawned windows. Refer to proposal to delete this checkpoint and ff. http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0212.html

Key Reference URLs:

   http://www.w3.org/WAI/UA/WAI-USERAGENT-19990809/

Issue 79: How do specialized browsers like pwWebSpeak and IBM Homepage Reader conform to the guidelines

Name: Rich Schwerdtfeger

Source URL: http://www.w3.org/WAI/UA/1999/07/wai-ua-telecon-19990721.html

Date: Mon Aug 16 15:17:19 1999

Category of issue: Conformance

Type of issue: Guidelines

Resolution summary: Consensus on only one type of user agent. There was a minority that felt that there should be a conformance means for "assistive technology" agents.

Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0447.html

First working draft: No reference

Comments:
Specialized browsers support speech and Braille primarily and therefore are not "graphical". While they are an assistive technology, they typically are not dependent on a "graphical" browser for rendering accessible information

Key References: none

Issue 80: Make audio output available as text

Name: Madeleine Rothberg

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0083.html

Date: Tue Aug 24 16:32:02 1999

Category of issue: Device Independence

Type of issue: Checkpoints

Resolution summary: Add text to guideline 1 related to using captioning or descriptive video information as an alternative output

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990922.html

First working draft: No reference

Comments:
> "And any output provided in audio should also be available in > text since most alternative output mechanisms rely on the presence > of system-drawn text on the screen."

Key References: none

Issue 81: Allow the user to turn on and off rendering of audio descriptions.

Name: Madeleine Rothberg

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0083.html

Date: Tue Aug 24 17:40:01 1999

Category of issue: Alternative content

Type of issue: Checkpoints

Resolution summary: Generalize Checkpoint 4.5 to continuous equivalents as used in SMIL note. (list each expected type) and Apply this language to related checkpoints.

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990922.html

First working draft: No reference

Comments: none

Key References: none

Issue 82: How to rendering text links for images in links that have no alt?

Name: Harvey Bingham

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0101.html

Date: Tue Aug 24 18:20:49 1999

Category of issue: Alternative content

Type of issue: Technique

Resolution summary: Reference ER groups "altifier" algorithms in the UA techniques document.

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990922.html

First working draft: No reference

Comments:
What to do with image with no alt text that's in a link.? How does this interact with 7.4 and 7.5? Worst case is an image map. We render part of the URL (the most we've got).

Key References: none

Issue 83: Split Checkpoint on voice characteristics?

Name: Jim Thatcher

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0163.html

Date: Fri Aug 27 16:51:02 1999

Category of issue: Speech

Type of issue: Checkpoints

Resolution summary: Combine volume with rate as a P1 and leave the rest a P3

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990922.html

First working draft: No reference

Comments:
Refers to 9 August version, checkpoint 6.15

Key References: none

Issue 84: Checkpoint on natural language applies to all UAs

Name: Kitch Barnicle

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0165.html

Date: Fri Aug 27 17:35:05 1999

Category of issue: Natural language

Type of issue: Checkpoints

Resolution summary: Apply to both grahical and dependent user agents

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990922.html

First working draft: No reference

Comments:
See Ian followup http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0257.html

Key References: none

Issue 85: Priority of checkpoint on language support

Name: Jim Thatcher

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0259.html

Date: Fri Aug 27 18:27:33 1999

Category of issue: Natural language

Type of issue: Checkpoints

Resolution summary: a) P1: Render according to language identification.
b) P3: For identified but unsupported languages, notify users of changes in language (when configured to do so).

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Refer also to [1] http://lists.w3.org/Archives/Public/w3c-wai-gl/1999AprJun/0112.html [2] http://lists.w3.org/Archives/Public/w3c-wai-gl/1999AprJun/0114.html

Key References: none

Issue 86: Should Guideline about support for W3C technologies be broadened or narrowed?

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0229.html

Date: Fri Aug 27 19:33:03 1999

Category of issue: Assistive technology compatibility

Type of issue: Guidelines

Resolution summary: IJ: Repropose Guideline text to include other technologies

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Proposed: Refer to [1] http://www.w3.org/WAI/UA/WAI-USERAGENT-19990809 We could either: a) Expand the scope of the guideline to something like "Support Open Specifications and Known Accessibility Features" We might add a checkpoint to the effect of "Support open standards", but I'm not convinced of the necessity. b) Reduce the scope of checkpoint 11.1 to be: "Implement accessibility features defined for supported W3C technologies."

Key References: none

Issue 87: Proposed wording change about user-control of highlight rendering

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0247.html

Date: Fri Aug 27 19:47:38 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Define "control" as "choose preferred behavior from predefined options".

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Issue is how much user control is necessary? Should this be color only?

Key References: none

Issue 88: Proposed wording change for checkpoint on access to selected content.

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0244.html

Date: Fri Aug 27 20:07:16 1999

Category of issue: Alternative content

Type of issue: Checkpoints

Resolution summary: IJ: Proposed
a) Move dependent-UA checkpoints to an informative appendix of the Guidelines.
b) Add checkpoint about requiring a selection (structured or unstructured).
c) People will review the next draft and decide whether the split is ok.

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Based on Thatch issue: What does selection mean? http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0110.html See also Charles proposal: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0245.html

Key References: none

Issue 89: Proposed changes in conformance based on interoperable UA and non-interoperable UA

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0365.html

Date: Thu Sep 16 08:28:39 1999

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Reviewed proposed items, see telecon minutes for details

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991006.html

First working draft: No reference

Comments: none

Key References: none

Issue 90: Development of a dependency list between UA and AU

Name: Charles McCathieNevile

Source URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990908.html#action

Date: Thu Sep 16 08:31:03 1999

Category of issue: Depdency with other W3C and WAI working groups

Type of issue: Guidelines

Resolution summary: Kitch and Jim compiled lists and they will be forwarded to the AU group

Resolution URL: http://www.w3.org/WAI/UA/1999/09/wai-ua-telecon-19990922.html

First working draft: No reference

Comments: none

Key Reference URLs:

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0362.html

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0361.html

Issue 91: Proposed reformulation of frames checkpoint

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0393.html

Date: Thu Sep 23 14:53:32 1999

Category of issue: Frames

Type of issue: Checkpoints

Resolution summary: a) Delete 4.12.
b) Mention frames in 3.1 Note on access to content
c) Put Ian's Note in 8.1 on frame navigation.

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 92: Proposed checkpoint about form orientation

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0395.html

Date: Thu Sep 23 15:04:17 1999

Category of issue: Forms

Type of issue: Checkpoints

Resolution summary: Move this to "AT appendix" (for review).

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 93: Proposed modification to definition of "applicable checkpoint"

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0396.html

Date: Thu Sep 23 15:05:12 1999

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Implement Ian's proposal on applicability.

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 94: Reenforcing the the use of standard keyboard APIs in guideline 2

Name: Charles McCathieNevile

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0417.html

Date: Fri Sep 24 11:20:14 1999

Category of issue: Keyboard

Type of issue: Guidelines

Resolution summary: leave Guidelines 2 since it such an important issue in GUI user interfaces

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key Reference URLs:

   http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0419.html

Issue 95: Proposed checkpoint: Choose from among style sheets

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0428.html

Date: Mon Sep 27 10:07:17 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Add checkpoint as a Priority 2.

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 96: Issues related to Checkpoint 2.1: Mapping of user agent functions to control mechanisms and memory demands related to sequential/direct access to functionalities

Name: Marja Koivunen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0437.html

Date: Sun Oct 3 14:20:23 1999

Category of issue: Keyboard

Type of issue: Guidelines

Resolution summary: Ian will ask maria to develop specific proposals for review by the group

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991006.html

First working draft: No reference

Comments: none

Key References: none

Issue 97: Questions about wording of document outline checkpoint

Name: Jim Thatcher

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0234.html

Date: Sun Oct 3 21:10:14 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Not resolved

Resolution URL: a) Leave 9.3 as is (no longer for dependent UAs).
b) Take note from 9.3 and make this a P3 checkpoint.

First working draft: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

Comments:
From 9 August version, 9.3 http://www.w3.org/WAI/UA/WAI-USERAGENT-19990809/ Thatch: The wording is not good. Don't we already have a 'navigate' by structural elements. Is this a technique for 8.6? CMN: I agree.

Key References: none

Issue 98: What does "appropriate" mean in "appropriate w3c recommendations"?

Name: Jim Thatcher

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0234.html

Date: Sun Oct 3 21:14:01 1999

Category of issue: Depdency with other W3C and WAI working groups

Type of issue: Checkpoints

Resolution summary: Being redefined as part of another issue, JT ok with redefinition

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 99: Priority of control of GUI layout should not be priority 1

Name: Jim Thatcher

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0234.html

Date: Sun Oct 3 21:15:01 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Dropped, no change

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Priority of 4.2 of 9 August version on configuration of user agent visual layout of controls should not be Priority 1.

Key References: none

Issue 100: Proposed Note on verifiability of some checkpoints

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0011.html

Date: Sun Oct 3 21:29:26 1999

Category of issue: Conformance

Type of issue: Problem

Resolution summary: Add IJ note

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
See proposed text

Key References: none

Issue 101: Wording of checkpoint on document change notification

Name: Kitch Barnicle

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0304.html

Date: Sun Oct 3 21:31:41 1999

Category of issue: Scripting events

Type of issue: Checkpoints

Resolution summary: no change

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Refers to: >10.1 Provide information about document and view changes (to the user and >through programming interfaces). [Priority 1]

Key References: none

Issue 102: List of problematic checkpoints.

Name: Jim Thatcher

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999JulSep/0234.html

Date: Sun Oct 3 21:33:44 1999

Category of issue: none specified

Type of issue: Checkpoints

Resolution summary: Issue cover in other issues

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments:
Detailed Issues list: 7.2 For dependent user agents. Ensure that the user has access to the content of an element selected by the user. The word "selected" gave me lots of problems. Since "selected" has a very different and very common meaning, I wish a different word or phrase could be found. I tried using "the current," rather than "selected by the user" and in HPR I think that works. 9.16 Identify a link selected by the user. 9.19 Identify a table selected by the user. 9.23 Make available the coordinates in the current table of a selected table cell 9.22 Identify the table containing a table cell selected by the user. 9.2 For dependent user agents. Provide the user with information about the number of viewports. Probably one example would clarify this for me. 9.10 Make available the number of links (to distinct targets) in a document. 9.11 Make available the number of visited links (to distinct targets) in a document. Why is this accessibility? Who cares about the number of visited links. And the requirement of distinct targets vs links seems out of line as a guideline. 9.17 Make available whether a chosen link (target) is local to the document. This does not seem to be an accessibility requirement. Does it have something to do with "downlevel" browsing configurations.

Key References: none

Issue 103: Proposed change to priority wording

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0029.html

Date: Mon Oct 4 11:28:16 1999

Category of issue: Conformance

Type of issue: none specified

Resolution summary: Adopt proposal: http://cmos-eng.rehab.uiuc.edu/ua-issues/issues-linear.html#103

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 104: Proposed additions to conformance claim requirements

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0031.html

Date: Mon Oct 4 11:29:29 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Adopt IJ proposal

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

First working draft: No reference

Comments: none

Key References: none

Issue 105: ACCESSKEY implementation issues

Name: Gregory Rosmaita

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0008.html

Date: Mon Oct 4 13:59:03 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Resolved not to try to specify behavior. User agent should document behavior and inform user of bindings

Resolution URL: http://www.w3.org/WAI/UA/1999/11/wai-ua-telecon-19991103.html

First working draft: No reference

Comments:
No group conensus on user agent priority for supporting the rendering of author supplied access key information. Will post the lack of consensus as last call issue.

Key References: none

Issue 106: Proposed Abstract revision

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0034.html

Date: Mon Oct 4 14:51:20 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Update document

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991027.html

First working draft: No reference

Comments: none

Key References: none

Issue 107: Proposed new checkpoint: 6.7 Support assistive technology accessibility standards defined for plug-in and virtual machine systems used by your browser. [priority 1]

Name: Rich Schwerdtfeger

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0082.html

Date: Fri Oct 8 10:50:19 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Add this as a note to existing checkpoint 6.3

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991020.html

First working draft: No reference

Comments: none

Key References: none

Issue 108: Proposed checkpoint for table summary information

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0092.html

Date: Mon Oct 18 16:40:32 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Ian will add checkpoint based on telecon discussion to working draft

Resolution URL: http://www.w3.org/WAI/UA/1999/11/wai-ua-telecon-19991103.html

First working draft: No reference

Comments: none

Key References: none

Issue 109: Proposed rewording of Checkpoints 1.1 and 1.6

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0098.html

Date: Mon Oct 18 16:58:09 1999

Category of issue: Device Independence

Type of issue: Checkpoints

Resolution summary: Integrate comments into next working draft

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991027.html

First working draft: No reference

Comments: none

Key References: none

Issue 110: Proposed changes to Guidelines 1, 2, and 11 re: keyboard

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0157.html

Date: Tue Oct 26 10:48:37 1999

Category of issue: Keyboard

Type of issue: Guidelines

Resolution summary: Accepted with modifications

Resolution URL: http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991027.html

First working draft: No reference

Comments: none

Key References: none

Issue 111 (Last Call): Proposal to make Checkpoint 6.1 have a relative priority

Name: Charles McCathieNevile

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0211.html

Date: Mon Nov 1 12:11:55 1999

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Resolved: Leave a P1.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-111

First working draft: No reference

Comments:
Leave current guideline with Priority 1, mark as an open issue for last call.

Key References: none

Issue 112 (Last Call): Split checkpoint 10.1 into two separate checkpoints for author and user agent input functionalities and mark as an issue during last call

Name: Ian Jacobs

Source URL: http://www.w3.org/WAI/UA/1999/11/wai-ua-telecon-19991103.html

Date: Thu Nov 4 13:11:20 1999

Category of issue: Keyboard

Type of issue: Checkpoints

Resolution summary: Keep checkpoints separate and at current priorities

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
Group could not reach consensus on:
1. Author and user agent input configuration information have the same importance for accessibility
2. Are author defined input information support by the user agent part of the UA functionality or separate functionality from the UA One proposal has been: a single P2 checkpoint. And from Martin Duerst: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0614.html > - 10.1/10.2: I personally feel that showing author-set > configurations is at least as important as user-set; > many (not all) users may be able to remember to their > own settings, while nobody will know author settings. Discussion 10 December in Austin http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-112 Resolution proposal by chair
http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0145.html
5 voted to accept proposal
3 voted to not accept the proposal
Chair overruled 3 objections and asked them to develop a minority opinon on the topic

Key Reference URLs:

   http://www.w3.org/WAI/UA/1999/10/wai-ua-f2f-199910-minutes.html

   http://www.w3.org/WAI/UA/1999/10/wai-ua-telecon-19991027.html

   http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0145.html

Issue 113 (Last Call): Deletion of Guideline 2: Support the Keyboard

Name: Bryan Campbell

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0254.html

Date: Wed Nov 10 13:13:05 1999

Category of issue: Keyboard

Type of issue: Guidelines

Resolution summary: Add a section to the checklist on the keyboard. Note that there is already a section on UI checkpoint.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-113

First working draft: No reference

Comments: none

Key References: none

Issue 114 (Last Call): How do requirements for APIs overlap (DOM? Platform standards? Provided by Tool)

Name: Rich Schwerdtfeger

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0314.html

Date: Tue Nov 16 10:44:54 1999

Category of issue: Assistive technology compatibility

Type of issue: Technique

Resolution summary: Delete 5.1 ; 5.2 ok (but clarify that meant for content) ; See minutes for rest

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-114

First working draft: No reference

Comments:
Refer to Mark Novak comments about how MSAA "works" when standard platform controls are used in an implementation. http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0453.html

Key References: none

Issue 115 (Last Call): Checkpoint to maintain relative font sizes?

Name: Al Gilman/Todd Fahrner

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0374.html

Date: Mon Nov 22 15:19:35 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: This is a technique for adjusting font sizes

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-115

First working draft: No reference

Comments: none

Key References: none

Issue 116 (Last Call): Non-editorial issues raised by Eric Hansen

Name: Eric Hansen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0409.html

Date: Wed Nov 24 08:20:14 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: See minutes 11/24/99

Resolution URL: http://www.w3.org/WAI/UA/1999/11/wai-ua-telecon-19991124.html

First working draft: No reference

Comments:
Eric's messages [1] http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0338.html [2] http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0337.html [3] http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0349.html

Key References: none

Issue 117 (Last Call): How are exception cases determined and by whom?

Name: Bridie Saccocio/Steve McAdoo (reply by Ian)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0360.html

Date: Tue Nov 30 09:33:29 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Add a statement that information about validation of claims will be found on the conformance page

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-117

First working draft: No reference

Comments: none

Key References: none

Issue 118 (Last Call): User Interface for text size (font size) control

Name: Todd Fahrner

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0372.html

Date: Tue Nov 30 09:38:06 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: Use OS controls that are available

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-118

First working draft: No reference

Comments:
1) Taken to PF. 2) AG feels should be in UAGL/UAT http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0374.html 3) Proposed checkpoint from Al's distillation of Todd's comments: 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.

Key References: none

Issue 119 (Last Call): Proposed narrowing of scope in definition of "applicability" (ALSO: Put back in conformance section? -IJ)

Name: Eric Hansen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0375.html

Date: Tue Nov 30 09:49:14 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Refer to ATAG definition of "applicability" and propose to list.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-119

First working draft: No reference

Comments:
Proposed change: "If a user agent offers a functionality, it must ensure that [CHANGE] people with disabilities [/CHANGE] have access to that functionality or an equivalent alternative." (my revised definition of "Applicable checkpoint"). This change from "all users" to "people with disabilities" is, in my view, essential because: 1. It keeps the UAAG document within scope. We have no authority except as it relates to accessibility, i.e., use by people with disabilities. 2. It may limit the unintended negative consequences by potential reducing (or minimizes increased burden) on developers. ALso: Since people can't find this definition, put back in conformance section.

Key References: none

Issue 120 (Last Call): The UAGL should pay more attention to UI accessibility

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 11:14:56 1999

Category of issue: User Interface Accessibility

Type of issue: Guidelines

Resolution summary: No changes, covered in a number of guidelines

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-120

First working draft: No reference

Comments: none

Key References: none

Issue 121 (Last Call): Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI)

Name: Earl Johnson/Peter Korn + Phill Jenkins

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 11:43:28 1999

Category of issue: User Interface Accessibility

Type of issue: Guidelines

Resolution summary: It's sufficient to identify UI/Content checkpoints within current Guidelines.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-121

First working draft: No reference

Comments:
Refer to Earl's proposal for creating two "buckets" within each Guideline: one for Content, one for UI. WOuld there be other buckets? http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0560.html

Key References: none

Issue 122 (Last Call): Proposed checkpoint related to input focus on controls

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 12:57:17 1999

Category of issue: User Interface Accessibility

Type of issue: Checkpoints

Resolution summary: Issue 122 is resolved with a note in 5.5

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-122

First working draft: No reference

Comments:
> Checkpoints for the UI - a major design access problem we run across is > windows that don't give an object input focus when they're made > activate. I'm not sure if it should be here or under guideline #7, #8, > or #9 but a checkpoint should say that a component needs to be assigned > input focus for the content -and- feature control portions of the UA > UI.

Key References: none

Issue 123 (Last Call): Proposed checkpoint to use standard UI components for the interface.

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 12:59:33 1999

Category of issue: User Interface Accessibility

Type of issue: Checkpoints

Resolution summary: Resolved: The new 5.3 covers this request., add earl's comments to techniques

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-123

First working draft: No reference

Comments: none

Key References: none

Issue 124 (Last Call): Should the Guidelines reference MSAA and JAAPI?

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 13:57:39 1999

Category of issue: Depdency with other W3C and WAI working groups

Type of issue: Issue

Resolution summary: Resolved to only list W3C specs right now

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-124

First working draft: No reference

Comments: none

Key References: none

Issue 125 (Last Call): To what APIs does 5.1 refer ( Provide accessible APIs to other technologies)

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 14:00:48 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: removed checkpoint 5.1

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209

First working draft: No reference

Comments: none

Key References: none

Issue 126 (Last Call): Proposed change in wording to 5.5 (Provide programmatic notification of changes to content and user interfacecontrols (including selection and focus).)

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 14:01:27 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Current wording is more general than proposed wording, but will talk about the types of interfaces that could be used to provide notification in the techniques document

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
Refer to proposal from JG and thread. http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0092.html

Key References: none

Issue 127 (Last Call): How to verify 5.7 (Provide programmatic exchange of information in a timely manner.)?

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 14:07:12 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Need better techniques to talk about the issue/add rationale on the importance of timely access

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments: none

Key References: none

Issue 128 (Last Call): Extend definition of focus to include GUI control focus

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 14:07:58 1999

Category of issue: User Interface Accessibility

Type of issue: none specified

Resolution summary: Clarify in Guidelines the two notions of focus (application focus v. content focus).

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-128

First working draft: No reference

Comments: none

Key References: none

Issue 129 (Last Call): Need to clarify 10.3 ("Allow the user to change and control the inputconfiguration. Users should be able to activate a functionality with a single-stroke (e.g., single-key, single voicecommand, etc.).)

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 16:04:03 1999

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: Allow the user to configure the user agent so that some functionalities may be activated with a single stroke (e.g., single key, single voice command, etc.).

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-129

First working draft: No reference

Comments:
Refer to Bryan Campbell's proposal for a Pri 1 checkpoint for single key access: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0530.html

Key References: none

Issue 130 (Last Call): Proposed rewording of 10.5: Avoid default> > input configurations that conflict with operating system navigation, control, and access conventions.

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 16:56:05 1999

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: No change.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-130

First working draft: No reference

Comments: none

Key References: none

Issue 131 (Last Call): Proposed change in wording of 10.8

Name: Earl Johnson/Peter Korn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0469.html

Date: Tue Nov 30 16:56:45 1999

Category of issue: User Interface Accessibility

Type of issue: none specified

Resolution summary: dd clarification to the document (e.g., to the glossary) that "user interface" means

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-131

First working draft: No reference

Comments:
Proposed: Allow the user to configure the graphical arrangement of user agent user interface controls.

Key References: none

Issue 132 (Last Call): Checkpoint 4.17 (Note): User should not be able to turn off default styles

Name: Liam Quinn

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0450.html

Date: Wed Dec 1 07:45:52 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Checkpoint 4.14 Allow the user to select from available author and user style sheets or to ignore them.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-132

First working draft: No reference

Comments: none

Key References: none

Issue 133 (Last Call): Priority of 10.1 compared to 10.3

Name: Jon Gardner

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0449.html

Date: Wed Dec 1 08:04:23 1999

Category of issue: Documentation

Type of issue: Checkpoints

Resolution summary: No change in priority

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991215.html

First working draft: No reference

Comments: none

Key References: none

Issue 134 (Last Call): Proposed modification of 10.3: "The controls mustbe user-selectable."

Name: Jon Gardner

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0449.html

Date: Wed Dec 1 08:06:15 1999

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: This is addressed by resolution of Issue 129.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-134

First working draft: No reference

Comments:
Refer also to comments by Martin Duerst http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0614.html > - 10.3: Single-stroke/single-key: Does this include modifiers > or not? There are in general not enough keys to have one > (unmodified) for each function. Proposed: We need to clarify that 10.3 does not refer to ALL functionalities being bound to a single key.

Key References: none

Issue 135 (Last Call): Add incremental forward/rewind for audio, video, speech?

Name: Scott Luebking

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0479.html

Date: Wed Dec 1 08:19:46 1999

Category of issue: Multimedia

Type of issue: Checkpoints

Resolution summary: Make 4.13 slightly more general to "advance" and "rewind"

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-135

First working draft: No reference

Comments: none

Key References: none

Issue 136 (Last Call): Proposal for checklist delivery (part of conformance)

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0404.html

Date: Wed Dec 1 08:49:30 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Provide a link in the current document and include what to date a claim

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
Refer to discussion at Austin ftf. Refer to Ian's proposed scheme: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0073.html Refer to discussion in GL http://lists.w3.org/Archives/Public/w3c-wai-gl/2000JanMar/0047.html

Key References: none

Issue 137 (Last Call): Use of terms for disabilities, impairment

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0449.html

Date: Wed Dec 1 09:46:34 1999

Category of issue: Editorial

Type of issue: Issue

Resolution summary: WAI CG chose not to use impairment

Resolution URL: http://lists.w3.org/Archives/Member/w3c-wai-cg/1999OctDec/0053.html

First working draft: No reference

Comments:
Comments also from Chuck Hitchcock: > Guideline 8: In the paragraph that follows the 3 bullet items, I would > change "learning disabilities" to "cognitive disabilities". This is a bit > broader and will include those who have orientation problems that are not > related to specific learning disabilities.

Key References: none

Issue 138 (Last Call): "Synchronized equivalent" v. "Continuous Equivalent"/ Proposed split of 2.5

Name: Eric Hansen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0337.html

Date: Wed Dec 1 09:51:00 1999

Category of issue: Multimedia

Type of issue: Issue

Resolution summary: Terminology changed, other issues forwarded to other groups for consideration, applicability clause can be applied to 2.6

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991222.html

First working draft: No reference

Comments:
Follow up in PF: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0459.html Opposing Comments from Marja: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0464.html Follow-up suggestions in tandem with WCAG http://lists.w3.org/Archives/Public/w3c-wai-gl/1999OctDec/0165.html Eric's proposed split: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0597.html Discussion in Austin http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-138

Key References: none

Issue 139 (Last Call): Need clarification of 4.11 (audio playback speed)

Name: T.V. Raman

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0476.html

Date: Wed Dec 1 09:57:13 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Change language to only refer to slowing down or deceleration

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991207.html

First working draft: No reference

Comments: none

Key References: none

Issue 140 (Last Call): Clarification on 2.3 required: how do you satisfy it if you don't support a language?

Name: Steven Pemberton

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0495.html

Date: Wed Dec 1 10:36:40 1999

Category of issue: Natural language

Type of issue: Checkpoints

Resolution summary: Proper I18N rendering of content is not an accessibility issue. Move checkpoint 2.2. to the section on ATs and talk about getting the info through the DOM.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-140

First working draft: No reference

Comments:
Refer also to comments from I18N Working Group http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0612.html

Key References: none

Issue 141 (Last Call): Need to qualify checkpoint 1.4 in same was as 1.1 is qualified re: "every"

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 12:24:24 1999

Category of issue: Device Independence

Type of issue: Checkpoints

Resolution summary: Agreed to use "special case" notes (editorial change)

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-141

First working draft: No reference

Comments: none

Key References: none

Issue 142 (Last Call): Checkpoint 1.5 (output device-independence) needs clarification.

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 12:28:59 1999

Category of issue: Device Independence

Type of issue: Checkpoints

Resolution summary: - Delete 9.1 and raise priority of 3.9 to P2 and change 1.5 to talk about redundancy

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
> 1.5 Says that all messages to the user must be available via all output > device APIs. [Priority 1] > That sounds like the UA must talk (to send messages out of the audio > channel) if it beeps (uses the audio channel for beeps). ?? Refer to ftf discussion http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-142

Key References: none

Issue 143 (Last Call): Proposed deletion of 2.6 since special case of 2.2

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 15:32:43 1999

Category of issue: Alternative content

Type of issue: Checkpoints

Resolution summary: The intention of 2.8 was to address equivalent audio tracks and therefore it's subsumed by 2.6 (for alternative equivalents).

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-143

First working draft: No reference

Comments: none

Key References: none

Issue 144 (Last Call): Editorial changes to some Guideline titles suggested

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 20:14:32 1999

Category of issue: Editorial

Type of issue: Guidelines

Resolution summary: Restore Guideline 6 and use guideline title changes in recent draft

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-144

First working draft: No reference

Comments:
> For convenience here are the guidelines in question. > > ----- > Guideline 3. Allow the user to turn off rendering or behavior that may > reduce accessibility > > Ensure that the user may turn off rendering or behavior specified by the > author that may obscure content or disorient the user. > > ----- > Guideline 6. Implement open specifications and their accessibility features > > In particular, implement W3C specifications when they are appropriate for a > task and follow accessibility guidelines for those specifications. > > ----- > Guideline 5. Observe operating system conventions and standard interfaces > > Communicate with other software (assistive technologies, the operating > system, plug-ins) through applicable interfaces and observe conventions for > the user interface, documentation, installation, etc. > > ----- > Guideline 9. Notify the user of content and viewport changes > > Alert users, in an output device-independent fashion, of changes to content > or the viewport. > > ----- > Guideline 10. Allow the user to configure the user agent > > Allow users to configure rendering, mouse, keyboard, the user interface, > etc. to facilitate daily use of the software. > > Compare these to the rest where the titles really are short enough or > telegraphic enough that they look like titles instead of guidelines.

Key References: none

Issue 145 (Last Call): Why is 3.7 Pri 1 and 3.10 Pri 3? (Re: blinking and flashing)

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 20:17:14 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Repose current 3.9 as priority 1

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991222.html

First working draft: No reference

Comments:
Refer to Austin discussion http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-145

Key References: none

Issue 146 (Last Call): Review priorities of 4.16, 5.2, 8.3, 8.5, 10.3, 10.6

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 21:19:02 1999

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: see minutes

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991215.html

First working draft: No reference

Comments: none

Key References: none

Issue 147 (Last Call): Need to review priority and wording of 5.8

Name: Gregg Vanderheiden/Gregory Rosmaita

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 21:38:17 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: In intro 1.2 on UI accessibility, discuss installation and updates; Add install to 1.1

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-147

First working draft: No reference

Comments:
For priority discussion, refer to Gregory's comments http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0562.html

Key References: none

Issue 148 (Last Call): Checkpoint 9.6: Does RETURN count as explicit submit?

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 21:39:02 1999

Category of issue: Forms

Type of issue: Checkpoints

Resolution summary: "Return" may mean explicit submission according to content. There are authoring issues. No change in UAGL.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-148

First working draft: No reference

Comments: none

Key References: none

Issue 149 (Last Call): 10.6: Wording (delete "and software") and Priority.

Name: Gregg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Thu Dec 2 21:50:00 1999

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: change to: Allow the user to configure the user agent in named profiles that may be shared by users.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-149

First working draft: No reference

Comments: none

Key References: none

Issue 150 (Last Call): Do APIs apply when the software is accessible on its own?

Name: Len Kasday

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0505.html

Date: Thu Dec 2 22:04:56 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Communication with ATs is fundamental to accessibility.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-150

First working draft: No reference

Comments: none

Key References: none

Issue 151 (Last Call): Proposed checkpoint: change audio rate without changing pitch

Name: Len Kasday

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0505.html

Date: Thu Dec 2 22:32:30 1999

Category of issue: Multimedia

Type of issue: Checkpoints

Resolution summary: This is a technique for the checkpoint about audio, animation control.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-151

First working draft: No reference

Comments: none

Key References: none

Issue 152 (Last Call): Proposed checkpoint: "Do not constrain the accessible output by constraints of the existingpresentation"

Name: Len Kasday

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0505.html

Date: Thu Dec 2 22:36:16 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: No change since content available through the DOM.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-152

First working draft: No reference

Comments:
> For example, even though a sighted user has to explicitly scroll to see a > page that is longer than a screen, a blind user should not have to worry > about scrolling a "screenful" vertically. Similarly, the blind user should > not have to scroll horizontally if the display is wider than the physical > screen, or scroll through selection lists a chunk at a a time.

Key References: none

Issue 153 (Last Call): Hold off on conformance until functional requirements between browsers/ATs more defined?

Name: Peter Meijer

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0511.html

Date: Sat Dec 4 10:10:05 1999

Category of issue: Conformance

Type of issue: none specified

Resolution summary: These guidelines will address general purpose user agents in a way that ATs can have access to information. We assume interoperability.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-153

First working draft: No reference

Comments: none

Key References: none

Issue 154 (Last Call): Proposed requirement that UAs give access to style sheet classes

Name: Len Kasday

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0555.html

Date: Sat Dec 4 11:19:36 1999

Category of issue: Natural language

Type of issue: Checkpoints

Resolution summary: Add exposure of class information as a technique to 4.14

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-154

First working draft: No reference

Comments:
Len's proposed wording (from private email): Give "access to semantic associations to style sheet classes"

Key References: none

Issue 155 (Last Call): Propose change of priorities for checkpoints 5.3 (r/w access) and 10.3 (single key)

Name: Hakon Wium Lie

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0529.html

Date: Sat Dec 4 13:30:58 1999

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: * Move first two sentences from 1.4 to note for 10.7; * Add a note about single key access to 10.7; * Add a cross-reference from 1.4 to 10.7

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991215.html

First working draft: No reference

Comments:
Refer also to Gregory Rosmaita's proposal to split checkpoint in two: higher priority for read, lower for write. http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0551.html Refer to Austin ftf discussion of single stroke in put (issue 129) http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-129

Key References: none

Issue 156 (Last Call): Propose change in priority of 5.6 (P1 -> P2)

Name: Hakon Wium Lie

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0529.html

Date: Sat Dec 4 13:32:06 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Leave as priority 1 with no changes

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000105.html

First working draft: No reference

Comments: none

Key References: none

Issue 157 (Last Call): Correct reference to XSL in checkpoint 6.2 since only a Working Draft.

Name: Hakon Wium Lie

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0529.html

Date: Sat Dec 4 13:33:28 1999

Category of issue: Depdency with other W3C and WAI working groups

Type of issue: Checkpoints

Resolution summary: Remove XSL from the list in 6.2

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-157

First working draft: No reference

Comments: none

Key References: none

Issue 158 (Last Call): Propose priority change (1 to 2) for checkpoint 4.1 (control of font family)

Name: Richard Premack

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0540.html

Date: Sat Dec 4 15:10:37 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Leave as P1

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000113.html

First working draft: No reference

Comments:
Resolved at 5 Jan teleconf to change to P2 http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000105.html Objections from Jon and David Poehlman

Key References: none

Issue 159 (Last Call): Propose raise priority of 4.13 to Priority 1

Name: Richard Premack

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0540.html

Date: Sat Dec 4 15:29:25 1999

Category of issue: User-control of Style

Type of issue: Checkpoints

Resolution summary: Move "start, stop, pause, rewind, advance" to P1.

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000105.html

First working draft: No reference

Comments: none

Key References: none

Issue 160 (Last Call): Delete checkpoints 7.3 and 8.2 (related to tables) since too vague

Name: Microsoft IE Team

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0590.html

Date: Sat Dec 4 15:31:31 1999

Category of issue: Tables

Type of issue: Checkpoints

Resolution summary: Merge 7.3 into 7.7 as P2 (since content available per 2.1). Mention tables explicitly in 7.7. ; Leave 8.1 as P1. Add note about DOM. Ensure sufficient information for ATs to get contextual information for the table.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-160

First working draft: No reference

Comments: none

Key References: none

Issue 161 (Last Call): Raise priority of 8.8 to P2 (highlighting and identifying selection/focus)

Name: Richard Premack

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0540.html

Date: Sat Dec 4 16:39:43 1999

Category of issue: User Interface Accessibility

Type of issue: Checkpoints

Resolution summary: Raise to P2.

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000105.html

First working draft: No reference

Comments: none

Key References: none

Issue 162 (Last Call): Raise priority of 8.9 (consistency in configs) to P2.

Name: Richard Premack

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0540.html

Date: Sat Dec 4 17:13:53 1999

Category of issue: User Interface Accessibility

Type of issue: Checkpoints

Resolution summary: Delete 8.9 and 1)Add a P2 checkpoint in G11 about documenting changes 2)Add a technique to config checkpoint about compatibility modes.

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000112.html

First working draft: No reference

Comments: none

Key References: none

Issue 163 (Last Call): Proposed new checkpoint on "Favorites" functionality

Name: Richard Premack

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0540.html

Date: Sat Dec 4 17:14:38 1999

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Not an accessibility issue

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-163

First working draft: No reference

Comments: none

Key References: none

Issue 164 (Last Call): Proposed change to wording of 4.8 in last call UAGL.

Name: Madeleine Rothberg

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0539.html

Date: Sat Dec 4 17:19:15 1999

Category of issue: Multimedia

Type of issue: Checkpoints

Resolution summary: Merge checkpoints add note about distortion

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991207.html

First working draft: No reference

Comments: none

Key References: none

Issue 165 (Last Call): Add information about system level flags to 5.2

Name: Wendy Chisholm

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0538.html

Date: Sat Dec 4 17:20:02 1999

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: 5.8 covers Wendy's requirement. No change.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-165

First working draft: No reference

Comments: none

Key References: none

Issue 166 (Last Call): Review priority of 10.5 (default configs that interfere with OS conventions)

Name: Wendy Chisholm

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0538.html

Date: Sat Dec 4 18:22:34 1999

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: Change 10.5 to P1 "Avoid default input configurations that interfere with operating system accessibility conventions." and Move first sentence of note afterwards to techniques for 5.6

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000112.html

First working draft: No reference

Comments: none

Key References: none

Issue 167 (Last Call): Proposed checkpoint to allow users to turn on/off multilingual support.

Name: Mark Hakkinen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0543.html

Date: Sat Dec 4 19:02:15 1999

Category of issue: Speech

Type of issue: Checkpoints

Resolution summary: Proposed: no change since this is an implementation issue.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-167

First working draft: No reference

Comments:
If a standard API is not available, then the UA would still be able to conform.

Key References: none

Issue 168 (Last Call): Checkpoint 2.7: Add object name in addition to type.

Name: Mark Hakkinen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0543.html

Date: Sat Dec 4 19:09:00 1999

Category of issue: Alternative content

Type of issue: Checkpoints

Resolution summary: Changed text to 2.4: When no text equivalent has been supplied for an object, make available author-supplied information to help identify the object (e.g., object type, file name, etc.).

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-168

First working draft: No reference

Comments:
What if the resource is not easily nameable (e.g., the URI is part of a query to a database)? (The same argument may be made for object type, but there may be more information, e.g., "type" attribute HTTP headers, etc. to identify object type).

Key References: none

Issue 169 (Last Call): What UI is required for turning on/off features that may impede accessibility?

Name: Mark Hakkinen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0543.html

Date: Sat Dec 4 19:18:04 1999

Category of issue: User Interface Accessibility

Type of issue: Checkpoints

Resolution summary: Suggest UI for accessibility be semantic in nature (so that average users will understand how to turn off blinking without knowing HTML.

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-169

First working draft: No reference

Comments:
I'd suggest that if the user interface here is designed with accessibility in mind, the user should not have to know about the object technologies. "Please turn off blinking things" would be a convenient request to the user agent. If the user agent allows the user to turn off the objects through other means (e.g., by turning off scripts), then this would also be sufficient, but the user agent should document that this is how the user can achieve this particular goal.

Key References: none

Issue 170 (Last Call): How can UAs "stay" accessible when there is a mass of inaccessible content?

Name: Mark Hakkinen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0543.html

Date: Sat Dec 4 19:19:02 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Not limited to accessible content

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210#issue-170

First working draft: No reference

Comments:
From Mark: > My suggested policy (and one that I would certainly include in any fine > > print regarding conformance), is that the content is only certified > > accessible using my UA IF the content being rendered meets the WAI Content > > Authoring Guidelines. Of course my UA will do the best it can with > > inaccessible content, but I cannot guarantee accessibility to all content. > > Can this be expressed clearly in the Guidelines where conformance is > > discussed?

Key References: none

Issue 171 (Last Call): 3.4: What does natively rendering audio mean?

Name: Greg Vanderheiden

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0507.html

Date: Sun Dec 5 11:41:13 1999

Category of issue: Multimedia

Type of issue: Checkpoints

Resolution summary: Remove term and combine multi-media checkpoints

Resolution URL: http://www.w3.org/WAI/UA/1999/12/wai-ua-telecon-19991207.html

First working draft: No reference

Comments:
> GV#13 ----------------------------- > 3.4 > What does natively rendering audio mean? A browser can't make a sound > except by doing it through the speaker. Does this refer to directly > driving the speaker -- not through the operating system? Is that > possible anymore? Does anyone do that? > > Techniques document should explain what "natively rendering audio" means.

Key References: none

Issue 172 (Last Call): Some clarification required in 1.1

Name: Earl Johnson/Wendy Chisholm

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0478.html

Date: Sun Dec 5 15:42:32 1999

Category of issue: Device Independence

Type of issue: Checkpoints

Resolution summary: Simplify Checkpoint 1.1 (Ian will proposed to the list)

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-172

First working draft: No reference

Comments:
Refer also to Wendy's comment from http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0544.html 1. Checkpoint 1.1 I found it very confusing to have so many special cases for checkpoint 1.1. Parts of the checkpoint are too generalized. I think it would be hard to determine when it was satisfied. Therefore, I suggest breaking it out into X number of separate, stronger checkpoints.

Key References: none

Issue 173 (Last Call): Proposed revision of "native" to account for OS features

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0603.html

Date: Sun Dec 5 17:04:15 1999

Category of issue: Conformance

Type of issue: Issue

Resolution summary: Accept proposal from Ian: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0603.html

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-173

First working draft: No reference

Comments: none

Key References: none

Issue 174 (Last Call): Natural language identification issues.

Name: Martin Duerst/I18N

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0612.html

Date: Mon Dec 6 07:41:44 1999

Category of issue: Natural language

Type of issue: Checkpoints

Resolution summary: Not an accessibility issue

Resolution URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991209#issue-174

First working draft: No reference

Comments:
Refer to proposals by Ian http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0619.html

Key References: none

Issue 175 (Last Call): Proposed raise (to P1) of checkpoint 4.18

Name: Terry Sullivan

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0608.html

Date: Mon Dec 6 09:08:34 1999

Category of issue: none specified

Type of issue: none specified

Resolution summary: 1)Leave P2 2)Move "SMIL" example in Note to techniques. (Ian to simplify) 3)Add cross-ref from 4.15 to 9.1

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000112.html

First working draft: No reference

Comments:
First, regarding Guideline 4.18, user control over UA-spawned viewports: seems to me that this needs to be a Priority 1 guideline. Currently, UA-spawned viewports "break" the history mechanism completely, and they provide the user with no cue(s) for understanding why basic UA functionality has suddenly stopped working. Further, I can't see how it'd be possible to implement Guideline 7.2 (a Priority 1) without *also* implementing 4.18; a promotion is clearly in order.

Key References: none

Issue 176 (Last Call): Proposed change in priority (P3 to P2) for checkpoint 8.7 (link information)

Name: Terry Sullivan

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0608.html

Date: Mon Dec 6 09:10:48 1999

Category of issue: Metadata

Type of issue: Checkpoints

Resolution summary: 1) Add (back the old) checkpoint for visited/unvisited links P2. If you don't have access to that information is to follow a link and then return. For complex pages, this becomes an unreasonable burden for people with non-graphical browsers or cognitive disabilities. 2) Leave 8.3 and 8.7 as is (removing visited).

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000112.html

First working draft: No reference

Comments:
> Second, regarding Guideline 8.7, user control over information > regarding links: again, I wonder if a promotion (to a Priority > 2) isn't in order. It's easy to imagine several scenarios in > which user control over link information would be crucial to > maintaining the overall "visibility of system status," which, > in turn has been extensively documented as a key element in > software usability. For example, consider UAs that do not > support a particular scripting language; a page full of links > that, in turn, rely on that scripting language will be > utterly unusable, and the user needs the ability to discover > *why* the page in question is "broken." >

Key References: none

Issue 177: User control of current focus change and notification.

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210

Date: Mon Dec 13 17:08:24 1999

Category of issue: Orientation

Type of issue: Issue

Resolution summary: Leave current checkpoint and create a new checkpoint tp address the issues discussed on the telecon

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments: none

Key References: none

Issue 178: In 10.1 and 10.2 what does communicate through an API mean

Name: Jon Gunderson

Source URL: http://www.w3.org/WAI/UA/1999/12/ftf-19991210

Date: Tue Dec 14 06:32:51 1999

Category of issue: Keyboard

Type of issue: Checkpoints

Resolution summary: Remove references to API from the checkpoints

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
Refer to proposal from JG: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0093.html

Key References: none

Issue 179: Priority of 5.8 should be 1

Name: Alan Cantor

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0676.html

Date: Fri Dec 17 15:20:15 1999

Category of issue: OS Conventions

Type of issue: Checkpoints

Resolution summary: Consensus was that it was a P2

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000113.html

First working draft: No reference

Comments:
Last call comment raised by EOWG about 10.8 of http://www.w3.org/TR/1999/WD-WAI-USERAGENT-19991105/

Key References: none

Issue 180: 10.8 should be priority 2

Name: Alan Cantor

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0676.html

Date: Fri Dec 17 15:48:42 1999

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: Due to lack of specificity on what are specific requirements for a higher priority, group resolved to leave at Priority 3 until new information is available

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
Raised in EO WG last call review (after the deadline)

Key References: none

Issue 181: Request for a wrapper note designed for AT developers explaining relation to guidelines

Name: EO WG

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0676.html

Date: Fri Dec 17 15:51:48 1999

Category of issue: Supporting materials

Type of issue: Issue

Resolution summary: Coordinate with EO in the preparation of the document

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
> - may need a friendly wrapper or lead-in Web page specifically for > assistive technology developers, to explain relevance and focus of the UAAG.

Key References: none

Issue 182: Should searching equivalent text be an AT responsibility

Name: UAWG

Source URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000106.html

Date: Thu Jan 6 15:20:18 2000

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Consensus that searching is important for accessibility in all user agents

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000113.html

First working draft: No reference

Comments: none

Key References: none

Issue 183: Proposed rewording to checkpoint 7.5 (search alt content)

Name: Jon Gunderson/Gregory Rosmaita

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0038.html

Date: Mon Jan 10 12:30:46 2000

Category of issue: Navigation

Type of issue: Checkpoints

Resolution summary: Adopt proposal: Checkpoint 7.5 Allow the user to search for rendered text content, including rendered text equivalents.

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000113.html

First working draft: No reference

Comments:
Checkpoint 7.5 Allow the user to search for rendered text content, including text equivalents rendered in place of or simultaneously with the primary content.

Key References: none

Issue 184: Proposed simplification to checkpoint 1.1 (device-independent access)

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0757.html

Date: Tue Jan 11 08:46:01 2000

Category of issue: Device Independence

Type of issue: Checkpoints

Resolution summary: Adopt changes in proposal

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000113.html

First working draft: No reference

Comments: none

Key References: none

Issue 185: clarification of "single key" access

Name: Bryan Campbell

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0756.html

Date: Tue Jan 11 08:47:02 2000

Category of issue: Keyboard

Type of issue: Checkpoints

Resolution summary: Accept Ian proposal to split the checkpoint into two separate checkpoints

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments:
Refer to Bryan Campbell clarification http://lists.w3.org/Archives/Public/w3c-wai-ua/1999OctDec/0756.html Refer to Dick Brown proposal http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0100.html

Key References: none

Issue 186: Proposed removal of Note in 2.1

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0106.html

Date: Sat Jan 15 16:33:12 2000

Category of issue: Alternative content

Type of issue: Technique

Resolution summary: Remove note

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000119.html

First working draft: No reference

Comments: none

Key References: none

Issue 187: Proposed change in wording to 1.6 (profiles)

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0109.html

Date: Sat Jan 15 16:34:44 2000

Category of issue: Configuration

Type of issue: Checkpoints

Resolution summary: Accept Ian's proposal

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000119.html

First working draft: No reference

Comments: none

Key References: none

Issue 188: Add definition of disability? (to CG)

Name: Phill Jenkins

Source URL: http://lists.w3.org/Archives/Member/w3c-wai-cg/1999OctDec/0058.html

Date: Sat Jan 15 16:42:06 2000

Category of issue: Definition

Type of issue: none specified

Resolution summary: We will link to any document developed

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000120.html

First working draft: No reference

Comments: none

Key References: none

Issue 189: Proposed change to checkpoint 2.3 (missing alt info)

Name: Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0105.html

Date: Sat Jan 15 16:59:13 2000

Category of issue: Alternative content

Type of issue: none specified

Resolution summary: Accept Ian's proposal

Resolution URL: http://www.w3.org/WAI/UA/2000/01/wai-ua-telecon-20000119.html

First working draft: No reference

Comments: none

Key References: none

Issue 190 (Candidate Recommendation): Reduce the scope of 5.1 to say "write access only for that which you can do through the UI."

Name: Hakon Lie (through Ian Jacobs)

Source URL: http://www.w3.org/WAI/UA/2000/02/wai-ua-telecon-20000203.html

Date: Fri Feb 4 16:43:51 2000

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Split checkpoint 5.1 into read and UI write

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000301.html

First working draft: No reference

Comments:
Full read access DOM and write to UI controls

1. Requires modifying new checkpoint to read only

2. Checkpoint A. Provide programatic read access to content by conforming to DOM level 2 core and HTML modules and exporting... [Priority 1]

3. Checkpoint B. Provide programatic read and write to author supplied user interface controls by conforming to DOM level 2 core and HTML modules and exporting... [Priority 1]

Key References: none

Issue 191 (Candidate Recommendation): Does a pause function satisfy checkpoint 2.2?

Name: RealNetworks (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 09:57:16 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: The user needs to be able to configure the user agent to pause automatically when the time dependent information is rendered

Resolution URL: http://www.w3.org/WAI/UA/2000/02/wai-ua-telecon-20000210.html

First working draft: No reference

Comments:
Denis Anson took and action item to make this clearer in the techniques document

Key References: none

Issue 192 (Candidate Recommendation): Does hiding video satisfy checkpoint 3.3

Name: Real Networks (through Charles McCathieNevile )

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:00:09 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Yes. There are many techniques to satisft this checkpoint and this would be an acceptable technique

Resolution URL: http://www.w3.org/WAI/UA/2000/02/wai-ua-telecon-20000210.html

First working draft: No reference

Comments: none

Key References: none

Issue 193 (Candidate Recommendation): In the case of animations, does checkpoint 4.5 mean a requirement to step through or slow the speed as well as being able to turn it off?

Name: Real Networks (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:01:15 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: The requirement is only to slow the rate of presentation of MM. Stepping through MM is part of checkpoint 4.6. There is not requirement in this checkpoint to turn off.

Resolution URL: http://www.w3.org/WAI/UA/2000/02/wai-ua-telecon-20000210.html

First working draft: No reference

Comments: none

Key References: none

Issue 194 (Candidate Recommendation): In a timed presentation does checkpoint 7.2 mean return to the time that the user was at in a previous MM rendering

Name: Real Networks (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:02:18 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Add to techniques synchronized MM and the concept of space and time

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000301.html

First working draft: No reference

Comments:
Proposed resolution:
1. Only for synchronized MM
2. Includes both space and time

Key References: none

Issue 195 (Candidate Recommendation): Problems understanding checkpoint 1.5

Name: Microsoft (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:03:54 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Modify checkpoint to require at least one text version for UA messages

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000301.html

First working draft: No reference

Comments: none

Key References: none

Issue 196 (Candidate Recommendation): It is unclear to developers how they know they conform to Checkpoint 6.2: Conform to W3C specifications when they are appropriate

Name: Microsoft (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:04:41 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Changed wording slightly

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 197 (Candidate Recommendation): Not clear with the scope of user preferences is in Checkpoint 10.7

Name: Microsoft (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:05:53 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Minimum set is configuration defined in our document

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 198 (Candidate Recommendation): How much information needs to be provided to satisfy Checkpoint 8.4

Name: Microsoft (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:06:58 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Minimum is author supplied information

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 199 (Candidate Recommendation): Poor wording of checkpoint 10.8, it is not clear what the requirement is to improve accessibility

Name: Microsoft (throughCharles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0243.html

Date: Mon Feb 7 10:07:52 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Minimum required are configuration options in UAGL

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 200 (Candidate Recommendation): Checkpoint 5.5, developers not unclear on how they know they have satisfied this checkpoint

Name: Microsoft (through Charles McCathieNevile)

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0280.html

Date: Mon Feb 7 11:48:10 2000

Category of issue: Conformance

Type of issue: Checkpoints

Resolution summary: Leave it and add a note

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 201 (Candidate Recommendation): 5.5 "Ensure that programmatic exchanges proceed in a timely manner" should be a priority 1

Name: Glen Gordon

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0309.html

Date: Thu Feb 17 14:37:43 2000

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Add reference to 2.1 about dynamic content and no change priority for 5.5

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 202 (Candidate Recommendation): User agent configuration to render NOFRAMES content

Name: Gregory J. Rosmaita

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0128.html

Date: Thu Feb 17 14:43:38 2000

Category of issue: Frames

Type of issue: Issue

Resolution summary: Add note discussed at Redmond FTF on NOFRAMES

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 203 (Candidate Recommendation): Checkpoint for access to content for non-HTML or non-XML WWW documents (i.e. Shockwave)

Name: Philippe Le Hegaret/Ian Jacobs

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0338.html

Date: Fri Feb 18 13:32:10 2000

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Add checkpoint for general access to content

Resolution URL: http://www.w3.org/WAI/UA/2000/02/wai-ua-telecon-20000224.html

First working draft: No reference

Comments: none

Key References: none

Issue 204 (Candidate Recommendation): Add collated text to Checkpoint 2.6 and 4.8 or create a new checkpoint at lower priority

Name: Eric Hansen

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0343.html

Date: Wed Feb 23 15:29:50 2000

Category of issue: Multimedia

Type of issue: Checkpoints

Resolution summary: Add collated text to the checkpoints 2.6 and 4.8

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 205 (Candidate Recommendation): Timing issues related to AT missing or not being synchronized to document changes

Name: Charles McCathieNevile

Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2000JanMar/0343.html

Date: Thu Feb 24 15:07:16 2000

Category of issue: Assistive technology compatibility

Type of issue: Checkpoints

Resolution summary: Add note to 2.1 and look at resolution of Issue CR#200

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Issue 206 (Candidate Recommendation): Precise specification of what parts of DOM are required

Name: Philippe Le Hegaret

Source URL: http://www.w3.org/WAI/UA/2000/02/wai-ua-telecon-20000217.html

Date: Thu Feb 24 15:16:52 2000

Category of issue: none specified

Type of issue: none specified

Resolution summary: Include only Core and HTML at P1; Include CSS and Style at P3

Resolution URL: http://www.w3.org/WAI/UA/2000/03/wai-ua-telecon-20000302.html

First working draft: No reference

Comments: none

Key References: none

Index of Issues by Category

Conformance

WD#1: Use subgrouping of checkpoints for conformance for assistive technology and desktop graphical user agents (Resolved)

WD#77: Validate conformance categories (Resolved)

WD#79: How do specialized browsers like pwWebSpeak and IBM Homepage Reader conform to the guidelines (Resolved)

WD#89: Proposed changes in conformance based on interoperable UA and non-interoperable UA (Resolved)

WD#93: Proposed modification to definition of "applicable checkpoint" (Resolved)

WD#100: Proposed Note on verifiability of some checkpoints (Resolved)

WD#103: Proposed change to priority wording (Resolved)

LC#111: Proposal to make Checkpoint 6.1 have a relative priority (Resolved)

LC#117: How are exception cases determined and by whom? (Resolved)

LC#119: Proposed narrowing of scope in definition of "applicability" (ALSO: Put back in conformance section? -IJ) (Resolved)

LC#136: Proposal for checklist delivery (part of conformance) (Resolved)

LC#146: Review priorities of 4.16, 5.2, 8.3, 8.5, 10.3, 10.6 (Resolved)

LC#150: Do APIs apply when the software is accessible on its own? (Resolved)

LC#153: Hold off on conformance until functional requirements between browsers/ATs more defined? (Resolved)

LC#155: Propose change of priorities for checkpoints 5.3 (r/w access) and 10.3 (single key) (Resolved)

LC#170: How can UAs "stay" accessible when there is a mass of inaccessible content? (Resolved)

LC#173: Proposed revision of "native" to account for OS features (Resolved)

CR#191: Does a pause function satisfy checkpoint 2.2? (Resolved)

CR#192: Does hiding video satisfy checkpoint 3.3 (Resolved)

CR#193: In the case of animations, does checkpoint 4.5 mean a requirement to step through or slow the speed as well as being able to turn it off? (Resolved)

CR#194: In a timed presentation does checkpoint 7.2 mean return to the time that the user was at in a previous MM rendering (Resolved)

CR#195: Problems understanding checkpoint 1.5 (Resolved)

CR#196: It is unclear to developers how they know they conform to Checkpoint 6.2: Conform to W3C specifications when they are appropriate (Resolved)

CR#197: Not clear with the scope of user preferences is in Checkpoint 10.7 (Resolved)

CR#198: How much information needs to be provided to satisfy Checkpoint 8.4 (Resolved)

CR#199: Poor wording of checkpoint 10.8, it is not clear what the requirement is to improve accessibility (Resolved)

CR#200: Checkpoint 5.5, developers not unclear on how they know they have satisfied this checkpoint (Resolved)

Assistive technology compatibility

WD#2: Recommend full implmentation of DOM level 1 for AT compatibility (Resolved)

WD#4: Use accessibility API and OS conventions for compatibility with AT (Resolved)

WD#5: User agents should provide information to AT on changes to the document object, selection, focus or system caret (Resolved)

WD#6: Provide a means for AT to change the DOM, selection, focus and/or system caret (Resolved)

WD#7: Provide a means for AT to simulate WWW document events (Resolved)

WD#8: Provide a means for AT to simulate user interface (non-WWW content) controls (Resolved)

WD#9: Require timely exchange of information between user agents and AT for rendering synchronization (Resolved)

WD#10: Use OS conventions and accessibility settings in interface design, configuration, product installation, and documentation. (Resolved)

WD#50: Modify Guideline 7.1 (Resolved)

WD#86: Should Guideline about support for W3C technologies be broadened or narrowed? (Resolved)

LC#114: How do requirements for APIs overlap (DOM? Platform standards? Provided by Tool) (Resolved)

LC#125: To what APIs does 5.1 refer ( Provide accessible APIs to other technologies) (Resolved)

LC#126: Proposed change in wording to 5.5 (Provide programmatic notification of changes to content and user interfacecontrols (including selection and focus).) (Resolved)

LC#127: How to verify 5.7 (Provide programmatic exchange of information in a timely manner.)? (Resolved)

LC#147: Need to review priority and wording of 5.8 (Resolved)

LC#156: Propose change in priority of 5.6 (P1 -> P2) (Resolved)

LC#165: Add information about system level flags to 5.2 (Resolved)

CR#190: Reduce the scope of 5.1 to say "write access only for that which you can do through the UI." (Resolved)

CR#201: 5.5 "Ensure that programmatic exchanges proceed in a timely manner" should be a priority 1 (Resolved)

CR#203: Checkpoint for access to content for non-HTML or non-XML WWW documents (i.e. Shockwave) (Resolved)

CR#205: Timing issues related to AT missing or not being synchronized to document changes (Resolved)

Navigation

WD#3: What should UAs do with recognize navigation bars? (Resolved)

WD#11: Move to the next element with the same attributes and element type (Resolved)

WD#15: Sequentially navigate between active elements (Resolved)

WD#16: Sequentially navigate to only link elements (Resolved)

WD#17: Sequentially navigate to only form controls in a document (Resolved)

WD#18: Sequentailly navigate to only elements with long descriptions (longdesc attribute or OBJECT content) (Resolved)

WD#20: Sequentially navigate header elements (Resolved)

WD#21: Search for link based on its text content (Resolved)

WD#22: Sequentially navigate between forms in a document (Resolved)

WD#23: Search for a form control based on text content (Resolved)

WD#24: Search for a form control based on its attribute values (i.e. label or control type) (Resolved)

WD#25: Sequentially navigate to all elements (block level) (Resolved)

WD#26: Search for an element based on its text content (Resolved)

WD#27: Move to the next element in the document tree as defined by DOM (Resolved)

WD#28: Move to the child level element of the current element in the document tree (Resolved)

WD#29: Move to the next (or previous) sibling element in the document tree (Resolved)

WD#30: Move to the parent element of the current element in the document tree (Resolved)

WD#38: Search for a link based on its attribute value (Resolved)

WD#40: What types of navigation commands support visually impaired users navigating a unfamilar document? (Resolved)

WD#41: What types of navigation commands support a user with a visual impairment navigating a familar document? (Resolved)

WD#42: How do users navigate documents with embedded list elements? (Resolved)

WD#43: Navigation and activation of elements with ACCESSKEY attributes defined (Resolved)

WD#44: Navigation of time dependent mult-mdeia elements rendered to the user (more than just stop, rewind and fast forward) (Resolved)

WD#57: Which attributes can be used to search for an element based on attribute values (Resolved)

WD#60: Need to give user final control over accesskey settings (Resolved)

WD#64: Keyboard mapping among assistive technology tools (Resolved)

WD#66: Proposal to simplify check points in guidelines 7 (11 June WD) (Resolved)

LC#163: Proposed new checkpoint on "Favorites" functionality (Resolved)

WD#182: Should searching equivalent text be an AT responsibility (Resolved)

WD#183: Proposed rewording to checkpoint 7.5 (search alt content) (Resolved)

MathML

WD#12: Recommend full implmentation of MathML (Resolved)

WD#13: Provide keyboard access to MathML similar to forms (Resolved)

WD#14: MathML objects should be included as part of the document tree (Resolved)

Scripting events

WD#19: Sequentially navigate to elements with explicit scripting event handlers (Resolved)

WD#45: Include a specific checkpoint to allow user to simulate scripting events (Resolved)

WD#46: Allow user to configure active elements to include scripting events (Resolved)

WD#47: Include scripting events in checkpoint on access to active elements (Resolved)

WD#54: User notification of document changes due to scripting and other events (Resolved)

WD#101: Wording of checkpoint on document change notification (Resolved)

Tables

WD#31: Allow users to navigate between cells of a table (Resolved)

WD#32: Allow the user to view one table cell at a time (Resolved)

WD#33: Allow the user to view header information associated with a cell (Resolved)

WD#34: Allow the user to view assumed headers associated with a cell (Resolved)

WD#35: Allow the user to view the summary attribute of a table (Resolved)

WD#36: Allow the user to view summary structural information about a table (Resolved)

WD#37: Allow user to navigate bewteen tables (Resolved)

WD#108: Proposed checkpoint for table summary information (Resolved)

LC#160: Delete checkpoints 7.3 and 8.2 (related to tables) since too vague (Resolved)

Servers

WD#39: Server side formatting of XML and other documents using XFO (Resolved)

Forms

WD#48: Saving form information to a local file and restoring the information when form is retrieved (Resolved)

WD#58: Keyboard access to select form controls when there is an ONCHANGE event handler attached to the control (Resolved)

WD#92: Proposed checkpoint about form orientation (Resolved)

LC#148: Checkpoint 9.6: Does RETURN count as explicit submit? (Resolved)

Animations

WD#49: Add a checkpoint that says that UAs should allow users to turn off flicker (Resolved)

WD#55: Priority of 5.1.7 Allow the user to control animation rate, due to photosensitive epilepsy (Resolved)

WD#65: Flicker frequencies of concern for photosensitive epilepsy (Resolved)

Language

WD#51: Language support (Resolved)

WD#71: Titles for ABBR and ACRONYM elements (Resolved)

Orientation

WD#52: Combining 6.1.9 and 6.1.10 in 31 March Draft (Resolved)

WD#69: Proposed Guideline for software consistency (Resolved)

WD#70: Recognizing paying links from micropayments markup (Resolved)

WD#177: User control of current focus change and notification. (Resolved)

Alternative content

WD#53: Proposed priority change to 5.2.9 from 2 to 1 (Resolved)

WD#73: Text rendering of client-side iamge maps (Resolved)

WD#81: Allow the user to turn on and off rendering of audio descriptions. (Resolved)

WD#82: How to rendering text links for images in links that have no alt? (Resolved)

WD#88: Proposed wording change for checkpoint on access to selected content. (Resolved)

LC#143: Proposed deletion of 2.6 since special case of 2.2 (Resolved)

LC#168: Checkpoint 2.7: Add object name in addition to type. (Resolved)

WD#186: Proposed removal of Note in 2.1 (Resolved)

WD#189: Proposed change to checkpoint 2.3 (missing alt info) (Resolved)

Multimedia

WD#56: Provide orientation to audio (or video) to length and/or position in the rendering of the information (Resolved)

WD#63: Checkpoint proposal from Marja to freeze time-sensitive content. (Resolved)

WD#74: Value of checkpoint on volume control (Resolved)

LC#135: Add incremental forward/rewind for audio, video, speech? (Resolved)

LC#138: "Synchronized equivalent" v. "Continuous Equivalent"/ Proposed split of 2.5 (Resolved)

LC#151: Proposed checkpoint: change audio rate without changing pitch (Resolved)

LC#164: Proposed change to wording of 4.8 in last call UAGL. (Resolved)

LC#171: 3.4: What does natively rendering audio mean? (Resolved)

CR#204: Add collated text to Checkpoint 2.6 and 4.8 or create a new checkpoint at lower priority (Resolved)

Editorial

WD#59: Reorder guidelines to place more important guidelines at the beginning of the document (Resolved)

WD#62: Renumbering guidelines similar to Web Content Guidelines (Resolved)

LC#137: Use of terms for disabilities, impairment (Resolved)

LC#144: Editorial changes to some Guideline titles suggested (Resolved)

Installation

WD#61: Proposed removing redundant checkpoint (Resolved)

Keyboard

WD#67: Adding guideline related to keyboard support in user agents (Resolved)

WD#68: Must the user be able to do everything with the mouse that they can with keyboard? (Resolved)

WD#94: Reenforcing the the use of standard keyboard APIs in guideline 2 (Resolved)

WD#96: Issues related to Checkpoint 2.1: Mapping of user agent functions to control mechanisms and memory demands related to sequential/direct access to functionalities (Resolved)

WD#110: Proposed changes to Guidelines 1, 2, and 11 re: keyboard (Resolved)

LC#112: Split checkpoint 10.1 into two separate checkpoints for author and user agent input functionalities and mark as an issue during last call (Resolved)

LC#113: Deletion of Guideline 2: Support the Keyboard (Resolved)

WD#178: In 10.1 and 10.2 what does communicate through an API mean (Resolved)

WD#185: clarification of "single key" access (Resolved)

Metadata

WD#72: What should UAs do to support author-supplied metadata? (Resolved)

LC#176: Proposed change in priority (P3 to P2) for checkpoint 8.7 (link information) (Resolved)

Documentation

WD#75: Does accessible doc checkpoint apply to non Web-based docs? (Resolved)

LC#133: Priority of 10.1 compared to 10.3 (Resolved)

Frames

WD#76: How to get to frames when the user turns off the rendering of frames (Resolved)

WD#91: Proposed reformulation of frames checkpoint (Resolved)

CR#202: User agent configuration to render NOFRAMES content (Resolved)

Other

WD#78: Review requirements for window spawning (Resolved)

WD#97: Questions about wording of document outline checkpoint (Resolved)

WD#102: List of problematic checkpoints. (Resolved)

WD#104: Proposed additions to conformance claim requirements (Resolved)

WD#105: ACCESSKEY implementation issues (Resolved)

WD#106: Proposed Abstract revision (Resolved)

WD#107: Proposed new checkpoint: 6.7 Support assistive technology accessibility standards defined for plug-in and virtual machine systems used by your browser. [priority 1] (Resolved)

LC#116: Non-editorial issues raised by Eric Hansen (Resolved)

LC#118: User Interface for text size (font size) control (Resolved)

LC#152: Proposed checkpoint: "Do not constrain the accessible output by constraints of the existingpresentation" (Resolved)

LC#175: Proposed raise (to P1) of checkpoint 4.18 (Resolved)

CR#206: Precise specification of what parts of DOM are required (Resolved)

Device Independence

WD#80: Make audio output available as text (Resolved)

WD#109: Proposed rewording of Checkpoints 1.1 and 1.6 (Resolved)

LC#141: Need to qualify checkpoint 1.4 in same was as 1.1 is qualified re: "every" (Resolved)

LC#142: Checkpoint 1.5 (output device-independence) needs clarification. (Resolved)

LC#172: Some clarification required in 1.1 (Resolved)

WD#184: Proposed simplification to checkpoint 1.1 (device-independent access) (Resolved)

Speech

WD#83: Split Checkpoint on voice characteristics? (Resolved)

LC#167: Proposed checkpoint to allow users to turn on/off multilingual support. (Resolved)

Natural language

WD#84: Checkpoint on natural language applies to all UAs (Resolved)

WD#85: Priority of checkpoint on language support (Resolved)

LC#140: Clarification on 2.3 required: how do you satisfy it if you don't support a language? (Resolved)

LC#154: Proposed requirement that UAs give access to style sheet classes (Resolved)

LC#174: Natural language identification issues. (Resolved)

User-control of Style

WD#87: Proposed wording change about user-control of highlight rendering (Resolved)

WD#95: Proposed checkpoint: Choose from among style sheets (Resolved)

WD#99: Priority of control of GUI layout should not be priority 1 (Resolved)

LC#115: Checkpoint to maintain relative font sizes? (Resolved)

LC#132: Checkpoint 4.17 (Note): User should not be able to turn off default styles (Resolved)

LC#139: Need clarification of 4.11 (audio playback speed) (Resolved)

LC#145: Why is 3.7 Pri 1 and 3.10 Pri 3? (Re: blinking and flashing) (Resolved)

LC#158: Propose priority change (1 to 2) for checkpoint 4.1 (control of font family) (Resolved)

LC#159: Propose raise priority of 4.13 to Priority 1 (Resolved)

Depdency with other W3C and WAI working groups

WD#90: Development of a dependency list between UA and AU (Resolved)

WD#98: What does "appropriate" mean in "appropriate w3c recommendations"? (Resolved)

LC#124: Should the Guidelines reference MSAA and JAAPI? (Resolved)

LC#157: Correct reference to XSL in checkpoint 6.2 since only a Working Draft. (Resolved)

User Interface Accessibility

LC#120: The UAGL should pay more attention to UI accessibility (Resolved)

LC#121: Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI) (Resolved)

LC#122: Proposed checkpoint related to input focus on controls (Resolved)

LC#123: Proposed checkpoint to use standard UI components for the interface. (Resolved)

LC#128: Extend definition of focus to include GUI control focus (Resolved)

LC#131: Proposed change in wording of 10.8 (Resolved)

LC#161: Raise priority of 8.8 to P2 (highlighting and identifying selection/focus) (Resolved)

LC#162: Raise priority of 8.9 (consistency in configs) to P2. (Resolved)

LC#169: What UI is required for turning on/off features that may impede accessibility? (Resolved)

Configuration

LC#129: Need to clarify 10.3 ("Allow the user to change and control the inputconfiguration. Users should be able to activate a functionality with a single-stroke (e.g., single-key, single voicecommand, etc.).) (Resolved)

LC#130: Proposed rewording of 10.5: Avoid default> > input configurations that conflict with operating system navigation, control, and access conventions. (Resolved)

LC#134: Proposed modification of 10.3: "The controls mustbe user-selectable." (Resolved)

LC#149: 10.6: Wording (delete "and software") and Priority. (Resolved)

LC#166: Review priority of 10.5 (default configs that interfere with OS conventions) (Resolved)

WD#180: 10.8 should be priority 2 (Resolved)

WD#187: Proposed change in wording to 1.6 (profiles) (Resolved)

OS Conventions

WD#179: Priority of 5.8 should be 1 (Resolved)

Supporting materials

WD#181: Request for a wrapper note designed for AT developers explaining relation to guidelines (Resolved)

Definition

WD#188: Add definition of disability? (to CG) (Resolved)

Index of Issues by Name of Person Raising the Issue

Jon Gunderson

WD#1: Use subgrouping of checkpoints for conformance for assistive technology and desktop graphical user agents (Resolved)

WD#2: Recommend full implmentation of DOM level 1 for AT compatibility (Resolved)

WD#4: Use accessibility API and OS conventions for compatibility with AT (Resolved)

WD#5: User agents should provide information to AT on changes to the document object, selection, focus or system caret (Resolved)

WD#6: Provide a means for AT to change the DOM, selection, focus and/or system caret (Resolved)

WD#7: Provide a means for AT to simulate WWW document events (Resolved)

WD#8: Provide a means for AT to simulate user interface (non-WWW content) controls (Resolved)

WD#10: Use OS conventions and accessibility settings in interface design, configuration, product installation, and documentation. (Resolved)

WD#16: Sequentially navigate to only link elements (Resolved)

WD#17: Sequentially navigate to only form controls in a document (Resolved)

WD#18: Sequentailly navigate to only elements with long descriptions (longdesc attribute or OBJECT content) (Resolved)

WD#19: Sequentially navigate to elements with explicit scripting event handlers (Resolved)

WD#20: Sequentially navigate header elements (Resolved)

WD#21: Search for link based on its text content (Resolved)

WD#22: Sequentially navigate between forms in a document (Resolved)

WD#23: Search for a form control based on text content (Resolved)

WD#24: Search for a form control based on its attribute values (i.e. label or control type) (Resolved)

WD#25: Sequentially navigate to all elements (block level) (Resolved)

WD#26: Search for an element based on its text content (Resolved)

WD#31: Allow users to navigate between cells of a table (Resolved)

WD#32: Allow the user to view one table cell at a time (Resolved)

WD#33: Allow the user to view header information associated with a cell (Resolved)

WD#34: Allow the user to view assumed headers associated with a cell (Resolved)

WD#35: Allow the user to view the summary attribute of a table (Resolved)

WD#36: Allow the user to view summary structural information about a table (Resolved)

WD#37: Allow user to navigate bewteen tables (Resolved)

WD#38: Search for a link based on its attribute value (Resolved)

WD#45: Include a specific checkpoint to allow user to simulate scripting events (Resolved)

WD#177: User control of current focus change and notification. (Resolved)

WD#178: In 10.1 and 10.2 what does communicate through an API mean (Resolved)

Al Gilman

WD#3: What should UAs do with recognize navigation bars? (Resolved)

WD#48: Saving form information to a local file and restoring the information when form is retrieved (Resolved)

Rich Schwerdtfeger

WD#9: Require timely exchange of information between user agents and AT for rendering synchronization (Resolved)

WD#79: How do specialized browsers like pwWebSpeak and IBM Homepage Reader conform to the guidelines (Resolved)

WD#107: Proposed new checkpoint: 6.7 Support assistive technology accessibility standards defined for plug-in and virtual machine systems used by your browser. [priority 1] (Resolved)

LC#114: How do requirements for APIs overlap (DOM? Platform standards? Provided by Tool) (Resolved)

Denis Anson

WD#11: Move to the next element with the same attributes and element type (Resolved)

WD#40: What types of navigation commands support visually impaired users navigating a unfamilar document? (Resolved)

WD#41: What types of navigation commands support a user with a visual impairment navigating a familar document? (Resolved)

WD#42: How do users navigate documents with embedded list elements? (Resolved)

Tom Wlodkowski

WD#12: Recommend full implmentation of MathML (Resolved)

WD#13: Provide keyboard access to MathML similar to forms (Resolved)

WD#14: MathML objects should be included as part of the document tree (Resolved)

Kathy Hewitt

WD#15: Sequentially navigate between active elements (Resolved)

Charles McCathieNevile

WD#27: Move to the next element in the document tree as defined by DOM (Resolved)

WD#28: Move to the child level element of the current element in the document tree (Resolved)

WD#29: Move to the next (or previous) sibling element in the document tree (Resolved)

WD#30: Move to the parent element of the current element in the document tree (Resolved)

WD#94: Reenforcing the the use of standard keyboard APIs in guideline 2 (Resolved)

William Loughborough

WD#39: Server side formatting of XML and other documents using XFO (Resolved)

Harvey Bingham

WD#43: Navigation and activation of elements with ACCESSKEY attributes defined (Resolved)

WD#60: Need to give user final control over accesskey settings (Resolved)

WD#64: Keyboard mapping among assistive technology tools (Resolved)

WD#65: Flicker frequencies of concern for photosensitive epilepsy (Resolved)

WD#68: Must the user be able to do everything with the mouse that they can with keyboard? (Resolved)

WD#82: How to rendering text links for images in links that have no alt? (Resolved)

Marja Koivunen

WD#44: Navigation of time dependent mult-mdeia elements rendered to the user (more than just stop, rewind and fast forward) (Resolved)

Charles McCathieNevile

WD#46: Allow user to configure active elements to include scripting events (Resolved)

WD#47: Include scripting events in checkpoint on access to active elements (Resolved)

WD#52: Combining 6.1.9 and 6.1.10 in 31 March Draft (Resolved)

WD#54: User notification of document changes due to scripting and other events (Resolved)

WD#90: Development of a dependency list between UA and AU (Resolved)

LC#111: Proposal to make Checkpoint 6.1 have a relative priority (Resolved)

CR#205: Timing issues related to AT missing or not being synchronized to document changes (Resolved)

Ian Jacobs

WD#49: Add a checkpoint that says that UAs should allow users to turn off flicker (Resolved)

WD#50: Modify Guideline 7.1 (Resolved)

WD#51: Language support (Resolved)

WD#59: Reorder guidelines to place more important guidelines at the beginning of the document (Resolved)

WD#61: Proposed removing redundant checkpoint (Resolved)

WD#62: Renumbering guidelines similar to Web Content Guidelines (Resolved)

WD#63: Checkpoint proposal from Marja to freeze time-sensitive content. (Resolved)

WD#66: Proposal to simplify check points in guidelines 7 (11 June WD) (Resolved)

WD#67: Adding guideline related to keyboard support in user agents (Resolved)

WD#69: Proposed Guideline for software consistency (Resolved)

WD#70: Recognizing paying links from micropayments markup (Resolved)

WD#71: Titles for ABBR and ACRONYM elements (Resolved)

WD#72: What should UAs do to support author-supplied metadata? (Resolved)

WD#73: Text rendering of client-side iamge maps (Resolved)

WD#77: Validate conformance categories (Resolved)

WD#78: Review requirements for window spawning (Resolved)

WD#86: Should Guideline about support for W3C technologies be broadened or narrowed? (Resolved)

WD#87: Proposed wording change about user-control of highlight rendering (Resolved)

WD#88: Proposed wording change for checkpoint on access to selected content. (Resolved)

WD#89: Proposed changes in conformance based on interoperable UA and non-interoperable UA (Resolved)

WD#91: Proposed reformulation of frames checkpoint (Resolved)

WD#92: Proposed checkpoint about form orientation (Resolved)

WD#93: Proposed modification to definition of "applicable checkpoint" (Resolved)

WD#95: Proposed checkpoint: Choose from among style sheets (Resolved)

WD#100: Proposed Note on verifiability of some checkpoints (Resolved)

WD#103: Proposed change to priority wording (Resolved)

WD#104: Proposed additions to conformance claim requirements (Resolved)

WD#106: Proposed Abstract revision (Resolved)

WD#108: Proposed checkpoint for table summary information (Resolved)

WD#109: Proposed rewording of Checkpoints 1.1 and 1.6 (Resolved)

WD#110: Proposed changes to Guidelines 1, 2, and 11 re: keyboard (Resolved)

LC#112: Split checkpoint 10.1 into two separate checkpoints for author and user agent input functionalities and mark as an issue during last call (Resolved)

LC#136: Proposal for checklist delivery (part of conformance) (Resolved)

LC#137: Use of terms for disabilities, impairment (Resolved)

LC#173: Proposed revision of "native" to account for OS features (Resolved)

WD#184: Proposed simplification to checkpoint 1.1 (device-independent access) (Resolved)

WD#186: Proposed removal of Note in 2.1 (Resolved)

WD#187: Proposed change in wording to 1.6 (profiles) (Resolved)

WD#189: Proposed change to checkpoint 2.3 (missing alt info) (Resolved)

Jim Allan

WD#53: Proposed priority change to 5.2.9 from 2 to 1 (Resolved)

Mark Novak

WD#55: Priority of 5.1.7 Allow the user to control animation rate, due to photosensitive epilepsy (Resolved)

WD#56: Provide orientation to audio (or video) to length and/or position in the rendering of the information (Resolved)

WD#57: Which attributes can be used to search for an element based on attribute values (Resolved)

Chris Kreussling

WD#58: Keyboard access to select form controls when there is an ONCHANGE event handler attached to the control (Resolved)

Jon Gunderson/Ian Jacobs

WD#74: Value of checkpoint on volume control (Resolved)

David Poehlman

WD#75: Does accessible doc checkpoint apply to non Web-based docs? (Resolved)

WD#76: How to get to frames when the user turns off the rendering of frames (Resolved)

Madeleine Rothberg

WD#80: Make audio output available as text (Resolved)

WD#81: Allow the user to turn on and off rendering of audio descriptions. (Resolved)

LC#164: Proposed change to wording of 4.8 in last call UAGL. (Resolved)

Jim Thatcher

WD#83: Split Checkpoint on voice characteristics? (Resolved)

WD#85: Priority of checkpoint on language support (Resolved)

WD#97: Questions about wording of document outline checkpoint (Resolved)

WD#98: What does "appropriate" mean in "appropriate w3c recommendations"? (Resolved)

WD#99: Priority of control of GUI layout should not be priority 1 (Resolved)

WD#102: List of problematic checkpoints. (Resolved)

Kitch Barnicle

WD#84: Checkpoint on natural language applies to all UAs (Resolved)

WD#101: Wording of checkpoint on document change notification (Resolved)

Marja Koivunen

WD#96: Issues related to Checkpoint 2.1: Mapping of user agent functions to control mechanisms and memory demands related to sequential/direct access to functionalities (Resolved)

Gregory Rosmaita

WD#105: ACCESSKEY implementation issues (Resolved)

Bryan Campbell

LC#113: Deletion of Guideline 2: Support the Keyboard (Resolved)

Al Gilman/Todd Fahrner

LC#115: Checkpoint to maintain relative font sizes? (Resolved)

Eric Hansen

LC#116: Non-editorial issues raised by Eric Hansen (Resolved)

LC#119: Proposed narrowing of scope in definition of "applicability" (ALSO: Put back in conformance section? -IJ) (Resolved)

LC#138: "Synchronized equivalent" v. "Continuous Equivalent"/ Proposed split of 2.5 (Resolved)

CR#204: Add collated text to Checkpoint 2.6 and 4.8 or create a new checkpoint at lower priority (Resolved)

Bridie Saccocio/Steve McAdoo (reply by Ian)

LC#117: How are exception cases determined and by whom? (Resolved)

Todd Fahrner

LC#118: User Interface for text size (font size) control (Resolved)

Earl Johnson/Peter Korn

LC#120: The UAGL should pay more attention to UI accessibility (Resolved)

LC#122: Proposed checkpoint related to input focus on controls (Resolved)

LC#123: Proposed checkpoint to use standard UI components for the interface. (Resolved)

LC#124: Should the Guidelines reference MSAA and JAAPI? (Resolved)

LC#125: To what APIs does 5.1 refer ( Provide accessible APIs to other technologies) (Resolved)

LC#126: Proposed change in wording to 5.5 (Provide programmatic notification of changes to content and user interfacecontrols (including selection and focus).) (Resolved)

LC#127: How to verify 5.7 (Provide programmatic exchange of information in a timely manner.)? (Resolved)

LC#128: Extend definition of focus to include GUI control focus (Resolved)

LC#129: Need to clarify 10.3 ("Allow the user to change and control the inputconfiguration. Users should be able to activate a functionality with a single-stroke (e.g., single-key, single voicecommand, etc.).) (Resolved)

LC#130: Proposed rewording of 10.5: Avoid default> > input configurations that conflict with operating system navigation, control, and access conventions. (Resolved)

LC#131: Proposed change in wording of 10.8 (Resolved)

Earl Johnson/Peter Korn + Phill Jenkins

LC#121: Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI) (Resolved)

Liam Quinn

LC#132: Checkpoint 4.17 (Note): User should not be able to turn off default styles (Resolved)

Jon Gardner

LC#133: Priority of 10.1 compared to 10.3 (Resolved)

LC#134: Proposed modification of 10.3: "The controls mustbe user-selectable." (Resolved)

Scott Luebking

LC#135: Add incremental forward/rewind for audio, video, speech? (Resolved)

T.V. Raman

LC#139: Need clarification of 4.11 (audio playback speed) (Resolved)

Steven Pemberton

LC#140: Clarification on 2.3 required: how do you satisfy it if you don't support a language? (Resolved)

Gregg Vanderheiden

LC#141: Need to qualify checkpoint 1.4 in same was as 1.1 is qualified re: "every" (Resolved)

LC#142: Checkpoint 1.5 (output device-independence) needs clarification. (Resolved)

LC#143: Proposed deletion of 2.6 since special case of 2.2 (Resolved)

LC#144: Editorial changes to some Guideline titles suggested (Resolved)

LC#145: Why is 3.7 Pri 1 and 3.10 Pri 3? (Re: blinking and flashing) (Resolved)

LC#146: Review priorities of 4.16, 5.2, 8.3, 8.5, 10.3, 10.6 (Resolved)

LC#148: Checkpoint 9.6: Does RETURN count as explicit submit? (Resolved)

LC#149: 10.6: Wording (delete "and software") and Priority. (Resolved)

Gregg Vanderheiden/Gregory Rosmaita

LC#147: Need to review priority and wording of 5.8 (Resolved)

Len Kasday

LC#150: Do APIs apply when the software is accessible on its own? (Resolved)

LC#151: Proposed checkpoint: change audio rate without changing pitch (Resolved)

LC#152: Proposed checkpoint: "Do not constrain the accessible output by constraints of the existingpresentation" (Resolved)

LC#154: Proposed requirement that UAs give access to style sheet classes (Resolved)

Peter Meijer

LC#153: Hold off on conformance until functional requirements between browsers/ATs more defined? (Resolved)

Hakon Wium Lie

LC#155: Propose change of priorities for checkpoints 5.3 (r/w access) and 10.3 (single key) (Resolved)

LC#156: Propose change in priority of 5.6 (P1 -> P2) (Resolved)

LC#157: Correct reference to XSL in checkpoint 6.2 since only a Working Draft. (Resolved)

Richard Premack

LC#158: Propose priority change (1 to 2) for checkpoint 4.1 (control of font family) (Resolved)

LC#159: Propose raise priority of 4.13 to Priority 1 (Resolved)

LC#161: Raise priority of 8.8 to P2 (highlighting and identifying selection/focus) (Resolved)

LC#162: Raise priority of 8.9 (consistency in configs) to P2. (Resolved)

LC#163: Proposed new checkpoint on "Favorites" functionality (Resolved)

Microsoft IE Team

LC#160: Delete checkpoints 7.3 and 8.2 (related to tables) since too vague (Resolved)

Wendy Chisholm

LC#165: Add information about system level flags to 5.2 (Resolved)

LC#166: Review priority of 10.5 (default configs that interfere with OS conventions) (Resolved)

Mark Hakkinen

LC#167: Proposed checkpoint to allow users to turn on/off multilingual support. (Resolved)

LC#168: Checkpoint 2.7: Add object name in addition to type. (Resolved)

LC#169: What UI is required for turning on/off features that may impede accessibility? (Resolved)

LC#170: How can UAs "stay" accessible when there is a mass of inaccessible content? (Resolved)

Greg Vanderheiden

LC#171: 3.4: What does natively rendering audio mean? (Resolved)

Earl Johnson/Wendy Chisholm

LC#172: Some clarification required in 1.1 (Resolved)

Martin Duerst/I18N

LC#174: Natural language identification issues. (Resolved)

Terry Sullivan

LC#175: Proposed raise (to P1) of checkpoint 4.18 (Resolved)

LC#176: Proposed change in priority (P3 to P2) for checkpoint 8.7 (link information) (Resolved)

Alan Cantor

WD#179: Priority of 5.8 should be 1 (Resolved)

WD#180: 10.8 should be priority 2 (Resolved)

EO WG

WD#181: Request for a wrapper note designed for AT developers explaining relation to guidelines (Resolved)

UAWG

WD#182: Should searching equivalent text be an AT responsibility (Resolved)

Jon Gunderson/Gregory Rosmaita

WD#183: Proposed rewording to checkpoint 7.5 (search alt content) (Resolved)

Bryan Campbell

WD#185: clarification of "single key" access (Resolved)

Phill Jenkins

WD#188: Add definition of disability? (to CG) (Resolved)

Hakon Lie (through Ian Jacobs)

CR#190: Reduce the scope of 5.1 to say "write access only for that which you can do through the UI." (Resolved)

RealNetworks (through Charles McCathieNevile)

CR#191: Does a pause function satisfy checkpoint 2.2? (Resolved)

Real Networks (through Charles McCathieNevile )

CR#192: Does hiding video satisfy checkpoint 3.3 (Resolved)

Real Networks (through Charles McCathieNevile)

CR#193: In the case of animations, does checkpoint 4.5 mean a requirement to step through or slow the speed as well as being able to turn it off? (Resolved)

CR#194: In a timed presentation does checkpoint 7.2 mean return to the time that the user was at in a previous MM rendering (Resolved)

Microsoft (through Charles McCathieNevile)

CR#195: Problems understanding checkpoint 1.5 (Resolved)

CR#196: It is unclear to developers how they know they conform to Checkpoint 6.2: Conform to W3C specifications when they are appropriate (Resolved)

CR#197: Not clear with the scope of user preferences is in Checkpoint 10.7 (Resolved)

CR#198: How much information needs to be provided to satisfy Checkpoint 8.4 (Resolved)

CR#200: Checkpoint 5.5, developers not unclear on how they know they have satisfied this checkpoint (Resolved)

Microsoft (throughCharles McCathieNevile)

CR#199: Poor wording of checkpoint 10.8, it is not clear what the requirement is to improve accessibility (Resolved)

Glen Gordon

CR#201: 5.5 "Ensure that programmatic exchanges proceed in a timely manner" should be a priority 1 (Resolved)

Gregory J. Rosmaita

CR#202: User agent configuration to render NOFRAMES content (Resolved)

Philippe Le Hegaret/Ian Jacobs

CR#203: Checkpoint for access to content for non-HTML or non-XML WWW documents (i.e. Shockwave) (Resolved)

Philippe Le Hegaret

CR#206: Precise specification of what parts of DOM are required (Resolved)

Index of Issues by Type

Checkpoints

WD#1: Use subgrouping of checkpoints for conformance for assistive technology and desktop graphical user agents (Resolved)

WD#2: Recommend full implmentation of DOM level 1 for AT compatibility (Resolved)

WD#3: What should UAs do with recognize navigation bars? (Resolved)

WD#4: Use accessibility API and OS conventions for compatibility with AT (Resolved)

WD#5: User agents should provide information to AT on changes to the document object, selection, focus or system caret (Resolved)

WD#6: Provide a means for AT to change the DOM, selection, focus and/or system caret (Resolved)

WD#7: Provide a means for AT to simulate WWW document events (Resolved)

WD#8: Provide a means for AT to simulate user interface (non-WWW content) controls (Resolved)

WD#9: Require timely exchange of information between user agents and AT for rendering synchronization (Resolved)

WD#10: Use OS conventions and accessibility settings in interface design, configuration, product installation, and documentation. (Resolved)

WD#11: Move to the next element with the same attributes and element type (Resolved)

WD#12: Recommend full implmentation of MathML (Resolved)

WD#13: Provide keyboard access to MathML similar to forms (Resolved)

WD#14: MathML objects should be included as part of the document tree (Resolved)

WD#15: Sequentially navigate between active elements (Resolved)

WD#16: Sequentially navigate to only link elements (Resolved)

WD#17: Sequentially navigate to only form controls in a document (Resolved)

WD#18: Sequentailly navigate to only elements with long descriptions (longdesc attribute or OBJECT content) (Resolved)

WD#19: Sequentially navigate to elements with explicit scripting event handlers (Resolved)

WD#20: Sequentially navigate header elements (Resolved)

WD#21: Search for link based on its text content (Resolved)

WD#22: Sequentially navigate between forms in a document (Resolved)

WD#23: Search for a form control based on text content (Resolved)

WD#24: Search for a form control based on its attribute values (i.e. label or control type) (Resolved)

WD#25: Sequentially navigate to all elements (block level) (Resolved)

WD#26: Search for an element based on its text content (Resolved)

WD#27: Move to the next element in the document tree as defined by DOM (Resolved)

WD#28: Move to the child level element of the current element in the document tree (Resolved)

WD#29: Move to the next (or previous) sibling element in the document tree (Resolved)

WD#30: Move to the parent element of the current element in the document tree (Resolved)

WD#31: Allow users to navigate between cells of a table (Resolved)

WD#32: Allow the user to view one table cell at a time (Resolved)

WD#33: Allow the user to view header information associated with a cell (Resolved)

WD#34: Allow the user to view assumed headers associated with a cell (Resolved)

WD#35: Allow the user to view the summary attribute of a table (Resolved)

WD#36: Allow the user to view summary structural information about a table (Resolved)

WD#37: Allow user to navigate bewteen tables (Resolved)

WD#38: Search for a link based on its attribute value (Resolved)

WD#39: Server side formatting of XML and other documents using XFO (Resolved)

WD#45: Include a specific checkpoint to allow user to simulate scripting events (Resolved)

WD#46: Allow user to configure active elements to include scripting events (Resolved)

WD#47: Include scripting events in checkpoint on access to active elements (Resolved)

WD#49: Add a checkpoint that says that UAs should allow users to turn off flicker (Resolved)

WD#50: Modify Guideline 7.1 (Resolved)

WD#51: Language support (Resolved)

WD#52: Combining 6.1.9 and 6.1.10 in 31 March Draft (Resolved)

WD#53: Proposed priority change to 5.2.9 from 2 to 1 (Resolved)

WD#54: User notification of document changes due to scripting and other events (Resolved)

WD#55: Priority of 5.1.7 Allow the user to control animation rate, due to photosensitive epilepsy (Resolved)

WD#60: Need to give user final control over accesskey settings (Resolved)

WD#61: Proposed removing redundant checkpoint (Resolved)

WD#65: Flicker frequencies of concern for photosensitive epilepsy (Resolved)

WD#66: Proposal to simplify check points in guidelines 7 (11 June WD) (Resolved)

WD#73: Text rendering of client-side iamge maps (Resolved)

WD#74: Value of checkpoint on volume control (Resolved)

WD#75: Does accessible doc checkpoint apply to non Web-based docs? (Resolved)

WD#76: How to get to frames when the user turns off the rendering of frames (Resolved)

WD#80: Make audio output available as text (Resolved)

WD#81: Allow the user to turn on and off rendering of audio descriptions. (Resolved)

WD#83: Split Checkpoint on voice characteristics? (Resolved)

WD#84: Checkpoint on natural language applies to all UAs (Resolved)

WD#85: Priority of checkpoint on language support (Resolved)

WD#87: Proposed wording change about user-control of highlight rendering (Resolved)

WD#88: Proposed wording change for checkpoint on access to selected content. (Resolved)

WD#89: Proposed changes in conformance based on interoperable UA and non-interoperable UA (Resolved)

WD#91: Proposed reformulation of frames checkpoint (Resolved)

WD#92: Proposed checkpoint about form orientation (Resolved)

WD#93: Proposed modification to definition of "applicable checkpoint" (Resolved)

WD#95: Proposed checkpoint: Choose from among style sheets (Resolved)

WD#98: What does "appropriate" mean in "appropriate w3c recommendations"? (Resolved)

WD#99: Priority of control of GUI layout should not be priority 1 (Resolved)

WD#101: Wording of checkpoint on document change notification (Resolved)

WD#102: List of problematic checkpoints. (Resolved)

WD#108: Proposed checkpoint for table summary information (Resolved)

WD#109: Proposed rewording of Checkpoints 1.1 and 1.6 (Resolved)

LC#111: Proposal to make Checkpoint 6.1 have a relative priority (Resolved)

LC#112: Split checkpoint 10.1 into two separate checkpoints for author and user agent input functionalities and mark as an issue during last call (Resolved)

LC#115: Checkpoint to maintain relative font sizes? (Resolved)

LC#122: Proposed checkpoint related to input focus on controls (Resolved)

LC#123: Proposed checkpoint to use standard UI components for the interface. (Resolved)

LC#125: To what APIs does 5.1 refer ( Provide accessible APIs to other technologies) (Resolved)

LC#126: Proposed change in wording to 5.5 (Provide programmatic notification of changes to content and user interfacecontrols (including selection and focus).) (Resolved)

LC#127: How to verify 5.7 (Provide programmatic exchange of information in a timely manner.)? (Resolved)

LC#129: Need to clarify 10.3 ("Allow the user to change and control the inputconfiguration. Users should be able to activate a functionality with a single-stroke (e.g., single-key, single voicecommand, etc.).) (Resolved)

LC#130: Proposed rewording of 10.5: Avoid default> > input configurations that conflict with operating system navigation, control, and access conventions. (Resolved)

LC#132: Checkpoint 4.17 (Note): User should not be able to turn off default styles (Resolved)

LC#133: Priority of 10.1 compared to 10.3 (Resolved)

LC#134: Proposed modification of 10.3: "The controls mustbe user-selectable." (Resolved)

LC#135: Add incremental forward/rewind for audio, video, speech? (Resolved)

LC#139: Need clarification of 4.11 (audio playback speed) (Resolved)

LC#140: Clarification on 2.3 required: how do you satisfy it if you don't support a language? (Resolved)

LC#141: Need to qualify checkpoint 1.4 in same was as 1.1 is qualified re: "every" (Resolved)

LC#142: Checkpoint 1.5 (output device-independence) needs clarification. (Resolved)

LC#143: Proposed deletion of 2.6 since special case of 2.2 (Resolved)

LC#145: Why is 3.7 Pri 1 and 3.10 Pri 3? (Re: blinking and flashing) (Resolved)

LC#146: Review priorities of 4.16, 5.2, 8.3, 8.5, 10.3, 10.6 (Resolved)

LC#147: Need to review priority and wording of 5.8 (Resolved)

LC#148: Checkpoint 9.6: Does RETURN count as explicit submit? (Resolved)

LC#149: 10.6: Wording (delete "and software") and Priority. (Resolved)

LC#151: Proposed checkpoint: change audio rate without changing pitch (Resolved)

LC#154: Proposed requirement that UAs give access to style sheet classes (Resolved)

LC#155: Propose change of priorities for checkpoints 5.3 (r/w access) and 10.3 (single key) (Resolved)

LC#156: Propose change in priority of 5.6 (P1 -> P2) (Resolved)

LC#157: Correct reference to XSL in checkpoint 6.2 since only a Working Draft. (Resolved)

LC#158: Propose priority change (1 to 2) for checkpoint 4.1 (control of font family) (Resolved)

LC#159: Propose raise priority of 4.13 to Priority 1 (Resolved)

LC#160: Delete checkpoints 7.3 and 8.2 (related to tables) since too vague (Resolved)

LC#161: Raise priority of 8.8 to P2 (highlighting and identifying selection/focus) (Resolved)

LC#162: Raise priority of 8.9 (consistency in configs) to P2. (Resolved)

LC#163: Proposed new checkpoint on "Favorites" functionality (Resolved)

LC#164: Proposed change to wording of 4.8 in last call UAGL. (Resolved)

LC#165: Add information about system level flags to 5.2 (Resolved)

LC#166: Review priority of 10.5 (default configs that interfere with OS conventions) (Resolved)

LC#167: Proposed checkpoint to allow users to turn on/off multilingual support. (Resolved)

LC#168: Checkpoint 2.7: Add object name in addition to type. (Resolved)

LC#169: What UI is required for turning on/off features that may impede accessibility? (Resolved)

LC#171: 3.4: What does natively rendering audio mean? (Resolved)

LC#172: Some clarification required in 1.1 (Resolved)

LC#174: Natural language identification issues. (Resolved)

LC#176: Proposed change in priority (P3 to P2) for checkpoint 8.7 (link information) (Resolved)

WD#178: In 10.1 and 10.2 what does communicate through an API mean (Resolved)

WD#179: Priority of 5.8 should be 1 (Resolved)

WD#180: 10.8 should be priority 2 (Resolved)

WD#182: Should searching equivalent text be an AT responsibility (Resolved)

WD#183: Proposed rewording to checkpoint 7.5 (search alt content) (Resolved)

WD#184: Proposed simplification to checkpoint 1.1 (device-independent access) (Resolved)

WD#185: clarification of "single key" access (Resolved)

WD#187: Proposed change in wording to 1.6 (profiles) (Resolved)

CR#190: Reduce the scope of 5.1 to say "write access only for that which you can do through the UI." (Resolved)

CR#191: Does a pause function satisfy checkpoint 2.2? (Resolved)

CR#192: Does hiding video satisfy checkpoint 3.3 (Resolved)

CR#193: In the case of animations, does checkpoint 4.5 mean a requirement to step through or slow the speed as well as being able to turn it off? (Resolved)

CR#194: In a timed presentation does checkpoint 7.2 mean return to the time that the user was at in a previous MM rendering (Resolved)

CR#195: Problems understanding checkpoint 1.5 (Resolved)

CR#196: It is unclear to developers how they know they conform to Checkpoint 6.2: Conform to W3C specifications when they are appropriate (Resolved)

CR#197: Not clear with the scope of user preferences is in Checkpoint 10.7 (Resolved)

CR#198: How much information needs to be provided to satisfy Checkpoint 8.4 (Resolved)

CR#199: Poor wording of checkpoint 10.8, it is not clear what the requirement is to improve accessibility (Resolved)

CR#200: Checkpoint 5.5, developers not unclear on how they know they have satisfied this checkpoint (Resolved)

CR#201: 5.5 "Ensure that programmatic exchanges proceed in a timely manner" should be a priority 1 (Resolved)

CR#203: Checkpoint for access to content for non-HTML or non-XML WWW documents (i.e. Shockwave) (Resolved)

CR#204: Add collated text to Checkpoint 2.6 and 4.8 or create a new checkpoint at lower priority (Resolved)

CR#205: Timing issues related to AT missing or not being synchronized to document changes (Resolved)

Issue

WD#40: What types of navigation commands support visually impaired users navigating a unfamilar document? (Resolved)

WD#41: What types of navigation commands support a user with a visual impairment navigating a familar document? (Resolved)

WD#42: How do users navigate documents with embedded list elements? (Resolved)

WD#43: Navigation and activation of elements with ACCESSKEY attributes defined (Resolved)

WD#44: Navigation of time dependent mult-mdeia elements rendered to the user (more than just stop, rewind and fast forward) (Resolved)

WD#48: Saving form information to a local file and restoring the information when form is retrieved (Resolved)

WD#56: Provide orientation to audio (or video) to length and/or position in the rendering of the information (Resolved)

WD#68: Must the user be able to do everything with the mouse that they can with keyboard? (Resolved)

WD#72: What should UAs do to support author-supplied metadata? (Resolved)

WD#77: Validate conformance categories (Resolved)

LC#117: How are exception cases determined and by whom? (Resolved)

LC#119: Proposed narrowing of scope in definition of "applicability" (ALSO: Put back in conformance section? -IJ) (Resolved)

LC#124: Should the Guidelines reference MSAA and JAAPI? (Resolved)

LC#136: Proposal for checklist delivery (part of conformance) (Resolved)

LC#137: Use of terms for disabilities, impairment (Resolved)

LC#138: "Synchronized equivalent" v. "Continuous Equivalent"/ Proposed split of 2.5 (Resolved)

LC#150: Do APIs apply when the software is accessible on its own? (Resolved)

LC#170: How can UAs "stay" accessible when there is a mass of inaccessible content? (Resolved)

LC#173: Proposed revision of "native" to account for OS features (Resolved)

WD#177: User control of current focus change and notification. (Resolved)

WD#181: Request for a wrapper note designed for AT developers explaining relation to guidelines (Resolved)

CR#202: User agent configuration to render NOFRAMES content (Resolved)

Technique

WD#57: Which attributes can be used to search for an element based on attribute values (Resolved)

WD#82: How to rendering text links for images in links that have no alt? (Resolved)

LC#114: How do requirements for APIs overlap (DOM? Platform standards? Provided by Tool) (Resolved)

WD#186: Proposed removal of Note in 2.1 (Resolved)

Problem

WD#58: Keyboard access to select form controls when there is an ONCHANGE event handler attached to the control (Resolved)

WD#64: Keyboard mapping among assistive technology tools (Resolved)

WD#100: Proposed Note on verifiability of some checkpoints (Resolved)

Guidelines

WD#59: Reorder guidelines to place more important guidelines at the beginning of the document (Resolved)

WD#62: Renumbering guidelines similar to Web Content Guidelines (Resolved)

WD#67: Adding guideline related to keyboard support in user agents (Resolved)

WD#69: Proposed Guideline for software consistency (Resolved)

WD#79: How do specialized browsers like pwWebSpeak and IBM Homepage Reader conform to the guidelines (Resolved)

WD#86: Should Guideline about support for W3C technologies be broadened or narrowed? (Resolved)

WD#90: Development of a dependency list between UA and AU (Resolved)

WD#94: Reenforcing the the use of standard keyboard APIs in guideline 2 (Resolved)

WD#96: Issues related to Checkpoint 2.1: Mapping of user agent functions to control mechanisms and memory demands related to sequential/direct access to functionalities (Resolved)

WD#110: Proposed changes to Guidelines 1, 2, and 11 re: keyboard (Resolved)

LC#113: Deletion of Guideline 2: Support the Keyboard (Resolved)

LC#120: The UAGL should pay more attention to UI accessibility (Resolved)

LC#121: Consider reordering/grouping the checkpoints/Guidelines (e.g., accessible content/accessible UI) (Resolved)

LC#144: Editorial changes to some Guideline titles suggested (Resolved)

No type

WD#63: Checkpoint proposal from Marja to freeze time-sensitive content. (Resolved)

WD#70: Recognizing paying links from micropayments markup (Resolved)

WD#71: Titles for ABBR and ACRONYM elements (Resolved)

WD#78: Review requirements for window spawning (Resolved)

WD#97: Questions about wording of document outline checkpoint (Resolved)

WD#103: Proposed change to priority wording (Resolved)

WD#104: Proposed additions to conformance claim requirements (Resolved)

WD#105: ACCESSKEY implementation issues (Resolved)

WD#106: Proposed Abstract revision (Resolved)

WD#107: Proposed new checkpoint: 6.7 Support assistive technology accessibility standards defined for plug-in and virtual machine systems used by your browser. [priority 1] (Resolved)

LC#116: Non-editorial issues raised by Eric Hansen (Resolved)

LC#118: User Interface for text size (font size) control (Resolved)

LC#128: Extend definition of focus to include GUI control focus (Resolved)

LC#131: Proposed change in wording of 10.8 (Resolved)

LC#152: Proposed checkpoint: "Do not constrain the accessible output by constraints of the existingpresentation" (Resolved)

LC#153: Hold off on conformance until functional requirements between browsers/ATs more defined? (Resolved)

LC#175: Proposed raise (to P1) of checkpoint 4.18 (Resolved)

WD#188: Add definition of disability? (to CG) (Resolved)

WD#189: Proposed change to checkpoint 2.3 (missing alt info) (Resolved)

CR#206: Precise specification of what parts of DOM are required (Resolved)