#23304
Evaluation of Websites for Older Adults: How "Senior-Friendly" Are They?
Thirty-six websites designed for older adults were evaluated as to how well they complied to 25 'senior-friendly' guidelines recommended by the National Institute of Aging. Results indicate that a majority of the sites complied to guidelines related to basic navigation and content style but not for text size, text weight, or site map availability. Implications of compliance to these guidelines on user satisfaction and performance are discussed.
Hart, Traci A. Usability News (2004). Design>Web Design>Accessibility>Elderly
#23082
Examples: WAI Web Content Accessibility Curriculum
Provides details or examples of one or more techniques that are associated with a particular checkpoint. Where possible, the examples are actually coded so that you will see how that particular technique displays or renders on your browser or user agent. In most cases, the markup that creates the 'live' example is also provided (although you can also 'View Source' to get the exact coding). Where necessary, some text is included to explain what is 'supposed' to happen (for example, if an HTML 4 attribute is not widely supported yet), or for user of non-graphical or older browsers.
Letourneau, Chuck and Geoff Freed. W3C. Design>Web Design>Accessibility>Education
#23000
Expanding Your Training Skills and Knowledge
Becoming an effective accessibility trainer and teacher does not happen overnight. For some, the ability to effectively teach others comes naturally. For others, a lot of work is involved. An accessibility trainer must be a Jack-of-all-trades, and an Ace of a few as well. The more tools you have at your convenience, the more effective you will be.
WebAIM (2005). Design>Web Design>Accessibility
#20367
Facts and Opinion About Fahrner Image Replacement
Fahrner Image Replacement and its analogues aim to combine the benefits of high design with the requirements of accessibility. But how well do these methods really work? Accessibility expert Joe Clark digs up much-needed empirical data on how FIR works (and doesn’t) in leading screen readers.
Clark, Joe. List Apart, A (2003). Design>Web Design>Accessibility>Usability
#22970
Fast Track to Web Accessibility in 5 Steps
Sometimes you don't have the time to sit down and plan out the ideal Web site. Maybe you've just recently been appointed as your organization's webmaster, or have recently been assigned to oversee accessibility operations at your organization, and you discover that your Web site has gaping holes in its accessibility. Rather than panic, you should start with the biggest problems and work your way through the site until you have fixed all of the accessibility errors. After you've 'plugged the holes,' then you can start thinking about a new design, but not until then. This workshop presents a 'fast track to accessibility' that prioritizes your tasks of sorting through and fixing your site's accessibility problems.
Bohman, Paul. WebAIM (2003). Design>Web Design>Accessibility>Project Management
#20655
The criteria for web-based technology and information are based on access guidelines developed by the Web Accessibility Initiative of the World Wide Web Consortium. Many of these provisions ensure access for people with vision impairments who rely on various assistive products to access computer-based information, such as screen readers, which translate what's on a computer screen into automated audible output, and refreshable Braille displays. Certain conventions, such as verbal tags or identification of graphics and format devices, like frames, are necessary so that these devices can 'read' them for the user in a sensible way. The standards do not prohibit the use of web site graphics or animation. Instead, the standards aim to ensure that such information is also available in an accessible format. Generally, this means use of text labels or descriptors for graphics and certain format elements. (HTML code already provides an 'Alt Text' tag for graphics which can serve as a verbal descriptor for graphics). This section also addresses the usability of multimedia presentations, image maps, style sheets, scripting languages, applets and plug-ins, and electronic forms. The standards apply to Federal web sites but not to private sector web sites (unless a site is provided under contract to a Federal agency, in which case only that web site or portion covered by the contract would have to comply). Accessible sites offer significant advantages that go beyond access. For example, those with 'text-only' options provide a faster downloading alternative and can facilitate transmission of web-based data to cell phones and personal digital assistants.
Usability.gov. Articles>Web Design>Accessibility>Section 508
#30475
Fieldsets, Legends and Screen Readers
The grouping and labelling of thematically related controls within a form is an important aspect of providing semantic information so users can understand and complete a form successfully. Differences in quality and implementation of support across user agents can hamper some users' ability to benefit from this information. This must not be taken as disincentive to developers, as the benefits of using these elements outweighs the negatives. But it is clear that some assistive technology vendors need to improve implementation of HTML features that enhance accessibility, so their users can gain the most benefit.
Lemon, Gez. Paciello Group, The (2007). Articles>Web Design>Accessibility>Semantic
#19438
When usability expert Jakob Nielsen proclaimed Flash was 99 percent bad, he was right on at least one account: accessibility. Until the release of Flash MX and the Flash 6 player, about 41 million disabled Web users could not take full advantage of Flash Web sites (According to World Bank in 2000). Even with Macromedia's move to support Section 508 guidelines, the government's plan for Web accessibility, the majority of Flash developers have not adopted the necessary best practices. Advertisement In previous versions of the Flash player, disabled Web users were unable to view any content generated by Flash. The Flash 6 player took a big step in this regard by retroactively providing text equivalents to the application's content. This change has allowed assistive Web browsers such as screen readers to view or speak Flash content. Many Flash developers question the need for Flash accessibility since proper accessibility requires a text-only version of existing Web content. This is a myth: images and animation can actually help users with nonvisual disabilities such as dyslexia. Flash can also benefit the blind by incorporating sound to notify the Web surfer of events.
Perry, Jason Michael. O'Reilly and Associates (2002). Design>Web Design>Accessibility>Flash
#13668
Those succeeding with Flash usually apply it as an element and mix it with other technologies or images such as streaming audio and video, GIF, JPG, DHTML, and CGI to name a few. Determine what elements you need on your site and study the strengths and weaknesses of each technology to determine which option would work best for each element. You're in good shape if you can use Flash without sacrificing accessibility, readability, navigability, usability, searchability, and ability to update.
Evans, Meryl K. Digital Web Magazine (2002). Design>Accessibility>Multimedia>Web Design
#27669
Formal Objection to WCAG Claiming to Address Cognitive Limitations
Lisa Seeman intends to make a formal objection about WCAG 2.0's claim that they address all requirements for learning difficulties and cognitive limitations, as they do not have the success criteria to back up their claim. Moreover, there are known techniques that WCAG have not included, and people who do intend to cater for people with learning difficulties and cognitive limitations would benefit from knowing of these techniques.
Seeman, Lisa. Juicy Studio (2006). Articles>Web Design>Accessibility>Cognitive Psychology
#28298
The Future of Web Accessibility
Accessibility is currently in a great state of change - find out what the future hold for web accessibility and how this may affect your website.
Moss, Trenton. Webcredible (2006). Design>Web Design>Accessibility
#18630
Getting Started: Making a Web Site Accessible
An initial introduction to resources for people new to Web accessibility.
Brewer, Judy. W3C (2002). Design>Web Design>Accessibility
#10043
An accessible site allows all users to access it, regardless of their browser, resolution, settings, or eyesight. Accessible sites are open to the world's 750 million disabled people, including the sizeable blind population. Through better authoring, Web information providers can avoid shutting out the world's disabled population from the information age, and can garner a good portion of this largely ignored market.
Quinn, Liam. Web Design Group, The (1997). Design>Accessibility>Web Design
#13281
Guidelines for Accessible Web Site: Technology and Users 
Accessible design goes beyond accommodating the mentally or physically impaired. With new technologies and greater global access, accessible design now includes technological as well as user considerations.
Ward, Michele, Philip Rubens and Sherry Southard. STC Proceedings (2000). Presentations>Accessibility>Web Design
#19186
Guidelines for Writing Accessible Online Help
This article describes how to write effective on-line help for blind and low vision users of text based readers. The authors draw on their collective experience in both using text (screen) readers like JAWS to access web applications as well as preparing accessibility help for web pages and applications. This article doesn't include specific information about building web interfaces or sites, use of controls for accessibility within web sites, Section 508 or WAI Standards and Guidelines, or specific information about hardware or software. We include JAWS instructions as an example because it is commonly used in the United States. Also, we don't include information about actual language used within an interface and how to write it to make the interface more accessible. We are only discussing how to write Help pertaining to the interface itself.
Reed, Will, Everyl Yankee and Wendi Fornoff. Usability Interface (2003). Design>Web Design>Accessibility>Visual
#23010
Most developers don't think about individuals who are deaf when they think of Web accessibility. For too many developers, Web accessibility consists of adhering to a few guidelines that ensure accessibility to screen readers for the blind. On one level, this is understandable. People who are blind will have the most trouble, since the Web is a visual medium...or is it?
WebAIM (2001). Design>Web Design>Accessibility>Audio
#25238
For this study, we recruited low-vision users with a variety of vision problems who need software to magnify computer text. Although we did not systematically recruit for specific vision problems, the fact that our users had different needs gave us one of the most critical insights in this study: The needs of low-vision users are too diverse for simple solutions to Web accessibility and usability. We show a few ways in which today’s Web sites are missing the needs of all low-vision users and provide guidelines for fixing those problems. However, the diversity of vision needs and the resulting adaptations that low-vision users require mean that there are no simple solutions to making Web sites work for everyone. In this article, therefore, you will not find many simple guidelines. Instead, we raise a critical issue and suggest a 'vision of the future' solution.
Theofanos, Mary Frances and Janice C. 'Ginny' Redish. Technical Communication Online (2005). Design>Web Design>Accessibility>Universal Usability
#30017
HERA: Accessibility Testing with Style
HERA is a tool to check the accessibility of Web pages accoridng to the specification Web Content Accessibility Guidelines (WCAG 1.0). HERA performs a preliminary set of tests on the page and identifies any automatically detectable errors or checkpoints met, and which checkpoints need further manual verification.
#23540
A free online tool to analyze the accessibility of websites. With Hermish, make your pages comply to accessibility guidelines. Accessibility relates to section 508 and priority levels.
Slinn, Gareth. Hermish (2004). Resources>Web Design>Accessibility>Section 508
#26471
High Accessibility Is Effective Search Engine Optimization
It’s no coincidence that search engines love highly accessible websites; in fact, by designing for accessibility, you’re already using effective search-engine optimization techniques. Andy Hagans explains yet another reason to pay attention to accessibility.
Hagans, Andy. List Apart, A (2005). Design>Web Design>Accessibility>Search
#24078
High Accessibility, High Design: CSS to the Rescue
Anyone with good graphic-design skills can use Web standards to produce attractive Web sites that function adequately for nearly all viewers and very well for most viewers – including people with disabilities. This article will explore a few details concerning the interplay of accessibility and Web design.
Voren, Naar. NaarVoren.nl (2004). Design>Web Design>Accessibility>CSS
#22935
When Apple released Safari on to the unsuspecting world in 2003, it caught a lot of people off guard. The ripples are still being felt - Mozilla's source code was rejected in favour of the smaller code base of KHTML, and more recently Opera has suggested that it may no longer make a version of its browser for the Macintosh platform. And then, of course, there's the whole issue of how web developers can keep up with yet another browser foisted upon them - does it support agreed web standards? Or does it break standards-compliant sites in horrible new inventive ways?
Lloyd, Ian and Garrett Smith. Accessify (2003). Design>Web Design>Accessibility>Web Browsers
#22065
How Disabled Users Access the Internet
There's more to web accessibility than making your website screen reader-friendly. Find out more here!
Moss, Trenton. Webcredible (2004). Design>Web Design>Accessibility
#23171
How Nationwide Tackled Accessibility - The Whole Story
A piece written by Ian Lloyd (Accessify bod) about how accessibility was worked into the project management life cycle.
Lloyd, Ian. Usability News (2003). Design>Web Design>Accessibility
#20058
How People with Disabilities Use the Web
This document provides an introduction to use of the Web by people with disabilities. It illustrates some of their requirements when using Web sites and Web-based applications, and provides supporting information for the guidelines and technical work of the World Wide Web Consortium's (W3C) Web Accessibility Initiative (WAI).
W3C (2001). Design>Accessibility>Web Design
