Web Access Centre Blog

Most of you won’t believe what I’m about to describe, and would never use heading structure in this way. This post isn’t for you, it’s for the people who believe that it’s OK to wrap several links inside a single heading tag, or in fact use one heading to enclose one or more other elements or types of content .

If you find this difficult to comprehend, you aren’t alone, it came as an enormous surprise to me too, but I’ve recently seen four different sites using one heading to enclose at least one other element.

Continue Reading »

Then look no further. We’re running two half day courses Thursday June 26th on Transitioning your website from WCAG 1.0 to WCAG 2.0 and Hidden Barriers to accessibility.

Transitioning from WCAG 1.0 to WCAG 2.0 - With WCAG 2.0 nearing completion now is the perfect time to get ahead of the game and get started. This practical course is your WCAG 2.0 starter kit and looks at the new guidelines, what’s changed, what’s new, supporting resources and tools as well as implementation advice. The course aims to enable and inform web managers, designers and developers, who have been working with WCAG 1.0 on how to start using WCAG 2.0.

Hidden Barriers to accessibility - While guidelines are designed to do just that, guide, developing accessible websites is about understanding your user and their needs. This technical course is designed to enable website designers, developers and programmers to identify and cure some common, but less obvious accessibility problems on their web sites such as TITLE text, hidden text, same page links and placeholder text (to name a few).

These courses go beyond standard accessibility advice and look into the knottier aspects of accessibility so you can walk away with some practical and implementable solutions for your web sites.

Find out more and sign up.

Hiding text off the screen view using CSS is one of the ways that web authors can provide contextual information for screen reader users. This is just to make the information that is visually obvious, potentially audible. It’s a great help, but you do need to be careful which CSS technique you use.

If DISPLAY: NONE; or VISIBILITY: HIDDEN; is used, there’s a very good chance that screen readers will “obey” this rule, and won’t read the hidden content.

The surest technique is negative positioning. this only places the text out of screen view, but doesn’t hide it from screen readers. So if the content you are styling out of sight should be available to screen readers, try the following rule:

.screenreader {
               position: absolute;
               left: -999em;
               }

This way, most screen reader users will benefit from your thoughtful additional content.

Do be careful to define a base (natural) language on all web pages. Otherwise, defining other languages can result in the entire page being read by a screen reader trying to use the pronunciation rules for the wrong language.

This can happen where the HTML tag isn’t given a LANG attribute, for instance:
<httml lang="en">

The problem arises if there is any coded “change” to the natural language on the page, because the “change” is, in fact, the first time that a language is defined. So everything after it may be pronounced as if it is in the “foreign” language. Continue Reading »

In forms that have fairly long implicit labels, the BR element is the worst way to control where the text will wrap. Screen readers may only read the text that comes after the BR element, because of course, it’s perfectly legitimate to have a line of instruction, followed by the BR element, followed by the implicit lable.

For example, if a label were: “If you have more than 14 chickens,
how many do you own?” Many screen reader users will hear only “how many do you own?”

There are two simple ways to avoid this issue.

Here’s another series of articles, designed to uncover techniques or practices that create difficulties for a wide range of disabled people. These are all techniques we’ve found in use on the web, on professionally run sites.

Some of the hidden barriers are created by coding errors or ommissions, others are due to too little or (conversely) too much thought being given to the needs of screen reader users. Continue Reading »