Accessibility: the benefits and challenges of Web 2.0
Design, design, design
The emergence of Web 2.0 technologies has created opportunities for the visualisation of much information on the web. For example, a dashboard showing the current state of a business can summarise a great deal of information on a single page and highlight areas of interest or concern.
Unfortunately, the way this information is presented may mean that it is difficult, or impossible, for people with various forms of disability to access it. A visual on a screen is of no use to someone who is blind. I will come back to how to present information in this situation; but I want to look at how to support other groups first, because good design can not only make visualisation accessible, but can also make the information more accessible.
The design principles underlying the WCAG standards apply equally to visualisation. I am going to look at various disabilities and see how they can be supported.
I will start with colour blindness because it is relatively common and because solutions are fairly easy to design-in if it is considered early. It also ensures that if the visual is displayed in monochrome or printed in black and white the information is still retained. The basic principle is that colour should not be the only distinguishing feature.
So for example, lines on a graph can be distinguished by colour but should also be distinguished by the type of line (dashed, dotted, thickened etc) or by the tick marks along the line (crosses, boxes, circles etc). Areas in a pie chart should be distinguished by a pattern as well as the colour. Furthermore the designer should consider how to use the power of Web 2.0 to improve the accessibility. In this case the slice of the pie could be highlighted when the legend is chosen and vice versa.
Many people find the standard text size on the web difficult to read and find text sizing a very useful feature. Clicking the size up one or two notches makes it more comfortable and less tiring to read. With visualisation there are three interrelated types of sizing:
- Zoom in/out
- Text and icon sizing
- Level of detail in the display
Maps are a good example of how these interact. Zoom enables the visualisation of the whole of the United States or just a single block in New York. As we zoom in, the visualisation will add more detail going from just showing the States, the major highways and rivers down to showing the house numbers, street names and traffic direction. The size of the text, or symbols, will not change as we zoom in.
A user with vision impairment will need to be able to configure the text and symbol so that, for instance, the text is always 24 points rather than the typical 10 points. Alternatively, it may be better for the user to point at the text or icon and have the detail displayed in a separate pane with a suitable size, font and colour.
Excessive detail, such as thin lines for streets, will not be visible to a user with poor vision and will just make the map fuzzy. The user should be able to specify the level of detail. A simple way to do that would be to specify that the level of detail is the same as it would be for a standard user one or two zoom levels out.
Sponsored: Network DDoS protection