W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > January to March 2006

Draft comments on Compound Document by Reference Framework 1.0 - Last Call

From: Jim Allan <allanj@tsbvi.edu>
Date: Fri, 20 Jan 2006 11:31:33 -0600
To: <w3c-wai-ua@w3.org>
Message-ID: <OKEMIPICHMIEKBHGPDMFGEKJDAAA.allanj@tsbvi.edu>

comments in reference to Compound Document by Reference Framework 1.0
[http://www.w3.org/TR/2005/WD-CDR-20051219/]
Please add additional comments.

Jim

2.1.4 SecurityException
http://www.w3.org/TR/2005/WD-CDR-20051219/#security-exception

Accessing parent or child documents through the DOM as described in sections
2.1.2 and 2.1.3 can be disabled for security reasons. In such cases user
agents should throw a SecurityException

<UAWG> User agents should inform the user that access has been blocked for
security reasons.
</UAWG>


2.3 Link Activation
http://www.w3.org/TR/2005/WD-CDR-20051219/#link-activation
<snip>

Nested hyperlinks are more complicated. The following illustrates nested
hyperlinks. Suppose the parent document is XHTML as follows:

<!-- parent.html -->
<html:a href="LargeMap.html">
  <html:object type="image/svg+xml" data="child.svg"/>
</html:a>

And the child SVG document contains the following:

<!-- child.svg -->
<svg:a xlink:href="DetailedCountyMap.html">
  <svg:text>county map</svg:text>
</svg:a>

<snip>

The implication is that the behavior of nested hyperlinks depends on how the
hyperlink is activated. Here are some examples which illustrate common
possibilities:

* Suppose the user gives focus to an <html:a> within the parent XHTML
document above and then hits the "Enter" key to activate that link. In the
example above, the <html:a> element is the event target. This would cause
execution of the hyperlink to "LargeMap.html".

* Suppose the user gives focus to an <svg:a> within the child SVG document
and then hits the "Enter" key to activate that link. In the example above,
the <svg:a> element is the event target. This would cause execution of the
hyperlink to "DetailedCountyMap.html".

* Suppose the user uses a mouse or other pointer device to click on the work
"county map" in the above example. Because this pointing device event occurs
over geometry controlled by both the parent XHTML and child SVG documents,
and because the SVG document is the most deeply nested, then the target
element will be chosen according to the rules in the SVG specification. In
the example above, this will cause the <svg:text> element to be the event
target. The <svg:a> element will receive the event after bubbling from the
<svg:text> element, which will cause a hyperlink to
"DetailedCountyMap.html".

<UAWG>The above scenario provides some intriguing accessibility problems. At
each stage the user must be given a choice 1) activate the anchor, 2) enter
the nested container. The user agent must inform the user of the available
paths, so the user is able to give focus to the required element.

Given the first 2 bullets in the scenario, the user agent will display the
text "county map" with html anchor designation (blue and underlined,
assuming no style sheet). When the user gives focus to the anchor "county
map", the user agent should inform the user that a hyperlink may be
activated or a child container may be entered. The user now has the option
of viewing "LargeMap.htm" or entering the "child.svg" container. After
entering the "child.svg" container can the user be informed that an
additional anchor (svg:a) is available to be given focus and execution to
display "DetailedCountyMap.htm" (the second bullet). At any point in the
tree the user (with information available from the user agent) should be
able to orient themselves (determine where they are) within the document(s)
tree (parent document - html:a - child.svg - svg:a) and navigate back up or
down the tree.

The 3rd bullet "* Suppose the user uses a mouse or other pointer device to
click on the work "county map" in the above example. Because this pointing
device event occurs over geometry controlled by both the parent XHTML and
child SVG documents, and because the SVG document is the most deeply nested,
then the target element will be chosen according to the rules in the SVG
specification. In the example above, this will cause the <svg:text> element
to be the event target. The <svg:a> element will receive the event after
bubbling from the <svg:text> element, which will cause a hyperlink to
"DetailedCountyMap.html".

Question: How will a pointing device user able to activate the html:a
"LargeMap.html"? or Where in the geometry does one point to activate the
html:a "LargeMap.html"?  How is the user agent to inform the user that two
(or possibly more) paths are available from a single (visually apparent)
anchor?
</UAWG>
Received on Friday, 20 January 2006 17:32:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:51:32 GMT