Re: Recent changes to the WCAG 2.2 SC 2.1.1 Understanding page

so  because it does not say that many many people think its not  nessasary
and i say if it does not say that why and when will it


Berkeley IT <https://technology.berkeley.edu/home>

Lucy Greco, Web Accessibility Evangelist

Campus IT Experience
Phone: (510) 289-6008 | Email: lgreco@berkeley.edu |

We champion diversity. We act with integrity. We deliver. We innovate.



On Mon, Aug 5, 2024 at 12:03 PM Patrick H. Lauke <redux@splintered.co.uk>
wrote:

> On 05/08/2024 18:56, Lucy Greco wrote:
> > hi I was going to stay out of this conversation but i find that i
> > can't!  if the standard keyboard     commands are  used in a way that is
> > not standard it can reely  cause  havoc
>
> All valid points, but again: this was never part of the WCAG SC 2.1.1.
> Nowhere did it state that a page must use "standard" keystrokes. Only
> that there must be a way for keyboard users to operate things. The
> "change" in 2.1.1 understanding that happened was to make that clear.
>
> Nobody is disputing that it isn't a problem, but there was never
> normative wording that said so.
>
> Ditto for the need to be "discoverable".
>
> P
> --
> Patrick H. Lauke
>
> * https://www.splintered.co.uk/
> * https://github.com/patrickhlauke
> * https://flickr.com/photos/redux/
> * https://mastodon.social/@patrick_h_lauke
>
>
>