Alternatives MUST NOT include information about the type of object (Editorial & Development)
When using standard controls for links, buttons, images etc. information about its type is assigned elsewhere and should not be repeated in the alternative. This information is generally provided by default for platform objects, controls, or elements and will be announced by speech output software. For example never use the text 'Add button' as an alternative, only 'Add'. Adding additional roles means the role is announced twice to users of speech output software. An exception to this may be when a role or state cannot be added in such as way. For example, in the case of an HTML page tabs that gracefully degrade it may be useful to add the word "Selected" to the link.
Speech output software renders content in the order in which it appears in the document object model (DOM). Place content in the DOM in the correct order either through source code or inserting nodes in the DOM
The title attribute specifies extra information about an element.
The information is most often shown as a tooltip text when the mouse moves
over the element.
This attribute seems to be required by Xerte if embedding images where the embed functionality is not available from the "optional properties" menu. (Why use this instead of "Alt"? - When screen reading a Xerte object the the Alt tag seems to get ignored but "title" tag gets read aloud)
If a teacher today is not technologically literate - and is unwilling to make the effort to learn more - it's equivalent to a teacher 30 years ago who didn't know how to read and write.
Many advocates of web accessibility tend to have rather dull, unattractive websites. This is unfortunate, as web accessibility need not affect the design of the website in any way whatsoever. To fully dispel this myth, have a look at the CSS Zen Garden
Any web developer with basic HTML and CSS design knowledge, and a bit of time on their hands, can easily learn and implement web accessibility.
The Before and After Demonstration is a multi-page resource that shows an inaccessible website and a retrofitted version of this same website. Each web page includes inline annotations that can be activated to highlight some of the key accessibility barriers or repairs. Each web page is also accompanied by an evaluation report to inform the developers on the level of conformance to the Web Content Accessibility Guidelines (WCAG).
Progressive Enhancement is a powerful methodology that allows Web developers to concentrate on building the best possible websites while balancing the issues inherent in those websites being accessed by multiple unknown user-agents.
WAI-ARIA 1.0 is currently a W3C "Candidate Recommendation".
Developing custom, cross-browser JavaScript widgets is more complex, and implementing WAI-ARIA in these is proportionally more complex.
"WAI-ARIA" is the abbreviation for the Accessible Rich Internet Applications documents. In order to avoid confusion, please use "WAI-ARIA" (instead of just "ARIA"), at least in titles, headings, and on first reference in documentation.
WAI-ARIA is already supported in several browsers and assistive technologies (even though it is not finalized yet). Once WAI-ARIA is stable, WAI will collect and publish a list of WAI-ARIA implementations, that is, what supports WAI-ARIA. Some information on WAI-ARIA support is already available on other Web sites.
Text is found in many places on your computer, such as in windows and dialogs, in content areas like webpages and help files, and in documents. This chapter explains how to use VoiceOver to read, select, and edit text.
Switch Control is one of many great new accessibility features in iOS 7. Switch Control will allow a whole new group of people (switch users) access to the iPhone, iPad, or iPod Touch. Like all of Apple's accessibility features Switch Control is available on all iOS 7 devices and works out-of-the-box.
High-stakes assessment has consequences that may make a serious
impact on the life-course of the participant. An example might be a
university entrance examination.
Why Can't Microsoft Build a Screen Reader into Windows?
As Windows screen reader users will know, there is no screen reader included in Windows. Instead, users requiring a screen reader must obtain and install a third party product. Yes, there is Microsoft Narrator, but even Microsoft know that this is hardly worthy of the name "screen reader". :)
Interesting discussion about the differences betweens Apple and Microsoft's built in screen readers and the reasons for the various strengths/limitations of each platform.