#27178
残障人士法案要求所提供的服务不得歧视残障人士。一个网站被认为是一种服务，因而受这一法案约束，所以必须对每个人具备无障碍性。 一些团体正在对他们的网站进行无障碍性改进，但是许多团体看起来没有采取行动。残障人士不会进入他们的网站，他们说，那为什么要在乎这些。
Moss, Trenton. uiGarden (2005). (Chinese) Design>Web Design>Accessibility>United Kingdom
#27177
网络无障碍性是关于使你的网站让所有因特网用户（残障用户和正常用户）易于获得，不管他们使用什么浏览技术。除了符合相关法律法规， 具备无障碍性将让您的网站和商业受益良多。 请参阅文章，《具备无障碍性的网站的益处 – 第一部分 》和《具备无障碍性的网站的益处 – 第二部分 》以了解更多关于网站的无障碍性的重要性。
Moss, Trenton. uiGarden (2006). (Chinese) Design>Web Design>Accessibility
#21846
More and more Web surfers are vision-impaired. Can they understand your site?
Williams, Maxine. Adobe Magazine (1999). Design>Web Design>Accessibility
#20059
If your company has a public website, it needs to be accessible - and that's the law.
Joseph, Cliff. Guardian Unlimited, The (2003). Design>Web Design>Accessibility>United Kingdom
#23081
The Access Board is an independent Federal agency devoted to accessibility for people with disabilities. It operates with about 30 staff and a governing board of representatives from Federal departments and public members appointed by the President.
Access Board, The. Organizations>Web Design>Accessibility>Government
#27725
Access Key, HTML Accesskey Generated by JavaScript
One of the great advantages of using first letter of the link text as access key is that it can be generated by code. Conventional wisdom states that it should be done server-side. Bad that it is much easier with JavaScript.
Tverskov, Jesper. Smack the Mouse (2003). Design>Web Design>Accessibility>JavaScript
#19645
This site is a jumping-off point for information on the features and capabilities of Adobe products that enhance electronic document accessibility for people with disabilities such as blindness, low vision, and motor impairments. There are also links to resources that help people with disabilities work more effectively with Adobe software and aid authors in optimizing content for accessibility.
Adobe (2000). Design>Accessibility
#28329
Web sites should be designed to ensure that everyone, including users who have difficulty seeing, hearing, and making precise movements, can use them. Generally, this means ensuring that Web sites facilitate the use of common assistive technologies. All United States Federal Government Web sites must comply with the Section 508 Federal Accessibility Standards.
Usability.gov (2006). Design>Web Design>Accessibility>Section 508
#27300
Since the discourse over creating accessible Web pages began, the standards organizations that helped inform the new Federal rules have stressed the separation of design and content. If the Internet is to reach its full potential, content will need to be authored so that it can be rendered by a broad array of devices: browsers, assistive technologies, PDAs, and devices that have yet to be imagined. Only by separating content from design will this be possible. By following the rules in Section 508, you will be doing more than providing access for those with disabilities; you will be creating content that is available to all users, no matter what devices are used to read it.
Apple Inc. (2006). Design>Web Design>Accessibility>Section 508
#19644
Internet technologies have provided many Canadians with an enhanced sense of intellectual and economic freedom. But for many people, gaining entry to Web content is more complicated than clicking mouse and operating a modem. Some Canadians rely on assistive technologies such as text readers, audio players and voice activated devices to overcome the barriers presented by standard technologies. Others may be limited by their own technology. But old browsers, non-standard operating systems, slow connections, small screens or text-only screens should not stand in the way of obtaining information that is available to others.
Treasury Board of Canada (2000). Design>Web Design>Accessibility
#23822
Accessibility and Cascading Style Sheets
An essay from an accessibility class, on the use of CSS to increase access to a page.
Bartlett, Kynn. HTML Writers Guild (1999). Design>Web Design>Accessibility>CSS
#20048
Accessibility and Macromedia Flash MX 2004
Macromedia Flash MX 2004 helps to accelerate accessible application development with a core set of UI components. These components can automate many of the most common accessibility practices related to labeling, keyboard access, and testing and help to ensure a consistent user experience across rich applications created with Macromedia Flash MX 2004. For each component, the designer or developer need only enable the accessibility object by using the command enableAccessibility(). This includes the accessibility object with the component as the movie is compiled. Because there is no simple means of removing an object once it has been added to the component, these options are turned off by default. It is therefore very important that the designer or developer enable accessibility for each component. This step needs to be done only once for each component; it is not necessary to enable accessibility for each instance of a component.
Adobe (2003). Design>Web Design>Accessibility>Flash
#14239
Accessibility and Usability of Information Technology by the Elderly
The population of elderly people and the use of computers and the Internet are both growing at extraordinary rates in the United States. The potential exists for elderly people to improve their own lives as well as the lives of others by making more use of this technology. However, the elderly are currently among the lowest users of computers and the Internet. The common belief that older people fear or are indifferent towards technology does not fully explain this low usage. Rather, the elderly are subject to the same income and education divisions that impede accessibility to the population as a whole, as well as certain physical, cognitive, and mental impairments that come with age and can impede usability. Thus, the keys to increasing the numbers of elderly people making effective use of technology are addressing both universal accessibility and universal usability. These solutions are applicable to many other people as well, making their implementation broadly useful and cost-effective.
Browne, Hilary. Universal Usability (2000). Design>Accessibility>Online>Elderly
#19037
Accessibility Arguments Revisited
Frontend has recently completed the delivery of the first version (1.1) of the Irish National Disability Authority (NDA) IT Accessibility Guidelines. In the course of our work for the NDA over the last year we’ve talked to a wide variety groups and individuals who have an interest in accessibility and as a result of their input, our approach has shifted a little. Here’s what we found out.
Poskitt, Henry. Frontend Infocentre (2002). Design>Web Design>Accessibility>Usability
#28470
Accessibility Audit vs. Accessibility Testing
Article outlining the difference between the two accessibility evaluation methods: The accessibility audit and accessibility testing.
Moss, Trenton. Webcredible (2007). Design>Web Design>Accessibility>Methods
#20659
This document summarizes the features of the Cascading Style Sheets (CSS), level 2 Recommendation ([CSS2]) known to directly affect the accessibility of Web documents. Some of the accessibility features described in this document were available in CSS1 ([CSS1]) as well. This document has been written so that other documents may refer in a consistent manner to the accessibility features of CSS.
#25097
Accessibility from the Ground Up
This accessibility thing sure is catching on. And it’s ready for prime time. Yes, Web accessibility is growing up.
May, Matt. Digital Web Magazine (2005). Design>Web Design>Accessibility
#25088
An Accessibility Frontier: Cognitive Disabilities and Learning Difficulties
With this paper... we are primarily concerned with the problems people with cognitive and learning difficulties might have when using the web and offering a few practical suggestions on how these problems might be addressed.
Hudson, Roger, Russ Weakley and Peter Firminger. Usability.com.au (2005). Articles>Web Design>Accessibility>Cognitive Psychology
#26675
The Accessibility Hat Trick: Getting Abbreviations Right
AAA-level compliance is the ideal of accessibility, the bonus-round of accessible design: AAA-level compliant pages meet the needs of every group of users. AAA is achievable, but requires preparation and forethought.
Lieberman, Colin. List Apart, A (2006). Design>Web Design>Accessibility
#24752
Accessibility Humanized: A User-Centred Approach to Web Accessibility
Most web developers act in blindness when they design accessible websites, since they know next to nothing about disabled people and the technology they use. Accessibility guidelines and validation tools doesn't provide this insight. Accessibility should rather be approached from a user centred perspective.
Olsen, Henrik. GUUUI (2004). Design>Web Design>Accessibility>User Centered Design
#10126
The next time you open a Web browser, try this: don’t use your mouse. Use your keyboard to navigate through your favorite site. You may very well find that keyboard navigation is not at all straightforward. On Yahoo.com, for example, you must press the Tab key over 75 times to get to all the options on the home page, and you must press the Tab key 10 times just to get to the main Search frame. Many sites, such as those that extensively use Macromedia Flash, aren’t accessible using the keyboard at all. The problems described here are problems of accessibility. In some cases, relatively minor changes can make the difference between an information design that can be used by anyone and a design that excludes people with certain disabilities – or preferences.
Birge, Colin. EServer (2001). Design>Accessibility>Web Design
#26626
A strict focus on accessibility as a scorecard item doesn't help users with disabilities. To help these users accomplish critical tasks, you must adopt a usability perspective.
Nielsen, Jakob. Alertbox (2005). Design>Web Design>Accessibility>Usability
#22942
Accessibility Links and Resources
An annotated collection of dozens of online resources in web accessibilty.
#19263
This paper identifies challenges for a user–centered design process with respect to infusing accessible design practices into electronic and information technology product development. Initially, it emphasizes that when user–centered design is paramount and concurrent with accessible design, electronic and information technology can be accessible for all. Next, it provides an overview of the Americans with Disabilities Act (ADA) Section 508. Last, it provides basic accessible design heuristics that can be integrated into the design process. It concludes with recommendations for a paramount and concurrent user–centered design approach to product development.
Reece, Gloria A. STC Proceedings (2002). Articles>User Centered Design>Accessibility>Usability
#26788
Accessibility of AJAX Applications
AJAX is a smorgasbord of web technologies put together to allow dynamic client-server interactions to occur in web applications without requiring pages to reload or refresh. AJAX stands for Asynchronous JavaScript And XML. AJAX itself is not a technology--it is a combination of technologies used in a certain way.
WebAIM (2006). Design>Web Design>Accessibility>Ajax
