- From: Shawn Lauriat <lauriat@google.com>
- Date: Tue, 1 Nov 2016 14:41:41 -0400
- To: Jeanne Spellman <jspellman@spellmanconsulting.com>
- Cc: WCAG <w3c-wai-gl@w3.org>
- Message-ID: <CAGQw2hnGjWO51Em8B9Bs9kOcUQCPXH_-sCSYE0mQKGQKUjqimA@mail.gmail.com>
+1 to Jeanne's take - we (working group) specifically went with an amended version <https://www.w3.org/WAI/GL/wiki/Process_of_Designing_Silver> of the "Greatest Flexibility Option <https://www.w3.org/WAI/GL/wiki/Greatest_Flexibility_Option>" in order to have a better ability to address emerging technologies and changes in interactions, so I don't think it makes sense to specify scope (even through implication) at this stage. -Shawn On Tue, Nov 1, 2016 at 1:51 PM, Jeanne Spellman < jspellman@spellmanconsulting.com> wrote: > I like the idea, although I don't think that verbal and conversational > interfaces should have a special callout, as that implies that it would be > the focus of new technologies we are addressing. We certainly want to > include them, but not to the exclusion of others. It brings too much > attention to them, IMO. > > How about this language? > > These guidelines will address technological and cultural web accessibility > requirements. These guidelines strive to anticipate where the web and other > internet technologies are headed so that the guidelines can continue to > evolve. > > On 11/1/2016 1:11 PM, Gregg Vanderheiden wrote: > > Friendly amendment > > I think that the objective should contain something that relates to > future technologies. > > Objective > > The objective of the task force is to perform preliminary development of a > new version of Accessibility Guidelines following a research-focused, > user-centered design methodology to produce the most effective and flexible > outcome. Code-named "Silver", these guidelines will address the process of > making content and functionality accessible to people with disabilities, > including the roles of content authoring, user agent support, and authoring > tool support. These guidelines will address current technological and > cultural web accessibility requirements, but also look to where the web > and broadening internet technologies are headed, including verbal and > conversational interfaces, in order to and provide a base for continued > evolution of the guidelines. > > *gregg* > > On Nov 1, 2016, at 12:57 PM, Andrew Kirkpatrick <akirkpat@adobe.com> > wrote: > > +1 to this CfC > > Thanks, > AWK > > Andrew Kirkpatrick > Group Product Manager, Standards and Accessibility > Adobe > > akirkpat@adobe.com > http://twitter.com/awkawk > > From: "josh@interaccess.ie" <josh@interaccess.ie> > Reply-To: "josh@interaccess.ie" <josh@interaccess.ie> > Date: Tuesday, November 1, 2016 at 12:46 > To: WCAG <w3c-wai-gl@w3.org> > Subject: CFC: Silver TF Work Statement > Resent-From: WCAG <w3c-wai-gl@w3.org> > Resent-Date: Tuesday, November 1, 2016 at 12:43 > > CALL FOR CONSENSUS – ends Thursday Nov 3rd at 5:00pm Boston time. > > This is a proposed work statement for the Silver TF that was surveyed, > discussed on the WG call, and approved (http://www.w3.org/2016/11/01- > wai-wcag-minutes.html). > > The original TF work statement can be seen: https://www.w3.org/WAI/ > GL/task-forces/silver/work-statement > > If you have concerns about this proposed consensus position that have not > been discussed already and feel that those concerns result in you “not > being able to live with” this position, please let the group know before > the CfC deadline. > > Thanks > > Joshue O Connor | Director > *InterAccess.ie <http://InterAccess.ie> - Accessible UX* > > > >
Received on Tuesday, 1 November 2016 18:42:15 UTC