- From: Chaals McCathie Nevile <chaals@yandex-team.ru>
- Date: Fri, 06 Nov 2015 17:21:08 +0100
- To: public-svg-a11y@w3.org
Wait, despite the question of whether we would have one and no agenda, there was a meeting? Should we assume by default that there is a meeting unless it is cancelled, or that there isn't a meeting unless we get an advance agenda? I realise I am not the one getting up at crazy early in the morning to make the meetings, but there is often still a pretty solid cost to being available. So it would be good to have a sense of how I should plan around this. cheers On Fri, 06 Nov 2015 16:58:46 +0100, Fred Esch <fesch@us.ibm.com> wrote: > > URL irc://irc.w3.org/svg-a11y Mode no mode Users 8, 0@, 0%, 0 > + > Topic <none> > > > > > #svg-a11y > -->| YOU (fesch) have joined #svg-a11y > fesch topic: SVG-AAM > AmeliaBR http://rawgit.com/AmeliaBR/aria/svg-aam/svg-aam/svg-aam.html > fesch scribe:fesch > AmeliaBR > http://rawgit.com/AmeliaBR/aria/svg-aam/svg-aam/svg-aam.html#mapping_state-property > fesch reviewing Amelia's changes > fesch abr: clarified xlink in section 9 (deprecated) with a new > paragraph > fesch ds: may not need to jump through all those hoops > fesch abr: trying to avoid painful rules > fesch ds: just refer the SVG spec... > fesch abr: can be clear this is our application the SVG rule > fesch rs: I will be updating the aria portion of the SVG 2 spec > fesch fe: are we changing the samples to not use xlink? > fesch abr: SVG 2 recommendation is that authoring tools should use > both > fesch ds: href works in IE 9, will check in chrome > fesch abr: if they have good support if in existing browsers we will > change the examples > fesch abr: date - will get tiedied up for publication > fesch abr: hidden vs visible - > fesch rs: have to work with the core AAM on hidden vs visible > fesch abr: I don't have too much trouble with def in glossary, since > I changed verbage in our SVG docs ... > to include perceivable > fesch abr: text in core AAM is more problematic as it references SVG > visibility property > fesch rs: sound fine for now > fesch ds: on mac href (no xlink) does not work on chrome or firefox > fesch abr: can't change examples to use href alone (need to include > xlink) > AmeliaBR > http://rawgit.com/AmeliaBR/aria/svg-aam/svg-aam/svg-aam.html#mapping_view > fesch abr: viewTarget - back to SVG WG > fesch abr: added editors note about status... and value of viewTarget > fesch abr: process I proposed for view - does not have a target in > accessibility tree - > fesch rs: can you navigate inside a view > fesch ds: all a view is like a link > fesch ds: navigation within the area is not dependent upon the view > fesch ds: we might want to change that > fesch ds: view is like a viewbox... focus could still be outside that > fesch abr: we want it to follow the link and have focus in the view > fesch discussion on navigation > fesch ds: view was originally a visible thing... > fesch abr: the view itself is not a link - viewTarget should get > focus > fesch ds: a view is a view! > fesch fe: could say a view does not support navigation > fesch abr: when we have a sprite sheet, want the AT to read the > title and description of the sprinte > fesch abr: when you have a map and you click on a link the map zooms > in... > fesch abr: when you navigate with a jump link you want the focus to > change > fesch abr: complication how we are implementing it with the > accessibility tree > fesch rs: may need new semantics > fesch fe: in the second case why can't we treat it like flowto? > fesch abr: focus doesn't move (only for AT) > fesch rs: we want a flowto + change in focus > fesch abr: a link will change focus... > fesch abr: view not in accessibility tree, can only treat it as > modifying the SVG. > fesch ds: how much is a view used? > fesch abr: not much -sprites > fesch ds: for the interactive document case, most people will use > JavaScript, for sprites, you want to > update the name and description > fesch s/ds/abr/ > fesch ds: if you link to a focus target we can do that, when a view > does not have a target, then the > author has to do it theirself > fesch rs: we would need to make it aware there is a change in content > fesch rs: this is automatic > fesch abr: no, if you follow a link and the target is a view. > fesch ds: only time it is "automatic" is via the URL, not the same > kind of thing that is a link > fesch abr: I would like the AT only to get the name/description from > the view, not lots of extra stuff. > fesch abr: for views, you have a sheet of sprites. > fesch ds: need everyone to understand use and view > fesch abr: are folks ok with the editors note? > fesch ds: at this point this is the best thing we can do > fesch abr: other big outstanding issue is use - > fesch abr: right now they are treated like a stamp (image) > fesch abr: if use does not have a name (label....) then can look in > content... > fesch abr: if SVG goes to a web components model, then a bigger > problem > fesch rs: web components would be ARIA 2.O for now treat as an image > fesch rs: goal is to get this document on par with core AAM - > fesch rs: this will be a heartbeat... > fesch rs: amelia will update, then we send to MC as a heartbeat to > get that done > fesch abr: we can do an end to end the Graphics Module... > fesch fe: I sent an email on that one too > fesch rs: target both Graphics Module and SVG AAM targeted for 1st > week of Dec > fesch rrsagent, make minutes > > > > 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, 6 November 2015 16:21:43 UTC