User Agent Issue List: Fourth Last Call

Link to Previous Issue List

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

No Open Issues

List of 9 Resolved Issues

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

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:

• Due to the status of this document, and because this seems largely to be an I18N issue, the UAWG decided not to add a new requirement.
• Instead, the Techniques document will make the reviewer's point.

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:

• Because the UAWG has no implementation experience with this requirement in a text-to-speech context, the group decided not to expand the checkpoint as proposed.
• Instead, the UAWG suggests adding a Note that this checkpoint would also make sense in the text-to-speech context.

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:

• The UAWG agrees with the reviewer that the scope of "single-key mode" needs to be clarified. A single-key mode of one single-key binding does not meet the expectations of the UAWG. The document will be updated to reflect that expectation, but not to set a minimal requirement about the number of bindings available in the single-key mode.

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:

• In normative inclusion 2: Change "Authors (and Webmasters) should use the redirect mechanisms of HTTP instead of client-side redirects." to "Authors (and Webmasters) should use server-side mechanisms instead of client-side redirects."
• We also reminded ourselves that this checkpoint does not require control of redirects, per the 13 Jun 2002 teleconf, in light of CR experience. More information is in the techniques document.

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:

• No change since (1) we are uncertain of real effect on users and (2) checkpoint 4.3 ensures user control of text colors. We also think that control of animation is likely to cover some cases of automatic color changes.
• Add a Note to say that style control is covered by other checkpoints. In particular, 4.3 ensure that users have control over dynamically changing colors.

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:

• No change to checkpoint 3.4. Seems like most user agents today implement per-scripting language switches.
• Add to techniques document information that (1) per-scripting language switches may be useful, but also (2) a global switch is important since users may not understand which technologies are in use.
• The fact that turning off Javascript also turns off support for style sheets is an implementation issue, and one that affects (confuses) all users, not just users with disabilities.

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:

• The UAWG agrees that the user must be able to make the same state//value changes (e.g., to form controls) programatically as can be done through the UI.
• The UAWG understands that state/value changes may not be stored internally in the DOM (or available through the DOM Core module).
• Therefore, the UAWG accepts this proposal to fix Guideline 6 checkpoints with the following additions/changes:
  • Make similar changes to language in checkpoint 6.5 (UI controls).
  • Use the terms "content" ("control" for 6.5) state" and "content ("control" for 6.5) value", and provide examples. Examples for state include information such as "checked" or "selected". Examples for value include the text of a text area element.

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)