jmuheim
commented
4 years ago Still needed
Before trying to implement one of the following, please investigate whether there exist other/better solutions already for examining the specific criterion.
1.3.5 Identify Input Purpose
- Script that rigidly inputs dummy data for each
autocomplete-attribute- 53 possible values: https://www.w3.org/TR/WCAG21/#input-purposes
- Then check visually whether it worked
2.5.3 Label in Name
- Calculate accessible name
- Display it next to each element
- Try to compare automatically
- Edge cases: visually hidden text, icons, images
Already implemented by others
Thanks to the online community, there exist already some of our own proposed bookmarklet ideas. 👍
1.4.12 Text Spacing
There exist already some:
- https://www.html5accessibility.com/tests/tsbookmarklet.html
- https://dylanb.github.io/bookmarklets.html
- https://testen.bitv-test.de/bookmarklets.html
- https://cdpn.io/stevef/debug/YLMqbo
All of them seem pretty similar, couldn't spot any differences yet.
2.1.4 Character Key Shortcuts
There exists already one, see "Tastatur-Kurzbefehle auslösen" on https://testen.bitv-test.de/bookmarklets.html.
2.5.2 Pointer Cancellation
There exists already one, see "Down-Events auslösen" on https://testen.bitv-test.de/bookmarklets.html.
Bookmarklets can be a very fast, easy and useful way to test for some accessibility stuff.
(So far, this issue is meant as a general brainstorming log.)
WCAG 2.1 introduces some new requirements that can be partly tested programmatically. We are discussing internally what different bookmarklets could be useful. Some of them could be implemented during a hackday sometime next year.