W3C LogoWeb Accessibility Initiative Logo User Agent Issue List: Fourth Last Call

Link to Previous Issue List

Last updated on: Mon Sep 30 19:04:56 2002

Open issues | Resolved issues | Numerical list | Categories | Name | Type

No Open Issues

List of 9 Resolved Issues


Issue details listed in numerical order

Issue 553 (Fourth Last Call): Add a requirement for per-script font-family configuration?
Name: Richard Ishida
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0154.html
Date: Thu Sep 26 12:17:02 2002
Category of issue: Internationalization
Type of issue: none specified
Resolution summary:
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173.html
First working draft: No reference
Comments:

Since global imposition of a Latin-only font could break text in other scripts, perhaps this should be finessed to say that it should be possible for the user to specify different user preferred fonts by script group (much like eg. the common browsers allow you to set default fonts for Unicode ranges).

Key References: none
Issue 552 (Fourth Last Call): Checkpoint 2.10: "language and script"
Name: Richard Ishida
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0154.html
Date: Thu Sep 26 12:15:52 2002
Category of issue: Internationalization
Type of issue: none specified
Resolution summary:
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173.html
First working draft: No reference
Comments:

The heading talks about 'language' whereas the checkpoint provision talks about 'scripts (ie. Writing systems)'. Both the title and text should be changed to 'language or script', to cover both the visual rendering case and the text-to-speech (or -to-braille) case.

Key References: none
Issue 551 (Fourth Last Call): Checkpoint 11.4: Single key mode and single-key access need fixing
Name: Steven Pemberton
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0160.html
Date: Thu Sep 26 12:11:04 2002
Category of issue: Keyboard
Type of issue: none specified
Resolution summary:
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173.html
First working draft: No reference
Comments:

Well, some people might see esc-p for "print" as a two-key binding, yet you say it is acceptable as an interpretation of single-key binding:

"A single-key binding is one where a single key press performs the task, with zero modifier keys.

Key References: none
Issue 550 (Fourth Last Call): Checkpoint 3.5: Clarification requested on HTTP headers and META data for automatic refresh or redirect
Name: Steven Pemberton
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0149.html
Date: Wed Sep 25 12:03:44 2002
Category of issue: none specified
Type of issue: none specified
Resolution summary:
Resolution URL: Not resolved
First working draft: No reference
Comments:
Ian's Proposed clarification: "For example, if an HTML author has used a META element for automatic content retrieval, the user agent should allow configuration to stop the automatic retrieval. Users can retrieve the content manually (e.g., "reload").
Key References: none
Issue 549 (Fourth Last Call): Checkpoint 3.3: Clarify definition of blinking to include alternating states of color
Name: Steven Pemberton
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0149.html
Date: Wed Sep 25 12:01:35 2002
Category of issue: Animations
Type of issue: Checkpoints
Resolution summary:
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173.html
First working draft: No reference
Comments: none
Key References: none
Issue 548 (Fourth Last Call): Checkpoint 2.2: Include the media type application/xhtml+xml to provide access explicit access to the source of XML content
Name: Steven Pemberton
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0149.html
Date: Wed Sep 25 11:57:36 2002
Category of issue: Views
Type of issue: Checkpoints
Resolution summary: For the purposes of this checkpoint, a text format is either: 1) any media object given an Internet media type of "text" (e.g., "text/plain", "text/html", or "text/*"), as defined in RFC 2046 [RFC2046], section 4.1., or 2) any media object identified by Internet media type to be an instance of an XML or SGML application. Note: As an example, RFC 3023 [2] defines some Internet media types for XML content.
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0186.html
First working draft: No reference
Comments:
Need to expand definition to include both 'text' and 'XML' content

Discussed and resolved at 26 Sep teleconf to add application/xhtml+xml

However, see proposal from IJ

and followup from Al Gilman
Key References: none
Issue 547 (Fourth Last Call): Checkpoint 1.2: Limit events to what can be triggered through user interface controls
Name: Steven Pemberton
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0149.html
Date: Wed Sep 25 11:49:51 2002
Category of issue: Scripting events
Type of issue: Checkpoints
Resolution summary: This is a bug in the spec and will be fixed. The checkpoint should only refer to input device event handlers.
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173.html
First working draft: No reference
Comments:
Need to limit activation of event handlers that could be activated by the user through input devices (i.e. mouse, keyboard, speech command, etc..)
Key References: none
Issue 546 (Fourth Last Call): Guideline 3: Increased granularity necessary (e.g., individual scripting languages on/off).
Name: Brian Kelly
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0115.html
Date: Wed Sep 18 17:35:05 2002
Category of issue: Scripting events
Type of issue: none specified
Resolution summary:
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0141.html
First working draft: No reference
Comments:
I think there is an issue concerning the granularity of this control. For example, it may be necessary to switch off JavaScript to disable certain features (e.g. animated text), but JavaScript may be needed for other reasons.
Key References: none
Issue 545 (Fourth Last Call): 6.5: Require DOM HTML to ensure that form values available through API
Name: Ray Whitmer (DOM WG)
Source URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0136.html
Date: Thu Jul 25 15:22:14 2002
Category of issue: DOM
Type of issue: Definitions
Resolution summary:
Resolution URL: http://lists.w3.org/Archives/Public/w3c-wai-ua/2002JulSep/0173.html
First working draft: No reference
Comments:
Discussed at 19 Sep teleconf Further proposal by IJ
Key References: none

Index of Issues by Category

DOM
LC(fourth)#545: 6.5: Require DOM HTML to ensure that form values available through API (Resolved)
Scripting events
LC(fourth)#546: Guideline 3: Increased granularity necessary (e.g., individual scripting languages on/off). (Resolved)
LC(fourth)#547: Checkpoint 1.2: Limit events to what can be triggered through user interface controls (Resolved)
Views
LC(fourth)#548: Checkpoint 2.2: Include the media type application/xhtml+xml to provide access explicit access to the source of XML content (Resolved)
Animations
LC(fourth)#549: Checkpoint 3.3: Clarify definition of blinking to include alternating states of color (Resolved)
Other
LC(fourth)#550: Checkpoint 3.5: Clarification requested on HTTP headers and META data for automatic refresh or redirect (Resolved)
Keyboard
LC(fourth)#551: Checkpoint 11.4: Single key mode and single-key access need fixing (Resolved)
Internationalization
LC(fourth)#552: Checkpoint 2.10: "language and script" (Resolved)
LC(fourth)#553: Add a requirement for per-script font-family configuration? (Resolved)

Index of Issues by Name of Person Raising the Issue

Ray Whitmer (DOM WG)
LC(fourth)#545: 6.5: Require DOM HTML to ensure that form values available through API (Resolved)
Brian Kelly
LC(fourth)#546: Guideline 3: Increased granularity necessary (e.g., individual scripting languages on/off). (Resolved)
Steven Pemberton
LC(fourth)#547: Checkpoint 1.2: Limit events to what can be triggered through user interface controls (Resolved)
LC(fourth)#548: Checkpoint 2.2: Include the media type application/xhtml+xml to provide access explicit access to the source of XML content (Resolved)
LC(fourth)#549: Checkpoint 3.3: Clarify definition of blinking to include alternating states of color (Resolved)
LC(fourth)#550: Checkpoint 3.5: Clarification requested on HTTP headers and META data for automatic refresh or redirect (Resolved)
LC(fourth)#551: Checkpoint 11.4: Single key mode and single-key access need fixing (Resolved)
Richard Ishida
LC(fourth)#552: Checkpoint 2.10: "language and script" (Resolved)
LC(fourth)#553: Add a requirement for per-script font-family configuration? (Resolved)

Index of Issues by Type

Definitions
LC(fourth)#545: 6.5: Require DOM HTML to ensure that form values available through API (Resolved)
No type
LC(fourth)#546: Guideline 3: Increased granularity necessary (e.g., individual scripting languages on/off). (Resolved)
LC(fourth)#550: Checkpoint 3.5: Clarification requested on HTTP headers and META data for automatic refresh or redirect (Resolved)
LC(fourth)#551: Checkpoint 11.4: Single key mode and single-key access need fixing (Resolved)
LC(fourth)#552: Checkpoint 2.10: "language and script" (Resolved)
LC(fourth)#553: Add a requirement for per-script font-family configuration? (Resolved)
Checkpoints
LC(fourth)#547: Checkpoint 1.2: Limit events to what can be triggered through user interface controls (Resolved)
LC(fourth)#548: Checkpoint 2.2: Include the media type application/xhtml+xml to provide access explicit access to the source of XML content (Resolved)
LC(fourth)#549: Checkpoint 3.3: Clarify definition of blinking to include alternating states of color (Resolved)

Return to homepage

Valid HTML 4.0!