#22936
Why Hiptops are Harmful to Web Standards
Found out why the author has reservations about this handheld device and why it appears not to properly support web standards.
Accessify (2003). Design>Accessibility>Wireless Web>Standards
#24082
Approaching accessibility as an afterthought is not an effective strategy. Rather, organizations that include accessibility management as part of their development plans and quality assurance and testing practices will have a tremendous economic advantage.
Yonaitis, Robert B. HiSoftware (2002). Design>Web Design>Accessibility
#28206
There are many reasons why you should strive to make your web site as accessible as possible: legal reasons; economic reasons; technical reasons.
O'Gribin, Niall. Erigena (2006). Articles>Web Design>Accessibility
#27142
The Web is not a panacea. If businesses, governments, and other organizations that publish information on the Web don't pay attention, the Web's promise of equal access for all could be fatally undermined by the rush to make Web sites technologically slick and visually exciting.
Garfinkel, Simson L. Boston Globe (1998). Articles>Web Design>Accessibility>Civic
#23787
Working to 508: Seeing, Hearing, and Understanding Accessible, Usable Web Pages 
Now that the U. S. Government has mandated that web pages comply with accessibility standards (Section 508, a 1998 amendment to the Rehabilitation Act of 1973), it is time to test web pages against the standards. “What do newcomers to these standards need to know to ensure that they are on the right tract with accessible, usable web page design? “What do web page designers need to know beyond 508 standards? Join us in an exploration of our personal experiences with “stuckness” when using web pages (visual accessibility), Reece; learn possible solutions to our “silent screams” (audio accessibility), Vinegar; and consider also the question of web page accessibility to users with cognitive or learning disabilities (comprehensibility), Gillen.
Reece, Gloria A., Judy A. Vinegar and Lori Gillen. STC Proceedings (2003). Design>Web Design>Accessibility>Section 508
#18788
This scenario–based progression targets designers and developers who are interested in learning about assessment for web page design for compliance with the Americans with Disabilities Act (ADA). It introduces the topic by providing a background on web page design for individuals with special needs (varying physical and sensory abilities). Then, it presents basic concepts for developing accessible web pages, raises awareness of the need to comply with the ADA, Section 508, and provides resources for further investigation. Emphasis will be given to interactive discussion that centers on assessment questions to consider for concurrent, accessible and user–centered design approaches for web pages.
Reece, Gloria A. STC Proceedings (2002). Design>Web Design>Accessibility>Section 508
#28237
Working with Others: Accessibility and User Research
After personally observing users with disabilities interacting with websites in unexpected ways, I have come to believe strongly in the value of user research--and to suspect that we really don't know quite as much about real-world accessibility as we think we do.
Boscarol, Maurizio. List Apart, A (2006). Design>Web Design>Accessibility>User Centered Design
#23005
World Wide Access: Accessible Web Design
This video presentation shows how to make web pages accessible to people with disabilities. It is particularly useful for self-instruction or group training for people who design and support websites and/or teach web design classes. The accompanying publication provides details and resources on this topic. The presentation is open-captioned and audio-described to assure access to the content for viewers who are deaf or blind, respectively.
University of Washington-Seattle (2003). Design>Web Design>Accessibility>Video
#27422
Writing a Good Accessibility Statement
Accessibility statements are an ideal place to empower visitors to your website. Most accessibility statements are too technical, and don't necessarily address the needs of the visitor. Those that do address the needs of visitors often have the information lost in a myriad of other information that is unlikely to be understood by the average visitor to the website. What should and shouldn't be included in an accessibility statement?
Lemon, Gez. Juicy Studio (2006). Design>Web Design>Accessibility>Writing
#25290
Writing Effective ALT Text for Images
Simply inserting ALT text isn't necessarily enough to ensure accessible images - the text must also be effectively written. Find out how to achieve this...
Moss, Trenton. Webcredible (2005). Design>Web Design>Accessibility
#23126
The library is committed to serving the entire public, and that means striving to ensure that all pages of our site are accessible to the greatest possible number of people and devices (including audio browsers, Braille readers, and other specialized browsing environments).
New York Public Library (2004). Design>Web Design>Accessibility>XHTML
#18634
This document provides guidelines for designing Extensible Markup Language (XML) applications that lower barriers to Web accessibility for people with disabilities (visual, hearing, physical, cognitive, and neurological). XML, used to design applications such as XHTML, SMIL, and SVG, provides no intrinsic guarantee of the accessibility of those applications. This document explains how to include features in XML applications that promote accessibility.
W3C (2002). Design>Web Design>Accessibility>XML
#19246
XML (eXtensible Markup Language) is a meta-syntax, used to create new languages. It can be seen as a simplification of SGML (Standard Generalized Markup Language), designed to promote a wider acceptance in Web markets, but serving the same functionality of extensibility and new language design. XML is therefore not to be seen as a replacement of HTML, but as a new building layer, usage examples of which are: XHTML (for general HyperText content). Furthermore, it is important to understand that XML is not only a User Interface technology (like HTML), but can and is often used in protocol communication, to serialize and encode data to be sent from one machine to another.
Franklin, Tom. TechDis (2002). Design>Web Design>Accessibility>XML
#30605
A zoom layout uses CSS (cascading stylesheets) to automatically reformat a page so it's easier for a low-vision user to read. Multiple columns become single columns, navigation gets simplified and put at the top, fonts become bigger, and (usually) colours are set to light on dark.
Clark, Joe. JoeClark.org (2005). Design>Web Design>Accessibility>Typography
#27666
この文書は2つの質問に答えるために書いてみたんだ。 1コ目は、「なんでサイトをアクセシブルにした方がいいのか」。だから、ここの情報はサイトを持ってない人には向かないかも。 2コ目は、「じゃどうしたらサイトをアクセシブルにできるのか」。 1コ目の答えが納得できるものじゃなかったら、2コ目はどうでもいいってことになるよね。
Pilgrim, Mark. Dive Into Accessibility (2002). (Japanese) Books>Web Design>Accessibility
#27662
這本書要回答兩個問題：第一個問題是「為什麼該讓我的網站更具親和力？」如果妳根本就沒有網站的話，顯然就不會成為本書的讀者了。第二個問題是「該如何讓我的網站更具親和力？」如果第一個問題的回答說服不了妳，那麼第二個問題大概也將無法引起妳的興趣。
Pilgrim, Mark. Dive Into Accessibility (2002). (Chinese) Books>Web Design>Accessibility
#32264
Checkpoints for Web Content Accessibility Guidelines 1.0
This document is an appendix to the W3C "Web Content Accessibility Guidelines 1.0". It provides a list of all checkpoints from the Web Content Accessibility Guidelines 1.0, organized by concept, as a checklist for Web content developers.
W3C (2005). Articles>Web Design>Accessibility>Standards
#32265
Exploiting Web Tools to Make HTML Documents Accessible
More accessible documents through authoring tool supports. Exploit mainstream tools for easier information retrieval and document manipulation.
Treviranus, Jutta and Jan Richards . University of Toronto (2004). Presentations>Web Design>Accessibility>Software
#32268
Web Browsing through Adaptive Technology: A Consumer Information Resource
The Adaptive Technology Resource Centre (ATRC), University of Toronto coordinated efforts with the Diversity Management Directorate (DMD), Public Services Commission of Canada to systematically evaluate how commercial World Wide Web (WWW) browsers functioned with various types of adaptive technology under different operating systems. The types of adaptive technology examined include screen magnifiers, scanning / switch access systems, alternative keyboards, screen readers, Morse code input devices and voice recognition systems.
Nguyen, Kevin K. and Linda S. Petty. University of Toronto (2007). Articles>Web Design>Accessibility>Web Browsers
#32425
Multiple Form Labels and Screen Readers
Just about every website needs some forms. Sometimes there are many of them, sometimes just a single contact form. Regardless of their number, they need to be usable and accessible, which can sometimes be a little more work than it would be if theory and practice aligned a little better.
Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility>Forms
#32441
Helping Others Understand Web Accessibility
When I hold workshops for people who want to learn more about web standards and accessibility, I often notice that the attendants really have tried to improve their accessibility knowledge. But they get overwhelmed when they go to the official documentation from the W3C and try to understand it.
Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility>Standards
#32442
Making Web Accessibility Accessible
when first learning web accessibility and uncovering its secrets, like many things, it can seem daunting and difficult. I think a lot of developers are downright intimidated by web accessibility — maybe even scared to go that route. But why? I suspect the reason is web accessibility is a discipline that lacks accessibility.
Cherim, Mike. Beast-Blog (2006). Articles>Web Design>Accessibility>Education
#32445
Sometimes when people first learn about Web accessibility they look for quick ways of improving the sites they build. This often leads to misuse or overuse of certain HTML features that are meant to aid accessibility, but when used wrongly have no effect and can actually have the opposite effect by making the page less accessible and less usable.
Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility
#32446
Accessibility is Part of Your Job
Accessibility is one of the fundamentals of the Web, so how people who claim to be passionate about the Web and say that they deliver high quality can choose to ignore it is beyond me.
Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>Standards
#32449
Choose an Accessible Image Replacement Method
The technique of using CSS to replace normal HTML text, mostly for headings, with a background image in order to achieve a particular look has been talked about many, many times since early 2003.Several different image replacement methods have been proposed, each with their pros and cons. Some methods create accessibility problems, while others place restrictions on the type of image you can use or force you to use extraneous markup. No method that I am aware of is perfect.
Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>CSS
