Wikipedia

Computer accessibility

(Redirected from Open Accessibility Framework)

Computer accessibility refers to the accessibility of a computer system to all people, regardless of disability type or severity of impairment. The term accessibility is most often used in reference to specialized hardware or software, or a combination of both, designed to enable the use of a computer by a person with a disability or impairment.

Accessibility Features

edit

Accessibility features are meant to make the use of technology less challenging for those with disabilities. Common accessibility features include text-to-speech, closed-captioning, and keyboard shortcuts. More specific technologies that need additional hardware are referred to as assistive technology.[1]

There are many disabilities or impairments that can be a barrier to effective computer use. Some of these impairments, which can be acquired from disease, trauma, or congenital disorders, include:

A topic closely linked to computer accessibility is web accessibility. Similar to computer accessibility, web accessibility is the practice of making the use of the World Wide Web easier to use for individuals with disabilities.[2]

 
a11y, numeronym of accessibility illustrated

Accessibility is often abbreviated as the numeronym a11y, where the number 11 refers to the number of letters omitted.[3] This parallels the abbreviations of internationalization and localization as i18n and l10n, respectively. Moreover, a11y is also listed on the USPTO Supplemental Register under Accessibility Now, Inc.[3]

Special Needs Assessments

edit

People wishing to overcome an impairment in order to use a computer comfortably may require a "special needs assessment" by an assistive technology consultant (such as an occupational therapist, a rehabilitation engineering technologist, or an educational technologist) to help them identify and configure appropriate assistive technologies to meet individual needs. Even those who are unable to leave their own home or who live far from assessment providers may be assessed (and assisted) remotely using remote desktop software and a web cam. For example, the assessor logs on to the client's computer via a broadband Internet connection, observes the user's computer skills, and then remotely makes accessibility adjustments to the client's computer where necessary.

Accessibility options for specific impairments

edit
 
BBC News shown in 'desktop mode,' with accessibility links at the top. The screenshot is taken from Windows Mobile.[needs update]
 
A single-switch assistive device that enables the user to access an on-screen keyboard

Cognitive impairments and illiteracy

edit

The biggest challenge in computer accessibility is to make resources accessible to people with cognitive disabilities—particularly those with poor communication and reading skills. For example, people with learning disabilities may rely on proprietary symbols and identify particular products via the product's symbols or icons. Unfortunately, copyright laws can limit icon or symbol release to web-based programs and websites by owners who are unwilling to release them to the public.

In these situations, an alternative approach for users who want to access public computer-based terminals in libraries, ATMs, and information kiosks is for the user to present a token to the computer terminal - such as a smart card - that has configuration information to adjust the computer speed, text size, etc. to their particular needs.

This concept is encompassed by the CEN standard "Identification card systems – Human-machine interface".[4][5] This development of this standard has been supported in Europe by SNAPI and has been successfully incorporated into the Local Authority Smartcards Standards e-Organisation (LASSeO) specifications.[6]

Visual impairment

edit

Since computer interfaces often require visual input and provide visual feedback, another significant challenge in computer accessibility involves making software usable by people with visual impairments.

For people with mild to medium vision impairment, things like large fonts, high DPI displays, high-contrast themes and icons combined with auditory feedback and screen magnifying software are very useful. In the case of severe vision impairment such as blindness, screen reader software that provides feedback via text to speech or a refreshable braille display is a necessary accommodation for interaction with a computer.

About 8% of men and about 0.4% of women have some form of color-blindness.[7] The main color combinations that might be confused by people with visual deficiency include red/green and blue/yellow. However, in a well-designed user interface, color isn't the primary way to distinguish between different pieces of information.

Motor and dexterity impairments

edit

Some people may not be able to use a conventional input device, such as the mouse or the keyboard. Therefore, it is important for software functions to be accessible using both devices. Ideally, the software will use a generic input API that permits the use even of highly specialized devices unheard of at the time of software's initial development. Keyboard shortcuts and mouse gestures are ways to achieve this access, as are more specialized solutions, including on-screen software keyboards and alternate input devices (switches, joysticks and trackballs). Users may enable a bounce key feature, allowing the keyboard to ignore repeated presses of the same key. Speech recognition technology is also a compelling and suitable alternative to conventional keyboard and mouse input as it simply requires a commonly available audio headset.

UI design can also improve accessibility for users with motor impairments. For example, barrier pointing design allows commonly-used functions to require less accuracy to select.

The astrophysicist Stephen Hawking is an example of someone with severe motor and physical limitations who used assistive technology to support activities of daily living. He used a switch, combined with special software, that allowed him to control his wheelchair-mounted computer using his limited and small movement ability. This personalized system allowed him to remain mobile, do research, and produce his written work. Prof. Hawking also used augmentative and alternative communication technology to speak and an environmental control device to access equipment independently.

A small amount of modern research indicates that utilizing a standard computer mouse device improves fine-motor skills.[8]

Hearing impairment

edit

While sound user interfaces have a secondary role in common desktop computing, these interfaces are usually limited to using sound effects as feedback. Some software producers take into account people who cannot hear due to hearing impairments, silence requirements, or lack of sound-producing software. The system sounds like beeps can be substituted or supplemented with visual notifications and captioned text (akin to closed captioning). Closed captions are a very popular means of relaying information for the Deaf and hearing-impaired communities. Modern computer animation also allows for translation of content into sign language by means of sign language avatars, such as SiMAX.[9][10]

Types of software accessibility

edit

Accessibility application programming interfaces

edit

Software APIs (application programming interfaces) exist to allow assistive technology products such as screen readers and screen magnifiers to work with mainstream software. The current or past APIs include:

Some of these APIs are being standardized in the ISO/IEC 13066 series of standards.[16][17]

Accessibility features in mainstream software

edit

Accessibility software can also make input devices easier to access at the user level. These include:

Support for learning disabilities

edit

Other approaches may be particularly relevant to users with a learning disability. These include:

Open Accessibility Framework

edit

The Open Accessibility Framework (OAF)[22] provides an outline of the steps that must be in place in order for any computing platform to be considered accessible. These steps are analogous to those necessary to make a physical or built environment accessible. The OAF divides the required steps into two categories: creation and use.

The "creation" steps describe the precursors and building blocks required for technology developers to create accessible applications and products. They are as follows:

  1. Define what "accessible" means for the identified use of the platform. It must be clear what is meant by "accessible" as this will differ according to the modality and capabilities of each platform. Accessibility features may include tabbing navigation, theming, and an accessibility API.
  2. Provide accessible stock user interface elements. Pre-built "stock" user interface elements, used by application developers and authoring tools, must be implemented to make use of the accessibility features of a platform.
  3. Provide authoring tools that support accessibility. Application developers and content authors should be encouraged to implement tools that will improve the accessibility features of a platform. Using these tools can support accessible stock user interface elements, prompt for information required to properly implement an accessibility API, and identify accessibility evaluation and repair tools.

The "use" steps describe what is necessary for the computing environment in which these accessible applications will run. They are as follows:

  1. Provide platform supports. Computing platforms must properly implement the accessibility features that are specified in their accessibility definition. For example, the accessibility API definitions must be implemented correctly in the program code.
  2. Provide accessible application software. Accessible applications must be available for the platform and they must support the accessibility features of the platform. This may be achieved by simply engaging the accessible stock elements and authoring tools that support accessibility.
  3. Provide assistive technologies. Assistive technologies (e.g. screen readers, screen magnifiers, voice input, adapted keyboards) must actually be available for the platform so that the users can effectively interface with the technology.

The following examples show that the OAF can be applied to different types of platforms: desktop operating systems, web applications[23] and the mobile platform. A more complete list can be found in the Open Source Accessibility Repository by the Open Accessibility Everywhere Group (OAEG).

  1. Accessibility APIs include the Assistive Technology Service Provider Interface and UI Automation on the desktop, WAI-ARIA in web applications, and the Blackberry Accessibility API[24] on the Blackberry operating system.
  2. Other APIs are keyboard access and theming in widget libraries like Java Swing for desktop applications, the jQuery UI and Fluid Infusion[25] for Web applications, and the Lightweight User Interface Toolkit (LWUIT) for mobile applications.
  3. Support for accessible development can be effective by using Glade (for the GTK+ toolkit),[26] the DIAS plugin for NetBeans IDE,[27] Xcode IDE for iOS applications.[28] Accessibility inspection tools like Accerciser (for AT-SPI)[29] and support for accessible authoring with the AccessODF plugin for LibreOffice and Apache OpenOffice[30] also fit into this step.
  4. Support for UI Automation on Microsoft Windows,[2][31] support for ATK and AT-SPI in Linux GNOME,[32] WAI-ARIA support in Firefox,[33][34] and the MIDP LWUIT mobile runtime[35] (or the MIDP LCDUI mobile runtime) that is available on mobile phones with Java are examples of APIs.
  5. The DAISY player AMIS on the Microsoft Windows desktop[36] and the AEGIS Contact Manager for phones with Java ME[37] are designed for accessibility.
  6. The GNOME Shell Magnifier and Orca on the GNOME desktop, GNOME's ATK (Accessibility Toolkit), the web-based screen reader WebAnywhere,[38] and the alternative text-entry system Dasher for Linux, iOS and Android[39][40] are examples of assistive technologies.

The goal of the listed tools is to embed accessibility into various mainstream technologies.[41]

Positive effects of computer accessibility

edit

Effects in school

edit

Computer accessibility plays a large role in the classroom. Accessible technology can enable personalized learning for all students.

Impacts in the classroom

edit

When accessible technology allows personalized learning, there are positive impacts on students. Personalized learning switches the focus from what is being taught to what is being learned. This allows the students to need to become an integral part of the learning process. Accessibility in the classroom allows millions of students of all backgrounds to have equal educational opportunities and keep up with their non-disabled peers.[42]

When PCs are personalized for students in the classroom, students are more comfortable in the classroom, special needs students are better assisted and teachers can save time and effort.[43]

While PCs can provide a large amount of support in the classroom, iPads and apps can play a large role as well. Apps are constantly being developed to aid teachers, parents, and children. Educators have noted that the ease and portability of tablets make them a preferred choice that offers usage in a variety of environments. The advantages include interactivity, Internet access and text messaging. Educators have noticed improvements in motor skills, reading skills, and interaction with others in students.[44]

Impacts outside the classroom

edit

Parents and teachers can notice the long-term effects that accessibility has on students with disabilities. This can include enhanced social skills, better relationships with family and friends, increased understanding of the world around them, and an exhibition of self-reliance and confidence. Changes can be seen in not only children but adults as well. Social media can help parents to learn, share knowledge, and receive moral support.[44][45]

Effects in the workplace

edit

Computer accessibility plays a large role in the workplace. In the past few years, adults have had their disabilities accommodated by the ability to work from home and by the availability of reliable software. This allows workers to work in a comfortable area while still being able to support themselves. This is allowing thousands of people with disabilities to create and earn jobs for themselves. The inexpensiveness and reliability of computers has facilitated the process.[46]

Standards and regulations regarding computer accessibility

edit

Section 508 of the Rehabilitation Act of 1973

edit

Section 508 requires US Federal agencies make their electronic and information technology (EIT) accessible to all disabled employees and members of the public. The US Access Board develops and maintains the Information and Communication Technology (ICT) accessibility standards.[47] The Access Board issued a final rule that went into effect on January 18, 2018, updating accessibility requirements under Section 508. This final rule requires that all electronic content generated by US Federal agencies must conform to Level A and Level AA success criteria in WCAG 2.0, with four exceptions for non-Web documents: 2.4.1 Bypass Blocks, 2.4.5 Multiple Ways, 3.2.3 Consistent Navigation, and 3.2.4 Consistent Identification.[48]

International Standards

edit
ISO 9241-171:2008

ISO 9241-171:2008 is a standard that provides ergonomics guidance and specifications for the design of accessible software for public use.

Compiled from independent standards experts, this document is the most comprehensive and technical standard for designing accessible features for software, covering all disabilities and all aspects of software. It provides examples of two priority levels ('Required' and 'Recommended') and offers a handy checklist designed to help with recording software testing results.

Because of its complexity and technical nature, and with upwards of 150 individual statements, ISO 9241-172 is difficult to interpret and apply. Luckily, not every statement is relevant to every situation, so it may be advisable to identify a subset of statements that are tailored to the particular software environment, making the use of this document much more achievable.[49]

See also

edit

References

edit
  1. ^ Wu, Ting-Fang; Meng, Ling-Fu; Wang, Hwa-Pey; Wu, Wu-Tien; Li, Tien-Yu (2002). "Computer Access Assessment for Persons with Physical Disabilities: A Guide to Assistive Technology Interventions". In Miesenberger, Klaus; Klaus, Joachim; Zagler, Wolfgang (eds.). Computers Helping People with Special Needs. Lecture Notes in Computer Science. Vol. 2398. Springer Berlin Heidelberg. pp. 204–211. doi:10.1007/3-540-45491-8_44. ISBN 978-3-540-45491-5.
  2. ^ a b Microsoft Developer Network: Accessibility (.NET Framework 4.5). Accessed 2013-01-17.
  3. ^ a b Roselli, Adrian (22 November 2016). "A11y". Adrian Roselli. Retrieved 2022-06-10. Evolving blog.
  4. ^ CEN: Personal identification, electronic signature and cards and their related systems and operations - Structure Archived 2013-10-05 at the Wayback Machine.
  5. ^ "Draft EN 1332-4 Identification Card Systems - Man-Machine Interface - Part 4 : Coding of user requirements for people with special needs". Tiresias.org. 2009-11-20. Retrieved 2013-07-28.
  6. ^ LASSeO: Feasibility Studies - Final Report Archived 2013-08-14 at the Wayback Machine. August 2011.
  7. ^ Chan X, Goh S, Tan N (2014). "Subjects with colour vision deficiency in the community: what do primary care physicians need to know?". Asia Pacific Family Medicine. 13 (1): 10. DOI:10.1186/s12930-014-0010-3.
  8. ^ Bohannon, John (December 19, 2013). "Click here to improve your motor skills". Science. Retrieved 23 December 2013.
  9. ^ "SiMAX". Sowartis. 2018. Retrieved 22 September 2020.
  10. ^ Kipp, Michael; Nguyen, Quan; Heloir, Alexis; Matthes, Silke (October 2011). "Assessing the deaf user perspective on sign language avatars". Proceedings of the 13th International ACM SIGACCESS Conference on Computers and Accessibility (ASSETS-11). 13th ACM SIGACCESS Conference on Computers and Accessibility. Dundee, Scotland: Association for Computing Machinery. pp. 107–114. doi:10.1145/2049536.2049557.
  11. ^ Oracle: Java Accessibility
  12. ^ Oracle: Java SE Desktop Accessibility (page containing a link to the Java Access Bridge).
  13. ^ ISO: ISO/IEC PRF TR 13066-6: Information technology -- Interoperability with Assistive Technology (AT) -- Part 6: Java accessibility application programming interface (API).
  14. ^ ISO: ISO/IEC PDTR 13066-4: Information Technology - Interoperability with Assistive Technology (AT) -- Part 4: Linux/UNIX graphical environments accessibility API.
  15. ^ ISO: ISO/IEC TR 13066-3:2012: Information technology -- Interoperability with assistive technology (AT) -- Part 3: IAccessible2 accessibility application programming interface (API).
  16. ^ Richard Hodgkinson: 7th Report on International ICT Accessibility Standards Proposed, Being Developed and Recently Published Archived 2013-06-17 at the Wayback Machine. 3 October 2008.
  17. ^ Richard Hodgkinson: 10th Report on International ICT Accessibility Standards Proposed, Being Developed and Recently Published Archived 2013-03-18 at the Wayback Machine. 26 June 2009.
  18. ^ Microsoft: Using ClickLock
  19. ^ Microsoft: To turn on ToggleKeys. Windows XP Professional Product Documentation.
  20. ^ Bates, Roger; Jones, Melanie (2003). "Using Computer Software To Develop Switch Skills". 2003 [Technology and Persons with Disabilities] Conference Proceedings. Archived from the original on 2007-02-03. Retrieved 2007-02-08.
  21. ^ Hawes, Paul; Blenkhorn, Paul (2002). "Bridging the Gap between Aspiration and Capability for Aphasic and Brain Injured People". 2002 [Technology and Persons with Disabilities] Conference Proceedings. Archived from the original on 2007-02-03. Retrieved 2007-02-08.
  22. ^ AEGIS Consortium: AEGIS OAF and high-level architecture. Accessed 2013-01-17.
  23. ^ AEGIS Consortium: AEGIS Architecture Definition. Accessed 2013-01-17.
  24. ^ Research in Motion (RIM): Package net.rim.device.api.ui.accessibility. BlackBerry JDE 6.0.0 API Reference. Accessed 2013-01-17.
  25. ^ Fluid Infusion. Accessed 2013-01-17.
  26. ^ Glade - A User Interface Designer. Accessed 2013-01-17.
  27. ^ DIAS Netbeans IDE plugin & Standalone. Accessed 2013-01-17.
  28. ^ Apple Inc.: Xcode 4. Accessed 2013-01-17.
  29. ^ Accerciser.
  30. ^ AccessODF. Accessed 2013-01-17.
  31. ^ Microsoft Windows Dev Center: UI Automation (Windows). Accessed 2013-01-17.
  32. ^ GNOME Dev Center: Introducing ATK, AT-SPI, GAIL and GTK+. Accessed 2013-01-17.
  33. ^ Access Mozilla. Accessed 2013-01-17.
  34. ^ Access Firefox: Firefox Accessibility Features. Accessed 2013-01-17.
  35. ^ AEGIS Consortium: LWUIT - Mobile Accessibility. Accessed 2013-01-21.
  36. ^ DAISY Consortium: AMIS: DAISY 2.02 & DAISY 3 Playback Software. Accessed 2013-01-17.
  37. ^ AEGIS Contact Manager. Accessed 2013-01-17.
  38. ^ WebInSight: WebAnywhere: A Screen reader on the go Archived 2016-05-23 at the Portuguese Web Archive. Accessed 2013-01-17.
  39. ^ Inference Group (University of Cambridge): Mobile Dasher. Accessed 2013-01-17.
  40. ^ Dasher for iOS on iTunes. Accessed 2013-01-17.
  41. ^ Iosif Klironomos, Julio Abascal, Ilse Bierhoff: D3.1 Report with background material needed to support the SDDP-2 Meeting: An Introduction to the Key Issues Relating to Accessible User Interfaces. Accessed 2013-01-17.
  42. ^ Hasselbring, Ted; Williams Glaser, Candyce (March 2012). "Use of Computer Technology to Help Students with Special Needs". The Future of Children. 10 (2): 102–22. doi:10.2307/1602691. JSTOR 1602691. PMID 11255702. ProQuest 222336763.
  43. ^ "Accessibility in Education" (PDF). Microsoft. 2011.
  44. ^ a b "Technology Opens Communication for Children with Special Needs". webaccess.psu.edu. Retrieved 2019-12-11.
  45. ^ Lourenço, Gerusa Ferreira; Mendes, Enicéia Gonçalves (2015-03-01). "Adaptação transcultural de um instrumento para avaliar a acessibilidade de alunos com paralisia cerebral ao computador" [Cross-cultural adaptation of an instrument to computer accessibility evaluation for students with cerebral palsy]. Cadernos de Terapia Ocupacional (in Portuguese). 23 (1): 85–100. doi:10.4322/0104-4931.ctoAO498. ISSN 0104-4931.
  46. ^ Joachim, David S. (2006-03-01). "Computer Technology Opens a World of Work to Disabled People". The New York Times. ISSN 0362-4331. Retrieved 2019-12-13.
  47. ^ "Section508.gov". www.section508.gov. Retrieved 30 March 2023.
  48. ^ "U.S. Access Board - Revised 508 Standards and 255 Guidelines".
  49. ^ "ISO 9241-171:2008". ISO. Retrieved 2019-12-13.
edit
Listen to this article (7 minutes)
 
This audio file was created from a revision of this article dated 17 September 2006 (2006-09-17), and does not reflect subsequent edits.
(Audio help · More spoken articles)
 
Wikimedia Commons has media related to Computer accessibility.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Computer_accessibility&oldid=1259485323#Open_Accessibility_Framework"