New Manual Tests Rule Creation Group

[HelenBurge]

We have a lot of rules missing for the manual tests.

I am proposing we create a sub group for those who are interested in helping to write the tests. These will be less technical than the automated tests and I hope to make a start on a few. (Well 1…)

Please let me know what you think, and who is interested in joining. We could meet once a month to discuss pain points or ideas separate from the main group discussions?

[HelenBurge]

TBD (short term):
Work out the format for the rules
Advertise the group
Work out 5 rules to focus on

[ChrisLoiselle]

@HelenBurge I can come back to this topic second week of November. Thanks!

[ChrisLoiselle]

@HelenBurge where do you want the .md file to be added to in the repo?

[gabalafou]

I'm interested

[HelenBurge]

@gabalafou - here is a copy of the email I sent around - note no WCAG 2.2 in this list yet too - feel free to take one of these on:
Hi Everyone,

Please feel free to forward this to anyone you know that might be interested in contributing!

So I made a start on creating a template we can use for writing any rules we know are not covered: Manual Rule Template with instructions. The instructions are to help us all, and to remember that no matter our technical abilities, the group can help!

For instance I made a start on a new rule: Focus Returns to Trigger and Dan has been great in helping me, by starting to write the examples that I listed but cannot write. I do have some pointers from Jean-Yves as the rule is a new type to what we currently have as not a fixed state rule... I will be updating and reviewing the text used.

Also a big shout out to Giacomo for his manual test rule: Error field is not identified using color differences only!

We made a start and would love reviews/help, or new rules that are missing from All ACT Rules.

Success Criterion (A and AA) that have no current tests are (I may be wrong so feel free to correct me):

1.3.5 Identify Input Purpose (AA)
2.1.4 Character Key Shortcuts (A)
2.3.1 Three Flashes or Below Threshold (A)
2.5.1 Pointer Gestures (A)
3.2.3 Consistent Navigation (AA)
3.2.4 Consistent Identification (AA)
3.3.3 Error Suggestion (AA)
3.3.4 Error Prevention (Legal, Financial, Data) (AA)
4.1.3 Status Messages (AA)
And the AAA ones that might be covered as secondary checkpoints but have no rule just for them:

1.2.6 Sign Language (Prerecorded) (AAA)
1.2.7 Extended Audio Description (Prerecorded) (AAA)
1.2.8 Media Alternative (Prerecorded) (AAA)
1.2.9 Audio-only (Live) (AAA)
1.3.6 Identify Purpose (AAA)
1.4.7 Low or No Background Audio (AAA)
1.4.9 Images of Text (No Exception) (AAA)
2.1.3 Keyboard (No Exception) (AAA)
2.2.3 No Timing (AAA)
2.2.4 Interruptions (AAA)
2.2.5 Re-authenticating (AAA)
2.2.6 Timeouts (AAA)
2.3.2 Three Flashes (AAA)
2.3.3 Animation from Interactions (AAA)
2.4.10 Section Headings (AAA)
2.4.8 Location (AAA)
2.5.5 Target Size (AAA)
2.5.6 Concurrent Input Mechanisms (AAA)
3.1.3 Unusual Words (AAA)
3.1.4 Abbreviations (AAA)
3.1.5 Reading Level (AAA)
3.1.6 Pronunciation (AAA)
3.2.5 Change on Request (AAA)
3.3.5 Help (AAA)
3.3.6 Error Prevention (All) (AAA)
However, some success criteria have automated tests but might be missing a test that needs to be checked manually.

Feel free to reach out if you have any ideas or want to run through any points. When we get enough people authoring manual test rules, we will start a separate call to go through updates or points of contention (my biggest is where to start!) We have a lot to cover, and do not worry. I did make a start and created a rule that duplicated another. It was pointed out, and the joy of GitHub was I could remove it and no harm done.

Regards,
Helen