[CDF Framework 1.0] 2.5.2.2 Focus Ring

I disagree with the concept of an activation/de-activation mechanism
to traverse focus into a child document.  Consider the use case of a
SVG menu where the SVG menu is one document referenced by the XHTML
parent document, and each menu item is a focusable entity within the
SVG.  In order to even get into the menu, i've got to tab to the menu,
press enter, then tab some more to get to the item, then have some
mechanism to de-activate the menu if I want to get out.  This is not
intuitive.

The end-goal of defining CDF rules is that the integration should
appear SEAMLESS to the user.  See the Section 2.5.4 in your "Compound
Documetn by Reference Use Cases and Requirements" document:

"2.5.4 SVG image is embedded interactive part of the Web page (SVG has links)

An SVG image is used as 2D-graphics in a Web page. The SVG image has
links. The user can navigate directly from an XHTML link into the
first link in the SVG image; the SVG image is SEAMLESSLY INTEGRATED
with the XHTML page. The user navigates directly from the last link
inside the SVG image to the next link, after the SVG image, in XHTML.
"

I have put emphasis on the words "SEAMLESSLY INTEGRATED".

Thus, I think the focus ring of a CDF should include the focus rings
of all child elements "un-rolled" into the parent focus ring.

For example, if a SVG document svg.svg is :

<svg focusable="auto">
    <rect id="box" focusEast="s_link2" .../>
    <a id="s_link1">....</a>
    <a id="s_link2" focusWest="#box">...</a>
    <a id="s_link3">...</a>
</svg>

Then the focus ring of this document is:

s_link1 -> s_link2 -> s_link3

If the parent document is:

<html>
    <body>
       <a id="h_link1">...</a>
       <object id="obj1" href="svg.svg" />
       <a id="h_link2">...</a>
    </body>
</html>

The child document's focus ring is un-rolled flat and inserted into
the parent document's focus ring.  The forward navigation focus ring
would then be:

h_link1 -> s_link1 -> s_link2 -> s_link3 -> h_link2

When going from h_link1 to s_link1, the user is now within the SVG
child document.  Forward navigation will lead to the "next" element
(s_link2).  Navigating "southeast" from here, the UA will attempt to
navigate via the focusSouthEast element (see
http://www.w3.org/TR/SVGMobile12/interact.html#specifyingnavigation). 
If the SVG document does not have a "South East" element, then this is
effectively navigating out of the SVG document back into the parent
document and user is placed at h_link2.  Navigating backwards will
lead to s_link3.

Regards,
Jeff

Received on Monday, 15 August 2005 15:31:15 UTC