W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > July to September 2016

Re: SVG 2 review request

From: Rich Morin <rdm@cfcl.com>
Date: Thu, 11 Aug 2016 09:01:02 -0700
Cc: Nikos Andronikos <Nikos.Andronikos@cisra.canon.com.au>, www-svg@w3.org
Message-Id: <89CC3AB5-E5A8-46F1-B1F0-7542AD2B32E5@cfcl.com>
To: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
To get an idea of what is being considered for SVG 2, I skimmed:

  SVG 2 new features

I only found two items that directly referenced accessibility:

 - Include WAI-ARIA attributes and define semantics

 - Change role mapping for the 'a' element to depend on whether
   it is actually a valid link.

Both of these seem reasonable, though the definition of semantics
for the WAI-ARIA attributes could be tricky.

However, it strikes me that some of the other changes (such as
the removal of SVG Fonts) might have an impact on accessibility.
Does any tooling currently depend on the use of these fonts?

Moving into the realm of science fiction, I have been speculating
about ways to make SVG-encoded charts and diagrams accessible:


For example, I typically use OmniGraffle to create data flow
and system architecture diagrams.  If I were to export these as
SVG, might it be possible to recognize the underlying semantics?
If so, it might be possible to describe the connectivity and/or
enable navigation and exploration of the nodes and edges.

Corresponding techniques could (conceivably) be applied to other
charts and diagrams, including functions graphs, histograms, pie
charts, scatter plots, and Venn diagrams.  

Might there be anything that SVG 2 could do to enable this sort
of thing over coming years?


http://www.cfcl.com/rdm           Rich Morin           rdm@cfcl.com
http://www.cfcl.com/rdm/resume    San Bruno, CA, USA   +1 650-873-7841

Software system design, development, and documentation
Received on Thursday, 11 August 2016 16:01:32 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 11 August 2016 16:01:33 UTC