- From: Lisa Seeman <lisa1seeman@gmail.com>
- Date: Thu, 18 Feb 2021 14:05:56 +0200
- To: Rain Michaels <rainb@google.com>
- Cc: Steve Lee <stevelee@w3.org>, public-cognitive-a11y-tf <public-cognitive-a11y-tf@w3.org>
- Message-ID: <CAKExBM+MBbyni_m0SKe-rGRdEosZUDtwAYuDWR=Ygbg24NXTuA@mail.gmail.com>
Hi Rain We are working on a "quick ref" type version Hopefully it will come out soon after this document. On Tue, Feb 16, 2021 at 5:40 PM Rain Michaels <rainb@google.com> wrote: > To be quite honest, I've always found wading through the documents when > finding information for WCAG very overwhelming, and this is something I'm > hoping to come up with recommendations around. This document is no > exception. > > When I was doing audits and vpats, my life-saver for the past few years > has been the quickref <https://www.w3.org/WAI/WCAG21/quickref/>. It > enabled me to get to the information I needed, and then drill in from > there. This model is helpful for a few reasons: > > - A combination of expanding + useful information up front > - A persistent table of contents that enables one to get to the > information > - Clear visual indications of the start and stop of specific sections > of information, so that it is really easy to focus in on everything related > to one specific idea > - Easy access to the link so that it can be shared with any > stakeholders who need to be convinced > > While expanding and collapsing carries its own cognitive challenges, it > would be great if we can find a way to give individuals easy access to the > specific amount of information they need when they need it. > > Rain > > On Tue, Feb 16, 2021 at 6:55 AM Steve Lee <stevelee@w3.org> wrote: > >> Hmm, I'm not convinced collapsible works for a "document", though it >> makes every sense in the coming Web version of the Design Guide. This >> will have a page per Pattern, so is much more manageable anyway. The >> "Details" can be collapsible there without causing any surprises as web >> pages are often interactive. >> >> If it is decided to go the collapsable route, the "What to do" >> (currently Description) would be better placed in the static text IMHO. >> Then you can scan the content an understand the patterns without having >> to expand, unless you want to drill down. >> >> I also feel quite strongly that most content is best covered in "what to >> do" and the "examples" which provide extra practical detail. Thus onl y >> a few have the more "details section". >> >> Steve >> >> On 16/02/2021 14:31, Lisa Seeman wrote: >> > Hi Folks >> > Do we like the idea of having most of the details for each pattern in a >> > "more detail" tab? >> > >> > Along the lines of /expand-demo/ >> > < >> https://raw.githack.com/w3c/coga/expand-demo/content-usable/index.html#pattern-make-the-purpose-of-your-page-clear >> > ? >> > Does it make it easier to follow? >> > >> > All the best >> > >> > Lisa >> >>
Received on Thursday, 18 February 2021 12:06:48 UTC