W3C home > Mailing lists > Public > public-cdf@w3.org > January 2007

PF group comments on WICD and CDR last call working drafts

From: Al Gilman <Alfred.S.Gilman@IEEE.org>
Date: Fri, 19 Jan 2007 13:58:18 -0500
Message-Id: <p06110408c1d6c38d217b@[192.168.1.100]>
To: public-cdf@w3.org
Cc: wai-liaison@w3.org

<note
class="inTransmittal">

References:
http://www.w3.org/TR/2006/WD-CDR-20061122/
http://www.w3.org/TR/2006/WD-WICD-20061122/
http://www.w3.org/TR/2006/WD-WICDFull-20061122/
http://www.w3.org/TR/2006/WD-WICDMobile-20061122/

These comments have been collected and lightly reviewed within the
User Agent Working Group and the Protocols and Formats Working Group.

Where they are not clear or you feel you need to reject a comment, we
would welcome the opportunity to discuss the issues for the purposes
of clarification and mutual understanding.

Some of these comments do seem to reflect a failure to implement
our comments the last time.

Thanks,

Al
/chair, PFWG

Gottfried Zimmermann and Jon Gunderson particularly contributed to 
these comments.

</note>

Compound Document by Reference Framework 1.0

Section 1.2
Related Documents: It would be nice to add "Web Integration
Compound Document" at least once when using the acronym "WICD".

Section 1.3
Have an example of an alternative to the MathML and how the user 
would be choose between alternatives

Section 2.1
Document Object Model.  Quote: "CSS property inheritance is
inhibited at inclusion boundaries."  Could this be an accessibility 
problem when users have their user-defined CSS?

Add Section
Describe keyboard navigation between compound documents by inclusion 
or reference and the ability to give interactive elements keyboard 
focus through ARIA techniques.

Definitions.
"Focus traversal" is a defined term, but nothing
in the document addresses this topic.  CDR should state that any profile
conforming to CDR shall define how focus traversal is handled, and how the
authors of parent and child documents can define navigation schemes.

WICD Core 1.0

Section 3.2.1
* No text equivalent in example

* Clarification of the difference between "static" and "frozen" rendering?

* Why are links in "static" and "frozen" not selectable, this would 
be very useful to people with disabilities who may need the "static" 
or "frozen" state to activate the link

Section 3.2.2
* Need to specify a keyboard model for activating interactive 
elements in sprites

Section 3.2.3
* The use of transparency can be a problem for people with visual 
impairments or visual processing disabilities.   There needs to be a 
way for users to configure the user agent to render the objects 
separately and to restyle content to meet their perceptual needs. 
For example rendering content separately in document order using a 
high contrast stylesheet.

Section 4.0
* No requirements for keyboard support for moving keyboard focus in 
and out of objects (Maybe Section 6??)

Sections 4.2 and 4.3
* Two separate standards for support for audio and video "pause", 
"start" and volume control, in XHTML the user will have no control 
and in SVG there is at least an option for users to have control
* Users need control over playing
* Users should have an option to have a player with the controls play audio

4.4 Child content accessibility guidelines
* "For accessibility, conforming WICD Core 1.0 user agents must 
provide the option of pausing, rewinding, or stopping video. See 
section 3.2 of [User Agent Accessibility Guidelines 1.0]."

needs to be changed to

"For accessibility, conforming WICD Core 1.0 user agents must provide 
the option of pausing, rewinding, or stopping audio and video. See 
Checkpoint 4.5 of [User Agent Accessibility Guidelines 1.0]."

* For accessibility, conforming WICD Core 1.0 user agents must allow 
the user to slow the presentation rate of rendered audio and 
animation content (including video and animated images). See section 
4.4 of [User Agent Accessibility Guidelines 1.0].

needs to be changed to

For accessibility, conforming WICD Core 1.0 user agents must allow 
the user to slow the presentation rate of rendered audio and 
animation content (including video and animated images). See 
Checkpoint 4.4 of [User Agent Accessibility Guidelines 1.0].

* A section should be included on user control of Volume, see UAAG 
1.0 Checkpoints 4.7 and 4.8

Section 5 Hyperlinking
* Again support text equivalents in code examples

* Expected behavior or user agents in providing the alternatives for 
selecting links

* Moving keyboard focus into and out of OBJECT elements (Section 6)

Section 6 Focus Handling
* Keyboard support is very important for accessibility

* Need to make sure there is keyboard support for ARIA techniques for 
interactive elements

* When authors set "focusable" to "skip" can the user interact with 
any of the skipped content, like with a pointing device?

NOTE: If users can still interact with pointing devices or some other 
interface then the user must have the ability to override author 
setting to use the keyboard to navigate content.

* Need concepts of "headers" or "sections" within compound documents 
with support for keyboard navigation

Section 10
* Support for users supply their own style sheet for rendering 
content is not addresses.  For example someone with a visual 
impairment or visual processing disability could define their own 
style sheet for rendering content and would want disable author 
styling and use their own style sheet.  How is this important issue 
addressed in the specification?
Received on Friday, 19 January 2007 18:58:42 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:22 UTC