Availability means that the task can be performed in different ways. The website uses people with different possibilities of seeing, hearing, motion and understanding, as well as users temporarily limited by injury, noise, sharp light or small screen. WCAG gives common criteria, but availability does not end with an automatic scanner. You need a correct HTML structure, keyboard support, understood content, assistive technology testing, and process that does not spoil quality in subsequent publications.
Structure, keyboard and visible focus
The headers should describe the hierarchy of content, and the regions of the site have the right meaning. Links and buttons must be used according to the function to make the screen reader correctly present them. The order in the code should correspond to the order of reading. Skipping header levels and building interaction with random elements hinders orientation.
The whole function needs to be handled with keyboard, without traps and unexpected focus transfer. The currently selected item must be clearly visible. Menu, dialog windows, carousels and forms require conscious focus management. Tab test quickly reveals many problems, but should be supplemented by a screen reader check.
Colour, text, images and multimedia
The text needs the right contrast and zoomability without losing content. The color cannot be the only way to pass an error or status. Simple language, short paragraphs, informative headers and descriptive links help all users. Instructions should tell what to do instead of referring exclusively to the position or color of the item.
The alternative text of the image should convey its function in a given context. Decorative images should be correctly marked, for example, with an empty alt attribute; graphs require the available equivalent of the information transmitted. Writings convey important sound information. Audiodescription describes important visual information not explained in the sound; an appropriate set of subtitles, description and transcription depends on the material type and level of availability required. Automatic playback makes it difficult to control.
Forms, tests and responsibility of the editorial board
Each field of the form requires a visible label, and the error should indicate where and how to improve it. The message must not disappear before the user reads it. The validation on the client side does not replace the server, but can help earlier. Time limits require the possibility to disable, adjust or extend according to the appropriate criterion and its exceptions.
Automatic tools detect only some of the problems. The test should include keyboard, zoom, contrast, screen reader and user scripts. Editors need rules for publication of headers, links, graphic descriptions and tables. Availability is easier when CMS components have good default settings.
Basic audit of accessibility
- Logical structure of headers and regions of the site.
- Full keyboard support and visible focus.
- Contrast and enlarge text without losing function.
- Description links and simple, understandable language.
- Adept alternative texts and subtitles for multimedia.
- Field labels and helpful error messages.
- Manual tests to supplement automatic tools.
Select a solution to the content of the recording
The video with an expression, demonstration without a voice and recording of the sound itself conveys the information differently. So it is not enough to check the general item “multimedia available”. First you need to recognize what the recipient needs to hear or see in order to understand the material.
WAI sets out the breakdown of such needs in audio and video planning guide. When preparing the recording, it is worth taking into account texts and descriptions immediately, instead of trying to reproduce all the information only after installation.
Give time to perform the task
The form, booking or session in the panel may have a limited duration of operation. You should know about the coming end and have appropriate response capabilities. The rules and specific exceptions are described in the time adjustment criterion.
Not every person reads and writes the data at the same rate. It is particularly difficult when a longer description prepared in the form disappears without warning.
Check the information that appears temporarily
- Can the message be read by the available method?
- Is an important answer available also after his disappearance?
- Doesn't the change bring it to another task unexpectedly?
- Does the user understand what has been saved?
For example, a short confirmation can be supplemented by a permanent status of the case. Then the recipient does not have to read the single, quickly disappearing information.
Keep requirements after publication
The new film, form or window can introduce a problem, even though the previous version of the site was tested. It is worth attributing responsibility for controlling new materials and components. We write about daily editorial work in a guidebook for graphic descriptionsAvailability is part of the maintenance of the service, not a one-time mark on the project.
The most common questions
Is accessibility needed only by public institutions?
No. Regardless of legal obligations, it increases the number of people who can take advantage of the offer and improves the overall usefulness.
Can compliance be provided with a plug?
No. The addendum can support the selected functions, but will not fix the structure, content, keyboard and processes of the entire service.
When do we start working on accessibility?
At the stage of requirements and components. Improving the ready-made service is possible, but usually more expensive and more fragmented.
Summary
The available page combines semantic code, readable content, keyboard support, appropriate media and tests. The most durable effect is to include accessibility in the project and daily editorial work.
