Explore chapters and articles related to this topic
Accessibility vs. Usability – Where is the Dividing Line?
Published in Philip D. Bust, Contemporary Ergonomics 2006, 2020
Sambhavi Chandrashekar, Rachel Benedyk
Web accessibility for people with disabilities may be looked upon as the overcoming of barriers that make it difficult for them to use Web resources. Design criteria for Web usability have evolved over the past decade but guidelines for Web accessibility are still emerging. Issues such as whether accessibility guidelines also encompass the usability needs of users with disabilities are being debated. This study analyses the relationship between accessibility and usability and concludes that accessibility includes both access and use of resources by people with disabilities, which could be supported by a combination of a set of accessibility guidelines and a set of usability guidelines for them. It proposes a criterion of distinction between these two types of guidelines and tests the idea on an experimental website with a sample of users with visual disabilities.
Common and Assistive Technology to Support People with Specific Learning Disabilities to Access Healthcare
Published in Christopher M. Hayre, Dave J. Muller, Marcia J. Scherer, Everyday Technologies in Healthcare, 2019
Dianne Chambers, Sharon Campbell
Accessibility of web-based content is an area that should be considered, and there are a number of tools that developers/website owners can use to ensure that they are meeting the needs of all users of a website. The World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) released updated guidelines, which include reference to the success criteria for people with learning disabilities (W3C WAI, 2018). The updated Web Content Accessibility Guidelines (WCAG) 2.1 suggest that developers include autocomplete features in commonly used fields, appropriate text spacing (or the ability to work with style sheets) in relation to line height, paragraph, letter and word spacing and provide timeout warnings for users. All of these considerations are relevant to people accessing healthcare on a computer or tablet device, including tasks such as making appointments and filling in electronic forms.
Nonfunctional Testing
Published in William E. Lewis, David Dobbs, Gunasekaran Veerapillai, Software Testing and Continuous Quality Improvement, 2017
William E. Lewis, David Dobbs, Gunasekaran Veerapillai
In 1998, Congress amended the Rehabilitation Act to require federal agencies to make their electronic and information technology accessible to people with disabilities. Inaccessible technology interferes with an individual’s ability to obtain and use information quickly and easily. Section 508 was enacted to eliminate barriers in information technology, to make available new opportunities for people with disabilities, and to encourage development of technologies that will help achieve these goals. The law applies to all federal agencies when they develop, procure, maintain, or use electronic and information technology. Under Section 508 (29 U.S.C. ‘ 794d), agencies must give disabled employees and members of the public access to information that is comparable to the access available to others. Web accessibility means that people with disabilities should be able to use the Web. More specifically, Web accessibility means that people with disabilities should be able to perceive, understand, navigate, and interact with the Web, and contribute to the Web. Web accessibility also benefits others, including older people with changing abilities due to aging.
Perceptions of web accessibility guidelines by student website and app developers
Published in Behaviour & Information Technology, 2022
Previous research indicates that Web accessibility is not only crucial for individuals with disabilities, but can also aid people without disabilities, who want to gain access to information on the Web (Bell, 2014; Hochheiser and Lazar, 2007; Lawton, 2005; Lawton and Liam, 2017; Loiacono et al., 2004; Loiacono and Despande, 2014). Some companies have been forced to improve their Web accessibility by legislation or lawsuit (Loiacono and Djamasbi, 2011). Web accessibility guidelines are a key resource to design and develop accessible WEB&APPs (Loiacono, 2004; Rouse, 2010). This section addresses the existing literature regarding the benefits of Web accessibility, the costs of inaccessible WEB&APPs, the current state of Web accessibility education, as well as the effects of education on students’ perceptions and behaviour.
Moving toward a universally accessible web: Web accessibility and education
Published in Assistive Technology, 2019
However, an abundance of evaluative tools are presently available. As of mid-2017, at least 93 are listed (but not necessarily endorsed) by W3C (w3.org/WAI/ER/tools/complete). The features and characteristics of these tools vary, for instance by language (English, German, etc.), license type (open source, commercial etc.), guideline version used (WCAG 1.0 or WCAG 2.0), and operating systems (Windows, Linux etc.). Amongst the tools available, some of the more noteworthy are: Functional Accessibility Evaluator: a web based tool Developed by the University of Illinois; available at http://fae.cita.uiuc.edu/WAVE: Developed by WebAIM, which is an initiative of Utah State University, WAVE is also a web based tool; available at http://wave.webaim.org/HERA: developed by Carlos Benavídez, HERA is another web based tool; available at http://www.sidar.org/hera/index.php.enFirefox Accessibility Extension: a Firefox web browser extension created by the Illinois Center for Information Technology and Web Accessibility (iCITA); available at http://firefox.cita.uiuc.edu/Bureau of Internet AccessibilitY tool; available at http://www.boia.org/w3c-free-2-0-aa-report
Wellbeing Supportive Design – Research-Based Guidelines for Supporting Psychological Wellbeing in User Experience
Published in International Journal of Human–Computer Interaction, 2023
S1. Comply with web accessibility standards – The Web Content Accessibility Guidelines (WCAG) are a stable technical standard (ISO/IEC 40500) Composed of 14 guidelines or “success criteria” for web and mobile content.S2. Test with a variety of platforms and with a range of users - Thorough testing, and anticipation of edge cases, can help pre-empt autonomy frustrations arising from the wide diversity of real-life constraints within which users access technologies.