I'm going against the grain. Up to now, I've been testing web pages with JAWS for Windows and determining where the Section 508 guidelines require certain techniques. I've started trying to prioritize and build statistics on how likely web content is to be inaccessibile. Things like Frames top the list and depreciated HTML are towards the bottom of the list. I hope this statistical approach (maybe just 'data driven' or 'metrics' approach is better?) will also become a *process* that can be used by non-technical staff to help determine which EIT is most likely to be at risk and target manual assessments on these high-risk items.
I started this because I had to review a 1500+ web page site - try that with JAWS! Eeek. I also want to use publicly available (freely available open source) tools and create publicly available tools and an open process that can be used by other agencies or groups at no direct costs. It will either be a complete failure or a new way of doing assessments!
No comments:
Post a Comment