Creating a new SC-based issue
How to create a snippet based on the template snippet (for 3.3.7 Accessible Authentication)
- Search/replace (mechanical work)
- Accessible Authentication -> Name
- accessible-authentication -> url-path
- 3.3.7 -> number
- Add the string "n/a" to the field file. It is mandatory, but we do not use it.
- Read the Understanding document, determine whether the is SC relevant for:
- web pages
- non-web documents
- non-web software
- Adjust accordingly by adding or removing sections under 9, 10 and 11, test clauses, and references from tables.
- For example, when adding "2.5.7 Dragging" it is not entirely obvious if it is relevant to non-web documents. I would argue it should be there, since it is possible to imagine a scripted pdf file or some other document format to offer dragging interaction. Furthermore, I am usure whether Dragging should be only associated with the principle "Operable", or if it should also have (as a secondary relevance) Perceivable (some content may be impossible to perceive if users must drag a canvas sideways to reveal a hidden part of it). In this case I believe Operable is enough, but everybody might not agree.
- Also try to determine what functional performance statements are relevant?
- Adjust table B.2 accordingly.
- Even here, there could be some disagreement, even though the Understanding documents provide some guidance.
- More things to consider:
- When adding a clause to section 11, split it into more than one if the new SC applies differently (or not at all) when there's closed functionality. See Consider closed functionality when adding new clauses
- Are there any overlaps or intersections between the new SC and any (non-wcag) content in EN301549? If so, perhaps we should not "mechanically" add anything to the EN but rather change or replace existing content.
- Are there any conflicts between the new SC and any (non-wcag) content in EN301549? If so, there is a real challenge that will have to be dealt with.
- Create new issue briefly presenting the proposed new clause and linking to the new snippet
- Update link from snippet to the new issue just created
- link path issues/4 -> issues/X
Question 1: Should we point out areas where we think the proposed new clause could cause problems - or should we leave such judgement to JWG members? If we are to identify problematic areas, where do we indicate this? It could be using notes in the snippet or in the issue, or as comments to the issue.