1. Accessibility

2. Accessibility
Accessibility refers to the design of products, devices, services, or environments for people who experience disabilities. 
Accessibility can be viewed as the "ability to access" and benefit from some system or entity. The concept focuses on enabling access for people with disabilities, or special needs, or enabling access through the use of  assistive technology for example, computer screen readers.

3. The Case for Web Accessibility
It is essential that the Web be accessible in order to provide equal access and equal opportunity to people with diverse abilities.
Accessibility supports social inclusion for people with disabilities as well as others.
Case studies show that accessible websites have better search results, reduced maintenance costs, and increased audience reach, among other benefits.

4. Web Content Accessibility Guidelines (WCAG)
Is developed through the W3C process in cooperation with individuals and organizations around the world, with a goal of proving a single shared standard for web content accessibility that meets the needs of individuals, organizations, and governments internationally.

5. WCAG documents 
 How to make web content more accessible to people with disabilities.
Web "content" generally refers to
natural information such as text, images, and sounds
code or markup that defines structure, presentation, etc.

6. The guidelines are intended for
All Web content developers (page authors and site designers)
Developers of authoring tools.

7. Following these guidelines
Promote accessibility.
 Make Web content more available to all users, whatever user agent they are using ( desktop browser, voice browser, mobile.) or constraints they may be operating under (e.g., noisy surroundings, under- or over-illuminated rooms, in a hands-free environment, etc.).
 Help people find information on the Web more quickly.

8. Guidelines(cont.)
These guidelines do not discourage content developers from using images, video, etc., but rather explain how to make multimedia content more accessible to a wide audience.

9. Techniques for WCAG 1.0
Discusses each checkpoint in more detail and provides examples using:
Hypertext Markup Language (HTML).
Cascading Style Sheets (CSS).
Synchronized Multimedia Integration Language (SMIL).
Mathematical Markup Language (MathML).
Includes techniques for document validation and testing. and an index of HTML elements and attributes .
Track changes in technology and is expected to be updated more frequently than the current document.

10. HTML Techniques for WCAG 1.0
 While the techniques in this document should help people author HTML that conforms to " WCAG 1.0“.
These techniques are neither guarantees of conformance nor the only way an author might produce conforming content.
This document is part of a series of documents about techniques for authoring accessible Web content

11. WCAG 2.0 It has 12 guidelines that are organized under 4 principles:
Perceivable
Operable
Understandable
Robust. 

12. WCAG 2.0 It has 12 guidelines that are organized under 4 principles:
Perceivable
Operable
Understandable
Robust. 

13. Better Web Browsing: Tips for Customizing Your Computer
Difficulty Seeing and Reading Websites:
Before changing the settings on your computer, make sure the screen and screen settings are optimal for you. Some screens will allow you to adjust the brightness, contrast, and other settings that effect the display. Also, make sure that the room lighting and your position in front of the screen are optimal for you.

14. Enlarging Text and Images:
In Your Web Browser:
Most web browsers will allow you to simply enlarge and reduce text and image sizes through the options in the menu bar, or by pressing "Ctrl +" and "Ctrl -" or other keyboard combinations (see browsing the Web by keyboard for more information on keyboard commands).

15. In Your Operating System:
You can also change the default display settings in the operating system of your computer, which will apply to all your applications, rather then changing only the settings of your web browser.
You can increase the default font-size which will make the text, but not the images, appear larger in all your applications.

16. Using Additional Tools:
There are screen magnifiers, some of which are built directly into your the operating system of your computer. These software tools enlarge the text and images, and can sometimes be set to read the text and the menus out loud. Vendors of such software usually provide detailed documentation on customization options and may sometimes provide training and support directly or through third-parties.

17. Changing Colors and Fonts
In Your Web Browser:
You can change the default colors for text, background, or links, and change the default font styles to make the content easier for you to distinguish and read. Several web browsers provide simple options for defining such color and font schemes, including options to reuse the color schemes of the operating system, in case you already defined custom settings.

18. Listening Rather than Reading
There are several tools that will read out loud the text on websites for you, some of which may already be installed on your computer. Talking browsers (sometimes also called "voice browsers") are web browsers that read aloud the text on websites. Screen readers and some screen magnifiers are specialized software that read aloud any text on the screen, including that in your web browser.

19. Authoring Tool Accessibility Guidelines (ATAG)
This specification provides guidelines for designing Web content authoring tools that are more accessible for people with disabilities. An authoring tool that conforms to these guidelines will promote accessibility by providing an accessible user interface to authors with disabilities as well as enabling, supporting, and promoting the production of accessible Web content by all authors.

20. Authoring Tool Accessibility Guidelines (ATAG)
The "Authoring Tool Accessibility Guidelines 2.0" (ATAG 2.0) is part of a series of accessibility guidelines published by the W3C Web Accessibility Initiative (WAI).

21. Articulate Storyline Accessibility
Articulate Storyline Is Compliant with Section Accessibility Guidelines.
Articulate Storyline’s includes support for:
JAWS readers.
Full keyboard navigation.
Visible focus indicator.
Video subtitles using timed text boxes.

22. Articulate Storyline Accessibility
Slide transcripts using the Notes tab
To view Storyline's Voluntary Product Accessibility Template (VPAT).
Note:
Content published for HTML5 and the Articulate Mobile Player isn't compliant with Section accessibility guidelines.

23. Adobe Captivate Accessibility
The most important aspect of creating accessible demonstrations and simulations with Adobe® Captivate® software is understanding the audience's varying needs; a demonstration is helpful only if it is consistent with the way the end user works with his or her computer. People who primarily use the keyboard will not be able to perform techniques that rely on the mouse, so demonstrations that describe such actions will be of little use to them.

24. Enable Accessibility for your captivate Project

25. Enable Accessibility for your captivate Project
Your Captivate project should have the Enable Accessibility preference set in the Project's Publish Settings.
Follow these steps to ensure the Publish Settings have Accessibility enabled:
Open the movie.
Choose Edit > Preferences.
Choose Publish Settings from the Project Category in the list of categories.
Check the box labelled Enable Accessibility if it is not checked.
Click OK.

26. PrincipleA.1: Authoring tool user interfaces follow applicable accessibility guidelines
Guideline A.1.1: (For the authoring tool user interface) Ensure that web-based functionality is accessible. [Implementing A.1.1] .
A Web-Based Accessible (WCAG):

27. Authoring tool user interfaces guidelines
Guideline A.1.2: (For the authoring tool user interface) Ensure that non-web-based functionality is accessible.
A Accessibility Guidelines:
If the authoring tool contains non-web-based user interfaces, then those non-web-based user interfaces follow user interface accessibility guidelines for the platform.

28. Principle A.2: Editing-views are perceivable
Guideline A.2.1: (For the authoring tool user interface) Make alternative content available to authors.
Rationale: Some authors require access to alternative content in order to interact with the web content that they are editing.
A Text Alternatives for Rendered Non-Text Content:

29. Editing-views are perceivable(cont.)
Guideline A.2.2: (For the authoring tool user interface) Ensure that editing-view presentation can be programmatically determined.
Rationale:
Some authors need access to details about the
editing-view presentation, via their assistive technology, when that presentation is used to convey status messages (e.g. underlining misspelled words) or provide information about how the end user will experience the web content being edited.

30. Principle A.3: Editing-views are operable
For the authoring tool user interface) Provide keyboard access to authoring features.
Rationale:
Some authors with limited mobility or visual disabilities do not use a mouse and instead require keyboard interface access to all of the functionality of the authoring tool.

31. Principle A.3: Editing-views are operable
A Keyboard Access (Minimum):
All functionality of the authoring tool is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints.

32. Principles B: Principle B.1:
Fully automatic processes produce accessible content.
Principle B.2:
Authors are supported in producing accessible content.
Principle B.3:
Authors are supported in improving the accessibility of existing content.
Principle B.4:
Authoring tools promote and integrate their accessibility features.

33. user agent definition:
A user agent is any software that retrieves and presents Web content for end users or is implemented using Web technologies.
User agents include Web browsers, media players, and plug-ins that help in retrieving, rendering and interacting with Web content.
The family of user agents also includes operating system shells, consumer electronics with Web- widgets, and stand-alone applications or embedded applications whose user interface is implemented as a combination of Web technologies.

34. User Agent Accessibility Guidelines (UAAG)
The User Agent Accessibility Guidelines (UAAG) documents explain how to make user agents accessible to people with disabilities, particularly to increase accessibility to Web content.
User agents include Web browsers, media players, and assistive technologies, which are software that some people with disabilities use in interacting with computers.

35. Who UAAG is for?
UAAG is primarily for developers of Web browsers, media players, assistive technologies, and other user agents.
UAAG and supporting resources are also intended to meet the needs of many different audiences, including policy makers, managers, and others.

36. Who UAAG is for? For example:
People who want to choose user agents that are more accessible can use UAAG to evaluate user agents.
People who want to encourage their existing user agent developer to improve accessibility in future versions can refer the user agent vendor to UAAG

37. UAAG Versions: 1.0 and 2.0
User Agent Accessibility Guidelines 1.0 was approved in December 2002 and is the stable and referenceable version.
UAAG 1.0 contains a comprehensive set of checkpoints that cover:
Access to all content, including content tied to events triggered by the mouse or keyboard.
User control over how content is rendered.
User control over the user interface, with documentation of accessibility features.

38. UAAG Versions: 1.0 and 2.0 User control over how content is rendered.
User control over the user interface, with documentation of accessibility features.
Standard programming interfaces, to enable interaction with assistive technologies.

39. UAAG 2.0:
UAAG 2.0 is being developed to help make future generations of Web browsers more accessible, to provide alternative information based on the users technology and platform, and to align with WCAG and ATAG 2.0. WAI anticipates UAAG 2.0 may be completed in 2013.
Because of the nature of the W3C development process, WAI cannot be certain when the final version of UAAG 2.0 will be available.
UAAG 1.0 will remain the latest approved version until version 2.0 is complete.

40. User Agent Accessibility Guidelines (UAAG) Overview.
Improving accessibility means considering a wide range of disabilities. These include visual, auditory, physical, speech, cognitive, language, learning, neurological disabilities, and disabilities related to aging. The goal of UAAG 2.0 is to ensure that all users, including users with disabilities, have equal control over the environment they use to access the web.

41. User Agent Accessibility Guidelines (UAAG) Overview.
Some users have more than one disability, and the needs of different disabilities can conflict. Many UAAG 2.0 requirements use configuration preferences to ensure that a feature designed to improve accessibility for one user does not interfere with the needs of another user. To avoid overwhelming users with an abundance of configuration options, UAAG 2.0 includes requirements that promote clear documentation and ease of configuration.

42. (UAAG) (Cont.)
The UAWG expects that software that satisfies the requirements of UAAG 2.0 will be more flexible, manageable, extensible, and beneficial for a broad range of users.

43. UAAG 2.0 Layers of Guidance
In order to meet the needs of different audiences, UAAG provides three layers of guidance: overall principles, general guidelines, and testable success criteria.
1- Principles:
Principle 1:
Ensures that the user agent is perceivable, so users can access user agent output.
Principle 2:
Ensures that the user agent is operable, so users can communicate with the user agent.

44. UAAG 2.0 Layers of Guidance
Principle 3 ensures that the user agent is understandable, so users know what to do to use the user agent
Principle 4 ensures that assistive technologies can access user agent controls
Principle 5 ensures that user agents comply with other accessibility specifications (e.g WCAG) and platform conventions (e.g. Windows, iOS, Linux, Blackberry). 

45. UAAG 2.0 Layers of Guidance cont.
Guidelines – Under each principle is a set of guidelines for making user agents more accessible to users with disabilities. These guidelines provide a framework to help authors understand the objectives for success criteria so they can better implement them.
Success Criteria – Under each guideline is a set of testable success criteria that can be used wherever conformance testing is necessary, including design specification, purchasing, regulation, and contractual agreements. 

46. Applications: Talkitt : WHO IT HELPS:
People with motor, speech and language disorders
WHAT IT DOES:
The Talkitt app translates unintelligible pronunciation into understandable speech.
allowing people to communicate using their own voice.
The technology behind the app is brilliant - by recognizing each individual user's vocal patterns, it “speaks” their words in a coherent manner.

47. Applications ( cont.)

48. Applications ( cont.)

49. Be My Eyes :
WHO IT HELPS:
People who are blind or visually impaired.
WHAT IT DOES:
connects blind people who need assistance with sighted volunteers who want to help out via a direct video connection.

50. Applications ( cont.)

51. RogerVoice:
WHO IT HELPS:
People who are deaf and hearing impaired. WHAT IT DOES:
RogerVoice uses voice recognition to convert voice to text, so deaf people can “hear” phone calls by reading.

52. LOOK AT ME:
WHO IT HELPS:
Autistic children.
WHAT IT DOES:
Designed to improve socialization skills for autistic children.
helping users learn to read moods, remember faces, and express themselves with facial expressions and poses.

54. HearYouNow:
WHO IT HELPS:
People with hearing difficulties who don’t use a hearing aid.
WHAT IT DOES:
Intended for use in public settings such as restaurants, meetings and parties as well as watching TV or listening to radio.

55. Stepping Stones :
WHO IT HELPS:
Children and adults who benefit from visual support
WHAT IT DOES:
This simple app allows users to create visual guides - or ‘paths’ - using their own photos, so as to make sense of daily routines and schedules or stories.
These visual supports help to increase the independence and flexibility that people with developmental disabilities can experience in their lives.

56. Applications ( cont.)

57. KinTrans:
WHO IT HELPS:
People who are deaf.
WHAT IT DOES:
Allows hearing impaired to communicate with others by translating sign language into voice and text in real time.