- From: Shawn Lauriat <lauriat@google.com>
- Date: Fri, 1 May 2020 16:40:58 -0400
- To: Silver TF <public-silver@w3.org>
- Message-ID: <CAGQw2hm_2+9uphPOnA4NsdUVG-UQh1Mt4AXkLWiQFZ0a=LE6NA@mail.gmail.com>
*Overview* - Essentials for Publishing approved by AGWG <https://docs.google.com/document/d/1tQHgVFaJYS1WWs9BKucZxWboMNVuclvdNqnQuzPbWwY/edit>: what the FPWD needs to include before we bring it for consensus, approved Tuesday with the overall Working Group - FPWD publication of the Challenges doc <https://www.w3.org/TR/accessibility-conformance-challenges/>: communications still to come, but published this morning - Let's define what we mean by "task" in terms of conformance - Talked through examples - General agreement that we should reuse and reference the research and hard work already done in the UX space for defining goals, user journeys, tasks, and what those things mean. For example: - From https://uxdesign.cc/start-designing-with-goals-in-mind-4723df5f8e88 Task: A task is a step taken by the user during the process of achieving a goal. In order to achieve a goal, users have to navigate through multiple steps completing small tasks. The information architecture of a digital product is formed by tasks. - Tasks can go beyond the boundaries of a page/site/app if the task requires use of a dependency - Talked through functionality provided as a part of a task, and whether importance should enter into it (probably not) - Discussion around the requirements of when someone would need to retrofit, or at least some guidance to help those in the regulatory space who need to adopt the guidelines and those needing to make a decision in that context. Full Minutes <https://www.w3.org/2020/05/01-silver-minutes.html>
Received on Friday, 1 May 2020 20:41:23 UTC