W3C home > Mailing lists > Public > public-w3process@w3.org > November 2015

Re: ISSUE-100

From: Chaals McCathie Nevile <chaals@yandex-team.ru>
Date: Tue, 17 Nov 2015 19:18:14 +0100
To: "public-w3process@w3.org" <public-w3process@w3.org>, "Stephen Zilles" <szilles@adobe.com>
Message-ID: <op.x79bsom2s7agh9@widsith.local>
On Tue, 17 Nov 2015 18:12:04 +0100, Stephen Zilles <szilles@adobe.com>  
wrote:

> Chaals,
>
> I am fine with your diagram and have no comment on the accessibility of  
> it.

OK. But since I am spending a fair bit of time on accessibility of SVG -  
in particular because some people assert that it is a viable way to make  
images accessible today, which doesn;t seem to be true but should - and  
since there are people in this group who cannot see the images as they are  
drawn, I think that is an important aspect.

> However, the request of Issue 101 (sic) was to list the key entry  
> criteria for each state transition rather than have (vague) text.

Yes.

> You have dropped most of the criteria listed in the diagram previously
> under discussion.

Actually, I haven't taken most of them in yet. I'm working from my source,  
to improve the accessibility as I go - whatever your tool was, it does a  
horrible job mangling a lot of basic stuff.

There is conceptually one diagram, but I have split it into 3 pieces for  
clarity, and to mess with one bit at a time.

The attached version shows the process for changing a Recommendation, adds  
some accessibility to the base, but *still* doesn't add the requirements  
piece nor link to transition requirements. I'm thinking my way through  
that and expect it to happen, but I am trying to keep the thing as  
uncluttered and easily followed as I can - which is hard.

The images are actually on github, so you can file issues directly,  
although the repo is primarily concerned with making accessible SVG  
images, not the W3C process:

The basic flow, WD to Rec:
http://github.com/SVG-access-W3CG/use-case-examples/rectrack.svg
- and http://svg-access-w3cg.github.io/use-case-examples/rectrack.svg to  
see the latest version.

Development with Notes included:
http://github.com/SVG-access-W3CG/use-case-examples/rectrack-note.svg
and http://svg-access-w3cg.github.io/use-case-examples/rectrack-note.svg

This version - how to change a Rec:
http://github.com/SVG-access-W3CG/use-case-examples/revisedrec2.svg
and http://svg-access-w3cg.github.io/use-case-examples/revisedrec2.svg

If people - especially Dave, who asked for improved diagrams to start with  
- have comments on the visual style, I think that's actually helpful...

> I have attached an updated version of that diagram with the last agreed  
> upon labels.

yes, I'll be copying that information as I get to it :)

> This diagram also splits out the cases for Edited Recommendations,  
> something that would only be needed in the section on Editing  
> recommendations much as the Notes section is only needed under Notes.

Yep.

cheers

> Steve Z
>
>> -----Original Message-----
>
>> From: Chaals McCathie Nevile [mailto:chaals@yandex-team.ru]
>
>> Sent: Friday, November 13, 2015 8:51 AM
>
>> To: public-w3process@w3.org
>
>> Subject: ISSUE-100
>
>>
>
>> Hi,
>
>>
>
>> I have tried to modify the graphics - and at the same time improve their
>
>> accessibility. Sadly the latter job is hard - weak aria implementation  
>> means
>
>> screen-reader accessibility is limited, and even weaker general SVG
>
>> implementation means that for the most part screen readers are getting  
>> the
>
>> best deal going - which is still rotten.
>
>>
>
>> Anyway, here is a diagram that includes the ability to publish as notes.
>
>>
>
>> I would anticipate having a stripped-down version of this for the start  
>> of
>
>> chapter 7, as the "standard" path, introduce this version where we talk  
>> about
>
>> notes and the fact that a WD might end up as a note instead of moving  
>> along
>
>> the hoped-for path, and then add underneath a similarly better-annotated
>
>> and more accessible version of what is already in there that covers the  
>> process
>
>> of revising a Rec.
>
>>
>
>> --
>
>> Charles McCathie Nevile - web standards - CTO Office, Yandex
>
>>   chaals@yandex-team.ru<mailto: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


revisedrec2.svg
(image/svg+xml attachment: revisedrec2.svg)

Received on Tuesday, 17 November 2015 18:18:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 17 November 2015 18:18:46 UTC