how 508 complaince testing is used
Please let me know if any one know how 508 testing is done in diff applications? and where it is used and what is the process that we follow to test the application.
Re: how 508 complaince testing is used
Such a basic question!
Browse through this Usability & Accessibility Testing sub-forum and you'll see lots of guidelines. In addition, a quick Google search turns up lots of answers http://www.google.com/search?q=508+compliance+testing
So, who should be running the compliance tests: QA or Developers?
It seems like it makes more sense for the Developers to run/execute these tests since they know exactly what areas in the application they would like to test instead of asking QA to run this test against this page and give the results.
QA run that. And few company require only certified QA should do that due to regulation ( in one of my previous org).
There is a standard VPAT test guideline and n-number of software to assist that.
Hmmm.....Still does not make much sense in our case.
We have a tool that can be learned by high school kids in minutes.
Start the tool.
Enter the AUT URL
Bring up the page to test
Click the Scan button
Save the generated script (contains only 3 or 4 lines TEST ON/OFF, GET, POST, TEST ON/OFF)
Click the Reports button
Send the results to Developer(s)
Developers review results and make changes to AUT then ask QA to rerun the test
QA do the steps all over again as many times as requested by developers.
Wow! If developers run this tool on their machine, lots of precious time will be saved and QA can concentrate on other QA tasks.
Maybe when developers have made their 'Final Changes', then QA can run the tests for them at that point.
,,,just my opinion...
Quality is a organizational responsibility, and test should only accept the build when there is enough test has been done by dev (or entry criteria).
high school kid - that may apply on 90% testing
For applications developed mainly for the company employees (not to sell to the general public), do you still execute this 508 compliance testing on them? What is the determining factor on whether or not this type of testing is needed for Not-For-Sale applications?
There are two main determining factors: legislation, and the company's own standards.
From Wikipedia: "Under Section 508 (29 U.S.C. § 794d), agencies must give disabled employees and members of the public access to information that is comparable to the access available to others." The key words you're looking at here are "disabled employees", so it follows that for federal agencies they are required to follow S508 for all internal applications / websites.
For non-federal companies they are still bound by relevant health and safety and employee legislation, but this will differ from country to country so you'll need to check the relevant accessibility legislation in your own country. This can make it quite tricky for an international company where their internal website may cross borders.
In addition to legislation, many larger companies have their own internal standards that must be met, such as being able to be viewed on a browser using larger accessibility fonts, or every image having a proper tag, etc. This will differ from company to company and you'll need to check with your IT compliance department (if you have one).
Thanks for the good info, meridian_05!
Sounds like you've done this 508 Compliance Testing before and maybe still doing it.
Not 508 compliance (I've never tested federal sites), but I've tested international corporate intranets before where the companies took accessibility by disabled employees very seriously - their internal policies were stronger than H&S and equality legislation in most countries. It's nice to test sites like that where the corporate governance is so strong, it makes defect advocacy much easier.
Most of my work is with larger corporates, so includes compliance with either internal policies or some form of legislation (SOx, GAAP, IFRS, tax laws, etc). Once you get the hang of following the rules it's pretty straightforward.