- From: Shawn Lauriat <lauriat@google.com>
- Date: Fri, 18 May 2018 16:42:59 -0400
- To: Silver TF <public-silver@w3.org>
- Message-ID: <CAGQw2hkFtd5u342GMifKPpc340vyDyp9KKV=_=Udx85kkM=TsQ@mail.gmail.com>
All, We've put together a high level draft of a Silver Requirements document <https://docs.google.com/document/d/15F4KuNXYK5q2rOgb4ktHiJQMQpAEL9EetARpMU3vD_A/edit> (HTML version <https://docs.google.com/document/d/e/2PACX-1vQwFWjpW-onA9hNb2L_U-jLppulk9cQNsttUdQFnEK9KkGNqoj1Hfc3c4kV1_JohqmCJXBVtZ3RaYAq/pub>), which we'll send to the overall Accessibility Guidelines Working Group in a couple of weeks. We still have several outstanding comment threads in there (largely around needed rewording and simplification of sentence structure), but please have a look through and add your thoughts or suggestions! Feel free to comment directly in the document or email A couple prompts: - Does this document make the requirements clear? - Did we leave anything out that we should explicitly speak to in this requirements document? For other examples, see: - WCAG 2.1's Requirements Document <https://w3c.github.io/wcag21/requirements/> - WCAG 2.0's Requirements Document <https://www.w3.org/TR/2006/NOTE-wcag2-req-20060425/> - A search of W3C of Requirements documents <https://www.w3.org/TR/?title=requirements> We'll create a more detailed version later on, once we've all agreed on the higher level points here. Then, we'll go into a little more detail about our plans on how to meet these goals and more explicitly what each requirement means. Much appreciated! Shawn
Received on Friday, 18 May 2018 20:43:36 UTC