Skip to content

Please review Test Cases related updates #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ghost wants to merge 24 commits into
base: master
Choose a base branch
from
Open

Please review Test Cases related updates #53

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
24 commits
Select commit Hold shift + click to select a range
98cc8ca
New test case: TC05-001-fail and update to TC10-001-fail
Aug 21, 2020
feeaa26
Add new test case TC10-008-dna (visibility:hidden) and update baselin…
Aug 22, 2020
116caa4
Add new test case TC10-009-dna (display:none)
Aug 22, 2020
267faec
Update to test case TC10-001-fail under "Test Instructions" to correc…
Aug 22, 2020
2345eb4
Updated baseline-align.css file to remove redundant background color
Aug 25, 2020
f156fbb
Updated test case TC05-001 (aria-live='off') to address baseline alig…
Aug 25, 2020
58a212a
updated TC05-001-fail to implement new test steps format
Aug 26, 2020
3c05654
Fix bullet in Test Steps table.
Aug 26, 2020
4fa021c
Updates to TC05-001-fail to align "Applicable ICT Baseline" section o…
Aug 26, 2020
c6bcaa9
Updates to Alan's Dreamweaver template, TC05-001-fail, FC10-001-fail,…
Aug 26, 2020
b3cbafb
update test file 05-001.html
Aug 27, 2020
4f1f358
Merge branch 'master' into akingkci-test-cases
drewnielson Aug 28, 2020
7e8d7eb
Updated Dreamweaver template
Aug 30, 2020
b1082ba
Updated TC05-001-fail.html to mirror baseline format
Aug 30, 2020
cd775fa
Updated TC10-001-fail.html to mirror baseline format
Aug 30, 2020
f6f6d30
Updated TC10-008-dna.html to mirror baseline format
Aug 30, 2020
578b055
Updated TC10-009-dna.html to mirror baseline format
Aug 30, 2020
9a7ccfe
Updated testCaseTemplate.html to match new Baseline format
Aug 31, 2020
b1e14b4
Updated testcases.html to add case TC05-001-fail to index
Aug 31, 2020
7040838
Merge branch 'master' into akingkci-test-cases
drewnielson Sep 2, 2020
f843d72
Updating both test case template files to reflect internal hyperlink …
Sep 8, 2020
e3119c9
Merge remote-tracking branch 'origin/akingkci-test-cases' into akingk…
Sep 8, 2020
27a2cd0
Updated test cases (TC5-001-fail, TC10-001-fail, TC10-008-dna, TC10-0…
Sep 8, 2020
ac21bca
Reconciling conflict for the testcases.html file within the akingkci-…
Sep 8, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 35 additions & 18 deletions Templates/BAWG-Tmpl-01.dwt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,34 +85,51 @@
<div class="col-md-9 col-xl-8 py-1 px-1 py-md-2 pl-md-3 offset-md-3 offset-xl-2 order-1">
<div class="card shadow">
<div class="card-body">
<h1 class="card-title" id="TCtitle"><!-- TemplateBeginEditable name="TCtitle" -->Test Case Title<!-- TemplateEndEditable --></h1>
<h1 class="card-title" id="TCtitle"><!-- TemplateBeginEditable name="TCtitle" -->Image - text equivalent in alt attribute<!-- TemplateEndEditable --></h1>
<h2 class="border-bottom" id="TCsum">Test Case Summary</h2>
<h3 id="TCid">Test Case ID</h3>
<p><!-- TemplateBeginEditable name="TCid" -->TC05-001-fail ([ParentBaseline-IncrementalTC#-Pass/Fail/DNA])<!-- TemplateEndEditable --></p>
<h3 id="TCdesc">Test Case Description</h3>
<p><!-- TemplateBeginEditable name="TCdesc" -->[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.<!-- TemplateEndEditable --></p>
<h3 id="TCbase">Applicable ICT Baseline</h3>
<p><!-- TemplateBeginEditable name="TCbaseURL" --> <a href="https://section508coordinators.github.io/ICTTestingBaseline/06Images.html">6. Images</a> ([Baseline Name linked to URL])<!-- TemplateEndEditable --></p>
<h4><!-- TemplateBeginEditable name="TCbaseheading4" -->
Meaningful Images (Test Case Heading)<!-- TemplateEndEditable --></h4>
<h5><!-- TemplateBeginEditable name="TProcedure" -->00.0 Test Procedure for Form Name<!-- TemplateEndEditable --></h5>

<!--Test instructions text: //-->
<!-- TemplateBeginEditable name="TCbasetext" -->
&lt;If the image is meaningful...&gt;
<!-- TemplateEndEditable -->
<p><!-- TemplateBeginEditable name="TCbaseURL" --><a href="https://section508coordinators.github.io/ICTTestingBaseline/06Images.html">6.1 Test Procedure for Meaningful Images</a><br>
<strong>Baseline Test ID:</strong> 6.1-MeaningfulImage<!-- TemplateEndEditable --></p>

<!-- Identify Content Heading //-->
<h4 id="identify-content">Identify Content</h4>
<!-- TemplateBeginEditable name="tcIdentifyContent" -->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.).<!-- TemplateEndEditable -->

<h6>Test Results</h6>
<!--Test Instructions Heading //-->
<h4 id="test-instructions">Test Instructions</h4>

<!--Test results text: //-->
<!-- TemplateBeginEditable name="TCbasetestresults" -->
<ul>
<li>&lt;If any of the above checks fail...&gt;</li>
</ul>
<!-- TemplateEndEditable -->
<!--Test instructions //-->
<!-- TemplateBeginEditable name="tcTestInstructions" -->
<ol>
<li>Check that the combination of the accessible name and accessible description is not empty. [SC 1.1.1]</li>
<li>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 <a href="https://www.w3.org/TR/html-aam-1.0/#img-element">HTML Accessibility API Mappings 1.0 for img</a>. [SC 1.1.1]
<ol>
<li>Descriptions of the image that are provided by page content must be programmatically associated.</li>
<li>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]</li>
</ol>
</li>
<li>Check that the ARIA role is NOT &ldquo;presentation&rdquo;.</li>
<li>Check that the ARIA role is NOT &ldquo;none&rdquo;.</li>
<li>Check that aria-hidden is NOT set to &ldquo;true&rdquo;.</li>
</ol>
<!-- TemplateEndEditable -->

<!--Test Results Heading //-->
<h4>Test Results</h4>


<!--Test results //-->
<!-- TemplateBeginEditable name="tcTestResults" -->
<ul>
<li>If any of the above checks fail, then Baseline Test 6.1-MeaningfulImage fails results</li></ul><!-- TemplateEndEditable -->



<h3 id="TCreq">Applicable WCAG/508 Requirement</h3>
<h3 id="TCreq">Applicable WCAG/508 Requirement</h3>
<!-- TemplateBeginEditable name="TCreqlink" -->
<ul>
<li>
Expand Down
10 changes: 8 additions & 2 deletions docs/testCaseTemplate.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,8 +81,14 @@ <h3 id="TCid">Test Case ID</h3>
<h3 id="TCdesc">Test Case Description</h3>
<p>[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</p>
<h3 id="TCbase">Applicable ICT Baseline</h3>
<p>[Baseline Name linked to URL]</p>
<p>[Baseline text with how to test]</p>
<p>[Baseline Test Procedure Statement linked to URL (<a href="https://section508coordinators.github.io/ICTTestingBaseline/06Images.html#61-test-procedure-for-meaningful-images">6.1 Test Procedure for Meaningful Images</a>) ] </p>
<p>[Baseline Test ID (<strong>Baseline Test ID:</strong> 6.1-MeaningfulImage) ]</p>
<h4 id="identify-content">Identify Content</h4>
<p>[Baseline steps for identifying content]</p>
<h4 id="test-instructions">Test Instructions</h4>
<p>[Baseline steps describing test instructions]</p>
<h4>Test Results</h4>
<p>[Test results (If any of the above checks fail, then Baseline Test 6.1-MeaningfulImage fails)]</p>
<h3 id="TCreq">Applicable WCAG/508 Requirement</h3>
<p>[WCAG/508 Req linked to URL]</p>
<p>[WCAG SC/508 Req text]</p>
Expand Down
5 changes: 5 additions & 0 deletions docs/testcases.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,11 @@ <h2 id="purpose">Placeholder Index</h2>
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.
</p>
<ul>
<li>5. Changing Content
<ul>
<li><a href="testcases/TC05-001-fail.html">TC05-001-fail</a> </li>
</ul>
</li>
<li>
6. Images
<ul>
Copy link
Author

@ghost ghost Sep 8, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed the duplicate unordered list items from this file in this branch.

Expand Down
114 changes: 60 additions & 54 deletions docs/testcases/TC05-001-fail.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,61 +92,67 @@ <h3 id="TCid">Test Case ID</h3>
<h3 id="TCdesc">Test Case Description</h3>
<p><!-- InstanceBeginEditable name="TCdesc" --> 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.<!-- InstanceEndEditable --></p>
<h3 id="TCbase">Applicable ICT Baseline</h3>
<p><!-- InstanceBeginEditable name="TCbaseURL" --> <a href="https://section508coordinators.github.io/ICTTestingBaseline/05Changing.html">05. Changing Content</a><!-- InstanceEndEditable --></p>
<h4><!-- InstanceBeginEditable name="TCbaseheading4" -->Visual and programmatically associated changes in content<!-- InstanceEndEditable --></h4>
<h5><!-- InstanceBeginEditable name="TProcedure" -->5.1 Test Procedure for Changes in Content<!-- InstanceEndEditable --></h5>

<!--Test instructions text: //-->
<!-- InstanceBeginEditable name="TCbasetext" -->
<p><strong>Baseline Test ID:</strong> 5.1-ChangeContent</p>

<h6>Identify Content</h6>
<p>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.</p>
<ul>
<li>It may be necessary to use the mouse to determine whether state changes occur on hover or on click.</li>
<li>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. </li>
</ul>
<h6>4.1.2 Name, Role, Value </h6>
<ol>
<li>Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]
<ol>
<li>Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.</li>
</ol>
</li>
<li>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]
<ol>
<li>Name: the name is accurate after a change.
<ul>
<li>Apply the <a href="https://www.w3.org/TR/html-aam-1.0/#accessible-name-and-description-computation">accessible name and description computation</a>, if applicable. </li>
</ul>
</li>
<li>Role: the role accurately describes the purpose of the element after a change, if applicable.
<ul>
<li>Consider ARIA role, element type, and other descriptive text. </li>
</ul>
</li>
<li>State: the state of the element is accurate after a change, if applicable
<ul>
<li>Evaluate ARIA and element-specific attributes (e.g., <code class="code">&lt;option selected=&rdquo;true&rdquo;&gt;</code>)</li>
</ul>
</li>
<li>Value: the value is updated after a change, if applicable.</li>
</ol>
</li>
</ol>
<!-- InstanceEndEditable -->
<p><!-- InstanceBeginEditable name="TCbaseURL" --> <a href="https://section508coordinators.github.io/ICTTestingBaseline/05Changing.html">5.1 Test Procedure for Changes in Content</a><br>
<br>
<strong>Baseline Test ID:</strong> 5.1-ChangeContent<br>
<!-- InstanceEndEditable --></p>

<!-- Identify Content Heading //-->
<h4>Identify Content</h4>
<!-- InstanceBeginEditable name="tcIdentifyContent" -->
<p>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.</p>
<ul>
<li>It may be necessary to use the mouse to determine whether state changes occur on hover or on click.</li>
<li>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. </li>
</ul>
<!-- InstanceEndEditable -->

<h6>Test Results</h6>
<!--Test Instructions Heading //-->
<h4 id="test-instructions">Test Instructions</h4>

<!--Test results text: //-->
<!-- InstanceBeginEditable name="TCbasetestresults" -->
<ul>
<li>If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.</li>
</ul>
<!-- InstanceEndEditable -->
<!--Test instructions //-->
<!-- InstanceBeginEditable name="tcTestInstructions" -->
<ol>
<li>Check that the page provides a notification of the change in content programmatically. [SC 4.1.2]
<ul>
<li>Programmatic event notifications include alert dialogs, focus shifts to the content that changed, and ARIA live regions.</li>
</ul>
</li>
<li>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]
<ul>
<li>Name: the name is accurate after a change.
<ul>
<li>Apply the <a href="https://www.w3.org/TR/html-aam-1.0/#accessible-name-and-description-computation">accessible name and description computation</a>, if applicable.</li>
</ul>
</li>
<li>Role: the role accurately describes the purpose of the element after a change, if applicable.
<ul>
<li>Consider ARIA role, element type, and other descriptive text.</li>
</ul>
</li>
<li>State: the state of the element is accurate after a change, if applicable
<ul>
<li>Evaluate ARIA and element-specific attributes (e.g., <code class="code">&lt;option selected=&rdquo;true&rdquo;&gt;</code>)</li>
</ul>
</li>
<li>Value: the value is updated after a change, if applicable.</li>
</ul>
</li>
</ol>
<!-- InstanceEndEditable -->

<!--Test Results Heading //-->
<h4>Test Results</h4>


<!--Test results //-->
<!-- InstanceBeginEditable name="tcTestResults" -->
<ul>
<li>If any of the above checks fail, then Baseline Test 5.1-ChangeContent fails.</li></ul><!-- InstanceEndEditable -->



<h3 id="TCreq">Applicable WCAG/508 Requirement</h3>
<h3 id="TCreq">Applicable WCAG/508 Requirement</h3>
<!-- InstanceBeginEditable name="TCreqlink" -->
<ul>
<li><a href="https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html">WCAG2 4.1.2 Name, Role, Value</a>: 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.</li>
Expand All @@ -167,7 +173,7 @@ <h3 id="TCresult">Expected Baseline Result</h3>

<p><strong>
<!-- InstanceBeginEditable name="Pass-Fail-DNA" -->
Fail
FAIL
<!-- InstanceEndEditable -->
</strong></p>

Expand Down Expand Up @@ -261,8 +267,8 @@ <h2 id="TCsteps">Test Steps</h2>
</tr>
<tr>
<td>5</td>
<td headers = "th_content th_detail rn2">If any of the above checks fail, then Baseline Test <strong>5.1-ChangeContent</strong> fails.</td>
<td headers = "th_content th_result rn2">Test step 3 fails due to the absence of the text change being conveyed programmatically in any way and therefore Baseline Test <strong>5.1-ChangeContent</strong> fails.</td>
<td headers = "th_content th_detail rn2">Determine whether any checks fail according to the <a href="#test-instructions">5.1 Test Procedure for Changes in Content test instructions</a>. </td>
<td headers = "th_content th_result rn2">This test fails due to the absence of the text change being conveyed programmatically and therefore Baseline Test ID <strong>5.1-ChangeContent</strong> fails.</td>
</tr>
</tbody>
</table>
Expand Down
Loading