In this blog, we'll cover several common misunderstandings in connection with accessibility problems on websites. Find out whether your website is doing it right or wrong.
“All images need an alt text.”
It is not necessarily correct to add text to an image. If the image doesn't provide any information, it will only create noise for the user. A common misunderstanding is that all images need an alternative text. This is not the case, but all images need an alt-tag (the code alt=""). Whether the image should have an alternative text depends on the context and purpose of the image. Ask yourself these questions:
- "Do I use the image as a decoration to create a visual context?" If this is the case, the image should not have an alternative text.
- "Do I use the image to provide information?" Then you need to describe what a visually impaired user can't see on the image (and this is not necessarily the same as describing what the image shows).
- "Does the image link?" Then you need to describe the destination of the link in the alternative text.
“Our CMS automatically puts in headings in fixed places on the pages.”
A website's main areas need to be categorized by headings. This means that your web editors should always check whether H1 tags, H2 tags, etc. are used correctly, and they should be able to enter these tags if they are missing. If you wish to logically and visually highlight an area by using bold font/large font/another color etc. then this heading should also be highlighted code-wise so the heading not only functions visually, but also structurally.
“The placeholder text in our search field is sufficient for explaining the purpose of the field.”
If you want to make sure that all users can identify and use your search field, and at the same time comply with accessibility guidelines, then you need to explicitly add text to the field through a label (the code label for="". If this is not possible, use title="").
“The audio reading tool we link to makes it possible for all disabled visitors to use our website.”
This is not necessarily true. An audio reading tool might help some people with dyslexia, but most people with impairments or dyslexia use specialized assistive technologies. They need significantly more help than what a simple audio reading tool can provide. The web standards and guidelines for accessibility are created in order for user agents (browsers, assistive technologies etc.) to be able to interpret a website and render it in a meaningful way to the user. That is why the most important element when working towards ensuring accessibility is to follow the standards and guidelines.
To get started with web accessibility,