- From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
- Date: Tue, 27 Jan 2015 19:20:18 -0700
- To: public-svg-a11y@w3.org
- Message-ID: <CAFDDJ7x8Teyu-d90MzN_syrO2gZAZDm6+p1O8gbq+QKypoAWfQ@mail.gmail.com>
One addition for the agenda: Default API mapping for elements not supported by the browser (Hopefully only an extra 5-10 minutes on Richards' discussion of edits to the API mappings document) This has come up a couple times as Richard has tried to implement the suggestions from last week. If the Accessibility Mapping isn't strictly tied to a specific version of SVG (and it can't be, because the SVG spec won't have strict versioning), browsers are going to encounter content with elements they don't support, either because the element is obsolete or because the element is new. An important thing to consider is that unrecognized tags in SVG are not rendered to the screen at all. This is very different from HTML, where unrecognized tags are just treated as `<span>` elements, and therefore can still be styled into visible widgets, so ARIA still needs to be supported. I think we should have a general rule for these cases, but I'm not sure whether it should be to ignore the element (since it isn't displayed for regular users) or to make it accessible (e.g., if the browser can't display a video/audio element, all the more important to make the text alternative available). ABR On 26 January 2015 at 15:44, Fred Esch <fesch@us.ibm.com> wrote: > Time of meeting is 9:00AM EST, 14:00 UTC, duration is 1 hour > Zakim Bridge +1.617.761.6200, conference 2742 ("ARIA"), IRC channel is > *#svg-a11y* > > *Please note we have a new IRC channel #svg-a11y * > > minutes from January 23 meeting: ?? > SVG Accessibility API Mappings > http://rawgit.com/w3c/aria/master/svg-aam/svg-aam.html > > agenda > 1. SVG Accessibility API Mappings 10 minutes Rich > 2. CSUN 10 minutes Fred > 3. Taxonomy next steps 15 minutes Fred > - Start expanding the taxonomy, put it on a Wiki? > 4. Scope task force effort - > A11y not just for blind users (Amelia, Doug, Rich...) > What will go into authoring practices vs taxonomy... > > > > Regards, > > Fred Esch > Accessibility, Watson Innovations > AARB Complex Visualization Working Group Chair > W3C SVG A11y Task Force > [image: IBM Watson Group] > > [image: Fred] > > >
Attachments
- image/jpeg attachment: 5F187264.jpg
- image/gif attachment: 5F883295.gif
Received on Wednesday, 28 January 2015 02:20:46 UTC