List Info

Thread: Re: @role in SVG




Re: @role in SVG
country flaguser name
United States
2007-10-16 07:58:02
Hi Henri,

In order for the non-namespaced version to be included, the attributes would need be part of the base language. After some work we have uncovered bugs int the IE implementation of namespaced attributes. Microsoft is tracking those down but the bottom line is using setAttributeNS is a major problem. It gets exacerbated when mixing document formats like SVG.

This deficiency requires people to use JavaScript to initiate UI updates because we can't just have have a style sheet trigger off a CSS property in html. Now we can say that well we should not be catering to IE bugs but the reality is we are dealing with a browser with a very large marketshare.

Now this may not all be a problem for SVG plug-ins but it would be easier for the developer to be able to set an attribute for a cross-cutting technology without using a namespace.

In the UI realm I view roles and states and properties as cross-cutting technologies. It would be nice to make it possible to set cross-cutting attributes consistently across UI technologies.

Rich


Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
us.ibm.com" border="0" alt="Inactive hide details for Henri Sivonen <hsivoneniki.fi>">Henri Sivonen <hsivoneniki.fi>


us.ibm.com); background-repeat: no-repeat; " width="40%">
          Henri Sivonen <hsivoneniki.fi>
          Sent by: public-xhtml2-requestw3.org

          10/10/2007 10:21 AM

us.ibm.com" border="0" alt="">
To
us.ibm.com" border="0" alt="">
Doug Schepers <schepersw3.org>
us.ibm.com" border="0" alt="">
cc
us.ibm.com" border="0" alt="">
www-svg <www-svgw3.org>, public-xhtml2w3.org, Simon Pieters <simonpopera.com&gt;, Aaron M Leventhal/Cambridge/IBMIBMUS, Dave Raggett <dsrw3.org>, public-cdfw3.org
us.ibm.com" border="0" alt="">
Subject
us.ibm.com" border="0" alt="">
Re: role in SVG
us.ibm.com" border="0" alt="">us.ibm.com" border="0" alt="">


On Oct 10, 2007, at 03:59, Doug Schepers wrote:

> 1) XHTML Namespace
> <svg
>   xmlns=&quot;
http://www.w3.org/2000/svg&quot;
>   xmlnslink=";
http://www.w3.org/1999/xlink&quot;
>;   xmlnshtml=";
http://www.w3.org/1999/xhtml&quot;
>;   xmlns:aaa="
http://www.w3.org/2005/07/aaa">
>   <g xhtml:role="checkbox" aaa:checked="true">...</g&gt;
> </svg&gt;

>; 2) Native Non-Namespaced Attribute
> <svg
>   xmlns=&quot;
http://www.w3.org/2000/svg&quot;
>   xmlnslink=";
http://www.w3.org/1999/xlink&quot;
>;   xmlns:aaa="
http://www.w3.org/2005/07/aaa">
>   <g role=";checkbox&quot; aaa:checked="true">...</g&gt;
> </svg&gt;

I'm curious why a third way isn't mentioned:
3) Non-Namespaced Attributes for both role and states/properties with  
the latter prefixed with "aria-" (and no qNames in content but opaque  
strings):
<svg
  xmlns=&quot;
http://www.w3.org/2000/svg&quot;
  xmlnslink=";
http://www.w3.org/1999/xlink&quot;>
  <g role=";checkbox&quot; aria-checked="true">;...</g&gt;
</svg>

Pros:
 * Matches what has recently been proposed for (X)HTML5 and XUL.  
Good both for implementation and author skill portability.
 * Fewer namespaces to deal with (i.e. easier).
 * Copy-paste-friendly.
 * DOM-friendly. (qNames in content are *bad* in the DOM.)
 * Not a chameleon namespace per se. The attributes would be in no  
namespace in XHTML5, SVG and XUL.
 * Semantics and processing can still be imported by normative  
reference from wherever they get defined for HTML5. No need to spec  
all this in the SVG spec.

Cons:
 * Not what the WAI PFWG draft currently says.
 * Unorthodox in terms of XML architecture.

--
Henri Sivonen
hsivoneniki.fi
http://hsivonen.iki.fi/




View Original Image
View Original Image
View Original Image
Re: @role in SVG
country flaguser name
Finland
2007-10-16 14:52:55
Hi,

On Oct 16, 2007, at 15:58, Richard Schwerdtfeger wrote:
> In order for the non-namespaced version to be included,
the  
> attributes would need be part of the base language.
In principle, yes, but in terms of spec organization, the
spec for  
the base language could still import them from another
spec.

[...]
> Now this may not all be a problem for SVG plug-ins but
it would be  
> easier for the developer to be able to set an attribute
for a cross- 
> cutting technology without using a namespace.
I take it that we agree that the namespaceless aria-*
attributes  
would make sense in SVG in addition to HTML5?

-- 
Henri Sivonen
hsivoneniki.fi
http://hsivonen.iki.fi/




[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )