W3C home > Mailing lists > Public > public-silver@w3.org > September 2019

Re: Agenda for Silver Content Meeting of 24 September 2019

From: John Foliot <john.foliot@deque.com>
Date: Tue, 24 Sep 2019 16:51:19 -0500
Message-ID: <CAKdCpxyQ_3X1VBKSB7Tm62UNZsaEvdB5W-9=EVtry81qwj6prQ@mail.gmail.com>
To: Silver Task Force <public-silver@w3.org>
Cc: Jeanne Spellman <jspellman@spellmanconsulting.com>, "Hall, Charles (DET-MRM)" <Charles.Hall@mrm-mccann.com>, Andrew Kirkpatrick <akirkpat@adobe.com>, Alastair Campbell <acampbell@nomensa.com>
Charles writes:

> The attendees were not in agreement of using the terms from EN 501 549
Annex B; OR in being limited to those specific 11 needs

I believe we need to include those pre-existing 11 terms as part of
our Recommendation. I would not be opposed to adding more terms, but
failing to add those pre-existing terms will frustrate take-up in Industry,
who are concerned about meeting legal compliance requirements, of which
those 11 specific needs have been identified legally in the EU. Silver
needs to work in the regulatory environment as well!


> We need to identify and agree on a method of tracking the progress and
preventing overlap on this work – like using GitHub issues.

A huge +1!

I personally am finding it quite difficult to track all of the activity
that is currently underway when all of the notes (etc.) are contained in
Google Docs that are hard to find and follow (especially when comments are
then added to the document).

Additionally, I am finding Google Docs to be inaccessible to me: for
example when attempting to review a Doc remotely on my phone, the text does
not scale or reflow per *SC **1.4.4 Resize text* and *SC 1.4.10 Reflow. *

Additionally, at least one of my non-sighted colleagues here at Deque also
has issues with Google Docs, stating, "*I would give Google Docs a solid D
minus. The **blind **people I know who work at Google don’t even use it. **It
works but it takes a lot of extra steps and is never close to as good an
experience as if it were a simple word or HTML document. Let me try to save
it, email it to myself, converted to Word, and see how it navigates.**" *

They continue, "*My take is Google is where Microsoft was 10 years ago.
Their solution has been to tell screen readers to learn a new set of
shortcut keys that tend to not be derived from any precedent setting
software. For example, in Google drive, one moves a document with the “z”
key and shares with the “.”. In Docs, turning on quick key navigation was
control alt “n” followed by control alt “h” and bloggers and webinars went
out and told us to use those commands. Then a month later they changed
them. I have no idea what they are THIS month."*



*"To get help, they told us to use “less than shift greater than plus
forward slash". Or <shift>+/. Or they could have just said the question
mark.**In Google Docs the control to Create a New Document is not actually
a link or a button. I asked [Deque Colleague] to look at the element in the
DOM and he confirmed it wasn’t a link or button. I called the folks at
Google and they told me it worked fine with ChromeVOX."*



*"The requirement of the user to both learn lots of new commands and to use
flow through keys almost resulted in a resolution at the NFB a year ago." *

I do not believe we should be making that kind of imposition on non-sighted
users - we should be eating our own dog food!

Shawn mentioned moving to Github Issues a number of weeks back, and I look
forward to a proper migration soon.

JF


On Tue, Sep 24, 2019 at 9:32 AM Hall, Charles (DET-MRM) <
Charles.Hall@mrm-mccann.com> wrote:

> RE: TPAC Review
>
>
>
> Since my mic was failing for the meeting, I just wanted to add some notes.
> I feel like we need an opportunity for the entire group to have a debrief
> from TPAC. The highlights affecting Content work are:
>
>    1. We need to finalize the editorial format of how functional needs
>    are described
>       1. The attendees were not in agreement on the proposal in the
>       document of: “People may have [with/without/who can/cannot] [action or
>       function] due to: human factors (like [example of disability]); technical
>       factors (like [example]); or contextual factors (like [example]).”
>       2. The attendees were not in agreement of using the terms from EN
>       501 549 Annex B; OR in being limited to those specific 11 needs
>    2. With methods, we need to discuss testing – which should include
>    different types of tests.
>    3. In regard to the Project Plan discussion, we need to identify and
>    invite greater participation – including possibly from the AGWG – to work
>    on writing and editing the user needs and methods in the Outline Map.
>       1. We need to identify and agree on a method of tracking the
>       progress and preventing overlap on this work – like using GitHub issues.
>
>
>
>
>
>
>
>
>
> *Charles Hall* // Senior UX Architect
>
>
>
> (he//him)
>
> charles.hall@mrm-mccann.com
> <charles.hall@mrm-mccann.com?subject=Note%20From%20Signature>
>
> w 248.203.8723
>
> m 248.225.8179
>
> 360 W Maple Ave, Birmingham MI 48009
>
> mrm-mccann.com <https://www.mrm-mccann.com/>
>
>
>
> [image: MRM//McCann]
>
> Relationship Is Our Middle Name
>
>
>
> Network of the Year, Cannes Lions 2019
>
> Ad Age Agency A-List 2016, 2017, 2019
>
> Ad Age Creativity Innovators 2016, 2017
>
> Ad Age B-to-B Agency of the Year 2018
>
> North American Agency of the Year, Cannes 2016
>
> Leader in Gartner Magic Quadrant 2017, 2018, 2019
>
> Most Creatively Effective Agency Network in the World, Effie 2018, 2019
>
>
>
>
>
>
>
> *From: *Jeanne Spellman <jspellman@spellmanconsulting.com>
> *Date: *Monday, September 23, 2019 at 5:49 PM
> *To: *Silver Task Force <public-silver@w3.org>
> *Subject: *[EXTERNAL] Agenda for Silver Content Meeting of 24 September
> 2019
> *Resent-From: *Silver Task Force <public-silver@w3.org>
> *Resent-Date: *Monday, September 23, 2019 at 5:48 PM
>
>
>
> ==Agenda==
>
> agenda+ TPAC week meeting review
>
> agenda+ Functional user needs working session
>
>
>
> == Links ==
>
> WCAG to Silver Migration Map
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1aCRXrtmnSSTso-2D6S-5FIO9GQ3AKTB4FYt9k92eT-5F1PWX4_edit&d=DwMCaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=FbsK8fvOGBHiAasJukQr6i2dv-WpJzmR-w48cl75l3c&m=IVogenZgrUTUIg7mpcXDQi9eAdAgrLybEBwiMlpJiHc&s=JShN-7hzG-F0tnuAiPM801tiADIdqVfKtSkRsygWQm8&e=>
> Functional User Needs
>
>
>
> == Conference Call Info ==
>
> https://www.w3.org/2017/08/telecon-info_silver-tue
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.w3.org_2017_08_telecon-2Dinfo-5Fsilver-2Dtue&d=DwMCaQ&c=Ftw_YSVcGmqQBvrGwAZugGylNRkk-uER0-5bY94tjsc&r=FbsK8fvOGBHiAasJukQr6i2dv-WpJzmR-w48cl75l3c&m=IVogenZgrUTUIg7mpcXDQi9eAdAgrLybEBwiMlpJiHc&s=EH44eS3p-BGvbleBVcLeXux2IXKfOy_8bwTgdoQbaeA&e=>
> This message contains information which may be confidential and
> privileged. Unless you are the intended recipient (or authorized to receive
> this message for the intended recipient), you may not use, copy,
> disseminate or disclose to anyone the message or any information contained
> in the message. If you have received the message in error, please advise
> the sender by reply e-mail, and delete the message. Thank you very much.
>


-- 
*​John Foliot* | Principal Accessibility Strategist | W3C AC Representative
Deque Systems - Accessibility for Good
deque.com

image001.jpg
(image/jpeg attachment: image001.jpg)

Received on Tuesday, 24 September 2019 21:52:22 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:31:46 UTC