From 98cc8caecec064a406a8ce2672eccd71a71f2ad5 Mon Sep 17 00:00:00 2001 From: Alan King Date: Thu, 20 Aug 2020 20:33:30 -0400 Subject: [PATCH 01/21] New test case: TC05-001-fail and update to TC10-001-fail --- docs/testcases/TC05-001-fail.html | 271 ++++++++++++++++++ docs/testcases/TC10-001-fail.html | 4 +- docs/testfiles/TF05/05-001.html | 54 ++++ docs/testfiles/{TF10-001 => TF10}/10-001.html | 0 4 files changed, 327 insertions(+), 2 deletions(-) create mode 100644 docs/testcases/TC05-001-fail.html create mode 100644 docs/testfiles/TF05/05-001.html rename docs/testfiles/{TF10-001 => TF10}/10-001.html (100%) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html new file mode 100644 index 00000000..7a552136 --- /dev/null +++ b/docs/testcases/TC05-001-fail.html @@ -0,0 +1,271 @@ + + + + + + Changing Content - aria-live='off' + + + + + + + + + + + + + + + + +
+ + + + + ICT Accessibility Testing Baseline Alignment +
+ + + + + + +
+ + + + + + +
+
+
+
+
+

Changing Content: aria-live='off'

+

Test Case Summary

+

Test Case ID

+

TC05-001-fail

+

Test Case Description

+

The aria-live politeness setting is used to set the priority with which screen readers should announce updates to designated live regions. The options are off, polite and assertive with the default being off. For any live region meant to convey meaningful information to assistive technology, the off setting, being the same as the omission of the live region altogether, would represent a failure of accessibility. The code sample presents aria-live='off'. A successful test should identify a failure against Baseline Test 5.1-ChangeContent.

+

Applicable ICT Baseline

+

05. Changing Content

+

Visual and programmatically associated changes in content

+
Test Instructions
+ + + +
4.1.2 Name, Role, Value
+
    +
  1. Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] +
      +
    1. Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
      2. +
    +
    2. +
  2. For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] +
      +
    1. Name: the name is accurate after a change. + +
      2. +
    2. Role: the role accurately describes the purpose of the element after a change, if applicable. +
        +
      • Consider ARIA role, element type, and other descriptive text.
        • +
      +
      3. +
    3. State: the state of the element is accurate after a change, if applicable +
        +
      • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
        • +
      +
      4. +
    4. Value: the value is updated after a change, if applicable.
      5. +
    +
    3. +
+ + +
Test Results
+ + + +
    +
  • If any of the above checks fail, then SC 4.1.2, and Baseline Requirement 05 fail.
    • +
+ + + +

Applicable WCAG/508 Requirement

+ +
    +
  • WCAG2 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
    • +
+ + + +
+
+
+
+ +

Test Case Detail

+

Expected Baseline Result

+ +

+ + Fail + +

+ +

+ + After content change, the text updated in the code sample is neither programmatically bound, given focus, nor included in a live region. + +

+ +

Test Data (code/link)

+

Code

+
+
+
+<fieldset>
+    <legend>aria-live='off'</legend>
+        <button onclick="document.getElementById('content2').textContent='The text has been updated.'">Update</button>&nbsp;
+        <button onclick="location.reload()">Reset</button>
+        <p id="content2" aria-live="off">Initial text.</p>
+</fieldset> 
+
+
+
+ +

Single-Page URL

+ +

+ https://section508coordinators.github.io/BaselineTestPages/testfiles/TF05-001/05-001.html +

+ +

Embedded Code

+ + + + + + +

Test Steps

+ + + + + + + + + + + + + + + + + + + + + + + + + + + +
Test StepStep DetailExpected Result
1Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] +
    +
  • Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
    • +
The text content being changed does not present notification of that change programmatically through alerts, shift in focus, or use of ARIA live regions.
2For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] +
    +
  • Name: the name is accurate after a change. + +
    • +
  • Role: the role accurately describes the purpose of the element after a change, if applicable. +
      +
    • Consider ARIA role, element type, and other descriptive text.
      • +
    +
    • +
  • State: the state of the element is accurate after a change, if applicable +
      +
    • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
      • +
    +
    • +
  • Value: the value is updated after a change, if applicable.
    • +
The text content change is accurate.
3If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.Test step 2 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails.
+ +
+
+
+
+
+ + + + + + + + + + + \ No newline at end of file diff --git a/docs/testcases/TC10-001-fail.html b/docs/testcases/TC10-001-fail.html index 749de8cb..b212afec 100644 --- a/docs/testcases/TC10-001-fail.html +++ b/docs/testcases/TC10-001-fail.html @@ -168,13 +168,13 @@

Code

Single-Page URL

- https://section508coordinators.github.io/BaselineTestPages/testfiles/TF10-001/10-001.html + https://section508coordinators.github.io/BaselineTestPages/testfiles/TF10/10-001.html

Embedded Code

- diff --git a/docs/testfiles/TF05/05-001.html b/docs/testfiles/TF05/05-001.html new file mode 100644 index 00000000..56f087b9 --- /dev/null +++ b/docs/testfiles/TF05/05-001.html @@ -0,0 +1,54 @@ + + + + +10-001-fail + + + + + + + + + + + + + + + + + +
+ aria-live='off' +   +

Initial text.

+
+ + + diff --git a/docs/testfiles/TF10-001/10-001.html b/docs/testfiles/TF10/10-001.html similarity index 100% rename from docs/testfiles/TF10-001/10-001.html rename to docs/testfiles/TF10/10-001.html From feeaa264a78143c84f5911b6adbb306202e63d11 Mon Sep 17 00:00:00 2001 From: Alan King Date: Sat, 22 Aug 2020 16:25:19 -0400 Subject: [PATCH 02/21] Add new test case TC10-008-dna (visibility:hidden) and update baseline-align.css style sheet --- docs/css/baseline-align.css | 17 ++- docs/testcases.html | 5 +- docs/testcases/TC10-008-dna.html | 229 +++++++++++++++++++++++++++++++ docs/testfiles/TF10/10-008.html | 33 +++++ 4 files changed, 281 insertions(+), 3 deletions(-) create mode 100644 docs/testcases/TC10-008-dna.html create mode 100644 docs/testfiles/TF10/10-008.html diff --git a/docs/css/baseline-align.css b/docs/css/baseline-align.css index 7bc902ae..9cefe0a5 100644 --- a/docs/css/baseline-align.css +++ b/docs/css/baseline-align.css @@ -138,4 +138,19 @@ header { .bypass-block-target:focus { outline: none; -} \ No newline at end of file +} + +code { + color: #C00000 !important; +} + +.code { + background-color: #bbb; + background-color: rgba(222,222,222,.5); + border-radius: 2px; + box-decoration-break: clone; + /*font:Consolas, "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", Monaco, "Courier New", "monospace";*/ + padding: 0 2px; + word-wrap: break-word; +} + diff --git a/docs/testcases.html b/docs/testcases.html index 47441b90..21e3d720 100644 --- a/docs/testcases.html +++ b/docs/testcases.html @@ -95,8 +95,9 @@

Placeholder Index

  • 10. Forms
    • diff --git a/docs/testcases/TC10-008-dna.html b/docs/testcases/TC10-008-dna.html new file mode 100644 index 00000000..b19231be --- /dev/null +++ b/docs/testcases/TC10-008-dna.html @@ -0,0 +1,229 @@ + + + + + + Input text element - Accessibility tree visibility (visibility:hidden) + + + + + + + + + + + + + + + + + +
    + + + + + ICT Accessibility Testing Baseline Alignment +
    + + + + + + +
    + + + + + + +
    +
    +
    +
    +
    +

    Input text element - Accessibility tree visibility (visibility:hidden)

    +

    Test Case Summary

    +

    Test Case ID

    +

    TC10-008-DNA

    +

    Test Case Description

    +

    The purpose of this test case is to detect attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative for input elements. The code sample does not present itself via the Accessibility tree/Accessibility object model (AOM), visually, or programmatically and consequently cannot be identified by the tester within the current test process. Consequently, a successful test should indicate that this test does not apply to Baseline Test 10 Forms.
    +
    + Note: If the intent of the developer is to make the input element available to users as a part of meaningful ICT functionality, then the CSS property visibility:hidden should not be used with interactive elements.

    +

    Applicable ICT Baseline

    +

    10. Forms

    +

    Complete and programmatically associated form labels and instructions

    +
    Test Instructions
    + + + +
    4.1.2 Name, Role, Value and 1.3.1 Info and Relationships
    +
      +
    1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
      2. +
    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.
      3. +
    3. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
      4. +
    4. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: + +
      5. +
    + + +
    Test Results
    + + + +
      +
    • If any of the above checks fail, then SC 1.3.1, SC 4.1.2, and Baseline Requirement 10 fail.
      • +
    • If there is no such content, then the result for the Baseline Test 10. Forms is DOES NOT APPLY (DNA)
      • +
    + + + +

    Applicable WCAG/508 Requirement

    + +
      +
    • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
      • +
    • WCAG2 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
      • +
    + + + +
    +
    +
    +
    + +

    Test Case Detail

    +

    Expected Baseline Result

    + +

    + + DNA + +

    + +

    + + [The input element in the code sample does not provide any attributes that would contribute to an accessible name or description. + +

    + +

    Test Data (code/link)

    +

    Code

    +
    +
+
+<div style="visibility:hidden">
+    <p class="plabel">First Name: <input type="text" size="25"></p>
+</div>
+
+
+
    + +

    Single-Page URL

    + +

    + https://section508coordinators.github.io/BaselineTestPages/testfiles/TF10/10-008.html +

    + +

    Embedded Code

    + + + + + + +

    Test Steps

    + + + + + + + + + + + + + + + + + +
    Test StepStep DetailExpected Result
    1Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.The single input element in this test case is enclosed in the visibility:hidden CSS property which removes it from the accessibility tree, visible, and programmatic detection. Even though the code exists in the DOM, this property renders the element undetectable and therefore not applicable to this Baseline Test based on the results of test step 1.
    + +
    +
    +
    +
    +
    + + +
    +
    + copyright notice and link to license page +
    +
    + + + + + + + + \ No newline at end of file diff --git a/docs/testfiles/TF10/10-008.html b/docs/testfiles/TF10/10-008.html new file mode 100644 index 00000000..d03f0ae3 --- /dev/null +++ b/docs/testfiles/TF10/10-008.html @@ -0,0 +1,33 @@ + + + + +10-008 + + + + + + + + + + + + + + +
    +

    First Name:

    +
    + + From 116caa4329df0c2b85f7b5b2db03b1d1cd6101aa Mon Sep 17 00:00:00 2001 From: Alan King Date: Sat, 22 Aug 2020 16:36:59 -0400 Subject: [PATCH 03/21] Add new test case TC10-009-dna (display:none) --- docs/testcases/TC10-009-dna.html | 229 +++++++++++++++++++++++++++++++ docs/testfiles/TF10/10-009.html | 32 +++++ 2 files changed, 261 insertions(+) create mode 100644 docs/testcases/TC10-009-dna.html create mode 100644 docs/testfiles/TF10/10-009.html diff --git a/docs/testcases/TC10-009-dna.html b/docs/testcases/TC10-009-dna.html new file mode 100644 index 00000000..c19dbb26 --- /dev/null +++ b/docs/testcases/TC10-009-dna.html @@ -0,0 +1,229 @@ + + + + + + Input text element - Accessibility tree visibility (display:none) + + + + + + + + + + + + + + + + + +
    + + + + + ICT Accessibility Testing Baseline Alignment +
    + + + + + + +
    + + + + + + +
    +
    +
    +
    +
    +

    Input text element - Accessibility tree visibility (display:none)

    +

    Test Case Summary

    +

    Test Case ID

    +

    TC10-009-DNA

    +

    Test Case Description

    +

    The purpose of this test case is to detect attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative for input elements. The code sample does not present itself via the Accessibility tree/Accessibility object model (AOM), visually, or programmatically and consequently cannot be identified by the tester within the current test process. Consequently, a successful test should indicate that this test does not apply to Baseline Test 10 Forms.
    +
    + Note: If the intent of the developer is to make the input element available to users as a part of meaningful ICT functionality, then the CSS property display:none should not be used with interactive elements.

    +

    Applicable ICT Baseline

    +

    10. Forms

    +

    Complete and programmatically associated form labels and instructions

    +
    Test Instructions
    + + + +
    4.1.2 Name, Role, Value and 1.3.1 Info and Relationships
    +
      +
    1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
      2. +
    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.
      3. +
    3. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
      4. +
    4. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: + +
      5. +
    + + +
    Test Results
    + + + +
      +
    • If any of the above checks fail, then SC 1.3.1, SC 4.1.2, and Baseline Requirement 10 fail.
      • +
    • If there is no such content, then the result for the Baseline Test 10. Forms is DOES NOT APPLY (DNA)
      • +
    + + + +

    Applicable WCAG/508 Requirement

    + +
      +
    • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
      • +
    • WCAG2 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
      • +
    + + + +
    +
    +
    +
    + +

    Test Case Detail

    +

    Expected Baseline Result

    + +

    + + DNA + +

    + +

    + + [The input element in the code sample does not provide any attributes that would contribute to an accessible name or description. + +

    + +

    Test Data (code/link)

    +

    Code

    +
    +
+
+<div style="display:none">
+ <p class="plabel">First Name: <input type="text" size="25"></p>
+</div>
+
+
+
    + +

    Single-Page URL

    + +

    + https://section508coordinators.github.io/BaselineTestPages/testfiles/TF10/10-009.html +

    + +

    Embedded Code

    + + + + + + +

    Test Steps

    + + + + + + + + + + + + + + + + + +
    Test StepStep DetailExpected Result
    1Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.The single input element in this test case is enclosed in the display:none CSS property which removes it from the accessibility tree, visible, and programmatic detection. Even though the code exists in the DOM, this property renders the element undetectable and therefore not applicable to this Baseline Test based on the results of test step 1.
    + +
    +
    +
    +
    +
    + + +
    +
    + copyright notice and link to license page +
    +
    + + + + + + + + \ No newline at end of file diff --git a/docs/testfiles/TF10/10-009.html b/docs/testfiles/TF10/10-009.html new file mode 100644 index 00000000..f7fd2f60 --- /dev/null +++ b/docs/testfiles/TF10/10-009.html @@ -0,0 +1,32 @@ + + + + +10-009 + + + + + + + + + + + + + +
    +

    First Name:

    +
    + + From 267faec3e40153c7eaf78267ac281d639aa2d448 Mon Sep 17 00:00:00 2001 From: Alan King Date: Sat, 22 Aug 2020 16:54:38 -0400 Subject: [PATCH 04/21] Update to test case TC10-001-fail under "Test Instructions" to correct formatting --- docs/testcases/TC10-001-fail.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/testcases/TC10-001-fail.html b/docs/testcases/TC10-001-fail.html index b212afec..fa170389 100644 --- a/docs/testcases/TC10-001-fail.html +++ b/docs/testcases/TC10-001-fail.html @@ -103,11 +103,11 @@
  • Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
  • Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include:
    • @@ -194,12 +194,12 @@

    Test Steps

    1 Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists. - One <input> element exists in the test data code sample. + One input element exists in the test data code sample. 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. - The <input> control has a visual label in the form of the text directly to the left of the control. + The input control has a visual label in the form of the text directly to the left of the control. 3 From 2345eb4de16b388155aa6bd6bab43da1c871069e Mon Sep 17 00:00:00 2001 From: Alan King Date: Tue, 25 Aug 2020 18:31:06 -0400 Subject: [PATCH 05/21] Updated baseline-align.css file to remove redundant background color --- docs/css/baseline-align.css | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/css/baseline-align.css b/docs/css/baseline-align.css index 9cefe0a5..d741964a 100644 --- a/docs/css/baseline-align.css +++ b/docs/css/baseline-align.css @@ -145,11 +145,9 @@ code { } .code { - background-color: #bbb; background-color: rgba(222,222,222,.5); border-radius: 2px; box-decoration-break: clone; - /*font:Consolas, "Andale Mono", "Lucida Console", "Lucida Sans Typewriter", Monaco, "Courier New", "monospace";*/ padding: 0 2px; word-wrap: break-word; } From f156fbb9b03fcc6a161fa93a41e85f0f5ce3302b Mon Sep 17 00:00:00 2001 From: Alan King Date: Tue, 25 Aug 2020 18:33:56 -0400 Subject: [PATCH 06/21] Updated test case TC05-001 (aria-live='off') to address baseline alignment to test steps, update URL pointer to testfile away from staging repo, clarification of aria-live default values --- docs/testcases/TC05-001-fail.html | 36 ++++++++++++++++++++----------- 1 file changed, 23 insertions(+), 13 deletions(-) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 7a552136..7e33c955 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -90,7 +90,7 @@

    Test Case Summary

    Test Case ID

    TC05-001-fail

    Test Case Description

    -

    The aria-live politeness setting is used to set the priority with which screen readers should announce updates to designated live regions. The options are off, polite and assertive with the default being off. For any live region meant to convey meaningful information to assistive technology, the off setting, being the same as the omission of the live region altogether, would represent a failure of accessibility. The code sample presents aria-live='off'. A successful test should identify a failure against Baseline Test 5.1-ChangeContent.

    +

    The aria-live politeness setting is used to set the priority with which screen readers should announce updates to designated live regions. The options are off, polite and assertive. With the exceptions of the ARIA roles of alert, log, and status (with default option settings of assertive, polite, and polite respectively), the default aria-live option is off. For any live region meant to convey meaningful information to assistive technology, the off setting, being the same as the omission of the live region altogether, would represent a failure of accessibility. The code sample presents aria-live='off'. A successful test should identify a failure against Baseline Test 5.1-ChangeContent.

    Applicable ICT Baseline

    05. Changing Content

    Visual and programmatically associated changes in content

    @@ -119,7 +119,7 @@
  • State: the state of the element is accurate after a change, if applicable
      -
    • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
      • +
    • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
  • Value: the value is updated after a change, if applicable.
    • @@ -187,13 +187,13 @@

    Code

    Single-Page URL

    - https://section508coordinators.github.io/BaselineTestPages/testfiles/TF05-001/05-001.html + https://section508coordinators.github.io/BaselineTestPages/testfiles/TF05/05-001.html

    Embedded Code

    - @@ -212,14 +212,24 @@

    Test Steps

    1 - Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] -
      -
    • Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
      • -
    - The text content being changed does not present notification of that change programmatically through alerts, shift in focus, or use of ARIA live regions. + It may be necessary to use the mouse to determine whether state changes occur on hover or on click. + For the test example, the content (text) changes on selection of a button element - either by mouse or keyboard selection. - 2 + 2 + Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc. + The state of HTML text updates in response to a clicking the "Update" button element. + + + 3 + Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] +
      +
    • Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
      • +
    + The page does not provide a programmatic notification of change in content through alerts, shift in focus, or use of ARIA live regions. The aria-live region attribute included in the code example, because it is set to "off", does not execute and therefore does not provide a programmatic notification. + + + 4 For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2]
    • Name: the name is accurate after a change. @@ -234,17 +244,17 @@

      Test Steps

    • State: the state of the element is accurate after a change, if applicable
        -
      • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
        • +
      • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
    • Value: the value is updated after a change, if applicable.
    - The text content change is accurate. + The change in content is not programmatically provided. 3 If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails. - Test step 2 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails. + Test step 3 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails. From 58a212a6da0b73c87c56da73c24904d3eddf1c90 Mon Sep 17 00:00:00 2001 From: Alan King Date: Wed, 26 Aug 2020 16:52:28 -0400 Subject: [PATCH 07/21] updated TC05-001-fail to implement new test steps format --- docs/testcases/TC05-001-fail.html | 45 ++++++++++++++++++------------- 1 file changed, 27 insertions(+), 18 deletions(-) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 7e33c955..6f0165b5 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -204,33 +204,39 @@

    Test Steps

    - - - + + + - - - + + + + + + - - - + + + + + + - - + - + - - + - + - - - + + + + + +
    Test StepStep DetailExpected ResultTest StepStep DetailExpected Result
    1It may be necessary to use the mouse to determine whether state changes occur on hover or on click.For the test example, the content (text) changes on selection of a button element - either by mouse or keyboard selection.

    Identify Content

    1It may be necessary to use the mouse to determine whether state changes occur on hover or on click.For the test example, the content (text) changes on selection of a button element - either by mouse or keyboard selection.
    2Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.The state of HTML text updates in response to a clicking the "Update" button element.2Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.The state of HTML text updates in response to a clicking the "Update" button element.

    Test Instructions
    3Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] + 1Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]
    • Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
    		The page does not provide a programmatic notification of change in content through alerts, shift in focus, or use of ARIA live regions. The aria-live region attribute included in the code example, because it is set to "off", does not execute and therefore does not provide a programmatic notification.The page does not provide a programmatic notification of change in content through alerts, shift in focus, or use of ARIA live regions. The aria-live region attribute included in the code example, because it is set to "off", does not execute and therefore does not provide a programmatic notification.
    4For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] + 2For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2]
    • Name: the name is accurate after a change.
        @@ -249,12 +255,15 @@

        Test Steps

      • Value: the value is updated after a change, if applicable.
    		The change in content is not programmatically provided.The change in content is not programmatically provided.
    3If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.Test step 3 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails.

    Test Results

  •  
    		• If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.Test instruction 2 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails.
    From 3c056545876efa02b46912e54a2f7d7be55e80e3 Mon Sep 17 00:00:00 2001 From: Alan King Date: Wed, 26 Aug 2020 16:58:16 -0400 Subject: [PATCH 08/21] Fix bullet in Test Steps table. --- docs/testcases/TC05-001-fail.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 6f0165b5..97d2419d 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -261,7 +261,7 @@

    Test Steps

    Test Results

    -
  •  
    • +
    •  
    If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails. Test instruction 2 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails. From 4fa021c3f86adf5d89b44051842149c13d600df8 Mon Sep 17 00:00:00 2001 From: Alan King Date: Wed, 26 Aug 2020 17:36:38 -0400 Subject: [PATCH 09/21] Updates to TC05-001-fail to align "Applicable ICT Baseline" section of test case with ICT Baseline format. --- docs/testcases/TC05-001-fail.html | 86 +++++++++++++++---------------- 1 file changed, 43 insertions(+), 43 deletions(-) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 97d2419d..1de76d1e 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -98,7 +98,15 @@
    Test Instructions
    -
    4.1.2 Name, Role, Value
    +

    Baseline Test ID: 5.1-ChangeContent

    + +
    Identify Content
    +

    Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc.

    +
      +
    • It may be necessary to use the mouse to determine whether state changes occur on hover or on click.
      • +
    • Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.
      • +
    +
    4.1.2 Name, Role, Value
    1. Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]
        @@ -133,7 +141,7 @@
        Test Results
          -
        • If any of the above checks fail, then SC 4.1.2, and Baseline Requirement 05 fail.
          • +
        • If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.
        @@ -204,69 +212,61 @@

        Test Steps

        - - - + + + - - - - + - + - - - - - + - + - - - - - - + + + - - - + + +
        Test StepStep DetailExpected ResultTest StepStep DetailExpected Result

        Identify Content

        11 It may be necessary to use the mouse to determine whether state changes occur on hover or on click. For the test example, the content (text) changes on selection of a button element - either by mouse or keyboard selection.
        22 Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc. The state of HTML text updates in response to a clicking the "Update" button element.

        Test Instructions

        1Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] + 3Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]
        • Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
        		The page does not provide a programmatic notification of change in content through alerts, shift in focus, or use of ARIA live regions. The aria-live region attribute included in the code example, because it is set to "off", does not execute and therefore does not provide a programmatic notification.The page does not provide a programmatic notification of change in content through alerts, shift in focus, or use of ARIA live regions. The aria-live region attribute included in the code example, because it is set to "off", does not execute and therefore does not provide a programmatic notification.
        2For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] -
          -
        • Name: the name is accurate after a change. - -
          • -
        • Role: the role accurately describes the purpose of the element after a change, if applicable. -
            -
          • Consider ARIA role, element type, and other descriptive text.
            • -
          -
          • -
        • State: the state of the element is accurate after a change, if applicable -
            -
          • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
            • -
          -
          • -
        • Value: the value is updated after a change, if applicable.
          • -
        		The change in content is not programmatically provided.

        Test Results

        		4For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] +
          +
        • Name: the name is accurate after a change. + +
          • +
        • Role: the role accurately describes the purpose of the element after a change, if applicable. +
            +
          • Consider ARIA role, element type, and other descriptive text.
            • +
          +
          • +
        • State: the state of the element is accurate after a change, if applicable +
            +
          • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
            • +
          +
          • +
        • Value: the value is updated after a change, if applicable.
          • +
        		The change in content is not programmatically provided.
        •  
        		If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.Test instruction 2 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails.5If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.Test step 3 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails.
        + From c6bcaa98e3d7a0c7ed2b630acb35154ce2fa4453 Mon Sep 17 00:00:00 2001 From: Alan King Date: Wed, 26 Aug 2020 18:12:33 -0400 Subject: [PATCH 10/21] Updates to Alan's Dreamweaver template, TC05-001-fail, FC10-001-fail, TC10-008-dna, TC10-009-dna - all for new format to align with Baseline format. --- Templates/BAWG-Tmpl-01.dwt | 4 ++-- docs/testcases/TC05-001-fail.html | 4 ++-- docs/testcases/TC10-001-fail.html | 28 ++++++++++++++--------- docs/testcases/TC10-008-dna.html | 38 +++++++++++++++++-------------- docs/testcases/TC10-009-dna.html | 38 +++++++++++++++++-------------- 5 files changed, 63 insertions(+), 49 deletions(-) diff --git a/Templates/BAWG-Tmpl-01.dwt b/Templates/BAWG-Tmpl-01.dwt index e0763696..bc200ece 100644 --- a/Templates/BAWG-Tmpl-01.dwt +++ b/Templates/BAWG-Tmpl-01.dwt @@ -95,14 +95,14 @@

        6. Images ([Baseline Name linked to URL])

        Meaningful Images (Test Case Heading)

        -
        Test Instructions
        +
        00.0 Test Procedure for Form Name
        <If the image is meaningful...> -
        Test Results
        +
        Test Results
        diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 1de76d1e..3806ba77 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -94,7 +94,7 @@

        Test Case Description

        Applicable ICT Baseline

        05. Changing Content

        Visual and programmatically associated changes in content

        -
        Test Instructions
        +
        5.1 Test Procedure for Changes in Content
        @@ -136,7 +136,7 @@
        4.1.2 Name, Role, Value
      -
      Test Results
      +
      Test Results
      diff --git a/docs/testcases/TC10-001-fail.html b/docs/testcases/TC10-001-fail.html index fa170389..4c1a3697 100644 --- a/docs/testcases/TC10-001-fail.html +++ b/docs/testcases/TC10-001-fail.html @@ -94,26 +94,32 @@

      Test Case Description

      Applicable ICT Baseline

      10. Forms

      Complete and programmatically associated form labels and instructions

      -
      Test Instructions
      +
      10.1 Test Procedure for Form Names
      -
      4.1.2 Name, Role, Value and 1.3.1 Info and Relationships
      -
        -
      1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
        2. -
      2. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: - +
        3. +
      -
      Test Results
      +
      Test Results
      diff --git a/docs/testcases/TC10-008-dna.html b/docs/testcases/TC10-008-dna.html index b19231be..7197fb73 100644 --- a/docs/testcases/TC10-008-dna.html +++ b/docs/testcases/TC10-008-dna.html @@ -97,28 +97,32 @@

      Test Case Description

      Applicable ICT Baseline

      10. Forms

      Complete and programmatically associated form labels and instructions

      -
      Test Instructions
      +
      10.1 Test Procedure for Form Names
      -
      4.1.2 Name, Role, Value and 1.3.1 Info and Relationships
      -
        -
      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
        2. -
      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.
        3. -
      3. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
        4. -
      4. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: - -
        5. -
      +

      Baseline Test ID: 10.1-FormName

      +
      Identify Content
      +
        +
      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
        2. +
      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.
        3. +
      +
      Test Instructions
      +
        +
      1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
        2. +
      2. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: + +
        3. +
      -
      Test Results
      +
      Test Results
      diff --git a/docs/testcases/TC10-009-dna.html b/docs/testcases/TC10-009-dna.html index c19dbb26..a9dbffe3 100644 --- a/docs/testcases/TC10-009-dna.html +++ b/docs/testcases/TC10-009-dna.html @@ -97,28 +97,32 @@

      Test Case Description

      Applicable ICT Baseline

      10. Forms

      Complete and programmatically associated form labels and instructions

      -
      Test Instructions
      +
      10.1 Test Procedure for Form Names
      -
      4.1.2 Name, Role, Value and 1.3.1 Info and Relationships
      -
        -
      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
        2. -
      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.
        3. -
      3. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
        4. -
      4. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: - -
        5. -
      +

      Baseline Test ID: 10.1-FormName

      +
      Identify Content
      +
        +
      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
        2. +
      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.
        3. +
      +
      Test Instructions
      +
        +
      1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
        2. +
      2. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: + +
        3. +
      -
      Test Results
      +
      Test Results
      From b3cbafbd8985632fb6ade5eb361281b738466a97 Mon Sep 17 00:00:00 2001 From: Alan King Date: Thu, 27 Aug 2020 17:57:05 -0400 Subject: [PATCH 11/21] update test file 05-001.html --- docs/testfiles/TF05/05-001.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/testfiles/TF05/05-001.html b/docs/testfiles/TF05/05-001.html index 56f087b9..3621549a 100644 --- a/docs/testfiles/TF05/05-001.html +++ b/docs/testfiles/TF05/05-001.html @@ -23,7 +23,7 @@ fieldset { border: 2px solid #CCA383; - width: 275px; + width: 250px; padding-left:15px; } From 7e8d7ebb5cc99b6ee278256bde9346d68d1af1e3 Mon Sep 17 00:00:00 2001 From: Alan King Date: Sun, 30 Aug 2020 00:39:56 -0400 Subject: [PATCH 12/21] Updated Dreamweaver template --- Templates/BAWG-Tmpl-01.dwt | 53 +++++++++++++++++++++++++------------- 1 file changed, 35 insertions(+), 18 deletions(-) diff --git a/Templates/BAWG-Tmpl-01.dwt b/Templates/BAWG-Tmpl-01.dwt index bc200ece..62d79dc6 100644 --- a/Templates/BAWG-Tmpl-01.dwt +++ b/Templates/BAWG-Tmpl-01.dwt @@ -85,34 +85,51 @@
      -

      Test Case Title

      +

      Image - text equivalent in alt attribute

      Test Case Summary

      Test Case ID

      TC05-001-fail ([ParentBaseline-IncrementalTC#-Pass/Fail/DNA])

      Test Case Description

      [Brief description of the code sample/issue to be tested. Include and detail about why this specific test case is necessary] - here is wehre we need to provide very specific guidance on description and intent.

      Applicable ICT Baseline

      -

      6. Images ([Baseline Name linked to URL])

      -

      - Meaningful Images (Test Case Heading)

      -
      00.0 Test Procedure for Form Name
      - - - - <If the image is meaningful...> - +

      6.1 Test Procedure for Meaningful Images
      + Baseline Test ID: 6.1-MeaningfulImage

      + + +

      Identify Content

      + Identify any image that conveys information (include images of text; functional images used to initiate action, convey meaning, or prompting a response; image maps, etc.). -
      Test Results
      + +

      Test Instructions

      - - -
        -
      • <If any of the above checks fail...>
        • -
      - + + +
        +
      1. Check that the combination of the accessible name and accessible description is not empty. [SC 1.1.1]
        2. +
      2. Check that the non-empty combination of accessible name and accessible description provides an equivalent description. Numerous attributes contribute to the computation of the accessible name and accessible description. Refer to HTML Accessibility API Mappings 1.0 for img. [SC 1.1.1] +
          +
        1. Descriptions of the image that are provided by page content must be programmatically associated.
          2. +
        2. When an image is updated to convey a new meaning, check that its text alternative is updated at the same time. [SCs 1.1.1 and 4.1.2]
          3. +
        +
        3. +
      3. Check that the ARIA role is NOT “presentation”.
        4. +
      4. Check that the ARIA role is NOT “none”.
        5. +
      5. Check that aria-hidden is NOT set to “true”.
        6. +
      + + + +

      Test Results

      + + + +
        +
      • If any of the above checks fail, then Baseline Test 6.1-MeaningfulImage fails results
      + + -

      Applicable WCAG/508 Requirement

      +

      Applicable WCAG/508 Requirement

      • From b1082ba92ff23973196a17b1262369c1382d698b Mon Sep 17 00:00:00 2001 From: Alan King Date: Sun, 30 Aug 2020 00:43:02 -0400 Subject: [PATCH 13/21] Updated TC05-001-fail.html to mirror baseline format --- docs/testcases/TC05-001-fail.html | 110 ++++++++++++++++-------------- 1 file changed, 58 insertions(+), 52 deletions(-) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 3806ba77..1b8e8e01 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -92,61 +92,67 @@

        Test Case ID

        Test Case Description

        The aria-live politeness setting is used to set the priority with which screen readers should announce updates to designated live regions. The options are off, polite and assertive. With the exceptions of the ARIA roles of alert, log, and status (with default option settings of assertive, polite, and polite respectively), the default aria-live option is off. For any live region meant to convey meaningful information to assistive technology, the off setting, being the same as the omission of the live region altogether, would represent a failure of accessibility. The code sample presents aria-live='off'. A successful test should identify a failure against Baseline Test 5.1-ChangeContent.

        Applicable ICT Baseline

        -

        05. Changing Content

        -

        Visual and programmatically associated changes in content

        -
        5.1 Test Procedure for Changes in Content
        - - - -

        Baseline Test ID: 5.1-ChangeContent

        - -
        Identify Content
        -

        Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc.

        -
          -
        • It may be necessary to use the mouse to determine whether state changes occur on hover or on click.
          • -
        • Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.
          • -
        -
        4.1.2 Name, Role, Value
        -
          -
        1. Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] -
            -
          1. Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
            2. -
          -
          2. -
        2. For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] -
            -
          1. Name: the name is accurate after a change. - -
            2. -
          2. Role: the role accurately describes the purpose of the element after a change, if applicable. -
              -
            • Consider ARIA role, element type, and other descriptive text.
              • -
            -
            3. -
          3. State: the state of the element is accurate after a change, if applicable -
              -
            • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
              • -
            -
            4. -
          4. Value: the value is updated after a change, if applicable.
            5. -
          -
          3. -
        - +

        5.1 Test Procedure for Changes in Content
        +
        + Baseline Test ID: 5.1-ChangeContent
        +

        + + +

        Identify Content

        + +

        Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc.

        +
          +
        • It may be necessary to use the mouse to determine whether state changes occur on hover or on click.
          • +
        • Depending on the component, a change of state may be triggered by various actions, such as changing values or states of other components, toggling a function, entering data in the component, mouseover, etc.
          • +
        + -
        Test Results
        + +

        Test Instructions

        - - -
          -
        • If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.
          • -
        - + + +
          +
        1. Check that the page provides a notification of the change in content programmatically. [SC 4.1.2] +
            +
          • Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.
            • +
          +
          2. +
        2. For each change in content, check that the combination of name, role, state, and value of the changed content is accurate. [SC 4.1.2] +
            +
          • Name: the name is accurate after a change. + +
            • +
          • Role: the role accurately describes the purpose of the element after a change, if applicable. +
              +
            • Consider ARIA role, element type, and other descriptive text.
              • +
            +
            • +
          • State: the state of the element is accurate after a change, if applicable +
              +
            • Evaluate ARIA and element-specific attributes (e.g., <option selected=”true”>)
              • +
            +
            • +
          • Value: the value is updated after a change, if applicable.
            • +
          +
          3. +
        + + + +

        Test Results

        + + + +
          +
        • If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.
        + + -

        Applicable WCAG/508 Requirement

        +

        Applicable WCAG/508 Requirement

        • WCAG2 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
          • @@ -167,7 +173,7 @@

          Expected Baseline Result

          - Fail + FAIL

          From cd775fadac3b12dcad46906c48f647b2c1a4421c Mon Sep 17 00:00:00 2001 From: Alan King Date: Sun, 30 Aug 2020 00:44:18 -0400 Subject: [PATCH 14/21] Updated TC10-001-fail.html to mirror baseline format --- docs/testcases/TC10-001-fail.html | 60 ++++++++++++++++--------------- 1 file changed, 32 insertions(+), 28 deletions(-) diff --git a/docs/testcases/TC10-001-fail.html b/docs/testcases/TC10-001-fail.html index 4c1a3697..9cf38e1d 100644 --- a/docs/testcases/TC10-001-fail.html +++ b/docs/testcases/TC10-001-fail.html @@ -92,44 +92,48 @@

          Test Case ID

          Test Case Description

          Detect attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative for the input element. The code sample data does not include attributes that contribute to accessible name or accessible description output. A successful test should identify a failure against Baseline Test 10.1 FormName.

          Applicable ICT Baseline

          -

          10. Forms

          -

          Complete and programmatically associated form labels and instructions

          -
          10.1 Test Procedure for Form Names
          - - - -

          Baseline Test ID: 10.1-FormName

          -
          Identify Content
          -
            -
          1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
            2. -
          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.
            3. -
          -
          Test Instructions
          +

          10.1 Test Procedure for Form Names
          +
          + Baseline Test ID:           10.1-FormName

          + + +

          Identify Content

          + +
            +
          1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
            2. +
          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.
            3. +
          + + + +

          Test Instructions

          + + +
          1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
          2. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include:
          - - -
          Test Results
          - - - -
            -
          • If any of the above checks fail, then SC 1.3.1, SC 4.1.2, and Baseline Requirement 10 fail.
            • -
          - + + + +

          Test Results

          + + + If any of the above checks fail, then Baseline Test 10.1-FormName fails. + + -

          Applicable WCAG/508 Requirement

          +

          Applicable WCAG/508 Requirement

          • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
            • @@ -151,7 +155,7 @@

            Expected Baseline Result

            - Fail + FAIL

            From f6f6d300facb32b8425376fcd94e4bde31baf5e8 Mon Sep 17 00:00:00 2001 From: Alan King Date: Sun, 30 Aug 2020 00:45:38 -0400 Subject: [PATCH 15/21] Updated TC10-008-dna.html to mirror baseline format --- docs/testcases/TC10-008-dna.html | 55 +++++++++++++++++--------------- 1 file changed, 29 insertions(+), 26 deletions(-) diff --git a/docs/testcases/TC10-008-dna.html b/docs/testcases/TC10-008-dna.html index 7197fb73..31a8a482 100644 --- a/docs/testcases/TC10-008-dna.html +++ b/docs/testcases/TC10-008-dna.html @@ -95,19 +95,24 @@

            Test Case Description


            Note: If the intent of the developer is to make the input element available to users as a part of meaningful ICT functionality, then the CSS property visibility:hidden should not be used with interactive elements.

            Applicable ICT Baseline

            -

            10. Forms

            -

            Complete and programmatically associated form labels and instructions

            -
            10.1 Test Procedure for Form Names
            - - - -

            Baseline Test ID: 10.1-FormName

            -
            Identify Content
            -
              -
            1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
              2. -
            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.
              3. -
            -
            Test Instructions
            +

            10.1 Test Procedure for Form Names
            +
            + Baseline Test ID: 10.1-FormName

            + + +

            Identify Content

            + +
              +
            1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
              2. +
            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.
              3. +
            + + + +

            Test Instructions

            + + +
            1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
            2. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: @@ -116,24 +121,22 @@
              Test Instructions
            3. HTML Accessibility API Mappings for input controls
            4. HTML Accessibility API Mappings for button element 
            5. HTML Accessibility API Mappings for input type="image"
              6. -
            6. HTML Accessibility API Mappings for Other Form Elements
              7. +
            7. HTML Accessibility API Mappings for Other Form Elements
    - - -
    Test Results
    - - - -
      -
    • If any of the above checks fail, then SC 1.3.1, SC 4.1.2, and Baseline Requirement 10 fail.
      • -
    • If there is no such content, then the result for the Baseline Test 10. Forms is DOES NOT APPLY (DNA)
      • -
    - + + + +

    Test Results

    + + + If any of the above checks fail, then Baseline Test 10.1-FormName fails. + + -

    Applicable WCAG/508 Requirement

    +

    Applicable WCAG/508 Requirement

    • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
      • From 578b055d4a4a8638214f1d04213864dc7edef0f5 Mon Sep 17 00:00:00 2001 From: Alan King Date: Sun, 30 Aug 2020 00:46:22 -0400 Subject: [PATCH 16/21] Updated TC10-009-dna.html to mirror baseline format --- docs/testcases/TC10-009-dna.html | 53 +++++++++++++++++--------------- 1 file changed, 28 insertions(+), 25 deletions(-) diff --git a/docs/testcases/TC10-009-dna.html b/docs/testcases/TC10-009-dna.html index a9dbffe3..f06f4590 100644 --- a/docs/testcases/TC10-009-dna.html +++ b/docs/testcases/TC10-009-dna.html @@ -95,19 +95,24 @@

      Test Case Description


      Note: If the intent of the developer is to make the input element available to users as a part of meaningful ICT functionality, then the CSS property display:none should not be used with interactive elements.

      Applicable ICT Baseline

      -

      10. Forms

      -

      Complete and programmatically associated form labels and instructions

      -
      10.1 Test Procedure for Form Names
      - - - -

      Baseline Test ID: 10.1-FormName

      -
      Identify Content
      -
        -
      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
        2. -
      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.
        3. -
      -
      Test Instructions
      +

      10.1 Test Procedure for Form Names
      +
      + Baseline Test ID: 10.1-FormName

      + + +

      Identify Content

      + +
        +
      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
        2. +
      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.
        3. +
      + + + +

      Test Instructions

      + + +
      1. Check that the combination of the accessible name and accessible description is not empty. [SC 4.1.2]
      2. Check that the non-empty combination of the accessible name and accessible description and other programmatic associations (e.g., table column and/or row associations) describes each form component and includes all relevant instructions and cues (textual and graphical). [SC 1.3.1] For details on the computation of the accessible name and accessible description, references include: @@ -120,20 +125,18 @@
        Test Instructions
    - - -
    Test Results
    - - - -
      -
    • If any of the above checks fail, then SC 1.3.1, SC 4.1.2, and Baseline Requirement 10 fail.
      • -
    • If there is no such content, then the result for the Baseline Test 10. Forms is DOES NOT APPLY (DNA)
      • -
    - + + + +

    Test Results

    + + + If any of the above checks fail, then Baseline Test 10.1-FormName fails. + + -

    Applicable WCAG/508 Requirement

    +

    Applicable WCAG/508 Requirement

    • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
      • From 9a7ccfeddcd551184f94c9e1e96ad8709526718d Mon Sep 17 00:00:00 2001 From: Alan King Date: Mon, 31 Aug 2020 16:46:29 -0400 Subject: [PATCH 17/21] Updated testCaseTemplate.html to match new Baseline format --- docs/testCaseTemplate.html | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/docs/testCaseTemplate.html b/docs/testCaseTemplate.html index 350355d0..e88b9ff0 100644 --- a/docs/testCaseTemplate.html +++ b/docs/testCaseTemplate.html @@ -81,8 +81,14 @@

      Test Case ID

      Test Case Description

      [Brief description of the code sample/issue to be tested. Include and detail about why this specific test case is necessary] - here is wehre we need to provide very specific guidance on description and intent

      Applicable ICT Baseline

      -

      [Baseline Name linked to URL]

      -

      [Baseline text with how to test]

      +

      [Baseline Test Procedure Statement linked to URL (6.1 Test Procedure for Meaningful Images) ]

      +

      [Baseline Test ID (Baseline Test ID: 6.1-MeaningfulImage) ]

      +

      Identify Content

      +

      [Baseline steps for identifying content]

      +

      Test Instructions

      +

      [Baseline steps describing test instructions]

      +

      Test Results

      +

      [Test results (If any of the above checks fail, then Baseline Test 6.1-MeaningfulImage fails)]

      Applicable WCAG/508 Requirement

      [WCAG/508 Req linked to URL]

      [WCAG SC/508 Req text]

      From b1e14b42560a01c9bd00bdd4327f307906eda730 Mon Sep 17 00:00:00 2001 From: Alan King Date: Mon, 31 Aug 2020 16:55:43 -0400 Subject: [PATCH 18/21] Updated testcases.html to add case TC05-001-fail to index --- docs/testcases.html | 36 ++++++++++++++++++++---------------- 1 file changed, 20 insertions(+), 16 deletions(-) diff --git a/docs/testcases.html b/docs/testcases.html index 21e3d720..2e2b7bbc 100644 --- a/docs/testcases.html +++ b/docs/testcases.html @@ -76,22 +76,26 @@

      Placeholder Index

      Test Case documents are organized by Baseline Test (each seving as a Test Scenario or general "functional requirement" for testing), which inculde multiple Test Cases. Will need to develop a Test Scenario template to summarize Test Scenario purpose and subordinate Test Cases.

        -
      • - 6. Images - +
      • 5. Changing Content + +
        • +
      • 6. Images +
      • 10. Forms
          From f843d7280b6eb5dd81a0dd4c4d4b298a87f0092d Mon Sep 17 00:00:00 2001 From: Alan King Date: Mon, 7 Sep 2020 21:09:53 -0400 Subject: [PATCH 19/21] Updating both test case template files to reflect internal hyperlink IDs for test-instructions and identify-content sections of template --- Templates/BAWG-Tmpl-01.dwt | 4 ++-- docs/testCaseTemplate.html | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Templates/BAWG-Tmpl-01.dwt b/Templates/BAWG-Tmpl-01.dwt index 62d79dc6..583ccaf7 100644 --- a/Templates/BAWG-Tmpl-01.dwt +++ b/Templates/BAWG-Tmpl-01.dwt @@ -96,11 +96,11 @@ Baseline Test ID: 6.1-MeaningfulImage

          -

          Identify Content

          +

          Identify Content

          Identify any image that conveys information (include images of text; functional images used to initiate action, convey meaning, or prompting a response; image maps, etc.). -

          Test Instructions

          +

          Test Instructions

          diff --git a/docs/testCaseTemplate.html b/docs/testCaseTemplate.html index e88b9ff0..c92c05a7 100644 --- a/docs/testCaseTemplate.html +++ b/docs/testCaseTemplate.html @@ -83,7 +83,7 @@

          Test Case Description

          Applicable ICT Baseline

          [Baseline Test Procedure Statement linked to URL (6.1 Test Procedure for Meaningful Images) ]

          [Baseline Test ID (Baseline Test ID: 6.1-MeaningfulImage) ]

          -

          Identify Content

          +

          Identify Content

          [Baseline steps for identifying content]

          Test Instructions

          [Baseline steps describing test instructions]

          From 27a2cd0b90f20067c14b9ab48e909dabb17dca4a Mon Sep 17 00:00:00 2001 From: Alan King Date: Mon, 7 Sep 2020 21:18:56 -0400 Subject: [PATCH 20/21] Updated test cases (TC5-001-fail, TC10-001-fail, TC10-008-dna, TC10-0090-dna) to point to internal hyperlinks of test-instructions or identify-content, in the Test Steps section of test case respectively. --- docs/testcases/TC05-001-fail.html | 10 +++++----- docs/testcases/TC10-001-fail.html | 10 +++++----- docs/testcases/TC10-008-dna.html | 16 ++++++++-------- docs/testcases/TC10-009-dna.html | 12 ++++++------ 4 files changed, 24 insertions(+), 24 deletions(-) diff --git a/docs/testcases/TC05-001-fail.html b/docs/testcases/TC05-001-fail.html index 1b8e8e01..2b633ada 100644 --- a/docs/testcases/TC05-001-fail.html +++ b/docs/testcases/TC05-001-fail.html @@ -99,7 +99,7 @@

          Applicable ICT Baseline

          Identify Content

          - +

          Identify changes in presented content (both user driven and automatic). Examples include changes to images, navigation trees, data table sort controls, automatic information updates, form elements, revealed content, etc.

          • It may be necessary to use the mouse to determine whether state changes occur on hover or on click.
            • @@ -108,7 +108,7 @@

            Identify Content

            -

            Test Instructions

            +

            Test Instructions

            @@ -152,7 +152,7 @@

            Test Results

            -

            Applicable WCAG/508 Requirement

            +

            Applicable WCAG/508 Requirement

            • WCAG2 4.1.2 Name, Role, Value: For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
              • @@ -267,8 +267,8 @@

              Test Steps

              5 - If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails. - Test step 3 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test 5.1-ChangeContent fails. + Determine whether any checks fail according to the 5.1 Test Procedure for Changes in Content test instructions. + This test fails due to the absence of the text change being conveyed programmatically and therefore Baseline Test ID 5.1-ChangeContent fails. diff --git a/docs/testcases/TC10-001-fail.html b/docs/testcases/TC10-001-fail.html index 9cf38e1d..4809a0f0 100644 --- a/docs/testcases/TC10-001-fail.html +++ b/docs/testcases/TC10-001-fail.html @@ -98,7 +98,7 @@

              Applicable ICT Baseline

              Identify Content

              - +
              1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
              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.
                3. @@ -106,7 +106,7 @@

                Identify Content

                -

                Test Instructions

                +

                Test Instructions

                @@ -133,7 +133,7 @@

                Test Results

                -

                Applicable WCAG/508 Requirement

                +

                Applicable WCAG/508 Requirement

                • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
                  • @@ -218,8 +218,8 @@

                  Test Steps

                  4 - If any of the above checks fail, then Baseline Test 10.1-FormName fails. - Test step 3 fails due to an empty accessible name and/or description in the text alternative computation output and therefore Baseline Test 10.1-FormName fails. + Determine whether any checks fail according to the 10.1 Test Procedure for Form Names test instructions. + This test fails due to an empty accessible name and/or description in the text alternative computation output and therefore Baseline Test 10.1-FormName fails. diff --git a/docs/testcases/TC10-008-dna.html b/docs/testcases/TC10-008-dna.html index 31a8a482..1c84487a 100644 --- a/docs/testcases/TC10-008-dna.html +++ b/docs/testcases/TC10-008-dna.html @@ -100,8 +100,8 @@

                  Applicable ICT Baseline

                  Baseline Test ID: 10.1-FormName

                  -

                  Identify Content

                  - +

                  Identify Content

                  +
                  1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
                  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.
                    3. @@ -109,7 +109,7 @@

                    Identify Content

                    -

                    Test Instructions

                    +

                    Test Instructions

                    @@ -136,7 +136,7 @@

                    Test Results

                    -

                    Applicable WCAG/508 Requirement

                    +

                    Applicable WCAG/508 Requirement

                    • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
                      • @@ -207,10 +207,10 @@

                      Test Steps

                      - 1 - Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists. - The single input element in this test case is enclosed in the visibility:hidden CSS property which removes it from the accessibility tree, visible, and programmatic detection. Even though the code exists in the DOM, this property renders the element undetectable and therefore not applicable to this Baseline Test based on the results of test step 1. - + 1 + Determine whether this test applies according to the 10.1 Test Procedure for Form Names identify content instructions. + The single input element in this test case is enclosed in the visibility:hidden CSS property which removes it from the accessibility tree, visible, and programmatic detection. Even though the code exists in the DOM, this property renders the element undetectable and therefore not applicable to this Baseline Test. + diff --git a/docs/testcases/TC10-009-dna.html b/docs/testcases/TC10-009-dna.html index f06f4590..d7b1a81e 100644 --- a/docs/testcases/TC10-009-dna.html +++ b/docs/testcases/TC10-009-dna.html @@ -100,8 +100,8 @@

                      Applicable ICT Baseline

                      Baseline Test ID: 10.1-FormName

                      -

                      Identify Content

                      - +

                      Identify Content

                      +
                      1. Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists.
                      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.
                        3. @@ -109,7 +109,7 @@

                        Identify Content

                        -

                        Test Instructions

                        +

                        Test Instructions

                        @@ -136,7 +136,7 @@

                        Test Results

                        -

                        Applicable WCAG/508 Requirement

                        +

                        Applicable WCAG/508 Requirement

                        • WCAG2 1.3.1 Info and Relationships: Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text.
                          • @@ -208,8 +208,8 @@

                          Test Steps

                          1 - Find all form components. Examples include buttons, text fields, radio buttons, checkboxes, read-only fields, and multi-select lists. - The single input element in this test case is enclosed in the display:none CSS property which removes it from the accessibility tree, visible, and programmatic detection. Even though the code exists in the DOM, this property renders the element undetectable and therefore not applicable to this Baseline Test based on the results of test step 1. + Determine whether this test applies according to the 10.1 Test Procedure for Form Names identify content instructions. + The single input element in this test case is enclosed in the display:none CSS property which removes it from the accessibility tree, visible, and programmatic detection. Even though the code exists in the DOM, this property renders the element undetectable and therefore not applicable to this Baseline Test. From ac21bcacca97ffff23af4c0005a74bdcd8ede362 Mon Sep 17 00:00:00 2001 From: Alan King Date: Mon, 7 Sep 2020 21:26:36 -0400 Subject: [PATCH 21/21] Reconciling conflict for the testcases.html file within the akingkci-test-cases branch. --- docs/testcases.html | 15 --------------- 1 file changed, 15 deletions(-) diff --git a/docs/testcases.html b/docs/testcases.html index 55798267..e4ade697 100644 --- a/docs/testcases.html +++ b/docs/testcases.html @@ -81,21 +81,6 @@

                          Placeholder Index

                        • TC05-001-fail
                        -
                      3. 6. Images -
                      4. 6. Images