Re: Agenda (updated) January 15, 2016 SVG accessibility Task Force meeting

Regrets…

On Thu, 14 Jan 2016 22:19:58 +0100, Fred Esch <fesch@us.ibm.com> wrote:

IMHO:

> SVG AAM issues
>    Issue: Does an empty title or description nullify title/description
>    presence when deciding whether to add an object to the accessibility
>    tree? Git Issue #134

Yes

>    Issue: Does role none/presentation always exclude an element from
>    inclusion in the accessibility tree?  Things that appear to conflict:
>    action listeners, presence of global aria properties.  If role
>    none/presentation always exclude an element from inclusion in the
>    accessibility tree, we need normative text stating so.  Git Issue #136

No? Only presentation? Do people change roles of stuff? I think of doing  
so to provide dynamic access… which is only relevant if we don't have  
enough state/poperty

>    Issue:  tspan element - should it be treated like a span and by  
> default
>    not appear in the accessibility tree?  Part of Git Issue #133

Yes

>    Issue: Should xml:title be xlink:title? Section 10.1 Name and
>    Description has a couple of references to the "xml:title attribute".
>    From some quick searching, I have yet to find any reference to that
>    attribute; I have, however, found references and documentation for
>    xlink:title. Typo? Git Issue #137

seems like it.

cheers

>    More on issue #137 Test alternative for accessible description
>
>     Regards,
>    Fred Esch
>  Watson, IBM, W3C
>   Accessibility
> IBM Watson       Watson Release Management and Quality
>
>


-- 
Charles McCathie Nevile - web standards - CTO Office, Yandex
  chaals@yandex-team.ru - - - Find more at http://yandex.com

Received on Friday, 15 January 2016 05:23:03 UTC