- From: Lisa Seeman <lisa1seeman@gmail.com>
- Date: Thu, 24 Sep 2020 18:14:34 +0300
- To: public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
- Message-ID: <CAKExBMLeSo-z+6mAJtFEitVEpfPsTi-U5sjTdkf+ChPz1ZMZBg@mail.gmail.com>
Hi Folks As per today's call here are the pattern assigned Instructions are at docs.google <https://docs.google.com/document/d/1wffN29_8YxjeL4E_wUHtKt6AGo0q3d--6cx2zZjThgg/edit#heading=h.yix8reek2djc> - * John K: Avoid Data Loss and "Time Outs" - minor editorial - missing non timeout data losses (if any) - * Steve: Keep Users' Information Safe and Help Users Understand Known Risks - editorial, missing WTD heading - * David: Provide a Login that Does Not Rely on Memory or Other Cognitive - editorial - review against proposed WCAG 2.2 SC - * Abi: Do Not Rely on Users Memorizing Information - editorial, trim - is it just processes?, are their multiple patterns here - * Jennie: Provide Human Help & Make It Easy to Find Help and Give Feedback - review overlap, which is UX and which location of help on pages, split Feedback? - - * Steve: Clearly Identify Controls and Their Use - editorial work - see [ https://docs.google.com/document/d/1mh_Pg3Whu545lJhmeWQoSbQPRmlbN8cEJMO7kdSKvps/edit#heading=h.yix8reek2djc example] - * Steve: Ensure the Hierarchy of the Site and Menu Structure is Logical & Use a Clear and Understandable Page Structure - editorial, which covers navigation, too long - * Steve: Ensure Controls and Content Do Not Move Unexpectedly - editorial - clarification of 'move' and 'when' - * Steve: Provide Flexible Form Inputs - editorial cover standard field types and validation It is also on are actions list at PlanningPage#Actions <https://www.w3.org/WAI/GL/task-forces/coga/wiki/PlanningPage#Actions> Thank you so much and keep well!
Received on Thursday, 24 September 2020 15:15:25 UTC