Success Criterion @@ x.x.x @@: @@ Short name @@ (Level @@ x @@)

[Flores-21]

---

See our first example of a completed template for 1.3.4 Orientation in Issue 58.

Instructional note: Places where the text needs to be replaced are denoted using "@@" (two at signs) so you can easily search for and know what to change. For example, on the first line of the template:

• where "@@ x.x.x @@" is found, replace that text with the Success Criterion number. (e.g. 1.1.1)
• where "@@ Short name @@ is found, replace with the short name of the Success Criterion (e.g. Non-text Content)
• where "@@ x @@" is found, replace with the SC level. (e.g. A)

When completed, it would read:

Success Criterion 1.1.1: Non-text Content (Level A)

---

From [Success Criterion @@ x.x.x @@](@@ URL for the SC in WCAG 2.2 @@):

@@ Copy in text of the SC from WCAG 2.2 along with any notes. Use markdown to format properly, as needed. @@

Applying SC @@ x.x.x @@ @@shortname@@ to Non-Web Documents and Software

---

Instructional note: Analyze the text of the SC for words such as "Web", "page", "content", "pages", "user agent", "markup" which will key you into the need for substitution verbiage. Use one of the following statements, depending on what you think is correct and remove the bullet markdown. Add the following to the bullet if the SC refers to Conformance Requirement 5: @@ , and removing “See Conformance Requirement 5: Non-Interference”. @@

---

• This applies directly as written, and as described in [Intent from Understanding Success Criterion @@ x.x.x @@](@@ URL of WCAG 2.2 understanding#intent @@) (also provided below).
• This applies directly as written, and as described in [Intent from Understanding Success Criterion @@ x.x.x @@](@@ URL of WCAG 2.2 understanding#intent @@) (also provided below), replacing “@@ Web-focused language @@” with “@@ replacement non-web language @@”, “@@ page-related language @@” with “@@ appropriate non-web language @@”.

With these substitutions, it would read: @@ Omit this line if no substitutions are needed. @@

@@ Add in the SC text with the substitutions made. Omit this line if no substitutions are needed. @@

---

Instructional note: If you think notes are needed for specific areas of difficulty (platform software, software with closed functionality, documents, mobile software, etc.), add them. When multiple notes are needed, number them starting with Note 1: The Task Force will have a discussion for every SC for the potential to add any notes and review thoughts you have on potential notes.

---

Note: @@ Whatever note is needed. Omit this line if not needed. @@

[maryjom]

@Flores-21 If you wish to open an issue on WCAG2ICT, use the open a blank issue link, not the one the Task Force has been using as a template for content development. It'll make it easier for you to document the issue you wish to post.