W3C home > Mailing lists > Public > public-eo-plan@w3.org > April to June 2018

Re: ra11y matrix project follow up (or whatever it's called this week)

From: Denis Boudreau <denis.boudreau@deque.com>
Date: Fri, 29 Jun 2018 10:25:51 -0400
Message-ID: <CAC=s1AjcyQifgDyzw8X5_6sFOpriCy+42BZ0VMJDRMpjsQ_9qQ@mail.gmail.com>
To: Shawn Henry <shawn@w3.org>
Cc: Sharron Rush <srush@knowbility.org>, "Tyler, Bill" <btyler@optum.com>, "Bakken, Brent" <brent.bakken@pearson.com>, "Kelly, Sean" <sean_kelly@optum.com>, "Sean Kelly (via Google Drive)" <lensmonkey@gmail.com>, public-eo-plan@w3.org
Hi Shawn,

Sure, why not. Providing a bit of context can help, but we've already done
that, and it the survey also links to the project plan, that's all the
context people need at this point, IMHO.

I just want to make sure we don't make this more of a burden than it needs
to. The more dense the instructions are, the less likely people are of
going through with them. The internationalization piece you're referring to
should not be any different than anything else we usually work on, so I
don't think any more it's relevant to mention it in this particular case
than any other document we've worked on in the past.

As for specific questions, I guess it's relevant, but again, if this makes
the survey longer than it needs to, then fewer people will make it through
it. Which also defeats our purpose. I'm thinking we can always go back to
it again later, as the document evolves. Because there's no way this is
going to be the final draft.



/Denis



*Denis Boudreau, CPACC* | Principal Accessibility Consultant & Training
Lead | 514-730-9168
Deque Systems - Accessibility for Good
Deque.com <http://www.deque.com>





On Fri, Jun 29, 2018 at 10:15 AM Shawn Henry <shawn@w3.org> wrote:

> I think it would be good to give just a little more guidance for the
> review. For example, include the context -- the purpose of this is who does
> what with WCAG SCs. Also maybe a few specific questions like Bill suggested.
>
> And include a link to the requirements.
>
> Also note about asking people from different regions/countries to look at
> it.
>
> On 6/29/2018 7:24 AM, Sharron Rush wrote:
> > I completely agree that we do not need long philosophical discussion at
> this point - in fact it should be avoided if possible - grin.
> >
> > So how about this for the survey:
> >
> > Please review the definition of roles proposed for the Roles and
> Responsibilities Matrix [link]. We would like to be sure we have not
> overlooked a critical role and if these categorizations make sense in the
> typical product development life cycle and EO is comfortable with them
> Indicate your agreement with how the roles are defined and presented by
> responding in GitHub or in the comments below.
> >
> > Answers will be gradients of agreement and links to put comments in
> GitHub with a comment box included as well on the survey.
> >
> > If no objection, I will put that question in this week's survey.
> >
> > Thanks guys!
> >
> > Best,
> > Sharron
> >
> >
> >
> >
> > On Thu, Jun 28, 2018 at 7:10 PM, Denis Boudreau <
> denis.boudreau@deque.com <mailto:denis.boudreau@deque.com>> wrote:
> >
> >     I agree with bill 100%. The goal is to define roles that are
> relevant to the web project lifecycle (design, dev, qa, etc.), and have a
> role to play with integrating accessibility in that process. Nothing more,
> which is why a lot of the roles from that other document just aren’t
> relevant to what we’re up to (though still important for other types of
> considerations).
> >
> >     The type of feedback we’re interested in at this time is about
> whether we’ve grossly missed something, if our catégorisations make sense
> to people and if they are comfortable with our definitions of what those
> roles are and what those people are expected to be doing as part of the
> lifecycle.
> >
> >     Other discussions are welcomed, philosophical or not, but our goal
> is to remain focused on our end game, which is defining the overarching set
> of stakeholders involved in creating a digital product with accessibility
> in mind.
> >
> >     /Denis
> >
> >
> >
> >
> >     On Thu, Jun 28, 2018 at 18:55 Tyler, Bill <btyler@optum.com <mailto:
> btyler@optum.com>> wrote:
> >
> >         As for the survey... I think Denis may have the best ideas for
> questions. I hope he can pass those along. Below I’ve added a start to the
> process (as best I understand the need).____
> >
> >         __ __
> >
> >         I can definitely discuss why we need a list different from the
> Silver Job Stories for Stakeholders <
> https://www.w3.org/WAI/GL/task-forces/silver/wiki/Job_Stories_for_Stakeholders>.
> Denis already discussed this in regard to project plan question #9 <
> https://github.com/w3c/wai-roles-responsbilities/issues/9>. If you’re
> referring to a different document please pass that along. ____
> >
> >         __ __
> >
> >         ...Bill____
> >
> >         __ __
> >
> >         We want a general review of the common roles in the typical
> digital product lifecycle with primary focus on web (HTML) documents and
> applications. Design and development team structures vary dramatically
> between different orgnaizations. It’s vital that we define what design
> tasks and responsibilities apply to the role names we use so they can be
> adapted a variety of team configurations.____
> >
> >         __ __
> >
> >         We want to confirmation the following are reasonable and reflect
> what is “typical” in the product lifecycle:____
> >
> >         __·__Role Groups (Design, Development, Testing, Management)____
> >
> >         __·__Titles (and alternate names)____
> >
> >         __·__Role definitions with emphasis on design input, content,
> code and implementation decisions that impact accessibility____
> >
> >         __·__Typical (non-accessibility) Tasks performed by the role____
> >
> >         __ __
> >
> >         The list is intended to cover the majority of teams large and
> small. It will include some roles that have little or no direct impact to
> accessibility design decisions. These are included to help indicate which
> roles do NOT impact accessiblity.____
> >
> >         __ __
> >
> >         Our purpose is mainly to define the roles we're deriving for
> analysis and process on our project. The roles are the foundation of our
> work but not our focus. We do not need a comprehensive or definitive list
> for this. We are not trying to create a standard set of definition for the
> W3C to adopt.____
> >
> >         __ __
> >
> >         If another appropriate list exists we will review and use it if
> it meets our needs. However we cannot have a dependency on external
> references that are not ready or do not cover the distinctions we see as
> critical to our work.____
> >
> >         __ __
> >
> >         Possible questions____
> >
> >         __·__Are the role titles, especially those impacting
> accessibility, typical for projects you have worked on?____
> >
> >         __·__Have we listed alternatives that match what you have
> used?____
> >
> >         __·__Are the lists of tasks appropriate for the role (as you
> understand them)?____
> >
> >         __·__Are there common tasks missing that should be included?____
> >
> >         __·__Are the distinctions between the roles obvious or do they
> overlap?____
> >
> >         __ __
> >
> >         Primary emphasis for our work will focus mainly on these
> roles:____
> >
> >         __·__UX Designer____
> >
> >         __·__Visual Designer____
> >
> >         __·__Content Creation____
> >
> >         __·__Front End Development____
> >
> >         __ __
> >
> >
>  _____________________________________________________________________
> >
> >
>  _____________________________________________________________________
> >
> >         __ __
> >
> >         -----Original Message-----
> >         From: Shawn Henry [mailto:shawn@w3.org <mailto:shawn@w3.org>]
> >         Sent: Thursday, June 28, 2018 4:53 PM
> >         To: Kelly, Sean; Sharron Rush; Denis Boudreau
> >         Cc: Bakken, Brent; Tyler, Bill; public-eo-plan@w3.org <mailto:
> public-eo-plan@w3.org>; Sean Kelly
> >         Subject: Re: ra11y matrix project follow up (or whatever it's
> called this week)
> >
> >         __ __
> >
> >         Looks like it will be short and Sharron put it as the first
> agenda item so you know when it will be. :-)____
> >
> >         __ __
> >
> >         On 6/28/2018 4:51 PM, Kelly, Sean wrote:____
> >
> >          > Hi Shawn,____
> >
> >          > ____
> >
> >          > If I've got this correct, it's not going to be an extended
> discussion item?____
> >
> >          > ____
> >
> >          > Trying to wrangle my schedule for tomorrow.____
> >
> >          > ____
> >
> >          > Thanks,____
> >
> >          > ____
> >
> >          > S____
> >
> >          > ____
> >
> >          > On 2018-06-28, 16:37:46, "Shawn Henry" <shawn@w3.org
> <mailto:shawn@w3.org>> wrote:____
> >
> >          > ____
> >
> >          >      Denis and all,____
> >
> >          > ____
> >
> >          >      Great!!!____
> >
> >          > ____
> >
> >          >      Please provide the information for the survey,
> including:____
> >
> >          >      * Brief context (1-2 sentences) and pointer to the
> Requirements____
> >
> >          >      * What you want people to comment on, and what you don't
> want them to comment on yet____
> >
> >          >      * Specific questions to help focus the review____
> >
> >          > ____
> >
> >          >      Info for ideas:____
> >
> >          >      * Review Stages and Levels:
> https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#Review_Stages_and_Levels
> <
> https://www.w3.org/WAI/EO/wiki/EOWG_Participation_Info#Review_Stages_and_Levels
> >____
> >
> >          >      -- Is this at the "complete draft" stage?____
> >
> >          >      * "About this survey" question in
> https://www.w3.org/2002/09/wbs/35532/20161014-FirstAid/ <
> https://www.w3.org/2002/09/wbs/35532/20161014-FirstAid/>____
> >
> >          >      * "Accessibility Statements" agenda item in <
> https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#Agenda <
> https://www.w3.org/WAI/EO/wiki/EOWG_Meetings#Agenda>>____
> >
> >          > ____
> >
> >          >      On the Friday call, could you also give us a bit of info
> on how this is related to and different from the Silver roles list.____
> >
> >          > ____
> >
> >          >      Thanks,____
> >
> >          >      ~Shawn____
> >
> >          > ____
> >
> >          > ____
> >
> >          >      On 6/28/2018 2:11 PM, Sharron Rush wrote:____
> >
> >          >      > Hi Denis,____
> >
> >          >      >____
> >
> >          >      > We can add to the agenda as an FYI and put a questions
> in tomorrow's survey to allow people to read and comment during the
> following week.____
> >
> >          >      >____
> >
> >          >      > Thanks for the progress!____
> >
> >          >      >____
> >
> >          >      > Best,____
> >
> >          >      > Sharron____
> >
> >          >      >____
> >
> >          >      > On Thu, Jun 28, 2018 at 12:41 PM, Denis Boudreau <
> denis.boudreau@deque.com <mailto:denis.boudreau@deque.com> <mailto:
> denis.boudreau@deque.com <mailto:denis.boudreau@deque.com>>> wrote:____
> >
> >          >      >____
> >
> >          >      >     Good afternoon esteemed friends. :)____
> >
> >          >      >____
> >
> >          >      >     As a first draft of our first deliverable with
> this project on a framework to define roles in the accessibility lifecycle
> (1), we'd like to share our roles definition document (2).____
> >
> >          >      >____
> >
> >          >      >     We understand that it's too late to be able to
> discuss it as part of this week's agenda, but we'd like to be able to at
> least bring it to everyone's attention to start gathering comments and
> feedback. Maybe have its review as part of the work for this week, or part
> of a survey or something.____
> >
> >          >      >____
> >
> >          >      >     I will personally not be able to attend tomorrow's
> call, as I'm currently attending a conference and I'll be flying back home
> tomorrow, but Bill could talk to the document and quickly introduce it to
> the working group if you think it's possible.____
> >
> >          >      >____
> >
> >          >      >     Let us know if it can be done. If it's too late,
> no worries, we can get back to it next week.____
> >
> >          >      >____
> >
> >          >      >     ​(​____
> >
> >          >      >     1____
> >
> >          >      >     ​)____
> >
> >          >      > https://www.w3.org/WAI/EO/wiki/RA11y_Matrix <
> https://www.w3.org/WAI/EO/wiki/RA11y_Matrix> <
> https://www.w3.org/WAI/EO/wiki/RA11y_Matrix <
> https://www.w3.org/WAI/EO/wiki/RA11y_Matrix>>____
> >
> >          >      >     (2)
> https://www.w3.org/WAI/EO/wiki/Role_definition_document <
> https://www.w3.org/WAI/EO/wiki/Role_definition_document> <
> https://www.w3.org/WAI/EO/wiki/Role_definition_document <
> https://www.w3.org/WAI/EO/wiki/Role_definition_document>>____
> >
> >          >      >____
> >
> >          >      >     ​____
> >
> >          >      >     /Denis____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      >     *Denis Boudreau, CPACC* | Principal Accessibility
> Consultant & Training Lead | 514-730-9168____
> >
> >          >      >     Deque Systems - Accessibility for Good____
> >
> >          >      >     Deque.com <http://www.deque.com>____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      >____
> >
> >          >      > --____
> >
> >          >      > Sharron Rush | Executive Director | Knowbility.org |
> @knowbility____
> >
> >          >      > /Equal access to technology for people with
> disabilities/____
> >
> >          > ____
> >
> >          > ____
> >
> >          > ____
> >
> >          > This e-mail, including attachments, may include confidential
> and/or____
> >
> >          > proprietary information, and may be used only by the person
> or entity____
> >
> >          > to which it is addressed. If the reader of this e-mail is not
> the intended____
> >
> >          > recipient or his or her authorized agent, the reader is
> hereby notified____
> >
> >          > that any dissemination, distribution or copying of this
> e-mail is____
> >
> >          > prohibited. If you have received this e-mail in error, please
> notify the____
> >
> >          > sender by replying to this message and delete this e-mail
> immediately.____
> >
> >          > ____
> >
> >
> >         This e-mail, including attachments, may include confidential
> and/or
> >         proprietary information, and may be used only by the person or
> entity
> >         to which it is addressed. If the reader of this e-mail is not
> the intended
> >         recipient or his or her authorized agent, the reader is hereby
> notified
> >         that any dissemination, distribution or copying of this e-mail is
> >         prohibited. If you have received this e-mail in error, please
> notify the
> >         sender by replying to this message and delete this e-mail
> immediately.
> >
> >     --
> >     /Denis
> >
> >     --
> >     Denis Boudreau
> >     Principal SME & trainer
> >     Web accessibility, inclusive design and UX
> >     Deque Systems inc.
> >     514-730-9168
> >
> >     Keep in touch: @dboudreau
> >
> >
> >
> >
> > --
> > Sharron Rush | Executive Director | Knowbility.org | @knowbility
> > /Equal access to technology for people with disabilities/
>
Received on Friday, 29 June 2018 14:26:52 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:44:03 UTC