categoryallspace2-Design Web Design Accessibility http://tc.eserver.org/dir/Design/Web-Design/Accessibility A directory of resources about design and web design and accessibility in the field of technical communication. en-us Copyright (c) 2005-08 by the EServer. All rights reserved. tclib-editorial@eserver.org (TC Library Editorial Board) webmaster@eserver.org (Geoffrey Sauer) http://tc.eserver.org/images/newlogo.gif http://tc.eserver.org/dir/Design/Web-Design/Accessibility http://tc.eserver.org/31073.html http://tc.eserver.org/31073.html When you design or modify Web sites to allow access to people with disabilities, you make the Web accessible. New Web sites and applications, however, are introducing new problems and barriers. There are complex graphics and multimedia applications that assistive technology simply has not solved. One solution to these new problems is to put accessibility in the hands of the Web developer and content author. Creating a Web site that is accessible by people with disabilities is relatively easy as long as the Web developer and author follow some basic guidelines. http://tc.eserver.org/31058.html http://tc.eserver.org/31058.html Discover the accessibility problems caused by AJAX and how it can be used to enhance web accessibility. http://tc.eserver.org/31059.html http://tc.eserver.org/31059.html Web developers often make the same errors as each other when implementing accessibility - find out what these are and how to avoid making these mistakes. http://tc.eserver.org/30821.html http://tc.eserver.org/30821.html The Stomper Scrutinizer is a webkit based browser that includes a simulation of human foveal and peripheral vision. By providing a realistic distortion of non-focused page content, the Scrutinizer reveals the perceptability of design features. It is also useful for conducting usability tests, design reviews, and has a number of features (including screenshots) for talking about design. http://tc.eserver.org/30765.html http://tc.eserver.org/30765.html Visually impaired people suffer from no faults of their own. This is quite worthy of consideration that a little more efforts toward adoption of certain features in your web site can help them retrieve information in the desired manner. Their ease of accessibility to your web site will not go unrewarded; they can well augment your business interests by turning into your most valuable customers. http://tc.eserver.org/30604.html http://tc.eserver.org/30604.html This document assesses WordPress 2.01 against the Authoring Tool Accessibility Guidelines 1.0. http://tc.eserver.org/30605.html http://tc.eserver.org/30605.html 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. http://tc.eserver.org/30557.html http://tc.eserver.org/30557.html The article underscores one of the key weaknesses in Section 508 today: the lack of self-regulation and commitment to Section 508 by federal agencies. Since Section 508 was released in June 2001, the primary enforcement focus has been on industry's role and responsibility. The pervasive thinking was that compliance could be better achieved by ensuring that industry designed, developed, and delivered accessible electronic and information technology for agency procurement. And there seems to be merit to this way of thinking. But if federal contracting and procurement officers do not include the 508 requirements as part of their procurement request documentation, industry has no motivation to invest money and resources required to enhance their products for accessibility. http://tc.eserver.org/30471.html http://tc.eserver.org/30471.html Charles L. Chen and T. V Raman have developed a common JavaScript framework to enhance the accessibility of AJAX-based applications. The framework is called AxsJAX, pronounced, 'Access JAX.' http://tc.eserver.org/30473.html http://tc.eserver.org/30473.html This article will explain how it is possible to apply WCAG 1.0 (and also how to comply with the future WCAG 2.0 and ISO 9241-151) to create an accessible e-shop shopping-cart and backend management system, analyzing the problems and the proposed solutions. http://tc.eserver.org/30475.html http://tc.eserver.org/30475.html 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. http://tc.eserver.org/30472.html http://tc.eserver.org/30472.html When an element is hidden with display: none, the browser doesn't generate a box for the element; the element is not visible on the screen, and the layout of the page isn't effected by the element. As screen readers are supposed to read the screen, it makes sense that they do not announce content that is hidden with display: none. http://tc.eserver.org/30299.html http://tc.eserver.org/30299.html Bobby tools can help you know some real touches you can give to your web site to enrich its accessibility. Since the Bobby document is the generalization of strategies and techniques to further web site usability concern, you can selectively and optimally adopt them to serve your purpose the best way. http://tc.eserver.org/30017.html http://tc.eserver.org/30017.html 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. http://tc.eserver.org/29758.html http://tc.eserver.org/29758.html Internetministeriet fokuserer på webdesign og SEO ud fra et tilgængeligheds og anvendeligheds -princip. http://tc.eserver.org/29733.html http://tc.eserver.org/29733.html This paper presents two sides of a debate over user-controlled text sizing of Web-based documents, and a suggested approach for designing Web sites that support full use of user-controlled text sizing, while maintaining the integrity of a site’s visual design. http://tc.eserver.org/29657.html http://tc.eserver.org/29657.html Although there is myriad research on the Internet and the web, there is limited research on sex and gender differences in web use, especially regarding navigating websites. As a step towards understanding possible differences, I draw from an extensive research study on sex and gender differences in web use. From this study, I present three key areas of sex differences in web navigation and two key areas of gender differences. Along with these differences, I provide several implications for web design. I recommend technical communicators consider not only these differences, but other possible differences to better create truly 'users'-centered design. http://tc.eserver.org/29658.html http://tc.eserver.org/29658.html Making accessible design part of your Web site management routine is not simple. Habit, practicalities, and even your Web publishing software seem to work against you, making it easy to skip important aspects of accessible design. This paper attempts to outline a framework for including accessible design in your Web publishing routine. Accessible design is the result the interaction of seven design aspects and two management processes. The design aspects are standards, structure, alternative texts, labeling, timing, linearity, and usability. The management processes are site design and page design. Developing a workflow that incorporates the seven aspects into the two processes, dealing with each aspect appropriately within each process, is our objective. http://tc.eserver.org/29877.html http://tc.eserver.org/29877.html Assuring the accessibility of a Web site is an ongoing process. Hear how the Web team for the AccessAbility SIG redesigned the SIG's Web site to incorporate more accessible features and how they stay on the accessibility road. http://tc.eserver.org/29687.html http://tc.eserver.org/29687.html The author shares some stories from her own life that may be useful in helping Web page designers and product developers better understand issues surrounding low vision, hearing loss, and mobility restrictions using her 'art of accommodation.' In this article, she discusses this art as it applies to seven areas: (1) reading structural cues and wayfinding, (2) multimedia, (3) graphics, (4) text design and visual threshold, (5) contrast, (6) glare and size of electronic displays, and (7) mobility. http://tc.eserver.org/29279.html http://tc.eserver.org/29279.html Accessible design requires a deeper understanding of context. It's about providing alternative routes to information, whether that route is a different sense (seeing or hearing), a different mode, (using a tab key or a mouse), or a different journey (using an A to Z site index instead of main navigation). However, accessibility is much easier to achieve when the right foundations are put in place as prerequisites during site planning and strategy. http://tc.eserver.org/29276.html http://tc.eserver.org/29276.html The unique requirements for motor impaired web users can often be overlooked or poorly implemented. Motor impairments can be caused by a stroke, Parkinson's disease, Multiple Sclerosis (MS), a physical disability or even a broken arm. This group of users essentially have limited or no ability to use a mouse. http://tc.eserver.org/28741.html http://tc.eserver.org/28741.html A common method of limiting access to services made available over the Web is visual verification of a bitmapped image. This presents a major problem to users who are blind, have low vision, or have a learning disability such as dyslexia. This document examines a number of potential solutions that allow systems to test for human users while preserving access by users with disabilities. http://tc.eserver.org/28701.html http://tc.eserver.org/28701.html Our web applications can suffer from inaccessibility problems due to inherent markup limitations. Martin Kliehm helps us sort through the WAI specs for Accessible Rich Internet Applications (ARIA) to increase usability. http://tc.eserver.org/28470.html http://tc.eserver.org/28470.html Article outlining the difference between the two accessibility evaluation methods: The accessibility audit and accessibility testing. http://tc.eserver.org/28329.html http://tc.eserver.org/28329.html 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. http://tc.eserver.org/28298.html http://tc.eserver.org/28298.html 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. http://tc.eserver.org/28295.html http://tc.eserver.org/28295.html WCAG 2.0, the second version of the W3C's accessibility guidelines are soon to be released - find out what accessibility experts at Webcredible think of these new guidelines. http://tc.eserver.org/28237.html http://tc.eserver.org/28237.html 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. http://tc.eserver.org/28208.html http://tc.eserver.org/28208.html Many people find it difficult to read from a computer screen - especially visually impaired users, and those with reading difficulties such as dyslexia. Many people print pages out to read them later, which isn't very efficient in terms of time (as well as paper consumption). Unsurprisingly, a number of 'read aloud' applications are emerging for web sites. http://tc.eserver.org/28206.html http://tc.eserver.org/28206.html There are many reasons why you should strive to make your web site as accessible as possible: legal reasons; economic reasons; technical reasons. http://tc.eserver.org/27855.html http://tc.eserver.org/27855.html Forms are a pain. You can make them pretty, make them accessible, or go a little crazy trying to achieve both. Nick Rigby offers a happy solution. http://tc.eserver.org/27725.html http://tc.eserver.org/27725.html 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. http://tc.eserver.org/27719.html http://tc.eserver.org/27719.html The traditional way of implementing the HTML accesskey attribute using unique letters does not work. I propose always to use the first letter of the link name as access key. The first letter can be generated by code. We badly need are more accessible Internet. http://tc.eserver.org/27712.html http://tc.eserver.org/27712.html The legislation referred to as "Section 508" is actually an amendment to the Workforce Rehabilitation Act of 1973. The amendment was signed into law by President Clinton on August 7, 1998. Section 508 requires that electronic and information technology that is developed by or purchased by the Federal Agencies be accessible by people with disabilities. http://tc.eserver.org/27666.html http://tc.eserver.org/27666.html この文書は2つの質問に答えるために書いてみたんだ。 1コ目は、「なんでサイトをアクセシブルにした方がいいのか」。だから、ここの情報はサイトを持ってない人には向かないかも。 2コ目は、「じゃどうしたらサイトをアクセシブルにできるのか」。 1コ目の答えが納得できるものじゃなかったら、2コ目はどうでもいいってことになるよね。 http://tc.eserver.org/27662.html http://tc.eserver.org/27662.html 這本書要回答兩個問題：第一個問題是「為什麼該讓我的網站更具親和力？」如果妳根本就沒有網站的話，顯然就不會成為本書的讀者了。第二個問題是「該如何讓我的網站更具親和力？」如果第一個問題的回答說服不了妳，那麼第二個問題大概也將無法引起妳的興趣。 http://tc.eserver.org/27665.html http://tc.eserver.org/27665.html Questo libro risponde a due domande. La prima è "Perchè dovrei rendere più accessibile il mio sito?" E se non avete un sito web, questo libro non è per voi. La seconda domanda è "Come posso rendere il mio sito più accessibile?" Se non siete convinti della vostra prima risposta, non sarete di certo interessati alla seconda. http://tc.eserver.org/27669.html http://tc.eserver.org/27669.html 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. http://tc.eserver.org/27663.html http://tc.eserver.org/27663.html Denne boka vil besvare to spørsmål. Det første spørsmålet er «Hvorfor bør jeg gjøre nettstedet mitt mer tilgjengelig?» Om du ikke har et nettsted, så er ikke denne boka for deg. Det andre spørsmålet er «Hvordan kan jeg gjøre nettstedet mitt mer tilgjengelig?» Er du ikke overbevist av svaret på det første spørsmålet, vil du nok ikke være interessert i det andre. http://tc.eserver.org/27670.html http://tc.eserver.org/27670.html The accessibility community is understandably concerned about the accessibility of client-side scripting, in particular using Asynchronous JavaScript and XML (Ajax) to produce Rich Internet Applications. Steve Faulkner of Vision Australia and founder member of the Web Accessibility Tools Consortium (WAT-C) and myself on behalf of The Paciello Group (TPG) have collaborated in an effort to come up with techniques to make Ajax and other client-side scripting techniques accessible to assistive technology. http://tc.eserver.org/27664.html http://tc.eserver.org/27664.html Ce livre répond à deux questions. La première question est Pourquoi je dois rendre mon site web plus accessible ? Si vous n'avez pas de sites web, ce livre n'est pas pour vous. La seconde question est Comment puis-je rendre mon site web plus accessible ? Si vous n'êtes pas convaincu par la première réponse, vous ne serez pas interessé par la seconde. http://tc.eserver.org/27674.html http://tc.eserver.org/27674.html The Web Content Accessibility Guidelines 1.0 were published in 1999 and quickly grew out of date. The proposed new WCAG 2.0 is the result of five long years’ work by a Web Accessibility Initiative (WAI) committee that never quite got its act together. In an effort to be all things to all web content, the fundamentals of WCAG 2 are nearly impossible for a working standards-compliant developer to understand. WCAG 2 backtracks on basics of responsible web development that are well accepted by standardistas. WCAG 2 is not enough of an improvement and was not worth the wait. http://tc.eserver.org/27667.html http://tc.eserver.org/27667.html Niniejsza książka odpowiada na dwa pytania. Pierwsze brzmi: 'Dlaczego powinienem uczynić swoją stronę WWW bardziej dostępną?' Jeżeli nie masz strony w sieci, ta książka nie jest dla Ciebie. Drugie pytanie to 'Jak mogę uczynić moją stronę bardziej dostępną?' Jeżeli nie zostaniesz przekonany przez odpowiedź na pierwsze pytanie, nie będziesz zainteresowany odpowiedzią na drugie. http://tc.eserver.org/27605.html http://tc.eserver.org/27605.html Find out how to go beyond the W3C accessibility guidelines and offer a truly accessible web experience. http://tc.eserver.org/27551.html http://tc.eserver.org/27551.html Is there a way to display text-based data on a map, keeping it accessible, useful and visually attractive? Yes: using an accessible CSS-based map in which the underlying map data is separated from the visual layout. http://tc.eserver.org/27486.html http://tc.eserver.org/27486.html Making the web accessible by disabled people doesn't necessarily make it usable. Does simplicity always make for ideal usability - or are there instances where an innovative website might be difficult to use, but also hold usability dividends for users prepared to meet the technology halfway? http://tc.eserver.org/27485.html http://tc.eserver.org/27485.html Setting legal standards for making websites 'accessible' to all won't help web designers, or users. http://tc.eserver.org/27482.html http://tc.eserver.org/27482.html To demonstrate an example of some accessibility issues in HTML Forms, the following content intentionally has accessibility errors. http://tc.eserver.org/27483.html http://tc.eserver.org/27483.html Web accessibility evaluation tools are software programs or online services that help determine if a Web site meets accessibility guidelines. While Web accessibility evaluation tools can significantly reduce the time and effort to evaluate Web sites, no tool can automatically determine the accessibility of Web sites. http://tc.eserver.org/27477.html http://tc.eserver.org/27477.html Users with special needs who are not sufficiently visually impaired to require assistive technologies can still be frustrated by poor contrast, problematic colour schemes, or tiny, unreadable text. Up to 10% of men are colour blind to some extent, and the increasing number of older users are less likely to have 20/20 vision than those designing the pages. http://tc.eserver.org/27408.html http://tc.eserver.org/27408.html We've all heard a great deal of buzz about AJAX in the last few months, and with this talk has come a legion of articles, tips, presentations and practical APIs designed to explore the possibilities and try to arrive at best-practice techniques. But, for all of the excitement and hype, still very little has been said on the subject of AJAX and accessibility. http://tc.eserver.org/27415.html http://tc.eserver.org/27415.html Identifies web accessibility problems throughout the web generations, and summarises where we are now, and what we can expect for the future. http://tc.eserver.org/27419.html http://tc.eserver.org/27419.html Photosensitive epilepsy is a form of epilepsy that is triggered by visual stimuli, such as flickering or high contrast oscillating patterns, and it's believed that around 3% to 5% of people with epilepsy are susceptible to photosensitive material. Photosensitive epilepsy is usually triggered where the flicker rate is between 16Hz to 25Hz, although it's not uncommon for seizures to be triggered by flicker rates between 3Hz to 60Hz. The condition most commonly effects children, and is usually developed between the ages of 9 and 15 years, and most prevalent in females. http://tc.eserver.org/27420.html http://tc.eserver.org/27420.html Access keys are a contentious area of accessibility, as they can sometimes clash with the shortcut keys used by user agents. One method to get around this problem is to allow users to define their own access keys. This post suggests a PHP class that allows users to define their own access keys. http://tc.eserver.org/27423.html http://tc.eserver.org/27423.html In order to encourage vendors of non-W3C technologies to include accessibility features in their technologies, and in recognition of emerging technologies that are beneficial for the Web, WCAG 2.0 is technology neutral. Rather than list each technology that the guidelines cover, WCAG 2.0 introduces the concept of a baseline. This post attempts to explain what is meant by this baseline concept. http://tc.eserver.org/27422.html http://tc.eserver.org/27422.html 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? http://tc.eserver.org/27300.html http://tc.eserver.org/27300.html 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. http://tc.eserver.org/27178.html http://tc.eserver.org/27178.html 残障人士法案要求所提供的服务不得歧视残障人士。一个网站被认为是一种服务，因而受这一法案约束，所以必须对每个人具备无障碍性。 一些团体正在对他们的网站进行无障碍性改进，但是许多团体看起来没有采取行动。残障人士不会进入他们的网站，他们说，那为什么要在乎这些。 http://tc.eserver.org/27177.html http://tc.eserver.org/27177.html 网络无障碍性是关于使你的网站让所有因特网用户（残障用户和正常用户）易于获得，不管他们使用什么浏览技术。除了符合相关法律法规， 具备无障碍性将让您的网站和商业受益良多。 请参阅文章，《具备无障碍性的网站的益处 – 第一部分 》和《具备无障碍性的网站的益处 – 第二部分 》以了解更多关于网站的无障碍性的重要性。 http://tc.eserver.org/27140.html http://tc.eserver.org/27140.html A step-by-step guide that covers more advanced techniques for optimizing Adobe Portable Document Format (PDF) files so that they can be made accessible to users with disabilities such as blindness or low vision. http://tc.eserver.org/27141.html http://tc.eserver.org/27141.html WebABLE is an authoritative Web site for disability-related internet resources. The WebABLE site goal is to stimulate education, research, and development of technologies that will ensure accessibility for people with disabilities to advanced information systems and emerging technologies. http://tc.eserver.org/27142.html http://tc.eserver.org/27142.html 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. http://tc.eserver.org/27110.html http://tc.eserver.org/27110.html Yet those of us who are fully sighted forget that as we make the Web our main information vehicle, we may be cutting out millions of customers or potential customers. And these millions (5 to 10 million in the U.S. alone, by some estimates) have every moral and legal right to have access to that information. http://tc.eserver.org/27043.html http://tc.eserver.org/27043.html This page contains information about making the Internet accessible. http://tc.eserver.org/26849.html http://tc.eserver.org/26849.html In the first part of this article, we analyze a number of communication challenges and relate them to problems in conveying the November draft of the Web Content Accessibility Guidelines 2.0. Based on our analysis, the second part of our article offers a number of recommendations for improving the comprehensibility of the WCAG 2.0 for its various intended audiences. Although our discussion has the November draft as its focal point, the recommendations are more widely applicable to other complex documents with diverse audiences. In the final part, we propose a new vision for the WCAG. http://tc.eserver.org/26850.html http://tc.eserver.org/26850.html This article reports on a study performed for AARP on the needs of older Web users. It defines a model of older users that includes four dimensions (age, ability, aptitude, and attitude). It defines 20 heuristics, as well as personas and tasks for reviewing Web sites, and a methodology for doing persona-based, task-based heuristic review that would allow us to evaluate many sites in a relatively short time in a highly realistic way. Finally, it reports the results of an analysis of 50 Web sites for general audiences that include older adults, using that methodology. http://tc.eserver.org/26848.html http://tc.eserver.org/26848.html This annotated bibliography discusses over 120 print and online resources related to Web accessibility. It lists and describes resources that offer practical advice on how to implement accessibility, particularly in relation to the WCAG 1.0 and Section 508 standards. It also summarizes the findings of empirical studies that have examined Web site accessibility via automated tests, such as Bobby, and studies that have gauged user performance with assistive technologies, such as screen readers. The bibliography lists forums for discussing accessibility with other practitioners and researchers, and it cites sources for news and events related to accessibility. The bibliography concludes with a short discussion of trends in accessibility research. http://tc.eserver.org/26853.html http://tc.eserver.org/26853.html This article discusses accessibility barriers as defined by the World Wide Web Consortium (W3C) and provides a basic primer on how technical communicators can remove these barriers during their Web design process and test to ensure the barriers were removed. The article focuses on 10 common barriers to a meaningful experience for people with disabilities, barriers that a technical communicator can consider when designing online information. Working on accessibility issues before online information goes live will help to reduce re-work and re-design and can save a lot of headaches for a technical communicator. http://tc.eserver.org/26788.html http://tc.eserver.org/26788.html 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. http://tc.eserver.org/26789.html http://tc.eserver.org/26789.html The Ajax express train rumbles on, threatening to crush anything in its path. Recent discussion has turned to those critical elements of good web development, usability and accessibility. Accessibility is a major issue with Ajax, mainly because anything that relies on JavaScript to function is inaccessible pretty much by default. There are two solutions: either provide a fall-back system where the site remains useful without its Ajax enhancements, or provide a whole separate interface that works without scripting. http://tc.eserver.org/26766.html http://tc.eserver.org/26766.html Accessibility is about making it as easy as possible for all members of society to fully take part in that society. It is about removing barriers. It is about inclusion and empowerment. It is about creating the sort of world that we all want to live in - a message that should resonate with us all. http://tc.eserver.org/26767.html http://tc.eserver.org/26767.html The number of older web users is growing at a dramatic rate. Find out how to make your website easy to use for this lucrative market. http://tc.eserver.org/26675.html http://tc.eserver.org/26675.html 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. http://tc.eserver.org/26648.html http://tc.eserver.org/26648.html There is no question that the vast majority of tables on the Web are layout tables, used to structure the visual appearance of the page. Often the structure of tables is remarkably complex, with tables nested in tables as much as seven deep. http://tc.eserver.org/26649.html http://tc.eserver.org/26649.html CSS and XHTML have given tables a pretty rough ride in recent times. Of course, this is the fault of just about all web developers who have at some point in their career used them for laying out page elements. This article is not about using tables for layout. It is about how to use tables to display information in an accessible manner. http://tc.eserver.org/26626.html http://tc.eserver.org/26626.html 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. http://tc.eserver.org/26471.html http://tc.eserver.org/26471.html 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. http://tc.eserver.org/26363.html http://tc.eserver.org/26363.html Describes an alternative to automatic page refresh in HTML. Automatic page refresh can confuse users with cognitive disabilities when a page reloads without the user's request. This article provides you with instructions on how to apply explicit manual control of page refreshing. http://tc.eserver.org/26220.html http://tc.eserver.org/26220.html The accessibility toolbar is to aid the manual process in validating web sites. Developed by AIS and provided in Europe and the UK by Southbourne Internet Ltd. http://tc.eserver.org/26154.html http://tc.eserver.org/26154.html Most government web writers are knowledgeable about alt-text by now... or at least semi-knowledgeable. But sometimes, alt-text is not enough. http://tc.eserver.org/26144.html http://tc.eserver.org/26144.html Every country has its own requirements for public sector web sites. Legislation and policies vary greatly, and express an attitude. I base my Quality Web Content workshops for government web content writers on the policy of the country concerned. Some countries consider that an accessible site requires accessible writing. Others don't. http://tc.eserver.org/26131.html http://tc.eserver.org/26131.html It's time to take a look at the working draft of WCAG 2.0. You'll see a fresh approach to a formidable challenge. http://tc.eserver.org/26099.html http://tc.eserver.org/26099.html Find out how to improve usability and accessibility for screen reader users. http://tc.eserver.org/26100.html http://tc.eserver.org/26100.html Automated accessibility testing tools can be useful, but there are a number of disadvantages with relying on them. http://tc.eserver.org/26037.html http://tc.eserver.org/26037.html Information that will help you to create more readable Web sites. http://tc.eserver.org/25968.html http://tc.eserver.org/25968.html Describes an alternative to automatic page refresh in HTML. Automatic page refresh can confuse users with cognitive disabilities when a page reloads without the user's request. This article provides you with instructions on how to apply explicit manual control of page refreshing. http://tc.eserver.org/25801.html http://tc.eserver.org/25801.html The spread of information systems and, in particular, information infrastructure throughout the economy and social fabric raises questions about the technology's ease of use by different people, from those with limited technical know-how to those with various disabilities to the so-called power users who push for higher performance on many dimensions. http://tc.eserver.org/25515.html http://tc.eserver.org/25515.html Discover how to improve both usability and accessibility for screen magnifier users using the Internet. http://tc.eserver.org/25503.html http://tc.eserver.org/25503.html Sometimes we have to use pop-ups — so we might as well do them right. This article will show you how to make them more accessible and reliable while simplifying their implementation. http://tc.eserver.org/25505.html http://tc.eserver.org/25505.html If you choose to make standards-compliant websites, inevitably you will have to follow the guidelines. It's foreseeable that you could be legally required to follow WCAG 2.0. You could opt into following the guidelines or they could be foisted upon you. You thus have an enlightened self-interest in ensuring the new guidelines actually make sense. Moreover, we simply need more contributors. http://tc.eserver.org/25508.html http://tc.eserver.org/25508.html Activist Jim Byrne sounds off on the importance of web accessibility, and the difficulty of doing it right. http://tc.eserver.org/25502.html http://tc.eserver.org/25502.html Debunks four myths about web accessibility and the law for those involved in the design and development of UK-based websites. http://tc.eserver.org/25465.html http://tc.eserver.org/25465.html Become fluent in X+V, today's versatile Web markup language (WML). X+V, short for XHTML+Voice, is a Web markup language that is comprised of voice and visual elements used for developing multimodal applications. This article provides the novice developer of Multimodal X+V, Web pages, and handheld devices with a process for creating and testing an X+V application. This article uses the IBM® Multimodal Toolkit 4.3.2 running on WebSphere® Studio Site Developer (Site Developer) or on WebSphere Studio Application Developer (Application Developer) 5.1.2. http://tc.eserver.org/25290.html http://tc.eserver.org/25290.html 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... http://tc.eserver.org/25262.html http://tc.eserver.org/25262.html Research shows that low-vision people need dramatically different web design. CSS lets you give them what they need. http://tc.eserver.org/25238.html http://tc.eserver.org/25238.html 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. http://tc.eserver.org/25131.html http://tc.eserver.org/25131.html Learn more on how to make your online forms accessible in part 2 of this HTML form tutorial http://tc.eserver.org/25097.html http://tc.eserver.org/25097.html This accessibility thing sure is catching on. And it’s ready for prime time. Yes, Web accessibility is growing up. http://tc.eserver.org/25096.html http://tc.eserver.org/25096.html This article examines the types of problems visitors may encounter when using the web, with insightful and practical suggestions on how to develop websites that are inclusive for people with cognitive impairments and learning difficulties. http://tc.eserver.org/25092.html http://tc.eserver.org/25092.html An attempt at a definition is a good idea; if we are clear what an accessible website is, we will have a better idea of what we should be doing to build one. http://tc.eserver.org/25091.html http://tc.eserver.org/25091.html All access to web pages are mediated through some type of technology; if it isn't accessible to the machine you are using, it won't be accessible to you. http://tc.eserver.org/25088.html http://tc.eserver.org/25088.html 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. http://tc.eserver.org/24861.html http://tc.eserver.org/24861.html Learn how to make your online forms accessible in this HTML form tutorial http://tc.eserver.org/24752.html http://tc.eserver.org/24752.html 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. http://tc.eserver.org/24517.html http://tc.eserver.org/24517.html One of the lesser-known benefits of web accessibility is the fact that a website more accessible to people is also more accessible to search engines. This article outlines the ways the two areas overlap. http://tc.eserver.org/24360.html http://tc.eserver.org/24360.html In an attempt to make their sites accessible to all, more and more websites are now offering text-only versions of their sites. Find out why this is a really bad idea. http://tc.eserver.org/24344.html http://tc.eserver.org/24344.html Did you know that nearly 20 percent of all Web users have some form of disability? http://tc.eserver.org/24078.html http://tc.eserver.org/24078.html 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. http://tc.eserver.org/24082.html http://tc.eserver.org/24082.html 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. http://tc.eserver.org/24038.html http://tc.eserver.org/24038.html Discover the truth about web accessibility. This article debunks seven accessibility common myths. http://tc.eserver.org/23822.html http://tc.eserver.org/23822.html An essay from an accessibility class, on the use of CSS to increase access to a page. http://tc.eserver.org/23820.html http://tc.eserver.org/23820.html Many pages relating to web accessibility address the needs of web users who have sensory limitations -- the classic example of accessible web authoring is the proper use of the ALT attribute of the IMG (image) tag to provide a textual equivalent that benefits, among others, web users with visual impairments. Similarly, keyboard-accessible techniques can open up the World Wide Web to users who are unable to use a mouse or other 'traditional' input device due to motor or dexterity disabilities. http://tc.eserver.org/23825.html http://tc.eserver.org/23825.html An introduction to the W3C's Web Content Accessibility Guidelines. http://tc.eserver.org/23823.html http://tc.eserver.org/23823.html How you can set your own stylesheet for greater accessibility; another lecture/essay. http://tc.eserver.org/23821.html http://tc.eserver.org/23821.html How can you display that your site is accessible? Why would you want to? These questions are answered. http://tc.eserver.org/23824.html http://tc.eserver.org/23824.html A HWG position paper for a W3C workshop on voice browsers. http://tc.eserver.org/23778.html http://tc.eserver.org/23778.html 'Accessible' is a higher standard than 'Section 508-compliant.' Identifying the design principles for accessible web page design, and which of those principles are required under Section 508, is a useful approach to the issue for any organization that must comply with the Section 508 standards. The legislation has no standards for determining whether your web site complies with Section 508. Possible processes include: evaluating the site using a text-to-speech application; evaluating the site using validation software; and usability testing. http://tc.eserver.org/23787.html http://tc.eserver.org/23787.html 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. http://tc.eserver.org/23758.html http://tc.eserver.org/23758.html Accessibility for vision-impaired users of corporate websites is becoming a critical issue. The federal government requires its agencies to provide effective, equal access to electronically delivered information. The W3C launched its accessibility initiative in 1999 and continues to expand it. Court rulings are mixed, as the judicial system struggles to clarify accommodation in relation to the web environment. Students in the Jack David Armold Honor Society at DeVry University researched, collaborated, and developed a community service website to convince corporations that web accommodation for visionimpaired users made financial sense. http://tc.eserver.org/23540.html http://tc.eserver.org/23540.html 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. http://tc.eserver.org/23353.html http://tc.eserver.org/23353.html An examination of government websites (those required to adhere to Section 508) revealed no common practices or themes. http://tc.eserver.org/23304.html http://tc.eserver.org/23304.html 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. http://tc.eserver.org/23239.html http://tc.eserver.org/23239.html Review of the DRC's report into web accessibility. http://tc.eserver.org/23240.html http://tc.eserver.org/23240.html Article points out some major accessibility mistakes made by very large websites. http://tc.eserver.org/23195.html http://tc.eserver.org/23195.html 米国IBMアクセシビリティ・センターの提供情報や、IBMアクセシビリティ・リサーチ・グループによる高齢者・視覚障害者関連情報の公開など、アクセシブルな情報社会のための関連リソース。インターネット閲覧支援ソフト「らくらくウェブ散策®」の紹介など。 http://tc.eserver.org/23181.html http://tc.eserver.org/23181.html W3Cが勧告として公開している「Web Content Accessibility Guidelines 1.0」をソシオメディア監修「ウェブ・アクセシビリティ〜すべての人に優しいウェブ・デザイン」（アスキー）にて日本語訳したもの。 http://tc.eserver.org/23172.html http://tc.eserver.org/23172.html AccessiBlog was a weblog of articles and sites dealing with the topic of Web accessibility (though it is no longer updated).