diff --git a/testcases.md b/testcases.md index 04ce0a20..e6bcf419 100644 --- a/testcases.md +++ b/testcases.md @@ -35,6 +35,20 @@ Test Case documents are organized by Baseline Test (each serving as a Test Scena * [CAPTCHA - no alternative form of CAPTCHA provided for users without vision (TC06.3-3-fail-1)](testcases/TC06.3-3-fail-1.html) * [CAPTCHA - no alternative form of CAPTCHA provided for users without hearing (TC06.3-3-fail-2)](testcases/TC06.3-3-fail-2.html) * [CAPTCHA - text alternative identifies and describes purpose, and alternative forms of CAPTCHA provided for users without vision and users without hearing (TC06.3-all-pass-1)](testcases/TC06.3-all-pass-1.html) +* `7.` Sensory Characteristics + * [Color - Colored text with alt text (TC07.1-1.a-pass-1)](testcases/07.1-1.a-pass-1.html) + * [Color - Text with Visual Differentiations (TC07.1-1.b-pass-1)](testcases/07.1-1.b-pass-1.html) + * [Color - Failed use of color and visual differentiations](testcases/07.1-all-fail-1.html) + * [Color - Use of both color and visual differentiations](testcases/07.1-all-pass-1.html) + * [Color - Neither color or visual differentiations apply to meaning of text](testcases/07.1-ic-dna-1.html) + * [Sensory Characteristics - Instructions rely solely on shape to convey meaning](testcases/07.2-1-fail-1.html) + * [Sensory Characteristics - Instructions rely solely on size to convey meaning](testcases/07.2-1-fail-2.html) + * [Sensory Characteristics - Instructions rely solely on location to convey meaning](testcases/07.2-1-fail-3.html) + * [Sensory Characteristics - Instructions rely solely on relative position to convey meaning](testcases/07.2-1-fail-4.html) + * [Sensory Characteristics - Instructions rely on shape and additional information to convey meaning](testcases/07.2-1-pass-1.html) + * [Sensory Characteristics - Instructions rely on size and additional information to convey meaning](testcases/07.2-1-pass-2.html) + * [Sensory Characteristics - Instructions rely on location and additional information to convey meaning](testcases/07.2-1-pass-3.html) + * [Sensory Characteristics - Instructions rely on their relative position and additional information to convey meaning](testcases/07.2-1-pass-4.html) * `8.` Contrast * [Contrast - insufficient contrast ratio for small text (TC08.1-2-fail-1)](testcases/TC08.1-2-fail-1.html) * [Contrast - Pass; text with contrast ratio greater than 4.5:1 (TC08.1-2-pass-1)](testcases/TC08.1-2-pass-1.html) @@ -53,6 +67,7 @@ Test Case documents are organized by Baseline Test (each serving as a Test Scena * [Form Label: Form component with a clear label (TC10.5-1-pass-1)](testcases/TC10.5-1-pass-1.html) * [Form Label: Form component with descriptive label (TC10.5-1-pass-2)](testcases/TC10.5-1-pass-2.html) * [Form label: Form component with descriptive instructions (TC10.5-1-pass3)](testcases/TC10.5-1-pass-3.html) + * [Form label: Form component does not apply (TC10.5-ic-dna-1)](testcases/TC10.5-ic-dna-1.html) * `12.` Tables * [Data Tables - data table with role="presentation" (TC12.1-2-fail-1)](testcases/TC12.1-2-fail-1.html) * [Table - data table in a `` element and `role="none"` (TC12.1-2-fail-2)](testcases/TC12.1-2-fail-2.html) diff --git a/testcases/TC01.1-ic-dna-1.md b/testcases/TC01.1-ic-dna-1.md new file mode 100644 index 00000000..b04344de --- /dev/null +++ b/testcases/TC01.1-ic-dna-1.md @@ -0,0 +1,51 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Example of keyboard access + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-1 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC01.1-ic-dna-1.md + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of a feature that is neither accessible via keyboard or mouse. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [1.1 Test Procedure for Keyboard Access](https://ictbaseline.access-board.gov/01Keyboard/#11-test-procedure-for-keyboard-access) + + **Baseline Test ID:** 1.1-KeyboardAccess + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: DNA + +# Brief description of the rationale for the expected result +result-descr: | + The functions + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF01.1-ic-dna-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| IC-1| Check that all functionality can be accessed and executed using only the keyboard.| DNA | +| IC-2| Check that individual keystrokes do not require specific timings for activation.| DNA | \ No newline at end of file diff --git a/testcases/TC07.1-1.a-pass-1.md b/testcases/TC07.1-1.a-pass-1.md new file mode 100644 index 00000000..9333cbfd --- /dev/null +++ b/testcases/TC07.1-1.a-pass-1.md @@ -0,0 +1,51 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Use of Color + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.1-1.a-pass-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This shows alternative text to convey the meaning for the use of color. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.1 Test Procedure Use of Color](https://ictbaseline.access-board.gov/07Sensory/#71-test-procedure-for-use-of-color) + + **Baseline Test ID:** 7.1-Color + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + This is an example of an element that uses color to convey meaning. It also provides on-screen alternate text to convey the same meaning. + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.1-1.a-pass-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | The element using color to convey meaning also provides on-screen alternate text describing the color and/or the meaning conveyed by the color. | Pass. Alt text is included | +| 1-b | The element using color to convey meaning also provides other visual differentiation (e.g., shape, position, size, underline) with a clear indication of its meaning| Fail. there are no other visual differentiations besides color. | \ No newline at end of file diff --git a/testcases/TC07.1-1.b-pass-1.md b/testcases/TC07.1-1.b-pass-1.md new file mode 100644 index 00000000..cd837596 --- /dev/null +++ b/testcases/TC07.1-1.b-pass-1.md @@ -0,0 +1,51 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Use of Color + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.1-1.b-pass-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This shows alternative text to convey the meaning for the use of color as well as other visual differentiations. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.1 Test Procedure Use of Color](https://ictbaseline.access-board.gov/07Sensory/#71-test-procedure-for-use-of-color) + + **Baseline Test ID:** 7.1-Color + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + This example passes the standard of 07.1 because it provides other visual differentiation (e.g., shape, position, size, underline) with a clear indication of its meaning + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.1-1.b-pass-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | The element using color to convey meaning also provides on-screen alternate text describing the color and/or the meaning conveyed by the color. | Fail. there is no alternative text. | +| 1-b | The element using color to convey meaning also provides other visual differentiation (e.g., shape, position, size, underline) with a clear indication of its meaning| Pass. the visual differentiations are the font size and the underline of the text. | \ No newline at end of file diff --git a/testcases/TC07.1-all-fail-1.md b/testcases/TC07.1-all-fail-1.md new file mode 100644 index 00000000..802c455d --- /dev/null +++ b/testcases/TC07.1-all-fail-1.md @@ -0,0 +1,51 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Use of Color + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.1-all-fail-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This shows neither alternative text or visual differentiations on the text. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.1 Test Procedure Use of Color](https://ictbaseline.access-board.gov/07Sensory/#71-test-procedure-for-use-of-color) + + **Baseline Test ID:** 7.1-Color + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Fail + +# Brief description of the rationale for the expected result +result-descr: | + This example does not pass the standard of 07.1 because it does not use color or other visual differentiations on the text. + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.1-all-pass-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | The element using color to convey meaning also provides on-screen alternate text describing the color and/or the meaning conveyed by the color. | Fail. Alt text is not included | +| 1-b | The element using color to convey meaning also provides other visual differentiation (e.g., shape, position, size, underline) with a clear indication of its meaning| Fail. there are no other visual differentiations besides color. | \ No newline at end of file diff --git a/testcases/TC07.1-all-pass-1.md b/testcases/TC07.1-all-pass-1.md new file mode 100644 index 00000000..eadce4c6 --- /dev/null +++ b/testcases/TC07.1-all-pass-1.md @@ -0,0 +1,51 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Use of Color + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.1-all-pass-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This shows alternative text to convey the meaning for the use of color as well as other visual differentiations. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.1 Test Procedure Use of Color](https://ictbaseline.access-board.gov/07Sensory/#71-test-procedure-for-use-of-color) + + **Baseline Test ID:** 7.1-Color + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + This is an example of an element using color to convey meaning which also provides both on-screen alternate text to convey the same meaning and other visual differentiations. + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.1-all-pass-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | The element using color to convey meaning also provides on-screen alternate text describing the color and/or the meaning conveyed by the color. | Pass. Alt text is included | +| 1-b | The element using color to convey meaning also provides other visual differentiation (e.g., shape, position, size, underline) with a clear indication of its meaning| Pass. there are other visual differentiations besides color. | \ No newline at end of file diff --git a/testcases/TC07.1-ic-dna-1.md b/testcases/TC07.1-ic-dna-1.md new file mode 100644 index 00000000..3729cd41 --- /dev/null +++ b/testcases/TC07.1-ic-dna-1.md @@ -0,0 +1,51 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Use of Color + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.1-ic-dna-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of color not being used to convey meaning. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.1 Test Procedure Use of Color](https://ictbaseline.access-board.gov/07Sensory/#71-test-procedure-for-use-of-color) + + **Baseline Test ID:** 7.1-Color + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: DNA + +# Brief description of the rationale for the expected result +result-descr: | + This result shows no correlation between the color being used and the message it conveys. + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.1-ic-dna-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | The element using color to convey meaning also provides on-screen alternate text describing the color and/or the meaning conveyed by the color. | DNA | +| 1-b | The element using color to convey meaning also provides other visual differentiation (e.g., shape, position, size, underline) with a clear indication of its meaning| DNA | \ No newline at end of file diff --git a/testcases/TC07.2-1-fail-1.md b/testcases/TC07.2-1-fail-1.md new file mode 100644 index 00000000..4e7d2f66 --- /dev/null +++ b/testcases/TC07.2-1-fail-1.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-fail-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely solely on shape without providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Fail + +# Brief description of the rationale for the expected result +result-descr: | + The shape is used to convey meaning, but there is no alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-fail-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Fail. There is no on-screen alternative text to describe the meaning conveyed by the shape. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-fail-2.md b/testcases/TC07.2-1-fail-2.md new file mode 100644 index 00000000..46827736 --- /dev/null +++ b/testcases/TC07.2-1-fail-2.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-fail-2 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely solely on size without providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Fail + +# Brief description of the rationale for the expected result +result-descr: | + The size is used to convey meaning, but there is no alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-fail-2.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Fail. There is no on-screen alternative text to describe the meaning conveyed by the size. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-fail-3.md b/testcases/TC07.2-1-fail-3.md new file mode 100644 index 00000000..dda69805 --- /dev/null +++ b/testcases/TC07.2-1-fail-3.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-fail-3 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely solely on its location without providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Fail + +# Brief description of the rationale for the expected result +result-descr: | + The location is used to convey meaning, but there is no alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-fail-3.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Fail. There is no on-screen alternative text to describe the meaning conveyed by the location. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-fail-4.md b/testcases/TC07.2-1-fail-4.md new file mode 100644 index 00000000..fb08af0f --- /dev/null +++ b/testcases/TC07.2-1-fail-4.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-fail-4 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely solely on its relative position without providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Fail + +# Brief description of the rationale for the expected result +result-descr: | + The relative position is used to convey meaning, but there is no alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-fail-4.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Fail. There is no on-screen alternative text to describe the meaning conveyed by the relative position of the information. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-pass-1.md b/testcases/TC07.2-1-pass-1.md new file mode 100644 index 00000000..4f714b90 --- /dev/null +++ b/testcases/TC07.2-1-pass-1.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-pass-1 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely on its shape while providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + The shape is used to convey meaning and there is alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-pass-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Pass. There is on-screen alternative text to describe the meaning conveyed by the shape of the information. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-pass-2.md b/testcases/TC07.2-1-pass-2.md new file mode 100644 index 00000000..59fa75ea --- /dev/null +++ b/testcases/TC07.2-1-pass-2.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-pass-2 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely on its size while providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + The size is used to convey meaning and there is alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-pass-2.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Pass. There is on-screen alternative text to describe the meaning conveyed by the size of the information. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-pass-3.md b/testcases/TC07.2-1-pass-3.md new file mode 100644 index 00000000..72a0a515 --- /dev/null +++ b/testcases/TC07.2-1-pass-3.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-pass-3 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely on its location while providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + The location is used to convey meaning and there is alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-pass-3.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Pass. There is on-screen alternative text to describe the meaning conveyed by the location of the information. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC07.2-1-pass-4.md b/testcases/TC07.2-1-pass-4.md new file mode 100644 index 00000000..1819a48a --- /dev/null +++ b/testcases/TC07.2-1-pass-4.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Test Procedure for Sensory Characteristics + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-19 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC07.2-pass-4 + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of instructions that rely on its relative position while providing additional information to allow it to be located, identified and understood. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [7.2 Test Procedure for Sensory Characteristics](https://ictbaseline.access-board.gov/07Sensory/#72-test-procedure-for-sensory-characteristics) + + **Baseline Test ID:** 7.2-Sensory Characteristics + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: Pass + +# Brief description of the rationale for the expected result +result-descr: | + The relative position is used to convey meaning and there is alternative text on screen to explain the meaning. + + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF07/07.2-1-pass-4.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| 1-a | Check that the instructions contain additional information that allows it to be located, identified, and understood without any knowledge of its shape, size, or relative position | Pass. There is on-screen alternative text to describe the meaning conveyed by the relative position of the information. | +| 1-b | Check that any auditory cues also provide programmatically determinable visual and/or textual cues.| DNA. No auditory cues. | \ No newline at end of file diff --git a/testcases/TC10.5-1-fail-1.md b/testcases/TC10.5-1-fail-1.md index b01bc877..1b29ea20 100644 --- a/testcases/TC10.5-1-fail-1.md +++ b/testcases/TC10.5-1-fail-1.md @@ -47,6 +47,6 @@ sample: /testfiles/TF10/10.5-1-fail-1.html --- | Test Instruction | Instruction Detail | Expected Test Case Result | |------------------|--------------------|---------------------------| -| IC-1| Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, multi-select lists.| Input field found. | -| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| | +| IC-1| Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, multi-select lists.| Fail | +| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| Fail, none of the instructions or cues were related to the form components. | | 10.5-1 | Check that each form component has label(s) or instructions. [SC 3.3.2] | Fail. There is no visible label or prompt. | \ No newline at end of file diff --git a/testcases/TC10.5-1-pass-1.md b/testcases/TC10.5-1-pass-1.md index e87fa6c5..77622607 100644 --- a/testcases/TC10.5-1-pass-1.md +++ b/testcases/TC10.5-1-pass-1.md @@ -48,5 +48,5 @@ sample: /testfiles/TF10/10.5-1-pass-1.html | Test Instruction | Instruction Detail | Expected Test Case Result | |------------------|--------------------|---------------------------| | IC-1| Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, multi-select lists.| Input field found. | -| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| | -| 10.5-1 | Check that each form component has label(s) or instructions. [SC 3.3.2] | Pass. Though there is an unclear prompt for this form component. | \ No newline at end of file +| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| Input field found. | +| 10.5-1 | Check that each form component has label(s) or instructions. [SC 3.3.2] | Pass. Though there is a prompt for this form component. | \ No newline at end of file diff --git a/testcases/TC10.5-1-pass-2.md b/testcases/TC10.5-1-pass-2.md index a4476264..c95daa39 100644 --- a/testcases/TC10.5-1-pass-2.md +++ b/testcases/TC10.5-1-pass-2.md @@ -48,5 +48,5 @@ sample: /testfiles/TF10/10.5-1-pass-2.html | Test Instruction | Instruction Detail | Expected Test Case Result | |------------------|--------------------|---------------------------| | IC-1| Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, multi-select lists.| Input field found. | -| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| | +| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| Input field found. | | 10.5-1 | Check that each form component has label(s) or instructions. [SC 3.3.2] | Pass. There is a brief prompt that tells you what to type in the form component. | \ No newline at end of file diff --git a/testcases/TC10.5-1-pass-3.md b/testcases/TC10.5-1-pass-3.md index 706b9a91..a7be5ec3 100644 --- a/testcases/TC10.5-1-pass-3.md +++ b/testcases/TC10.5-1-pass-3.md @@ -48,5 +48,5 @@ sample: /testfiles/TF10/10.5-1-pass-3.html | Test Instruction | Instruction Detail | Expected Test Case Result | |------------------|--------------------|---------------------------| | IC-1| Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, multi-select lists.| Input field found. | -| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| | +| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| Input field found. | | 10.5-1 | Check that each form component has label(s) or instructions. [SC 3.3.2] | Pass. There is a descriptive prompt that tells you what to type in the form component. | \ No newline at end of file diff --git a/testcases/TC10.5-ic-dna-1.md b/testcases/TC10.5-ic-dna-1.md new file mode 100644 index 00000000..c7ec35f0 --- /dev/null +++ b/testcases/TC10.5-ic-dna-1.md @@ -0,0 +1,52 @@ +--- +# The layout must be 'testcase'; DO NOT Change +layout: testcase + +# Brief, descriptive title for the test case +title: Example of Form with no applicable test standard + +# The Test Case ID should follow the pattern: +# TC10.5-1-fail-1 +# [Expected Result (pass/fail/dna)]-[example #], e.g., TC05.1-1-fail-1 +tcid: TC10.5-ic-dna-1.md + +# Description of the Test Case, the included code sample, test considerations, +# and rationale for the expected result according to the applicable ICT +# Baseline test +descr: | + This is an example of a form with no prompt applicable to our test standards. + +# Reference and link to the applicable ICT Baseline test +app-baseline: | + [10.5 Forms with unapplicable standards](https://ictbaseline.access-board.gov/10Forms/#105-test-procedure-for-form-has-a-label) + + **Baseline Test ID:** 10.5-FormTitleDNA + + **Test Instruction:** 1 + +# Expected result that the ICT Baseline would predict +# [Pass | Fail | DNA] +result: DNA + +# Brief description of the rationale for the expected result +result-descr: | + The form component is labeled with a basic prompt for what it wants you to type. + +# URL for the code sample +# In the sample code file, add id="tc_code" to the +# element that contains the relevant code snippet. +# +# Then upload the code sample to the 'testfiles' folder +# and provide the link (and only the url) below. +sample: /testfiles/TF10/10.5-ic-dna-1.html + +# Table of test instructions, including the following table headers: +# Test Instruction #; Instruction Detail; Expected Test Case Result +# +# Include the table in the content section below +--- +| Test Instruction | Instruction Detail | Expected Test Case Result | +|------------------|--------------------|---------------------------| +| IC-1| Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, multi-select lists.| Input field found. | +| IC-2| Find all instructions and cues (textual and graphical) that are related to form components, including groupings, order of completion, special conditions or qualifiers, format instructions, etc.| Input field found. | +| 10.5-ic | Check that each form component has label(s) or instructions. [SC 3.3.2] | DNA. The form component does not apply to the standards of 10.5 | \ No newline at end of file diff --git a/testfiles/TF07/07.1-1.a-pass-1.html b/testfiles/TF07/07.1-1.a-pass-1.html new file mode 100644 index 00000000..9f6da646 --- /dev/null +++ b/testfiles/TF07/07.1-1.a-pass-1.html @@ -0,0 +1,15 @@ + + + + + + 07.1-1.a-pass-1 + + +
+

+

This is what our blue looks like! alt="Dodger Blue color used as font color to show the reader an example of it!"

+

+

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.1-1.b-pass-1.html b/testfiles/TF07/07.1-1.b-pass-1.html new file mode 100644 index 00000000..21d8f060 --- /dev/null +++ b/testfiles/TF07/07.1-1.b-pass-1.html @@ -0,0 +1,13 @@ + + + + + 07.1-1.b-pass-1 + + +
+

The text that is underlined is important!

+ +
+ + \ No newline at end of file diff --git a/testfiles/TF07/07.1-all-fail-1.html b/testfiles/TF07/07.1-all-fail-1.html new file mode 100644 index 00000000..99605000 --- /dev/null +++ b/testfiles/TF07/07.1-all-fail-1.html @@ -0,0 +1,16 @@ + + + + + + 07.1-all-fail-1 + + +
+

+

This is what our blue looks like!

+ alt="The text is underlined" fix +

+
+ + \ No newline at end of file diff --git a/testfiles/TF07/07.1-all-pass-1.html b/testfiles/TF07/07.1-all-pass-1.html new file mode 100644 index 00000000..0c08f2e0 --- /dev/null +++ b/testfiles/TF07/07.1-all-pass-1.html @@ -0,0 +1,16 @@ + + + + + + 07.1-all-pass-1 + + +
+

+

This is what our blue looks like! alt="Dodger Blue color used as font color to show the reader an example of it!"

+ +

+
+ + \ No newline at end of file diff --git a/testfiles/TF07/07.1-ic-dna-1.html b/testfiles/TF07/07.1-ic-dna-1.html new file mode 100644 index 00000000..e543120c --- /dev/null +++ b/testfiles/TF07/07.1-ic-dna-1.html @@ -0,0 +1,15 @@ + + + + + + 07.1-ic-dna-1 + + +
+

+

Hello World

+

+

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-fail-1.html b/testfiles/TF07/07.2-1-fail-1.html new file mode 100644 index 00000000..3be7ee5b --- /dev/null +++ b/testfiles/TF07/07.2-1-fail-1.html @@ -0,0 +1,16 @@ + + + + + + 07.2-1-fail-1 + + +
+

+

If you are an employee of the U.S Access Board, do not click the button.

+ +

+

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-fail-2.html b/testfiles/TF07/07.2-1-fail-2.html new file mode 100644 index 00000000..7847018d --- /dev/null +++ b/testfiles/TF07/07.2-1-fail-2.html @@ -0,0 +1,11 @@ + + + + + + 07.2-1-fail-2 + + +

If you are an employee of the U.S Access Board, follow the instructions in the larger font.

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-fail-3.html b/testfiles/TF07/07.2-1-fail-3.html new file mode 100644 index 00000000..1a787400 --- /dev/null +++ b/testfiles/TF07/07.2-1-fail-3.html @@ -0,0 +1,12 @@ + + + + + + 07.2-1-fail-3 + + + +

If you are an employee of the U.S Access Board, please refer to the instructions. The instructions are for you to click the button.

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-fail-4.html b/testfiles/TF07/07.2-1-fail-4.html new file mode 100644 index 00000000..b99dbeaa --- /dev/null +++ b/testfiles/TF07/07.2-1-fail-4.html @@ -0,0 +1,16 @@ + + + + + + 07.2-1-fail-4 + + +
+

+

If you are an employee of the U.S Access Board, your instructions are to click the button.

+ +

+

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-pass-1.html b/testfiles/TF07/07.2-1-pass-1.html new file mode 100644 index 00000000..77139891 --- /dev/null +++ b/testfiles/TF07/07.2-1-pass-1.html @@ -0,0 +1,16 @@ + + + + + + 07.2-1-pass-1 + + +
+

+

If you are an employee of the U.S Access Board, do not click the button. The button is directly underneath this text and it reads "Click Me", it's in a different font and size than this sentence.

+ +

+

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-pass-2.html b/testfiles/TF07/07.2-1-pass-2.html new file mode 100644 index 00000000..f1e77686 --- /dev/null +++ b/testfiles/TF07/07.2-1-pass-2.html @@ -0,0 +1,12 @@ + + + + + + 07.2-1-pass-2 + + +

If you are an employee of the U.S Access Board, follow the instructions in the larger font.

+

The above text has a font size of 40px, instructions in that size are specifically for employees of the USAB only. Instructions in a font size of 18px (the font size of this sentence) are for everyone else.

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1-pass-3.html b/testfiles/TF07/07.2-1-pass-3.html new file mode 100644 index 00000000..9bf375e0 --- /dev/null +++ b/testfiles/TF07/07.2-1-pass-3.html @@ -0,0 +1,12 @@ + + + + + + 07.2-1-pass-3 + + + +

If you are an employee of the U.S Access Board, please refer to the instructions at the end this sentence. The instructions are for you to click the button above this sentence. The button is in a different font and text size, it reads "Click Me!".

+ + \ No newline at end of file diff --git a/testfiles/TF07/07.2-1.pass-4.html b/testfiles/TF07/07.2-1.pass-4.html new file mode 100644 index 00000000..75b2c48c --- /dev/null +++ b/testfiles/TF07/07.2-1.pass-4.html @@ -0,0 +1,16 @@ + + + + + + 07.2-1-fail-4 + + +
+

+

If you are an employee of the U.S Access Board, please click the button underneath this sentence. It reads "Click Me!" and it is in a differnt text size and font than this sentence.

+ +

+

+ + \ No newline at end of file diff --git a/testfiles/TF10/10.5-1-fail-1.html b/testfiles/TF10/TC10.5-1-fail-1.html similarity index 100% rename from testfiles/TF10/10.5-1-fail-1.html rename to testfiles/TF10/TC10.5-1-fail-1.html diff --git a/testfiles/TF10/10.5-1-pass-1.html b/testfiles/TF10/TC10.5-1-pass-1.html similarity index 100% rename from testfiles/TF10/10.5-1-pass-1.html rename to testfiles/TF10/TC10.5-1-pass-1.html diff --git a/testfiles/TF10/10.5-1-pass-2.html b/testfiles/TF10/TC10.5-1-pass-2.html similarity index 100% rename from testfiles/TF10/10.5-1-pass-2.html rename to testfiles/TF10/TC10.5-1-pass-2.html diff --git a/testfiles/TF10/10.5-1-pass-3.html b/testfiles/TF10/TC10.5-1-pass-3.html similarity index 100% rename from testfiles/TF10/10.5-1-pass-3.html rename to testfiles/TF10/TC10.5-1-pass-3.html diff --git a/testfiles/TF10/TC10.5-ic-dna-1.html b/testfiles/TF10/TC10.5-ic-dna-1.html new file mode 100644 index 00000000..d0083ecc --- /dev/null +++ b/testfiles/TF10/TC10.5-ic-dna-1.html @@ -0,0 +1,16 @@ + + + + + + 10.5-1-pass-1 + + +
+

+ + +

+
+ + \ No newline at end of file