Re: WCAG redesign comments

Thank you very much, Michele!

Comments inline below.

for reference:
* preview: https://deploy-preview-35--wai-wcag-redesign.netlify.app
* known issues: https://github.com/w3c/wcag-redesign/pull/35#issuecomment-1248890252

On 21-Sep-22 2:31 PM, Michele Williams wrote:
> Found the following while exploring (mostly randomly spot-checking the various pages):
> 
> *UNDERSTANDING DOCS*
> *Global* - no "skip navigation" links are present /(mentioned during a past meeting)/

documented under "Things that are in some pages, but not propagated throughout yet" in https://github.com/w3c/wcag-redesign/pull/35#issuecomment-1248890252

> 
> *Global* - if you're on the last SC or Guideline in a series, "Next ->" shows up and is active in the navigation but doesn't move the page; this is confusing - seems like it should just keep moving down the line; example: https://deploy-preview-35--wai-wcag-redesign.netlify.app/understanding/non-text-content <https://deploy-preview-35--wai-wcag-redesign.netlify.app/understanding/non-text-content>

documented under "Known issues with this preview" in https://github.com/w3c/wcag-redesign/pull/35#issuecomment-1248890252

> 
> *Global-ish* - when I spot-check the "Techniques" pages, there's about 50% that have empty bullets; I would ensure each page is thoroughly QAed prior to publication

documented under "Known issues with this preview" in https://github.com/w3c/wcag-redesign/pull/35#issuecomment-1248890252 pointing to https://github.com/w3c/wcag-redesign/issues/22 content bug

> 
> *"All Understanding Docs" page* - would be really helpful if the "Page Contents" side navigation offered an additional way to shortcut through the links - such as adding links to jump to Perceivable, Operable, Understandable, and Robust as sections; right now keyboard users have a lot of Tabs to go through if they start on this page

documented under "Known issues with this preview" in https://github.com/w3c/wcag-redesign/pull/35#issuecomment-1248890252 with pointer to more robust solution https://github.com/w3c/wcag-redesign/issues/6 [Understanding index page] structure

(fyi, this one is at risk for not getting implemented in the first iteration. if so, maybe we can do https://github.com/w3c/wcag-redesign/pull/1#issuecomment-1254376776 )

> 
> *"SC 2.5 Input Modalities" page* - has an empty "Benefits" section: https://deploy-preview-35--wai-wcag-redesign.netlify.app/understanding/input-modalities <https://deploy-preview-35--wai-wcag-redesign.netlify.app/understanding/input-modalities>

huh. looks like that's a content / source file issue as it's also missing in the existing 2.1 and 2.2 documentation.
- empty Benefits section in Understanding Guideline 2.5: Input Modalities in [2.1](https://www.w3.org/WAI/WCAG21/Understanding/input-modalities#benefits) and [2.2](https://www.w3.org/WAI/WCAG22/Understanding/input-modalities#benefits)

Are you up for filing an issue in the WCAG repo?

> 
> *TECHNIQUES DOCS*
> Nothing much except it's really unfortunate that most code examples use red & green to call out differences (& brown seems to be primary tertiary). Not sure if that can be revisited one day.

ug. I thought the color in the code had already been nixed. sigh. I added it to a new section "other" in https://github.com/w3c/wcag-redesign/pull/35#issuecomment-1248890252

> 
> Randomly I found on this page that "Other Sources" is empty: https://deploy-preview-35--wai-wcag-redesign.netlify.app/techniques/general/g217 <https://deploy-preview-35--wai-wcag-redesign.netlify.app/techniques/general/g217>

looks like another content / source file issue as it's also missing in the existing 2.1 and 2.2 documentation.
- empty Related Resources section in G217 (and maybe others?) in [2.2](https://www.w3.org/WAI/WCAG21/Techniques/general/G217#resources) and [2.2](https://www.w3.org/WAI/WCAG22/Techniques/general/G217#resources)

Are you up for filing an issue in the WCAG repo?

> 
> 
> Ta ta for now!

Thanks!
~Shawn

Received on Thursday, 22 September 2022 01:56:58 UTC