- From: Steve Lee <stevelee@w3.org>
- Date: Tue, 16 Feb 2021 15:57:27 +0000
- To: public-cognitive-a11y-tf@w3.org
PS Hidde has provided mockups of various WCAG supporting docs here https://w3c.github.io/wai-wcag-supporting-documents-redesign/ COGA is at the bottom Steve On 16/02/2021 15:55, Steve Lee wrote: > Rain > > I agree and the Quickref is a great place to point people for the > reasons you say. It also links to the supporting documents as well. > > FYI There is a WAI project to improve all the WCAG Supporting documents > and the Web Design Guide work I mentioned is part of that. > > https://github.com/w3c/wai-wcag-supporting-documents-redesign/wiki/Requirements-Analysis > > > Here's a mockup - using the old Pattern template - > https://w3c.github.io/wai-wcag-supporting-documents-redesign/2020-07-15-coga.html > > > A while back I did a rough proof of concept for a collapsible Design > Guide after Designers / Developers made it clear they prefer the type of > interactive resource you mention rather than a long document. > > https://w3c.github.io/wai-coga/coga-draft/guide/design-notes > > Steve > > > > On 16/02/2021 15:39, Rain Michaels 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 >> <mailto: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 >> >> >> <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 Tuesday, 16 February 2021 15:57:31 UTC