W3C home > Mailing lists > Public > public-svg-a11y@w3.org > April 2016

Re: Agenda April 6 SVG accessibility task force meeting

From: Chaals McCathie Nevile <chaals@yandex-team.ru>
Date: Wed, 06 Apr 2016 14:54:31 +0200
To: public-svg-a11y@w3.org
Message-ID: <op.yfh0s5its7agh9@widsith.local>
Regrets - I *may* be able to attend the first half, but no more.

On Tue, 05 Apr 2016 18:17:47 +0200, Fred Esch <fesch@us.ibm.com> wrote:

> Role mapping for SVG element
> HTML has different roles for the SVG element than SVG AAM
> That spec does not map <svg> to any existing ARIA role
> It does, however, map it to the relevant graphics-related roles in each  
> API (or group if no appropriate role exists) vs group role

Is there a clearer explanation of this issue somewhere?

SVG in HTML seems to be a container element, if we want to allow it to be  
accessible, since role=img would effectively block looking inside it.

> Expectations for presentational element with title child
> Should role none/presentation exclude an SVG element from the  
> accessibility
> tree when the element has a title/desc
> https://lists.w3.org/Archives/Public/public-svg-a11y/2016Mar/0064.html
> https://lists.w3.org/Archives/Public/public-svg-a11y/2016Mar/0062.html

IMHO, not sure about title, but where there is a desc that should remain  
discoverable at least for role=presentation.


Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Wednesday, 6 April 2016 12:55:33 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:28:20 UTC