Re: Wiki updated…

Thanks Chaals,

As far as the SVG on GitHub goes, I made a branch and will be dropping
marked up SVG (roles, titles and desc added) into my branch.  I don't think
replacing the originals is the way to go, since my markup is a simply a
first guess at what we might want to do.  Is a branch the best way to keep
stuff we experiment with? Or should I be doing something else?

                                                              
                                                              
                    Regards,                     Fred         
                                                              
                   Fred Esch                                  
       Accessibility, Watson Innovations                      
    AARB Complex Visualization Working Group                  
                     Chair                                    
        W3C SVG Accessibility Task Force                      
                   IBM Watson                                 
                                                              
                                                              






From:	chaals@yandex-team.ru
To:	SVG WG axs TF TLA þ-f ... <public-svg-a11y@w3.org>
Date:	04/28/2015 07:48 AM
Subject:	Wiki updated?



Hi folks,

I have updated the wiki pages a fair bit:
https://www.w3.org/wiki/SVG_Accessibility is now grouped into a few
sections:

1. Use case examples, sorted by rough categories
These are SVG images that I am slowly uploading to the wiki, organised by
categories... I am trying to make sure that as images are added, they get
at minimum a reasonable description, and a link to the code in github.
Ideally I'd also like to have notes about what good (or bad) practices they
implement, and what makes sense for navigation.

2. Draft documents
Currently there is Rich's draft on navigation, our categorisation of issues
based on types of disability, and the cognitive task forces requirements
and issues document. I guess an obvious thing to add is draft techniques
for content accessibility, as we start drafting them?

3. Specs and such
This is links to actual specification documents, and articles about how to
get it right. If there are more than 3 of these in the world, it would be
helpful to get them linked.

People should feel free to edit the pages and add stuff - I am never going
to have time to maintain it, so I hoped to set up a reasonably clear
structure that is useful and easy for people to build on in the bit that
interests them.

Cheers

Chaals

--
Charles McCathie Nevile - web standards - CTO Office, Yandex
chaals@yandex-team.ru - - - Find more at http://yandex.com