Group items tagged

One major new piece of work undertaken by WAI is the EC-funded WAI-AGE Project (http://www.w3.org/WAI/WAI-AGE/), a look at the implications of an ageing population for web access, given the older people are more likely to have disabilities and may also be less familiar with new technologies. “Demographics worldwide are dramatically changing at the moment,” says Andrew Arch, who works with Abou-Zahra on WAI-AGE. “The proportions of older to younger people are changing as well as the numbers. We’re living longer, and we haven’t got the support behind us. “Lots of things have got to change in governments and organisations - with an ageing workforce, you have to keep learning to stay accessible.”

The WAI-AGE project is partly aimed at finding out whether there are any significant new pieces of work needed to ensure web accessibility for an older population, Arch says. “We’ve looked at what research and user observation has gone on over the decade. There is a pretty big overlap between older people and others with disabilities - sight starts to decline, motor dexterity - and individually these overlap. But with older people there is often a lack of recognition that there is a disability there. For example some people might just say they can’t remember so well, rather than that they have a cognitive impairment. Or people won’t see failing eye-sight as a disability, it’s just ‘part of growing old’. But they are disabilities, and often multiple disabilities.”

Having gained a grasp of current research the project returned to guidelines such as WCAG 2.0 to see if any changes might be needed. “A large proportion of the needs of older people are met by the new guidelines, but other things might need to feed into the guidance we will issue on implementing the guidelines, for example guidance on how people prepare content for older people.,” said Arch. “Many older people have not grown up with computers, and may not realise their capabilities, for example that you can magnify text in your browser.”

AJAX is

a smorgasbord of web technologies put together to allow dynamic client-server interactions to occur in web applications without requiring pages to reload or refresh.

AJAX uses the following:

Any web developer who has created a reasonably complex form is probably aware of the concept of multiple select elements that are connected – choosing something from one select box either makes a new select box appear or changes the options of one that is already visible. There are usually two problems with this approach. One is that most implementations are completely dependent on JavaScript being available. Often there either is no submit button at all, or there is a submit button but without JavaScript there is no way to access the options that appear only as a result of changing the first select box. The other problem is that in some browsers, using the cursor keys to change the selected option triggers the onchange event immediately, so you can never get past the first option unless you know how to use your keyboard to display all options. I normally work around these problems by requiring users to submit the form to get the next set of options from the server. Obviously that isn’t an ideal solution either. So what other options do we have? One option that looks promising is described by Christian Heilmann in Unobtrusive connected select boxes - yet another solution approach. It involves using optgroup elements to create a two-level select box, which is then split into two separate select boxes if JavaScript is available. Neat. The solution Chris describes solves (or at least mitigates) the keyboard access problem since it doesn’t reload the page when the onchange event is triggered. And if JavaScript is unavailable, there is a single select box with option groups. The catch is that nested optgroup elements are not allowed in current versions of HTML, so this will not work when more than two connected select boxes are needed. Nested optgroup elements are allowed in the current Web Forms 2.0 Working Draft, so I guess there is a reasonable chance of that change making it into HTML 5.

One of the things that have long irritated me about HTML is the restriction on what elements are allowed inside lists. The specs for both HTML 4 and 5 allow only li for ul, ol, and only dt and dd are allowed inside dl definition lists. I’d like to expand that to allow h1…h6, section and div.

There's been widespread speculation about the new legislation being introduced under the DDA (Disability Discrimination Act), which will ensure that websites are accessible to blind and disabled users. Try to find specific information about it on the Internet and chances are you'll come up empty handed.The RNIB (Royal National Institute for the Blind) and the DRC (Disability Rights Commission), two of the most renowned advocates for the DDA (Disability Discrimination Act) and accessible websites, have no specific information about the laws and what websites specifically need to do in order to meet the legal requirements.

2.2 (p7): "The Act makes it unlawful for a service provider to discriminate against a disabled person by refusing to provide any service which it provides to members of the public."

4.7 (p39): "From 1st October 1999 a service provider has to take reasonable steps to change a practice which makes it unreasonably difficult for disabled people to make use of its services."

I’ve been using this for years and can’t understand why it isn’t available in Mail’s GUI. Here’s what to do: Quit Mail.app Open Terminal.app Enter defaults write com.apple.mail PreferPlainText -bool TRUE and press enter (toggle it back by changing TRUE to FALSE) Open Mail.app View an HTML message and marvel at the readable plain text The catch is that this only works for messages that actually contain a plain text alternative, which far from all HTML email does.

Specify the minimum font size Apple Mail uses for HTML messages As a fallback for the messages that do not contain a plain text alternative it is useful to make sure that the text at least has a readable size: Quit Mail.app Open Terminal.app Enter defaults write com.apple.mail MinimumHTMLFontSize 13 in the Terminal window and press enter Open Mail.app View an HTML message and marvel at the readable font size You can change the font size to whatever suits your eyes. Apply both of these and you should be able to read most of the HTML email that you receive.

In the UK In the US 2m people have a vision impairment3 10m people have a vision impairment4 8.2m people have mild to moderate deafness5, 688,000 people have severe to profound deafness6 28m people have a hearing impairment7 3.4m people have a physical disability8 8m people have a physical disability9 1.5m people have a learning disability10 6.8m people have a learning disability11 6m people have dyslexia12 25m people have dyslexia13

Most people who are blind will rely on screen reading software such as

JAWS or Windows-Eyes

WAI-ARIA (Accessible Rich Internet Applications or ARIA) is a W3C protocol for enhancing and supporting accessibility of scripted and dynamic content.

ARIA provides accessible interactive controls (such as tree menus, drag and drop, sliders, sort controls, etc.), content roles for identifying page structure (navigation, search, main content, etc.), areas that can be dynamically updated (called "live regions" in ARIA), better support for keyboard accessibility and interactivity, and much more.

accessibility issues with rich internet applications can be characterized as: Providing the semantic structure of page areas and functionality (e.g., navigation, main content, search, etc.) Maintaining accessibility of content that is dynamic and may change within the page (e.g., AJAX content updates) Allowing certain non-focusable page elements to receive keyboard focus (e.g., setting focus to an error message within the page) Providing keyboard and screen reader accessibility with complex widgets and navigation elements (e.g., sliders, menu trees, etc.)

Captivate has a number of accessibility features in version 3 and 4 although there are some issues that Adobe is working on.

Ensure that the “enable accessibility” checkbox is checked under the File > Publish settings in order for accessibility to be exposed to assistive technologies.

Slide Accessibility Text Each slide can contain accessibility text. This can be added by going to the slide properties, activating the Accessibility button and entering text in the text field.

We received 1121 valid responses to the screen reader survey, which was conducted Dec. 2008 - Jan. 2009.

Skip to content22% Skip to main content28%

33 respondents (2.9%) reported being both deaf and blind.