SNOW (Special Needs Opportunity Windows) Just-in-Time, On-Line Information for Educators

Computer hardware, software and Internet connections - these are the new tools for education which are appearing in classrooms everywhere. At the same time, more and more students with special needs are taking part in the "regular" school activities as educators are asked to integrate these learners into their mainstream classrooms.

Gay, Greg and Laurie Harrison. University of Toronto (2006). Articles>Education>Accessibility

Access to Web-Based Special Education

Although, web-based distance education programs address geographical and cost barriers, they usually ignore access barriers to students with special needs (i.e. those with sensory, motor or cognitive disabilities). Distance education programs should ensure that conduits, and not barriers, to information are created. When planning a web-based special education program the following concerns should be considered: how to increase Web access to persons with disabilities by addressing access issues on both the client and the service side; how to optimize the use of innovative web technologies to transmit interesting yet accessible learning materials; how to increase community amongst special education students and teachers.

Nguyen, Kevin K. University of Toronto (2008). Articles>Education>Accessibility>Online

Web Browsing through Adaptive Technology: A Consumer Information Resource

The Adaptive Technology Resource Centre (ATRC), University of Toronto coordinated efforts with the Diversity Management Directorate (DMD), Public Services Commission of Canada to systematically evaluate how commercial World Wide Web (WWW) browsers functioned with various types of adaptive technology under different operating systems. The types of adaptive technology examined include screen magnifiers, scanning / switch access systems, alternative keyboards, screen readers, Morse code input devices and voice recognition systems.

Nguyen, Kevin K. and Linda S. Petty. University of Toronto (2007). Articles>Web Design>Accessibility>Web Browsers

Multiple Form Labels and Screen Readers

Just about every website needs some forms. Sometimes there are many of them, sometimes just a single contact form. Regardless of their number, they need to be usable and accessible, which can sometimes be a little more work than it would be if theory and practice aligned a little better.

Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility>Forms

Helping Others Understand Web Accessibility

When I hold workshops for people who want to learn more about web standards and accessibility, I often notice that the attendants really have tried to improve their accessibility knowledge. But they get overwhelmed when they go to the official documentation from the W3C and try to understand it.

Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility>Standards

Making Web Accessibility Accessible

when first learning web accessibility and uncovering its secrets, like many things, it can seem daunting and difficult. I think a lot of developers are downright intimidated by web accessibility — maybe even scared to go that route. But why? I suspect the reason is web accessibility is a discipline that lacks accessibility.

Cherim, Mike. Beast-Blog (2006). Articles>Web Design>Accessibility>Education

Overdoing Accessibility

Sometimes when people first learn about Web accessibility they look for quick ways of improving the sites they build. This often leads to misuse or overuse of certain HTML features that are meant to aid accessibility, but when used wrongly have no effect and can actually have the opposite effect by making the page less accessible and less usable.

Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility

Accessibility is Part of Your Job

Accessibility is one of the fundamentals of the Web, so how people who claim to be passionate about the Web and say that they deliver high quality can choose to ignore it is beyond me.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>Standards

Choose an Accessible Image Replacement Method

The technique of using CSS to replace normal HTML text, mostly for headings, with a background image in order to achieve a particular look has been talked about many, many times since early 2003.Several different image replacement methods have been proposed, each with their pros and cons. Some methods create accessibility problems, while others place restrictions on the type of image you can use or force you to use extraneous markup. No method that I am aware of is perfect.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>CSS

The Rules of Unobtrusive JavaScript

One of the most important things to keep in mind when writing JavaScript for the Web is to make it unobtrusive, since You cannot rely on JavaScript being available.Sadly, there are many developers who do not seem to spend any energy at all on considering how to do that. Instead they choose to blindly forge ahead and assume that everybody who comes visiting will have full support for JavaScript and use a mouse.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>JavaScript

Manual for Apple VoiceOver in Mac OS X 10.5 Leopard

Apple’s screen reader, VoiceOver, comes bundled with Mac OS X (yes, it’s free) and has received a number of updates in Mac OS X 10.5 Leopard. The updates include a new voice, Braille support, and improved navigation and searching.

Johansson, Roger. 456 Berea Street (2007). Articles>Usability>Accessibility>Macintosh

Use the Label Element to Make Your HTML Forms Accessible

There are plenty of articles and tutorials that describe how to create accessible HTML forms out there. Despite that it is common to come across forms that do not use a single label element and forms that use label elements but do so incorrectly.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>Forms

Screen Readers Sometimes Ignore display:none

Using display:none does not always hide content from screen readers like JAWS and Window-Eyes, but there is a workaround.

Johansson, Roger. 456 Berea Street (2008). Articles>Web Design>Accessibility>CSS

Autopopulating Text Input Fields with JavaScript

Few people will argue against the need to explain to users what they are supposed to enter into text input fields. One common workaround when no label can be displayed is to put some placeholder text in the text field and let that act as the label.This approach works reasonably well, but it burdens the user with having to clear the input before entering their own text, which can lead to frustration and mistakes. An approach that avoids that is using JavaScript to clear the input when it receives focus. Since that won’t work when JavaScript support is missing, JavaScript should be used to insert the placeholder text as well.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>Forms

How to Create an Unobtrusive Print this Page Link With JavaScript

When a client requests that I duplicate functionality that should be (and is) handled by web browsers, I always try to avoid doing it by explaining why I believe it is better to leave such functionality to the browser. Most of the time I succed, but occasionally I don’t.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>JavaScript

Can the alt Attribute Be Omitted Without Hurting Accessibility?

In the current editor’s draft of the HTML 5 specification, the alt attribute for images is no longer required. I am not convinced that this is a good idea.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>HTML5

Introduction to Screen Readers

Begins by showing us the core functionality of screen readers and how they interact with the desktop. In the second part it demonstrates how a blind user may use them to explore and understand web sites, how sites are “linearized”, and how using semantic markup to build sites supports accessible navigation and usability.

Tsaran, Victor. Yahoo (2007). Articles>Web Design>Accessibility>Universal Usability

Introduction to Screen Magnifiers

Karo Caran and Victor Tsaran show how the screen magnifier ZoomText is used to make the computer desktop and web sites readable to people with reduced vision.

Caran, Karo and Victor Tsaran. Yahoo (2007). Articles>Web Design>Accessibility>Universal Usability

From the Mouth of a Screenreader

Talks about the history of screen reading software and how they analyse what is displayed on the screen in order to speak it to the user.

Geoffray, Doug. Yahoo (2007). Articles>Web Design>Accessibility>Video

Accessible Expanding and Collapsing Menu

A website’s navigation should, in my opinion, be visible and straightforward, not hidden away like this or in flyout/dropdown menus. But...

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>DHTML

Unobtrusive and Keyboard Accessible Connected Select Boxes

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.

Johansson, Roger. 456 Berea Street (2007). Articles>Web Design>Accessibility>CSS

The Language of Accessibility

Good markup is accessible by default. As long as you’re using HTML elements in a semantically meaningful way—which you should be doing anyway, without even thinking about accessibility—then your documents will be accessible to begin with.

Keith, Jeremy. Adactio (2006). Articles>Web Design>Accessibility>Standards

Introduction to WAI ARIA

This article is for those who are new to ARIA. You need an understanding of HTML and the potential difficulties that people with disabilities can face using the Web. It is useful to be familiar with some Rich Internet Applications from a user's perspectiveAfter reading this article, you'll understand what ARIA is for, how to integrate it into your sites, and how you can use it now to make even the simplest of sites more accessible.

Lemon, Gez. Opera (2008). Articles>Web Design>Accessibility>Flash

Building Accessible Static Navigation with CSS

When building a navigation menu for a web site, steps should be taken to ensure that it is accessible, and degrades gracefully in older browsers with lesser CSS support. In this article we will explore one such implementation. The navigation menu you see in this example is built with valid, semantic HTML and CSS - no JavaScript is involved, as I felt this was unnecessary. The static (non-expanding/collapsing) nature of the example suits a web site comprised of twenty or less target pages.

Palinkas, Frank M. Opera (2008). Articles>Web Design>Accessibility>CSS

Replacing NOSCRIPT with Accessible, Unobtrusive DOM/JavaScript

Modern user agents with JavaScript enabled will hide content contained within NOSCRIPT, and reveal it when JavaScript is disabled. User agents that do not support JavaScript will display the content within it. User agents with partial/antiquated JavaScript capabilities however interpret the element correctly and do not show the content, but when JavaScript is disabled also do not show the content - it never gets seen. This has an impact on the accessibility of the content. If your writing is targeted at modern, standards-based, compliant, and fully capable JavaScript user agents, employing the NOSCRIPT element is no problem. If the user agents among your audience are unpredictable, however, replacing the NOSCRIPT element with another mechanism becomes significant. This article looks at one such solution.

Palinkas, Frank M. Opera (2008). Articles>Web Design>Accessibility>JavaScript