Recommended
Recommended
More Related Content
Similar to Accessible Design in Open Source (FOSDEM 2015)
Similar to Accessible Design in Open Source (FOSDEM 2015) (20)
Recently uploaded
Recently uploaded (20)
Accessible Design in Open Source (FOSDEM 2015)
- 1. 1 Accessible Design in Open Source Christophe Strobbe Stuttgart Media University / Hochschule der Medien FOSDEM 2015
- 2. 2 Liberté #0 / Freedom #0 http://liberte0.org/wiki/
- 5. 5 0.4%
- 12. 12 Ageing
- 13. 13 The “Ageing of Europe” Public Domain; Wikipedia
- 14. 14 Ageing world population Wikipedia; based on UN World Population Prospect, 2008
- 15. 15 20% over 45 (UN 2012)
- 16. 16 15% age 65-74: declining eyesight
- 17. 17 55% age 60+: deaf or hard of hearing
- 20. 20 Components of accessibility: Open Accessibility Framework
- 23. 23 1. Define “Accessible” ● Web Content Accessibility Guidelines 2.0 ● European standard ETSI EN 301 549 ● ISO/IEC TR 13066-3:2012: IAccessible2 API ● ISO 14289-1:2012: PDF for Universal Accessibility (PDF/UA)
- 24. 24 2. Stock/re-usable components ● Web: Dijit, jQuery UI, Fluid Infusion, … ● Standard Widget Toolkit (SWT) ● WxWidgets ● Java Swing
- 26. 26 3. Developer tools: DIAS ● Simulation of visual impairments in DIAS (NetBeans plugin) ● http://sourceforge.n et/projects/diasnb/
- 27. 27 4. Support “Accessible” in the platform
- 29. 30 Automatic adaptation: from Linux
- 30. 31 Automatic adaptation: to Windows
- 33. 34 Where is this being done? ● Debian: http://www.debian.org/devel/debian- accessibility/ ● Gnome: https://wiki.gnome.org/Accessibility ● Mozilla: https://developer.mozilla.org/en- US/docs/Web/Accessibility
- 34. 35 More examples ● Guadalinex: http://www.guadalinex.org/ ● OpenOffice & LibreOffice ● Specialised distros: Sonar GNU/Linux, Vinux ● Kolibre: www.kolibre.org
Editor's Notes
- One of the groups I represent is Liberté #0 / Freedom #0, a fairly young association that promotes accessibility in free and open source software. The association’s wiki is available at http://liberte0.org/wiki/. The wiki is currently in French only, but there is also an English mailing list at http://sympa.liberte0.org/sympa/info/tech.
- I also represent the European project Cloud4all, which is one of the projects that is contributing to the Global Public Inclusive Infrastructure or GPII. One of the goals of GPII is to make user interfaces adapt to the needs and preferences of the user. (More about this will be said in the second half of this presentation.)
- Accessibility is usually defined as the extent to which products, devices, services or environments can be used by people with disabilities. Persons with disabilities are often seen as a niche market. Looking at a few statistics may confirm this idea …
- Roughly 0.4% of the population is blind. (Blind persons can use a screen reader to access a computer. A screen reader attempts to identify and interpret what is visible on the screen and output it as Braille or synthetic speech. The image shows a laptop resting on a Braille display. Braille displays are very expensive devices and not every blind person knows Braille, so many people simply use synthetic speech instead of Braille.)
- Roughly 0.1% of the population is deaf. (The screenshot show SignLinkStudio, a tool for signlinking, i.e. adding links directly into sign videos on the Web. See http://www.signlinkstudio.com/. People who were born deaf typically use a sign language as their native language.) Image source: http://www.signlinkstudio.com/en/index.php (copyright Ryerson University, The Canadian Hearing Society, ATRC, Signencode & Canadian Heritage).
- Roughly 0.1% of the population cannot use their fingers. This can have a variety of reasons, such as missing limbs, extreme tremor, quadriplegia, muscular dystrophy, multiple sclerosis (MS) or amyotrophic lateral sclerosis (ALS). The theoretical physicist Stephen Hawking has been paralysed by ALS. A recent article in Wired describes his assistive technologies: he uses an on-screen keyboard, word predction software and a “cheek switch”. See “Giving Stephen Hawking a Voice”, Wired, 2 Dec. 2014. The animation on the right shows how scanning an on-screen keyboard works. Image sources: https://archive.org/details/200804210005HQ (public domain) https://commons.wikimedia.org/wiki/File:AnimatedTyping_by_ScanningExample.gif (CC-BY-SA 3.0)
- At least 1% of the population is dyslexic (estimations vary greatly).
- Image source: https://commons.wikimedia.org/wiki/File:Europe_population_over_65.png (public domain, based on materials that originally came from the United States Central Intelligence Agency's World Factbook). Image used in https://en.wikipedia.org/wiki/Ageing_of_Europe.
- Image source: https://commons.wikimedia.org/wiki/File:Percentage_of_the_World_Population_Over_65_-_1950-2050.png (CC-BY 3.0; source: UN World Population Prospect, 2008.)
- 60 or 65 years of age may seem a long time in the future for many of us, but we will reach that age and by likely to be faced with one or more of the impairments on the previous slides. For this reason, practicing accessible design is also designing for our future selves.
- Accessibility can be thought of as the outcome of several steps or components as defined in the Open Accessibility Framework (OAF). The concept of the OAF was formulated by Peter Korn during the AEGIS project (2008-2012, http://www.aegis-project.eu/). See also https://www.youtube.com/watch?v=X8miIhqQ3MU and https://en.wikipedia.org/wiki/Computer_accessibility#Open_Accessibility_Framework.
- Quoted from https://en.wikipedia.org/wiki/Computer_accessibility#Open_Accessibility_Framework The “creation” steps describe the necessary precursors and building blocks to enable developers to create accessible applications and products. They are: Define what “accessible” means for the platform: It must be clear what is meant by “accessible” because this will differ according to the modality and capabilities of each platform. The definition may include accessibility features such as tabbing navigation, theming, and an accessibility API. 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 the platform. Provide authoring tools that support accessibility: The tools used by application developers and content authors must be implemented to encourage use of the accessibility features of the platform. This may include features such as encouraging the use of accessible stock user interface elements, prompting for information required to properly implement an accessibility API, and accessibility evaluation and repair tools.
- Quoted from https://en.wikipedia.org/wiki/Computer_accessibility#Open_Accessibility_Framework The “use” steps describe what is necessary in the computing environment in which these accessible applications will run. They are: Provide platform support: Computing platforms must properly implement the accessibility features that are specified in their accessibility definition. For example, the accessibility API definitions must, in fact, be implemented correctly in the program code. Provide accessible application software: Accessible applications must actually be available for the platform. These applications must support the accessibility features of the platform. This may have been achieved using the accessible stock elements and authoring tools that support accessibility. Provide assistive technologies: Assistive technologies (e.g. screen readers, screen magnifiers, voice input, adapted keyboards) must actually be available for the platform.
- Image sources: SWT: http://www.eclipse.org/swt/ (© 2015 The Eclipse Foundation) Audacity: from https://www.wxwidgets.org/about/screenshots/ (© wxWidgets?)
- (Source ??)
- Image source: http://www.accessible-project.eu/index.php/dias-detailed-information.html (© 2008-2010 ACCESSIBLE Consortium)
- Image source: https://developer.gnome.org/accessibility-devel-guide/stable/gad-how-it-works.html.en (© 2005‒2014 The GNOME Project)