- From: Fred Esch <fesch@us.ibm.com>
- Date: Mon, 2 Feb 2015 16:51:57 -0500
- To: public-svg-a11y@w3.org
- Message-ID: <OF297FEC46.86433452-ON85257DE0.006E7A61-85257DE0.00781E5D@us.ibm.com>
Having another SVG accessibility document or section won't help much
without having authoring tools use the accessibility features. I would hate
to spend a lot of time on documents and not see adoption and user agent
support increase. Once we get the taxonomy fleshed out, I would suggest
getting authoring tools using it be a priority. I am also concerned that we
suggest not inlining styles is useful, but we haven't created a tool that
can show how not inlining styles can benefit color blind, (non AT using)
low vision users or persons with cognitive disabilities.
What do you all want to have on the agenda for Friday? Go back to the
taxonomy or flesh out support for non assistive technology users?
Regards, Fred
Fred Esch
Accessibility, Watson Innovations
AARB Complex Visualization Working Group
Chair
W3C SVG A11y Task Force
IBM Watson Group
From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
To: Fred Esch/Arlington/IBM@IBMUS
Cc: public-svg-a11y@w3.org
Date: 01/30/2015 02:28 PM
Subject: Re: authoring guidance
I think the first step is to review all authoring guidance that is out
there, and identify what needs to be changed!
To get the list started, I did a search of the w3 domain. It turned up:
Accessibility Features of SVG, a W3C note from August 2000
http://www.w3.org/TR/SVG-access/
The Accessibility Support appendix from the main SVG specs
http://www.w3.org/TR/SVG11/access.html (SVG 1.1)
http://www.w3.org/TR/SVGTiny12/access.html (SVG Tiny 1.2, added
section on "user agent accessibility guidelines" which includes
interesting ideas like providing color information or supporting
directional navigation)
https://svgwg.org/svg2-draft/access.html (SVG 2 editor's draft,
doesn't currently include the extra section from SVG Tiny, not that
it's relevant anyway)
It looks like that appendix was based on Charles MN's working draft
of "SVG Techniques for Web Content Accessibility Guidelines"; I don't
think this document was otherwise continued, but I'm sure Charles can
correct me if I'm wrong.
http://www.w3.org/2000/10/wcag2-svg-techs-020318
The section on <desc> and <title> in the main SVG specs
http://www.w3.org/TR/SVG11/struct.html#DescriptionAndTitleElements
(SVG 1.1)
https://svgwg.org/svg2-draft/struct.html#DescriptionAndTitleElements
(SVG 2 editor's draft)
The section on WAI-ARIA attributes in the SVG 2 draft spec
https://svgwg.org/svg2-draft/struct.html#WAIARIAAttributes
Various parts of the Interactivity chapter in SVG 2
https://svgwg.org/svg2-draft/interact.html
Some work on "SVG Linearization" from 2002:
http://www.w3.org/2001/svgRdf/
A few "SHOULD" statements referencing SVG elements in the main
WAI-ARIA specs (nothing controversial, search the page for "svg"):
http://www.w3.org/TR/wai-aria/roles
More links, ideas, and discussion on various mailing lists and
working group wiki pages, e.g.
http://www.w3.org/Graphics/SVG/IG/wiki/Accessibility_Activity
http://www.w3.org/Graphics/SVG/WG/wiki/Accessibility_Issues
http://www.w3.org/community/infographics/wiki/Main_Page
ABR
On 30 January 2015 at 11:28, Fred Esch <fesch@us.ibm.com> wrote:
We had a good discussion today on authoring guidance. What should be our
next steps concerning authoring guidance?
Regards, Fred
Fred Esch
Accessibility, Watson Innovations
AARB Complex Visualization Working
Group Chair
W3C SVG A11y Task Force
IBM Watson Group
Attachments
- image/gif attachment: 39742103.gif
- image/jpeg attachment: 39411264.jpg
- image/gif attachment: graycol.gif
Received on Monday, 2 February 2015 21:53:31 UTC