When Optiem was engaged to build the new website for Cuyahoga County Public Library, I was lucky enough to meet Will Reed. He works for Cleveland Public Library at the Library for the Blind and Physically Handicapped and helped facilitate testing of our proof-of-concepts with a blind user.
He recently took time out from his work at the Library and ASCLA to answer 5 questions (by email) concerning accessibility on the web.
Me:
Do you feel the increase of CSS based layouts and interest (by developers) in adhering to the W3C standards have made web pages better for users with accessibility issues?
Will:
The increase of CSS based layouts and the efforts of conscientious web developers have probably helped make web pages more accessible. However, a CSS based layout is not the only way a web author can produce accessible web pages conforming to the World Wide Web Consortium's (W3C) Web Accessibility Initiative (WAI) or Section 508 guidelines. Therefore, I believe it comes down to the awareness, realization, and thoughtfulness by developers and those hiring developers to include and ensure accessibility and usability for people with disabilities.
Me:
Do you think the rumor of AJAX support in JAWS will put to rest some of the problems with this technology (AJAX)?
Will:
Honestly, I feel that AJAX or any JAVA scripting for that matter was never really designed with screen reader users or anyone who cannot use a point and click device such as a mouse, in mind. Sure, web developers can use AJAX and JAVA, and screen readers will support it, but the underlying problem is usability. Web developers adhering to the standards and guidelines of W3C and Section 508, and those developers who truly take the time to really learn how screen readers work with web pages will recognize the challenges that AJAX poses to screen reader accessibility, and conclude that there maybe other more accessible and perhaps visually pleasing approaches.
Me:
Can well-meaning developers be overzealous and over-use/misuse attributes like title and alt – can there be too much accessibility?
Will:
If developers are correctly following the guidelines and standards set forth by W3C and Section 508, then no, there can never be too much accessibility. In fact, W3C web content accessibility techniques often describe and discuss how attributes or any design element should be appropriately and effectively used. Section 508 has a FAQ, which also deals with the appropriate use of attributes as well.
Me:
What is one thing that developers always miss that, you think, should be included in every site and one thing that could always be left off?
Will:
Honestly, I think the one thing that developers always miss that should be included in every web site is simply the premise that everyone should be able to access all the content on a web page. Universal design and accessible web pages can offer developers a rather challenging task, but it’s by no means impossible.
Me:
What sites or books would you recommend designers or developers reading?
Will:
- W3C Web Accessibility Initiative – www.w3c.org/wai
- Section 508 – www.section508.gov
- Mates, Barbara. Adaptive technology for the Internet : Making electronic resources accessible to all. Chicago: American Library Association, 2000. - online version
I'd like to thank Will for sharing his thoughts. Personally I think that some accessibility problems for people who use assistive technology, like screen readers, can be avoided ahead of time by developers taking a little more time thinking about their implementation and educating themselves and their clients on the benefits of implementing the standards and resources already available to them.
Technorati tags: w3c standards, usability, accessibility, section508
Blogged with Flock
|