Re: CFC - Add Findable Help to WCAG 2.2 draft


I still have a number of concerns with this SC, ones that I've put into
survey before. But to summarize:

- I don't believe this SC should be as broadly applicable as it is now
made. An anonymous blog someone writes in their spare time does not benefit
from a contact option. It may even defeat the purpose of the site all

- The definition of "single page app" is far too generic. Given this
definition, every page where even small content changes occur should now be
treated as SPAs.

- "consistent location" is too generic. What does that mean? If the link is
always in the heading, is that consistent? Does it need to be a fixed
position in the UI and it moving even a single pixel causes this to fail?
Can it even more along with scrolling?


On Fri, Jun 12, 2020 at 8:50 PM Rachael Bradley Montgomery <> wrote:

> Call For Consensus — ends Wednesday June 17th at 11:59 Boston time.
> The Working Group has discussed the new Success Criteria for WCAG 2.2:
> Findable Help
> The Pull Request in github shows the changes, and includes links to
> preview the additional SC, the understanding document, and the technique:
> This was discussed via a survey:
> The last call was:
> If you have concerns about this proposed consensus position that have not
> been discussed already and feel that those concerns result in you “not
> being able to live with” this decision, please let the group know before
> the CfC deadline.
> Kind regards,
> Rachael
> --
> Rachael Montgomery, PhD
> Director, Accessible Community

*Wilco Fiers*
Axe for Web product owner - Co-facilitator WCAG-ACT - Chair ACT-R

Received on Monday, 15 June 2020 09:07:03 UTC