kengdoj/acrt-bart

Development of Baseline Alignment Reporting Tool (BART) tool

acrt-bart's Issues

Remove license page

Visual edits to home page

1. Remove image
2. Align heading 1 so it isn't right against the margin (I imagine this is somewhere in the CSS--I can look for it next week)
3. Align body text directly under heading 2

Add a column for test process ID next to test process result

Then test process ID to Baseline test ID mapping could be generated

Indented H2s

They're weird and unnecessary. Should we modify the CSS, or are we better off not touching it?

Edits to index page

Since I couldn't figure out how to get you a proper pull request, attaching suggested edits to the index file.

• "do" should be "to": "to determine how well"
• put "email the" inside the mailto link

Except it won't let me attach an HTML file! Aaarrrggh!

Content edits to home page

Replace text:
##What is BART?
BART is an open source tool developed by the Baseline Working Group to help test process owners enter their test results for Baseline Test Cases to determine how well they align to expected Baseline results.
##Wait! What is the Baseline Working Group?
Let's back up a bit.

Section 508 of the Rehabilitation Act of 1973, as amended, requires Federal agencies to, among other things, make their websites accessible to people with disabilities.

The ICT Testing Baseline for Web, which the Baseline Working Group developed, identifies the minimum requirements of any test process used to determine conformance of web content with the Section 508 standards. The ICT Testing Baseline for Web is a Best Practice of the Federal CIO Council Accessibility Community of Practice (ACOP). Federal agencies are encouraged to use the Baseline for Web in their efforts to test web content for Section 508 conformance.

If you have a process for testing web content, you can use BART to compare it to the ICT Testing Baseline for Web.

##What do I do to test my process?
Through BART, you can access test cases that allow you to determine whether your interpretation of accessibility requirements matches the interpretation of the ICT Testing Baseline for Web.

Follow the instructions on the Create Report page to enter your results and compare them to the expected ones. Feel free to save your results and come back often as you refine your process. You can upload results to the [View Report page](/ACRT_View_webReport.html].

##Need more information? Have a suggestion?
We encourage and welcome feedback and suggestions from the testing community! For user support, email the ICT Baseline Working Group.

You can also download BART from the GitHub Repository.

##Acknowledgments
Many thanks to DHS OAST for their support with development of this tool.

Suggested fields for "Product" section of ACRT_Web_Input_Form.html

1. 1Change “product” to “process” throughout this section
2. Keep first three fields, with that edit
3. Remove “product type” altogether

Test Cases JSON

Baseline Test Cases JSON needs to be created to work with this BART.

1. Capitalize expected test result (to match capitalization of entered test result)
2. Add 508 requirement for each test case to help with mapping later

Thoughts on fields for "Testing Information" section of ACRT_Web_Input_Form.html

• Instead of "tester," do we want "submitter," "point of contact," or similar?
• Remove TT ID
• Hmm, I'm not sure what to say about "testing scope." Is it useful to us? Is that the right label?