Re: Accessibility of SVG - low vision issues?

I have already started studying these examples.  It is an interesting
problem.  I am going to refer you to an example (not SVG) that Tom Jewett
did for UML diagrams.  The key thing is a data dictionary associated with
the diagram.  The thing about such a diagram is that it records the binary
relation expressed by the graph (combinatorial).  The site is at:

Example from my online text, Database Design with UML and SQL:

http://www.tomjewett.com/accessibility/alt-text.html

I believe that any accessibility interface that is automated should capture
the "data dictionary" of the defining combinatorial graph. Note how each of
these diagrams is really based on a combinatorial graph.  Even the "cool
graph" is a bipartate directed graph. The pie charts are just graphs of
functions.  etc.
The degree to which an SVG object can express the embedded combinatorial
graph is the degree to which a data dictionary can be constructed.


Wayne





On Tue, May 26, 2015 at 9:02 AM, <chaals@yandex-team.ru> wrote:

> Thank you Vedran, and Wayne...
>
> Please look at the SVG images in each of
> https://www.w3.org/wiki/SVG_Accessibility/School_Graphs
> https://www.w3.org/wiki/SVG_Accessibility/Cool_Graphs
> https://www.w3.org/wiki/SVG_Accessibility/Directed_Graphs
> <https://www.w3.org/wiki/SVG_Accessibility/School_Graphs>
> https://www.w3.org/wiki/SVG_Accessibility/Mapping_Graphs
> <https://www.w3.org/wiki/SVG_Accessibility/School_Graphs>
> https://www.w3.org/wiki/SVG_Accessibility/Other_Graphs
> <https://www.w3.org/wiki/SVG_Accessibility/School_Graphs>
> https://www.w3.org/wiki/SVG_Accessibility/Schematic_Graphs
> <https://www.w3.org/wiki/SVG_Accessibility/School_Graphs>
>
> and see what issues there are for low vision users.
>
> One important task is writing them down -  in reply to this thread, or
> editing the wiki page directly if you have a login, or write to me and
> getting me to pass it on...
>
> Another useful thing to do is to try out SVG implementation in whatever
> browsers you use, and figure out what works and is helpful, and what
> doesn't work and causes problems. Please remember to specify what
> browser/OS/version you are using. I suspect we have a limited understanding
> of how magnification really works across the web platform, and getting some
> systematic sense of it would be good.
>
> For example, some browsers zoom text, some zoom pages, some reflow things
> and some may not, etc.
>
> Also, if you have examples of images that we are missing - currently we've
> got nothing interactive and there are a lot of interactive SVG things out
> there - which we can publish (i.e. are public domain or similar), we'd be
> grateful for them...
>
> cheers
>
> Chaals
>
> 26.05.2015, 08:53, "Vedran Vucic" <vedran.vucic@gmail.com>:
>
> I am willing to help. Please let me know what I am supposed to do.
>
> Thanks
>
> Vedran
>
> On Tue, May 26, 2015 at 1:30 AM, <chaals@yandex-team.ru> wrote:
>
> Hi,
>
> the SVG accessibility task force is trying to do a bunch of things. One of
> them is to collect somewhat representative SVG images found "in the wild",
> and figure out what issues they pose to users - which is a useful thing
> when we try to figure out how to solve those problems.
>
> There is something of a collection at <
> https://www.w3.org/wiki/SVG_Accessibility#Images_for_playing_with_to_determine_use_cases_and_requirements>
> although there is a lot that we probably need to add.
>
> Anyway, if people want to look over that, and provide comments, whether
> here, on the github repository, or to the SVG accessibility task force,
> that could be a helpful thing to do…
>
> cheers
>
> chaals
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
>
>
>
> --
> Charles McCathie Nevile - web standards - CTO Office, Yandex
> chaals@yandex-team.ru - - - Find more at http://yandex.com
>
>