Skip to content
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.

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

Update test case guide #142

Open
wants to merge 55 commits into
base: bletalien-testCaseGuide
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
55 commits
Select commit Hold shift + click to select a range
6f123e2
files for 16.1-2-fail-2
kengdoj Oct 28, 2021
f502b95
Merge pull request #140 from Section508Coordinators/kengdoj-16.1-2-fa…
kengdoj Oct 28, 2021
44af5c9
Made test update to base README.md
Nov 4, 2021
25070d7
Merge pull request #143 from Section508Coordinators/adk_Testcases
Nov 5, 2021
df518de
Change "wither" to "whether"
bletalien Jan 3, 2022
c477c8a
Changed "conrast" to "contrast"
bletalien Jan 3, 2022
34157ef
Update 12.1-3-fail-1.html
cliffbert Feb 3, 2022
e3c5578
Merge pull request #146 from Section508Coordinators/bletalien-fixTypo
kengdoj Feb 10, 2022
f2735ad
13.3 test cases
kengdoj Mar 15, 2022
9cfcdcf
dna tc
kengdoj Mar 16, 2022
eea7698
13.4 tc
kengdoj Mar 16, 2022
4d15181
Merge pull request #153 from Section508Coordinators/kengdoj-13.3
kengdoj Mar 16, 2022
b146184
13.4-3
kengdoj Mar 16, 2022
913ec18
more 13.4 tc
kengdoj Mar 16, 2022
8286a41
Merge pull request #154 from Section508Coordinators/kengdoj-13.4
kengdoj Mar 16, 2022
c1c29a9
5.1, 10.4, 10.7 (#145)
JohnCotterSSA Apr 7, 2022
242e7e3
init (#148)
JohnCotterSSA Apr 12, 2022
97297e1
Cotter 06.3 (#149)
JohnCotterSSA Apr 12, 2022
7db0590
draft
jzmnbrjs Jul 6, 2022
84d2045
10.5-1-fail-1
jzmnbrjs Jul 6, 2022
c388d2f
10.5-1-pass-1
jzmnbrjs Jul 7, 2022
03d9f06
10.5-1-pass-2
jzmnbrjs Jul 7, 2022
cf88e9c
draft
jzmnbrjs Jul 7, 2022
f6c2a57
jzmnbrjs Jul 7, 2022
0eb46d9
changes
jzmnbrjs Jul 12, 2022
b0ee110
Update TC10.5-1-pass-3.md
jzmnbrjs Jul 12, 2022
7e971e1
just updates the testcases.md
jzmnbrjs Jul 14, 2022
1e41f64
practice draft
jzmnbrjs Jul 14, 2022
4ad5625
Update testcases.md
jzmnbrjs Jul 14, 2022
5986bce
Update testcases.md
jzmnbrjs Jul 14, 2022
57aa6a8
Update testcases.md
kengdoj Jul 15, 2022
9918164
Merge pull request #159 from Section508Coordinators/jzmnbrjs-patch-1
kengdoj Jul 15, 2022
5f202cb
gitignore update
drewnielson Aug 16, 2022
d3c9386
Vip 14.1 1 fail 1 (#129)
vprentice Aug 26, 2022
0a59b9f
8.1-3-Pass-2 for Review (#111)
CJStegall Aug 26, 2022
94d4222
Revert "8.1-3-Pass-2 for Review (#111)" (#163)
drewnielson Aug 26, 2022
410654c
CStegall (#164)
drewnielson Aug 26, 2022
839c2f3
Cs11 (#112)
cliffbert Aug 28, 2022
52de425
Bletalien testcases (#94)
bletalien Aug 29, 2022
d2a0970
Added TC11.1-1,2 (#113)
cliffbert Sep 12, 2022
c6ce537
Cliff 11pass1 (#115)
cliffbert Sep 12, 2022
fa67c96
Cs 1.2 dna (#116)
cliffbert Sep 12, 2022
811946e
Cs 2.1 foc dna (#117)
cliffbert Sep 12, 2022
412086e
Cs dna img txt (#118)
cliffbert Sep 12, 2022
2eb665a
Cs 6.3 dna (#120)
cliffbert Sep 12, 2022
2b2b397
Add files via upload (#119)
cliffbert Sep 12, 2022
d9d424e
Cs 6.4 1 fail 1 (#121)
cliffbert Sep 12, 2022
d8ea4ae
intro and contributing updates (#168)
drewnielson Mar 16, 2023
e7ec4ad
remove footer (#170)
drewnielson Mar 16, 2023
26e7579
Cs 13.3 ic dna1 (#128)
cliffbert Apr 17, 2023
94ef44e
TC8.1-3-pass-1.md is ready for review (#126)
CJStegall May 13, 2023
ff19a3c
Cjs 8.1 3 fail 2 (#131)
CJStegall May 13, 2023
081c30e
Bump tzinfo from 1.2.9 to 1.2.10 (#160)
dependabot[bot] May 13, 2023
5ada32c
Cjs 8.1 2 fail 2 (#132)
CJStegall May 13, 2023
d05fd80
Cjs 8.1 2 fail 3 (#136)
CJStegall May 15, 2023
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
Expand Up @@ -2,6 +2,7 @@ _site
.sass-cache
.jekyll-metadata
.jekyll-cache
node_modules
public/
*~
*dwsync.xml
Expand Down
2 changes: 1 addition & 1 deletion Gemfile.lock
Expand Up @@ -68,7 +68,7 @@ GEM
terminal-table (2.0.0)
unicode-display_width (~> 1.1, >= 1.1.1)
thread_safe (0.3.6)
tzinfo (1.2.9)
tzinfo (1.2.10)
thread_safe (~> 0.1)
tzinfo-data (1.2021.1)
tzinfo (>= 1.0.0)
Expand Down
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -16,4 +16,4 @@ The ICT Baseline Alignment Validation Framework provides test cases as a way for
## How to Contribute
Working Group members can use the [editor on GitHub](https://github.com/Section508Coordinators/BaselineTestPages/edit/master/README.md) to directly edit this file to add references. Members can also navigate to the [Baseline Test Pages repository](https://github.com/Section508Coordinators/BaselineTestPages) to add files to test. Static pages can be viewed via GitHub Pages from this repository at the following url: <https://section508coordinators.github.io/BaselineTestPages/>.

Contributors do not need to be highly technical nor make a long-term commitment, although both skills and time can certainly be helpful. The ICT Baseline Alignment Working Group needs help developing and evaluating test cases. Accessibility advocates are also needed to spread the word about the Framework, develop a governance structure, participate in governance, develop and maintain the website, provide user experience and plain language expertise, and even provide legal support. Please visit our [How You Can Help](https://section508coordinators.github.io/BaselineTestPages/contributing.html#helping) and [How We Work](https://section508coordinators.github.io/BaselineTestPages/contributing.html#how-we-work) sections or contact us at <ictbaseline@gsa.gov> for more information about getting involved.
Contributors do not need to be highly technical nor make a long-term commitment, although both skills and time can certainly be helpful. The ICT Baseline Alignment Working Group needs help developing and evaluating test cases. Accessibility advocates are also needed to spread the word about the Framework, develop a governance structure, participate in governance, develop and maintain the website, provide user experience and plain language expertise, and even provide legal support. Please visit our [How You Can Help](https://section508coordinators.github.io/BaselineTestPages/contributing.html#helping) and [How We Work](https://section508coordinators.github.io/BaselineTestPages/contributing.html#how-we-work) sections or contact us at <ictbaseline@gsa.gov> for more information about getting involved..
4 changes: 2 additions & 2 deletions Templates/_testcase-template.md
Expand Up @@ -16,7 +16,7 @@ tcid:
descr:

# Reference and link to the applicable ICT Baseline test
app-basline:
app-baseline:

# Expected result that the ICT Baseline would predict
# [Pass | Fail | DNA]
Expand All @@ -40,4 +40,4 @@ sample:
---
| Test Instruction | Instruction Detail | Expected Test Case Result |
|------------------|--------------------|---------------------------|
| # | Detail | Step Result |
| # | Detail | Step Result |
2 changes: 0 additions & 2 deletions _layouts/base.html
Expand Up @@ -16,8 +16,6 @@

{{ content }}

{% include footer.html %}

{% include scripts.html %}
</body>

Expand Down
6 changes: 3 additions & 3 deletions contributing.md
Expand Up @@ -4,10 +4,10 @@ title: Contributing to the ICT Baseline Alignment Framework
---
# Contributing to the ICT Baseline Alignment Framework
## How you can help
### Developing and Evaluating Test Cases
Need content from people doing this work. What do you need?
If you are a federal employee or providing direct contract support to a federal agency, we invite you to contribute directly as a member of our ICT Baseline Working Group (with supervisor and/or client approval). If you are not a federal employee, we can still use your help and welcome your feedback and contributions via sumission of [issues](https://github.com/Section508Coordinators/baselinealignment/issues) and [pull requests](https://github.com/Section508Coordinators/baselinealignment/pulls) in the [GitHub repository](https://github.com/Section508Coordinators/baselinealignment). We are also happy to accept input and/or recommendations for other methods of contributions via [ictbaseline@gsa.gov](mailto:ictbaseline@gsa.gov).

I have a note about issuing templates. Does that belong bundled with this topic?
### Developing and Evaluating Test Cases
We welcome any input and feedback on the Baseline Alignment Framework Test Cases. If you have experience in front-end web development, we need help to develop code samples with various examples of both failures and passes against specific Section 508 conformance standards. Even if you aren't a developer, but you have some good examples of web content passes and failures, we welcome those suggestions as well. We will use contributed code samples to complete development of our Test Cases, which help test process and tool owners evaluate whether their tools/processes produce the same test results that the ICT Testing Baseline would predict.

### Planning and Conducting Outreach
We need people to know about our work so they can contribute and use it! Whether you enjoy giving presentations or would prefer to remain behind the scenes writing and editing, your skills are needed. Can you help with any of the following?
Expand Down
8 changes: 5 additions & 3 deletions index.md
Expand Up @@ -13,14 +13,16 @@ Members of the U.S. federal accessibility community must agree on what constitut

The Section 508 standards incorporate the [Web Content Accessibility Guidelines (WCAG) 2.0](https://www.w3.org/TR/WCAG20/), levels A and AA. The ICT Testing Baseline for Web establishes the minimum tests and evaluation guidance for determining whether Web content meets the requirements of WCAG 2.0 A and AA and, therefore, Section 508.

Although the ICT Testing Baseline does not provide processes or tools for conducting baseline tests, it can be used to develop test processes and evaluate how well test processes cover all Section 508 requirements.
Although the ICT Testing Baseline does not provide processes or tools for conducting baseline tests, it can be used to develop test processes and evaluate how well test processes address all Section 508 requirements.

The ICT Baseline Alignment Validation Framework provides test cases as a way for agencies to check whether their own test processes and use of testing tools cover all Section 508 requirements. Two different processes that align to the Baseline should produce the same replicable and reliable test results.
The ICT Baseline Alignment Validation Framework provides test cases as a way for agencies to check whether their own test processes and use of testing tools adequately address all Section 508 requirements. Two different processes that align to the Baseline should produce the same replicable and reliable test results.

## How to contribute

Contributors do not need to be highly technical nor make a long-term commitment, although both skills and time can certainly be helpful. The ICT Baseline Alignment Working Group needs help developing and evaluating test cases. Accessibility advocates are also needed to spread the word about the Framework, develop a governance structure, participate in governance, develop and maintain the website, provide user experience and plain language expertise, and even provide legal support. Please visit our [How You Can Help](contributing.html#helping) and [How We Work](contributing.html#how-we-work) sections or contact us at [ictbaseline@gsa.gov](mailto:ictbaseline@gsa.gov) for more information about getting involved.

## How to validate alignment to the ICT Baseline

Some basic info, then link to the "Validating Alignment" detailed guidance.
Our ICT Baseline Working Group is still developing test cases and guidance for test process and tool owners to evaluate alignment to the ICT Testing Baseline. The basic purpose of the Baseline Alignment Framework [Test Cases](testcases.html) is to provide code samples along with the ICT Testing Baeline's expected conformance test result for a specific code sample and specific Baseline test procedure. Test process and tool owners can test the same sample code, using their own relevant test procedures and/or test rules, and compare their test results to those in the test cases to determine whether their tools/processes produce the same results that the ICT Testing Bseline would predict.

More detailed guidance is still to come. As our working group continues to develop test cases and accompanying guidance, we invite test process and tool owners to review the test cases and provide feedback.