Error handling
This covers any warning, information or error message that needs to be drawn to the attention of the user. It is also important for the user to be provided with an easy way of rectifying the situation.
Visual warnings that do not take the focus, such as text changing colour or a graphic symbol appearing next to the field, will not be picked up by screen reader users. Moving the focus to the location of the error without any accompanying explanation is confusing and frustrating for many users, who will not know what is wrong or how to put it right.
A pop up dialog box containing information about the error is good because all the necessary information can be contained in the text. When the dialog is dismissed, it is helpful if the cursor is placed at the location of the error as well, to save having to navigate there from the keyboard.
If information is routinely placed on a status line and users know it is there, then this can be a place to put warning and error messages if a notification dialog is not possible. Screen reader and magnification software can pick up messages that are consistently placed in a location that is programmatically identified as a status line, usually at the very bottom of a window.
Visual effects
Animation and blinking or flashing content can distract users from the task in hand. Flashing light at some frequencies can even cause illness. It can also play havoc with access technology if it draws the focus away. There may be circumstances when these visual effects are justified but it should always be possible to turn them off and access a static alternative version.
If animation is what the software is for, then clearly it makes no sense to provide a non-animated version. Here we stray into the areas of entertainment and e-learning - there are many other guidelines associated with these areas, including the need for captioning and audio description. These are specialist fields that we cannot cover here. Becta is a useful reference point for educational technology and accessibility, and RNIB's Media and Culture team can advise on issues around entertainment.
Help, documentation and manuals
Most users need help with software every now and then, and the use of online and context-sensitive help is well accepted. Software in public areas will not have user documentation or manuals but, in most other situations documentation, is expected.
All users will appreciate the use of jargon-free plain English. As described in the section about Visual display characteristics, for online text it should be possible to change font size and colour to suit the reader. RNIB's Web Accessibility Centre offers a great deal of guidance about how to make electronic and printed text as accessible as possible.
The content of online help, manuals and documentation must be appropriate to the audience. This is not only in terms of the language, level of technical content and jargon but also any device-specific instructions. Not everyone will be clicking with a mouse to carry out tasks. Of course, it should go without saying that features of the software for ease of use should be well documented, and easy to find and activate.
Images and screen shots are extremely useful for those who can see them but explanation and description of any concepts should be available for those who cannot use the images.