From 7ec6f157aceb9af378542f799661ca417ab7db36 Mon Sep 17 00:00:00 2001 From: Andrew Nielson <29068131+drewnielson@users.noreply.github.com> Date: Fri, 22 May 2020 13:59:08 -0400 Subject: [PATCH 1/5] Minor changes in index and previous test cases. Added test case index placeholder. Added two new test cases. --- docs/index.html | 181 +++++----- docs/testcases.html | 112 ++++++ docs/testcases/TC06-001-fail.html | 296 ++++++++-------- docs/testcases/TC06-002-pass.html | 320 +++++++++--------- docs/testcases/TC06-003-pass.html | 195 +++++++++++ docs/testcases/TC06-004-pass.html | 195 +++++++++++ docs/testfiles/TC06-002-pass/06-002-pass.html | 3 +- docs/testfiles/TC06-003-pass/06-003-pass.html | 12 + docs/testfiles/TC06-004-pass/06-004-pass.html | 12 + 9 files changed, 930 insertions(+), 396 deletions(-) create mode 100644 docs/testcases.html create mode 100644 docs/testcases/TC06-003-pass.html create mode 100644 docs/testcases/TC06-004-pass.html create mode 100644 docs/testfiles/TC06-003-pass/06-003-pass.html create mode 100644 docs/testfiles/TC06-004-pass/06-004-pass.html diff --git a/docs/index.html b/docs/index.html index 6040bb86..8c52d1cc 100644 --- a/docs/index.html +++ b/docs/index.html @@ -3,100 +3,103 @@ + ICT Testing Baseline Alignment Home - + - - - - + + + + -
- - - - - ICT Accessibility Testing Baseline Alignment -
- - - - - - -
- - - - - - -
-
-
-
-
-

ICT Baseline Alignment Framework

-

Purpose and Objectives

-

GSA's Government-wide IT Accessibility program is encouraging adoption of the Baseline more broadly across government. To facilitate adoption of the Baseline, we must create a process and framework for validating alignment of individual test processes (including testing tools) to the Baseline. The Trusted Tester process is one prime example of a test process that aligns to the Baseline. A Baseline Alignment Validation Framework will make it possible for more agencies to demonstrate alignment of their test processes (whether they subscribe to Trusted Tester or other methods) while providing broader flexibility in the selection of testing tools and contributing test methods. In the end, the more agencies that demonstrate alignment to the Baseline, the more we can share testing results and reduce redundancy in our accessibility testing and market research efforts.

-
-
-
-
-

How to contribute

-

Some basic info, then link to the "Contributing" detailed guidance.

-
-
-
-
-

How to validate alignment to the ICT Baseline

-

Some basic info, then link to the "Validating Alignment" detailed guidance.

-
-
-
-
-
- - - - - - - + +
+ + + + + ICT Accessibility Testing Baseline Alignment +
+ + + + + + +
+ + + + + + +
+
+
+
+
+

ICT Baseline Alignment Framework

+

Purpose and Objectives

+

GSA's Government-wide IT Accessibility program is encouraging adoption of the Baseline more broadly across government. To facilitate adoption of the Baseline, we must create a process and framework for validating alignment of individual test processes (including testing tools) to the Baseline. The Trusted Tester process is one prime example of a test process that aligns to the Baseline. A Baseline Alignment Validation Framework will make it possible for more agencies to demonstrate alignment of their test processes (whether they subscribe to Trusted Tester or other methods) while providing broader flexibility in the selection of testing tools and contributing test methods. In the end, the more agencies that demonstrate alignment to the Baseline, the more we can share testing results and reduce redundancy in our accessibility testing and market research efforts.

+
+
+
+
+

How to contribute

+

Some basic info, then link to the "Contributing" detailed guidance.

+
+
+
+
+

How to validate alignment to the ICT Baseline

+

Some basic info, then link to the "Validating Alignment" detailed guidance.

+
+
+
+
+
+ + + + + + + + - \ No newline at end of file + diff --git a/docs/testcases.html b/docs/testcases.html new file mode 100644 index 00000000..2b72c903 --- /dev/null +++ b/docs/testcases.html @@ -0,0 +1,112 @@ + + + + + + Test Case Index + + + + + + + + + + + + +
+ + + + + ICT Accessibility Testing Baseline Alignment +
+ + + + + + +
+ + + + + + +
+
+
+
+
+

ICT Baseline Alignment Framework

+

Placeholder Index

+

+ Until we modify the primary index file, this serves as a placeholder with links to current test case documents.

+

+ Test case documents are organized by Test Scenarios (aligned directly to Baseline Tests), which inculde multiple Test Cases. Will need to develop a Test Scenario template to summarize Test Scenario purpose and subordinate Test Cases. +

+ +
+
+
+
+
+ + + + + + + + + + diff --git a/docs/testcases/TC06-001-fail.html b/docs/testcases/TC06-001-fail.html index be7719c0..f8b1c9f2 100644 --- a/docs/testcases/TC06-001-fail.html +++ b/docs/testcases/TC06-001-fail.html @@ -14,168 +14,168 @@ -
- - - - - ICT Accessibility Testing Baseline Alignment -
+ +
+ + + + + ICT Accessibility Testing Baseline Alignment +
- - + + + +
- - - -
-
-
-
-
-

Image - no accessible name or description

-

Test Case Summary

-

Test Case ID

-

TC06-001-fail

-

Test Case Description

-

Detect existence/absence of attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative output for the image.

-

The code sample data input does not include any attributes that would contribute to accessible name or accessible description output. A successful test should identify a failure against Baseline 6. Images.

-

Applicable ICT Baseline

-

6. Images

-

Meaningful Images

-
Test Instructions
-

If the image is meaningful:

-
    -
  1. Check that the combination of accessible name and accessible description provide 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. -
      -
    1. Descriptions of the image that are provided by page content must be programmatically associated.
      2. -
    -
    2. -
  2. Check that the role is NOT “presentation”.
    3. -
  3. Check that aria-hidden is NOT set to true.
    4. -
+ + -
Test Results
-
    -
  • If any of the above checks fail, then SC 1.1.1, SC 4.1.2, and Baseline Requirement 6 fail.
    • -
-

Applicable WCAG/508 Requirement

-
    -
  • WCAG2 SC: 1.1.1. Non-Text – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations listed.
    • -
  • WCAG2 SC: 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

-

The image in the code sample does not provide any attributes that would contribute to an accessible name or description text alternative output.

-

Test Data (code/link)

-

Code

- 
-										
+  	
+  	

+  		

+  			

+  				

+  					

+  						
Image - no accessible name or description

+  							
Test Case Summary

+  								
Test Case ID

+  									
TC06-001-fail

+  								
Test Case Description

+  									
Detect existence/absence of attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative output for the image.

+  									
The code sample data input does not include any attributes that would contribute to accessible name or accessible description output. A successful test should identify a failure against Baseline 6. Images.

+  								
Applicable ICT Baseline

+  									
6. Images

+  									
Meaningful Images

+  										
Test Instructions

+  										
If the image is meaningful:

+  										
    
+  										  
  1. Check that the combination of accessible name and accessible description provide 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.
+  											
      
+  											  
    1. Descriptions of the image that are provided by page content must be programmatically associated.
      2. 
+  											
    
+  										  
    2. 
+  										  
  2. Check that the role is NOT “presentation”.
    3. 
+  										  
  3. Check that aria-hidden is NOT set to true.
    4. 
+  										

 
+  										
Test Results

+  										
    
+  										  
  • If any of the above checks fail, then SC 1.1.1, SC 4.1.2, and Baseline Requirement 6 fail.
    • 
+  										

+  								
Applicable WCAG/508 Requirement

+  									
    
+  									  
  • WCAG2 SC: 1.1.1. Non-Text – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations listed.
    • 
+  									  
  • WCAG2 SC: 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

+  								
The image in the code sample does not provide any attributes that would contribute to an accessible name or description text alternative output.

+  							
Test Data (code/link)

+  								
Code

+  									
+  										
   <body>
 	<img src="../assets/images/corplogo.png" width="50" height="50" class="">
 	<p>This is a meaningful image</p>
   </body>
+  										
+  									

+  								
Single-Page URL

+  									
https://section508coordinators.github.io/BaselineTestPages/testfiles/TC06-001-fail0=/06-001-fail.html

+  								
Embeded Code

+  									
+  						
Test Steps

+  							
+  								
+  									
+  										
+  										
+  										
+  									
+  								
+  								
+  									
+  										
+  										
+  										
+  									
+  									
+  										
+  										
+  										
+  									
+  									
+  										
+  										
+  										
+  									
+  									
+  										
+  										
+  									
+  								
+  							
Test StepStep DetailExpected Result
1.Identify any <img> elements.One <img> exists in the test data code sample.
2.Determine whether the image is meaningful. Review the page content and image context to determine whether the image conveys meaningful information.The image is meaningful, based on the text directly below the image.
3.Calculate the accessible name and accessible description output for the image according to HTML Accessibility API Mappings 1.0 for img.The output for the accessible name and accessible descriptions computations is NULL.
4.Determine whether any checks fail according to the 6. Images test instructions.The first check fails due to absence of accessible name or description in the text alternative computation output.

+  					

+  				

+  			

+  		

+  	

 
-										
-
-

Single-Page URL

-

https://section508coordinators.github.io/BaselineTestPages/testfiles/TC06-001-fail0=/06-001-fail.html

-

Embeded Code

- -

Test Steps

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Test StepStep DetailExpected Result
1.Identify any <img> elements.One <img> exists in the test data code sample.
2.Determine whether the image is meaningful. Review the page content and image context to determine whether the image conveys meaningful information.The image is meaningful, based on the text directly below the image.
3.Calculate the accessible name and accessible description output for the image according to HTML Accessibility API Mappings 1.0 for img.The output for the accessible name and accessible descriptions computations is NULL.
4.Determine whether any checks fail according to the 6. Images test instructions.The first check fails due to absence of accessible name or description in the text alternative computation output.
-
-
-
-
-
+ + - - - - - - - + + + + diff --git a/docs/testcases/TC06-002-pass.html b/docs/testcases/TC06-002-pass.html index cc1f6b38..d17d8741 100644 --- a/docs/testcases/TC06-002-pass.html +++ b/docs/testcases/TC06-002-pass.html @@ -14,176 +14,182 @@ -
- - - - - ICT Accessibility Testing Baseline Alignment -
+ +
+ + + + + ICT Accessibility Testing Baseline Alignment +
- - + + + +
- - - -
-
-
-
-
-

Image - text equivalent in alt attribute

-

Test Case Summary

-

Test Case ID

-

TC06-002-pass

-

Test Case Description

-

Detect existence attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative output for the image. Then determine whether the text alternative output for the image provides an equivalent description of the image.

-

The code sample provides an equivalent description of the image in an alternative attribute. A successful test should identify a PASS against Baseline 6. Images.

-

Applicable ICT Baseline

-

6. Images

-

Meaningful Images

-
Test Instructions
-

If the image is meaningful:

-
    -
  1. Check that the combination of accessible name and accessible description provide 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. -
      -
    1. Descriptions of the image that are provided by page content must be programmatically associated.
      2. -
    -
    2. -
  2. Check that the role is NOT “presentation”.
    3. -
  3. Check that aria-hidden is NOT set to true.
    4. -
+ + -
Test Results
-
    -
  • If any of the above checks fail, then SC 1.1.1, SC 4.1.2, and Baseline Requirement 6 fail.
    • -
-

Applicable WCAG/508 Requirement

-
    -
  • WCAG2 SC: 1.1.1. Non-Text – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations listed.
    • -
  • WCAG2 SC: 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

-

The image in the code sample does not provide any attributes that would contribute to an accessible name or description text alternative output.

-

Test Data (code/link)

-

Code

- 
-										
+  	
+  	

+  		

+  			

+  				

+  					

+  						
Image - text equivalent in alt attribute

+  							
Test Case Summary

+  								
Test Case ID

+  									
TC06-002-pass

+  								
Test Case Description

+  									
Detect existence attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative output for the image. Then determine whether the text alternative output for the image provides an equivalent description of the image.

+  									
The code sample provides an equivalent description of the image in an alternative attribute. A successful test should identify a PASS against Baseline 6. Images.

+  								
Applicable ICT Baseline

+  									
6. Images

+  									
Meaningful Images

+  										
Test Instructions

+  										
If the image is meaningful:

+  										
    
+  										  
  1. Check that the combination of accessible name and accessible description provide 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.
+  											
      
+  											  
    1. Descriptions of the image that are provided by page content must be programmatically associated.
      2. 
+  											
    
+  										  
    2. 
+  										  
  2. Check that the role is NOT “presentation”.
    3. 
+  										  
  3. Check that aria-hidden is NOT set to true.
    4. 
+  										

 
+  										
Test Results

+  										
    
+  										  
  • If any of the above checks fail, then SC 1.1.1, SC 4.1.2, and Baseline Requirement 6 fail.
    • 
+  										

+  								
Applicable WCAG/508 Requirement

+  									
    
+  									  
  • WCAG2 SC: 1.1.1. Non-Text – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations listed.
    • 
+  									  
  • WCAG2 SC: 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

+  								
The image in the code sample does not provide any attributes that would contribute to an accessible name or description text alternative output.

+  							
Test Data (code/link)

+  								
Code

+  									
+  										
   <body>
-	<img src="../assets/images/corplogo.png" width="50" height="50" class="" alt="Bland Corp. logo">
+	<img src="../assets/images/corplogo.png" width="50" height="50"
+          class="" alt="Bland Corp. logo">
 	<p>This is a meaningful image</p>
   </body>
+  										
+  									

+  								
Single-Page URL

+  									
https://section508coordinators.github.io/BaselineTestPages/testfiles/TC06-002-pass/06-002-pass.html

+  								
Embeded Code

+  									
+  						
Test Steps

+  							
+  								
+  									
+  										
+  										
+  										
+  									
+  								
+  								
+  									
+  										
+  										
+  										
+  									
+  									
+  										
+  										
+  										
+  									
+  									
+  										
+  										
+  										
+  									
+                    
+                      
+  										
+  										
+                    
+                    
+  										
+  										
+  									
+  									
+  										
+  										
+  									
+  									
+  										
+  										
+  									
+  								
+  							
Test StepStep DetailExpected Result
1.Identify any <img> elements.One <img> exists in the test data code sample.
2.Determine whether the image is meaningful. Review the page content and image context to determine whether the image conveys meaningful information.The image is meaningful, based on the text directly below the image.
3.Calculate the accessible name and accessible description output for the image according to HTML Accessibility API Mappings 1.0 for img.The output for the accessible name and accessible descriptions computations is "Bland Corp. logo". In this case, the text alternative is provided via an alt attribute.
4.Determine whether the text alternative provides an equivalent description of the the image.Based on the page context, the text alternative provides an equivalent description of the image.
5.Check that the <img> DOES NOT include role="presentation".There is no role attribute defined for the <img> element.
6.Check that the <img> DOES NOT have aria-hidden set to "true".There is no aria-hidden attribute defined for the <img> element.
7.Determine whether any checks fail according to the 6. Images test instructions.All checks pass; therefore, the result for Baseline 6. Images is a PASS.

+  					

+  				

+  			

+  		

+  	

 
-										
-
-

Single-Page URL

-

https://section508coordinators.github.io/BaselineTestPages/testfiles/TC06-002-pass/06-002-pass.html

-

Embeded Code

- -

Test Steps

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Test StepStep DetailExpected Result
1.Identify any <img> elements.One <img> exists in the test data code sample.
2.Determine whether the image is meaningful. Review the page content and image context to determine whether the image conveys meaningful information.The image is meaningful, based on the text directly below the image.
3.Calculate the accessible name and accessible description output for the image according to HTML Accessibility API Mappings 1.0 for img.The output for the accessible name and accessible descriptions computations is "Bland Corp. logo". Based on the page context, the text alternative provides an equivalent description of the image.
4.Check that the <img> DOES NOT include role="presentation".There is no role attribute defined for the <img> element.
5.Check that the <img> DOES NOT have aria-hidden set to "true".There is no aria-hidden attribute defined for the <img> element.
6.Determine whether any checks fail according to the 6. Images test instructions.All checks pass; therefore, the result for Baseline 6. Images is a PASS.
-
-
-
-
-
+ + - - - - - - - + + + + diff --git a/docs/testcases/TC06-003-pass.html b/docs/testcases/TC06-003-pass.html new file mode 100644 index 00000000..54e4c3a5 --- /dev/null +++ b/docs/testcases/TC06-003-pass.html @@ -0,0 +1,195 @@ + + + + + + Image - text equivalent in title attribute + + + + + + + + + + + + +
+ + + + + ICT Accessibility Testing Baseline Alignment +
+ + + + + + +
+ + + + + + +
+
+
+
+
+

Image - text equivalent in title attribute

+

Test Case Summary

+

Test Case ID

+

TC06-003-pass

+

Test Case Description

+

Detect existence attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative output for the image. Then determine whether the text alternative output for the image provides an equivalent description of the image.

+

The code sample provides an equivalent description of the image in an alternative attribute. A successful test should identify a PASS against Baseline 6. Images.

+

Applicable ICT Baseline

+

6. Images

+

Meaningful Images

+
Test Instructions
+

If the image is meaningful:

+
    +
  1. Check that the combination of accessible name and accessible description provide 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. +
      +
    1. Descriptions of the image that are provided by page content must be programmatically associated.
      2. +
    +
    2. +
  2. Check that the role is NOT “presentation”.
    3. +
  3. Check that aria-hidden is NOT set to true.
    4. +
+ +
Test Results
+
    +
  • If any of the above checks fail, then SC 1.1.1, SC 4.1.2, and Baseline Requirement 6 fail.
    • +
+

Applicable WCAG/508 Requirement

+
    +
  • WCAG2 SC: 1.1.1. Non-Text – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations listed.
    • +
  • WCAG2 SC: 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

+

The image in the code sample does not provide any attributes that would contribute to an accessible name or description text alternative output.

+

Test Data (code/link)

+

Code

+ 
+  										
+  <body>
+	<img src="../assets/images/corplogo.png" width="50" height="50"
+          class="" title="Bland Corp. logo">
+	<p>This is a meaningful image</p>
+  </body>
+  										
+
+

Single-Page URL

+

https://section508coordinators.github.io/BaselineTestPages/testfiles/TC06-003-pass/06-003-pass.html

+

Embeded Code

+ +

Test Steps

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Test StepStep DetailExpected Result
1.Identify any <img> elements.One <img> exists in the test data code sample.
2.Determine whether the image is meaningful. Review the page content and image context to determine whether the image conveys meaningful information.The image is meaningful, based on the text directly below the image.
3.Calculate the accessible name and accessible description output for the image according to HTML Accessibility API Mappings 1.0 for img.The output for the accessible name and accessible descriptions computations is "Bland Corp. logo". In this case, the text alternative is provided via a title attribute.
4.Determine whether the text alternative provides an equivalent description of the the image.Based on the page context, the text alternative provides an equivalent description of the image.
5.Check that the <img> DOES NOT include role="presentation".There is no role attribute defined for the <img> element.
6.Check that the <img> DOES NOT have aria-hidden set to "true".There is no aria-hidden attribute defined for the <img> element.
7.Determine whether any checks fail according to the 6. Images test instructions.All checks pass; therefore, the result for Baseline 6. Images is a PASS.
+
+
+
+
+
+ + + + + + + + + + diff --git a/docs/testcases/TC06-004-pass.html b/docs/testcases/TC06-004-pass.html new file mode 100644 index 00000000..57e560cf --- /dev/null +++ b/docs/testcases/TC06-004-pass.html @@ -0,0 +1,195 @@ + + + + + + Image - text equivalent in aria-label attribute + + + + + + + + + + + + +
+ + + + + ICT Accessibility Testing Baseline Alignment +
+ + + + + + +
+ + + + + + +
+
+
+
+
+

Image - text equivalent in aria-label attribute

+

Test Case Summary

+

Test Case ID

+

TC06-004-pass

+

Test Case Description

+

Detect existence attributes that would contribute to the accessible name and accessible description computation and calculate the text alternative output for the image. Then determine whether the text alternative output for the image provides an equivalent description of the image.

+

The code sample provides an equivalent description of the image in an alternative attribute. A successful test should identify a PASS against Baseline 6. Images.

+

Applicable ICT Baseline

+

6. Images

+

Meaningful Images

+
Test Instructions
+

If the image is meaningful:

+
    +
  1. Check that the combination of accessible name and accessible description provide 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. +
      +
    1. Descriptions of the image that are provided by page content must be programmatically associated.
      2. +
    +
    2. +
  2. Check that the role is NOT “presentation”.
    3. +
  3. Check that aria-hidden is NOT set to true.
    4. +
+ +
Test Results
+
    +
  • If any of the above checks fail, then SC 1.1.1, SC 4.1.2, and Baseline Requirement 6 fail.
    • +
+

Applicable WCAG/508 Requirement

+
    +
  • WCAG2 SC: 1.1.1. Non-Text – All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for [specific] situations listed.
    • +
  • WCAG2 SC: 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

+

The image in the code sample does not provide any attributes that would contribute to an accessible name or description text alternative output.

+

Test Data (code/link)

+

Code

+ 
+  										
+  <body>
+	<img src="../assets/images/corplogo.png" width="50" height="50"
+          class="" aria-label="Bland Corp. logo">
+	<p>This is a meaningful image</p>
+  </body>
+  										
+
+

Single-Page URL

+

https://section508coordinators.github.io/BaselineTestPages/testfiles/TC06-004-pass/06-004-pass.html

+

Embeded Code

+ +

Test Steps

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Test StepStep DetailExpected Result
1.Identify any <img> elements.One <img> exists in the test data code sample.
2.Determine whether the image is meaningful. Review the page content and image context to determine whether the image conveys meaningful information.The image is meaningful, based on the text directly below the image.
3.Calculate the accessible name and accessible description output for the image according to HTML Accessibility API Mappings 1.0 for img.The output for the accessible name and accessible descriptions computations is "Bland Corp. logo". In this case, the text alternative is provided via an aria-label attribute.
4.Determine whether the text alternative provides an equivalent description of the the image.Based on the page context, the text alternative provides an equivalent description of the image.
5.Check that the <img> DOES NOT include role="presentation".There is no role attribute defined for the <img> element.
6.Check that the <img> DOES NOT have aria-hidden set to "true".There is no aria-hidden attribute defined for the <img> element.
7.Determine whether any checks fail according to the 6. Images test instructions.All checks pass; therefore, the result for Baseline 6. Images is a PASS.
+
+
+
+
+
+ + + + + + + + + + diff --git a/docs/testfiles/TC06-002-pass/06-002-pass.html b/docs/testfiles/TC06-002-pass/06-002-pass.html index b8f128d9..b7be7c96 100644 --- a/docs/testfiles/TC06-002-pass/06-002-pass.html +++ b/docs/testfiles/TC06-002-pass/06-002-pass.html @@ -2,8 +2,7 @@ - 06-001-fail - + 06-002-pass Bland Corp. logo diff --git a/docs/testfiles/TC06-003-pass/06-003-pass.html b/docs/testfiles/TC06-003-pass/06-003-pass.html new file mode 100644 index 00000000..04d2184d --- /dev/null +++ b/docs/testfiles/TC06-003-pass/06-003-pass.html @@ -0,0 +1,12 @@ + + + + + 06-003-pass + + + + +

This is a meaningful image

+ + diff --git a/docs/testfiles/TC06-004-pass/06-004-pass.html b/docs/testfiles/TC06-004-pass/06-004-pass.html new file mode 100644 index 00000000..89061701 --- /dev/null +++ b/docs/testfiles/TC06-004-pass/06-004-pass.html @@ -0,0 +1,12 @@ + + + + + 06-004-pass + + + + +

This is a meaningful image

+ + From 281b4879a2092017bed2ef5af9a5138fd57c17c8 Mon Sep 17 00:00:00 2001 From: Andrew Nielson <29068131+drewnielson@users.noreply.github.com> Date: Fri, 22 May 2020 15:22:15 -0400 Subject: [PATCH 2/5] Add TC06-04-pass.html to test case links page --- docs/testcases.html | 3 +++ 1 file changed, 3 insertions(+) diff --git a/docs/testcases.html b/docs/testcases.html index 2b72c903..5a68460b 100644 --- a/docs/testcases.html +++ b/docs/testcases.html @@ -88,6 +88,9 @@

Placeholder Index

  • TC06-003-pass
    • +
  • + TC06-003-pass +
    • From 4f8ca352d4c8a15f6a645e1a32561afdac10ee93 Mon Sep 17 00:00:00 2001 From: Andrew Nielson <29068131+drewnielson@users.noreply.github.com> Date: Fri, 22 May 2020 15:24:36 -0400 Subject: [PATCH 3/5] correct link text --- docs/testcases.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/testcases.html b/docs/testcases.html index 5a68460b..c1889f69 100644 --- a/docs/testcases.html +++ b/docs/testcases.html @@ -89,7 +89,7 @@

    Placeholder Index

    TC06-003-pass
  • - TC06-003-pass + TC06-004-pass
    • From 8478fb1dba764fa37152f9b57b0251a62bebc23d Mon Sep 17 00:00:00 2001 From: Andrew Nielson <29068131+drewnielson@users.noreply.github.com> Date: Thu, 28 May 2020 13:22:14 -0400 Subject: [PATCH 4/5] Addressed comments/edits from Kathy's review --- docs/index.html | 2 +- docs/testCaseTemplate.html | 28 ++++++++++++++-------------- docs/testcases.html | 2 +- docs/testcases/TC06-001-fail.html | 4 ++-- docs/testcases/TC06-002-pass.html | 10 +++++----- docs/testcases/TC06-003-pass.html | 8 ++++---- docs/testcases/TC06-004-pass.html | 10 +++++----- 7 files changed, 32 insertions(+), 32 deletions(-) diff --git a/docs/index.html b/docs/index.html index 8c52d1cc..f36f4c10 100644 --- a/docs/index.html +++ b/docs/index.html @@ -71,7 +71,7 @@

    Table of Contents

    ICT Baseline Alignment Framework

    Purpose and Objectives

    -

    GSA's Government-wide IT Accessibility program is encouraging adoption of the Baseline more broadly across government. To facilitate adoption of the Baseline, we must create a process and framework for validating alignment of individual test processes (including testing tools) to the Baseline. The Trusted Tester process is one prime example of a test process that aligns to the Baseline. A Baseline Alignment Validation Framework will make it possible for more agencies to demonstrate alignment of their test processes (whether they subscribe to Trusted Tester or other methods) while providing broader flexibility in the selection of testing tools and contributing test methods. In the end, the more agencies that demonstrate alignment to the Baseline, the more we can share testing results and reduce redundancy in our accessibility testing and market research efforts.

    +

    GSA's Government-wide IT Accessibility program is encouraging adoption of the Baseline more broadly across government. To facilitate adoption of the Baseline, we must create a process and framework for validating alignment of individual test processes (including testing tools) to the Baseline. A Baseline Alignment Validation Framework will make it possible for more agencies to demonstrate alignment of their test processes while providing broader flexibility in the selection of testing tools and contributing test methods. In the end, the more agencies that demonstrate alignment to the Baseline, the more we can share testing results and reduce redundancy in our accessibility testing and market research efforts.

    diff --git a/docs/testCaseTemplate.html b/docs/testCaseTemplate.html index 9651c39f..6aacbd5a 100644 --- a/docs/testCaseTemplate.html +++ b/docs/testCaseTemplate.html @@ -4,7 +4,7 @@ ICT Testing Baseline Alignment - Test Case Template - + @@ -21,8 +21,8 @@ ICT Accessibility Testing Baseline Alignment - - + + - +
    - - + + - + -
    -
    +
    +
    @@ -102,7 +102,7 @@

    Code

    include the code here

    Single-Page URL

    [URL to page hosted within this repository]

    -

    Embeded Code

    +

    Embedded Code

    [embed page within iframe]

    Test Steps

    @@ -130,9 +130,9 @@

    Test Steps

    -
    +
    - +