Re: Outlines for new Implementation guide documents for Core (previously WAI-ARIA), HTML 5.1, and SVG2

Hi Brian,

I can see your point wrt. a group. I can suggest alternative text. The HTML
spec. allows it on all elements but there are places where we would not
have a mapping. I would refer to not make it applicable on all elements
but,


Here is the role definition in HTML5:
http://www.w3.org/TR/2012/CR-html5-20121217/dom.html#aria-role-attribute

I redefine the text similar to the text we put in HTML5:

This is an ARIA Role attribute as defined by [ARIA] Section 5.4 Definition
of Roles.


The attribute, if specified, must have a value that is a set of
space-separated tokens representing the various WAI-ARIA roles that the
element belongs to.The WAI-ARIA role that an SVG element has assigned to it
is the first non-abstract role found in the list of values generated when
the role attribute is split on spaces.

The implementation guide will define how SVG elements and their attributes
map to platform accessibility API services on OS platforms. It is important
to note that because SVG objects are persistent there will be instances
where accessible objects are not created to improve performance, reduce
memory footprint, and allow for greater assistive technology performance.

Thoughts?

Rich


Rich Schwerdtfeger



From:	Brian Birtles <bbirtles@mozilla.com>
To:	"'www-svg'" <www-svg@w3.org>, Richard
            Schwerdtfeger/Austin/IBM@IBMUS
Cc:	Kurosawa Takeshi <taken.spc@gmail.com>
Date:	01/15/2014 06:49 PM
Subject:	Re: Outlines for new Implementation guide documents for Core
            (previously WAI-ARIA), HTML  5.1, and SVG2



(Replying to www-svg since this is SVG-specific)

(2014/01/16 6:34), Richard Schwerdtfeger wrote:
> Here is the URL to find links to the 3 outlines:
> http://www.w3.org/WAI/PF/wiki/ARIA
>
> This is a work in progress but I have started the outlines for each. We
> should discuss these at the Face to Face.

Hi Rich,

Thank you for this. At last week's telcon I brought to the group the
issue raised by Kurosawa-san that SVG2 currently says that only rendered
SVG elements can have role attributes.[1][2]

Kurosawa-san pointed out that "rendered elements" is not really defined
and the attribute index defines the places where role is allowed
inconsistently. I raised the question whether we need to restrict the
set of elements at all or whether we can just allow role attributes
everywhere like I believe HTML allows.[3]

We decided we should ask someone who knows more about ARIA (like
Kurosawa-san and yourself).

Will the documents referred to in your mail cover this role (haha)? If
not, do you have any suggestions about this?

Thanks,

Brian

[1] Discussion here: http://www.w3.org/2014/01/09-svg-minutes.html#item01
[2] Original issue here:
http://lists.w3.org/Archives/Public/www-svg/2013May/0000.html
[3]
http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#wai-aria