Have been asked by a customer to do testing of a web based which also needs to include Section 508 : Web Accessibility Standards.Does anyone have any prior experience testing the Section 508 : Web Accessibility ....,
Have started reading through the documents from internet and within the time span it seems to be difficult to read and understand and implement the same.
If anyone has any idea and what are the basic things that can/should be tested for 508 please let me know....
Does anyone have any idea of any free or online Web Accessibility tools and also any tool that can grey out the Web Pages...to check the Color aspect of Section 508.
I also would like to know that how screen readers work...tried working on Jaws,Thunder(did not have time to go through the application).Once when we start the screen reader and are on a page does the screen reader read all the labels and textfield values or does it read only when we navigate through....Waiting to hear from you.
I think the OP was looking for some insight as to methods or ideas of how to do this. The OP does state that they already have the documentation they want to know if anyone hase any advice on doing this proceedure.
But in the end doesn't it all come down to BEER? Beer is the ultimate answer to all questions in the universe so yes the answer to your question is BEER.
I can't speak for other screen readers, but JAWS reads at a level of verbosity that you choose. It has a huge number of configurable options, and what and when it speaks depends on some of those options.
But it is not a tool for testing Section 508 compliance per se.
A quick search in Google should give you some pointers to free Section 508 Assessment tools...such as http://webxact.watchfire.com/. Typically these will only allow you to submit one page at a time.
I've not done any Section 508 assessments but have done some WAI assessments. Here is an outline of what I do...
I run the site/selected pages against two tools (HiSoftware AccVerify and Watchfire's Bobby tools, both of these can run WAI and 508 checks). Where there are any non-conformances reported I will investigate these manually and make an assessment to ensure no false positives are being reported.
I also run the pages using a screen reader (JAWS and IBM Homepage Reader) to check that the pages read OK and are easy to navigate.
I also have to check a number of other things that the tools do not (and cannot) check...for example does the ALT text suitably describe the image.
I also validate the XHTML/HTML and CSS and check for broken links.
To do these kind of assessments effectively you need to tools (although you can do it without them) but also an understanding of the standard as the tools cannot check everything.
Hi. A great place to look for tools is on the W3C. W3C will give you a plethora of information on Accessibility Testing. If you are just looking for tools, here's a link to a search page that will allow you to search for tools that meet your Accessibility needs.
I've tested on section 508 and my understanding is that your web site should be user friendly and easy to access and navigate.
Following sections are kicking off for you
1) Test the color contrast (White on Black), (Black on White) (Large Text) and Default.
1.1 You need to test if the website allows mentioned color combination for those people who have eye side problem
2) Allow key access to buttons so for example if I like to click Logout I should be able to press combination of [Ctrl]+  to click the button without mouse.
3) The Navigation structure is consistent and not falling around.
Keep in mind Section 508 is accessibility to disable people. Read the following site which is standard section 508 site and it tells you law of 508