W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2019

Re: Automatied testing options for 2.1.4 Character key Shortcuts and 2.5.2 Pointer Cancellation

From: Wilco Fiers <wilco.fiers@deque.com>
Date: Mon, 4 Feb 2019 12:06:58 +0100
Message-ID: <CAHVyjGOx2ph=jr3qLxOQvF9ST-nYBdkX8Aixkf3oFgrOE7sCKw@mail.gmail.com>
To: Detlev Fischer <detlev.fischer@testkreis.de>
Cc: Accessibility Conformance Testing <public-wcag-act@w3.org>, WCAG group <w3c-wai-gl@w3.org>
Hey Detlev,
Thank you for the suggestions. Unfortunately there is no way to pick up
event listeners from the DOM once they are set. There is an issue on it at
WHATWG in the DOM repo, but it hasn't gotten any traction:
https://github.com/whatwg/dom/issues/412

I think such a capability would be incredibly helpful, if only to rule out
that most pages don't have key or device orientation related event handlers
on the page. It also wouldn't be difficult to implement, browsers already
have this capability build into the devtools, They just never exposed it to
the DOM itself:
https://developers.google.com/web/tools/chrome-devtools/console/utilities#geteventlistenersobject

Wilco

On Thu, Jan 17, 2019 at 2:30 PM Detlev Fischer <detlev.fischer@testkreis.de>
wrote:

> Hi,
>
> apologies for cross-posting.
>
> There are two new WCAG 2.1 Success Critieria which might lend themselves
> well to automatic testing.
>
> SC 2.1.4 Character key Shortcuts
>
> I have written a draft Failure for 2.1.4  Character key Shortcuts
> https://github.com/w3c/wcag/pull/584 which currently has a rather clumsy
> and in any case time-consuming manual test (press each character key,
> watch for functions being triggered). Are there reliable ways to check
> for the presence of key event handlers that do not use modifier keys in
> all possible script invocation scenarios? If so, having a bookmarklet or
> similar to carry out this check would be great.
>
> SC 2.5.2 Pointer Cancellation
>
> A possibly automated check would look for functions on a page that
> trigger actions on "down events" (mousedown, touchdown  - not sure if we
> need to include mouseenter and touchenter since these would presumably
> also be fired). Since multistep events as in drag-n-drop are OK if there
> is a way to undo, abort, revert the action (which I guess cannot be
> safely tested automatically) the automatic part would be a first step in
> a semi-automatic test procedure.
>
> I wonder if people in the ACT TF have already contemplated the
> feasibility of automatic checks for these two SCs, or are aware of
> anyone who might have put something together already which could be
> referenced in a Sufficient Technique or Failure test procedure.
>
> Detlev
>
> --
> Detlev Fischer
> Testkreis
> Werderstr. 34, 20144 Hamburg
>
> Mobil +49 (0)157 57 57 57 45
>
> http://www.testkreis.de
> Beratung, Tests und Schulungen für barrierefreie Websites
>
>
>

-- 
*Wilco Fiers*
Senior Accessibility Engineer - Co-facilitator WCAG-ACT - Chair Auto-WCAG

deque_logo_180p.gif
(image/gif attachment: deque_logo_180p.gif)

Received on Monday, 4 February 2019 11:07:33 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 21:08:29 UTC