7 web accessibility myths

Web accessibility is not a new concept. The Web Accessibility Initiative was launched back in 1997, and yet 15 years later it is still a widely ignored and neglected aspect of web development. There are many deep-rooted misconceptions about accessibility which prevent people from making a conscious effort to incorporate it into their websites. Let’s take a closer look at the top 7 web accessibility myths:

1. Accessible websites are ugly and boring

Some of them certainly are. But so are millions of totally inaccessible websites. The point is, accessibility has nothing to do with how visually attractive or interesting a website is.

This misconception comes from the early days of the Internet, when technology did in fact restrict the developers’ choices in terms of accessibility and design. Text-only websites, stripped of any kind of elements increasing the visual appeal, were considered the only acceptable solution.

The times, however, have changed. It is absolutely possible nowadays to create a beautiful, media-rich, interactive, engaging AND accessible website. People who claim otherwise usually misinterpret the accessibility requirements and in effect see them as more restrictive than they actually are.

WCAG guidelines don’t forbid anyone to use images, videos or JavaScript on their website. The only thing they say is, if you do, make sure that the content of the website is still accessible if the users are not able to, or choose not to, use them. That means providing captions and transcripts for videos, alternative text descriptions for images, mechanisms to control slideshows or using accessible JavaScript plugins, etc.

2. Web accessibility is expensive, time-consuming & hard to implement

It stems from some strange idea that the process of creating an accessible website is very complicated and much different from creating one that is not. But there is no AccessibleHTML or AccessibleCSS. The same languages and technologies are used, but perhaps more thoughtfully, with more understanding, attention to detail, and in accordance with best practices.

Creating an accessible website is also not a particularly expensive or time-consuming process, especially if you do things the right way from the beginning. It has to be said that rebuilding an inaccessible site for accessibility can in some cases be difficult, time-consuming and quite expensive (all the more reasons to incorporate accessibility into your website from the beginning), but it is still worth doing. Price paid in money and effort can be seen as a future investment that will in the long run pay off (see point 7 for the many benefits of having an accessible website).

Also, as web accessibility is in some cases required by law, ignoring it can prove to be very expensive and troublesome. So it’s probably not a question of whether you can afford to build an accessible site, but rather if you can afford not to.

3. Accessible sites only benefit small percentages of people

This seems to be the main argument for business owners who don’t want to make an effort toward making their websites accessible. They often say that people with disabilities don’t use their sites. Well, how can they if the website is inaccessible to them? It’s like saying there’s no point in installing a lift in a building with a restaurant on the top floor, because people who use wheelchairs don’t dine there. It’s a case of confusing cause and effect.

Then there are other people saying that there’s no point in making an effort which will benefit so few people. Let’s then try to work out the number of these ‘few people’.

It is estimated that around 10% of the population worldwide has a disability that affects Internet use. I personally wouldn’t describe 650 million people as ‘few’.

But even this number is not correct. Most of us experience some sort of temporary disability at some point of our lives. Browsing through sites with flickering images and badly contrasted colours may prove unbearable for someone with migraine, and a broken wrist can mean that mouse navigation is no longer an option. Also, whether we like it or not, we’re all getting older, and with age our hearing, sight and dexterity diminish, changing our ability to use the Internet.

So now we know that accessibility benefits people with some sort of health problems, permanent or temporary. But even that is not the whole truth. For example, WCAG guidelines mention building websites with clear layout, consistent navigation and meaningful link names, to make them accessible to people with cognitive disabilities. But aren’t all these features useful to everyone, especially when visiting a content-heavy site for the first time?

Providing alternative text descriptions for images can benefit not only blind users, but also people who use low-bandwidth connections and turn off the images in order to increase the speed of browsing. Creating text captions for video and audio files, done mainly with deaf people in mind, can be very useful for people who don’t have speakers or would like to access the content without disturbing the people around them. And building keyboard accessible websites will benefit not only disabled users, but people using the Internet on their mobiles as well.

Considering all the above, I think it is safe to say that making sites accessible benefits us all, the entire web community, including the healthy users and the people without real medical disabilities.

4. Web accessibility is optional

Well, not really. Accessibility of a website is actually required by law. The Equality Act 2010, which came into force in October 2010, replacing the Disability Discrimination Act (DDA) in England, Scotland and Wales, makes it illegal to discriminate against people with disabilities. The Act applies to anyone providing a service; public, private and voluntary sectors. The Code of Practice: Rights of Access – Goods, Facilities, Services and Premises document published by the government’s Equality and Human Rights Commission to accompany the Act does in fact refer explicitly to websites as one of the “services to the public” which should be considered covered by the Act. In effect, if someone with a disability can’t access the information on a website, then it could be seen as discrimination, so for example it may be seen as unlawful to have links that are not accessible to a screen reader or use colour contrast that make the website inaccessible to a partially sighted service user.

To date, very few companies have faced such legal action in the UK. In two cases, actions were initiated by the Royal National Institute for the Blind, and both settled without being heard by a court. There were some cases abroad as well; in 2000 in Australia a blind man successfully sued the Sydney Olympics organising committee over their inaccessible website, and in the USA target.com and, recently, netflix.com were also successfully sued over the accessibility of their websites.

5. Web accessibility is the sole responsibility of developers

It is widely believed that the only people responsible for making the web accessible are web developers. But is it fair on them?

Web developers work in a complex environment of interconnected technologies, with components that have an impact on overall accessibility. These include web browsers, media players, assistive technologies (like screen readers or alternative keyboard), authoring tools used to create websites, accessibility evaluation tools, HTML and CSS validators, etc. What sense would it make for the web developers to try incorporating accessibility into websites they’re building, if other components are unable to implement it or support it? If user agents and authoring tools don’t support certain features correctly and consistently, it’s no wonder web developers sometimes don’t see a point of making an effort.

In turn, if user agents provide some functions to help develop compliant websites, web developers should design the websites making use of them. For example, since the browsers support text resizing, why would you use absolute rather than relative size units for text or sections containing text?

But responsibility for web accessibility also rests on people outside ‘the industry’; authorities creating laws and codes of practice, and website owners – various businesses and organizations. We already have the law regulations in place – The Equality Act 2010 came into force in October 2010 and The Code of Practice: Rights of Access – Goods, Facilities, Services and Premises in April 2011. Now it’s time for leaders of organizations to realize the importance of accessibility and ensure it’s incorporated in their websites.

6. Automated evaluation tools are enough

Automated evaluation tools are very helpful, as they can reduce the time and effort necessary for accessibility testing by identifying some potential issues. However, they can’t replace manual testing, because many of the WCAG checkpoints are not objective enough to be tested automatically and require human judgment. An automated tool can check if an image has an alternative text description, but is not able to judge if the description is accurate and meaningful.

7. Making websites accessible doesn’t have any additional benefits

Many people treat web accessibility as a necessary evil; something that has to be done for the sake of it, but that is not really rewarding. Maybe the additional benefits of web accessibility listed below will help to change that:

- Search engine optimisation

Unlike accessibility, SEO is something companies don’t usually hesitate to spend money on. And yet many accessibility guidelines are the same as SEO techniques, for example valid HTML, clear link names, using text rather than images of text, descriptive ‘title’ tags, providing text equivalents for multimedia, creating a site map, etc. This means that incorporating accessibility will at the same time help to improve websites’ search engines ranking;

- Increased website use

As accessible websites are easier to find, access and use, they maximise the number of possible visitors. And this in turn can boost company’s profits – e-commerce websites can increase sales and non-profit organizations get more funding;

- Cost savings

Accessibility can help to decrease costs, such as maintenance costs, server costs, cost of upgrading to new technologies, cost of customer support services (as more people are able to complete many of the tasks online), etc.;

- Increased usability

In general, accessibility increases usability of a website, and in effect improves quality of user experience. Some accessibility guidelines are similar to the usability ones, such as promoting clear and consistent design and navigation, dividing blocks of information into logical sections, good colour contrast, etc. Increased usability makes users more likely to return to the website, use it more thoroughly and recommend it to others, which again can result in increased profit;

- Reduced site development and maintenance time

Although incorporating accessibility can increase site development time initially, in long term it reduces time spent on site improvements and maintenance. Using style sheets and coding to standards reduces effort needed to change presentation across a site.

- Improved interoperability

Accessible websites enable content to be presented and interacted with on many different configurations, which increases interoperability and device independence;

- Reduced server load

Many web accessibility techniques, such as using external style sheets rather than in-line styling or text rather than text images, reduce the server load and increase the download speed;

- Reputation

Last but not least,a  company’s efforts towards making their website accessible can have a positive impact on company’s reputation, as it creates an image of ethical and socially responsible organization.

So that’s the top 7 web accessibility myths. If you dozed off half way through reading them, here’s the summary:

  1. Accessible websites are only ugly and boring if you really want them to be;
  2. Creating them doesn’t take years, cost a fortune and require an army of geniuses;
  3. They benefit few people. Few billions in fact;
  4. Web accessibility is totally optional, if you don’t mind being sued and taken to court;
  5. The Web would be a better place, if we all stopped pointing fingers and took the responsibility;
  6. Until artificial intelligence reaches the level of human intelligence, automated accessibility testing is not enough;
  7. Web accessibility comes with many freebies.

Now why would you say no to that?

Share this post

About the Author

Gosia Mlynarczyk is an Accessibility Consultant. When she’s not inspecting websites, with one eye on the screen and the other on accessibility guidelines, she likes travelling, reading, watching science programs, and listening to music.


  1. Brian Kelly says:

    I think you have fallen into that trap of conflating with conformance with WCAG guidelines with being accessible. WCAG are just a set of guidelines which can help address some accessibility issues, but WCAG conformance is no guarantee of accessibility. One example I give to illustrate the need to think beyond WCAG is my favourite sports headline: “Super Caley go ballistic, Celtic are atrocious” – witty if Mary Poppins was part of your cultural background but inaccessible if this wasn’t the case. The accessibility connections relate to people with learning disabilities, such as Asperger’s Syndrone and do not understand metaphorical writing.

    Such issues were touched on in Jonathan Hassell’s post on We Accessibility myths He commented at http://www.hassellinclusion.com/2012/01/web-accessibility-myths-2011-part2/

    “Ask the four million people in the UK who have dyslexia, literacy or learning difficulties. These guys would love you to remove much of the text from your website, and replace it with carefully selected, informational images and video”.

    This post went on to challenge the view that “Web accessibility is expensive” is a myth:

    “I’d love it if, for a while at least, we turned the accessibility orthodoxy on its head, and all text had to have a ‘video equivalent’ created for it ‘for accessibility reasons’.
    Although the cost would be considerable, that 360-degree change would make the web more accessible for more disabled people. And it might make all of us think a bit more, and understand that multimedia is good, not bad, for accessibility.”

    The biggest myth is that implementing WCAG AAA will deliver universal accessibility – for me that’s the biggest challenge. WAI has been great in raising awareness of the importance of accessibility for web products; the challenge now is to develop appropriate ways of addressing these challenges. For me, BS8878 should be the starting point.

    I’d welcome your thoughts on the relevance of BS 8878 and the limitations of WAI’s model and WCAG.

  2. Katie Bourke says:

    You bring up a really interesting point, and draw attention to users that are often forgotten in relation to web accessibility. Often we get wrapped up in technology and guidelines and forget to take into consideration simple linguistic challenges that may face people.

    I do have to disagree slightly though I do not believe that universally accessible website delivery must be highly costly. You mentioned a desire for those literacy/ learning difficulties to remove text entirely from websites and replace with video content, however that in itself would be exclusive to those with hearing impairment. Further more I am sure some people with hearing impairment can also have literacy difficulties and as such, should we also provide regionally specific sign language with all video?

    My point is that whilst trying to be universally accessible as possible you may not always be able to satisfy each users personal preference. All we as designers/developers can do is try to take into account as many people as possible and follow guidelines as presented. Not every developer has intimate knowledge of the disability sector.

    Perhaps, beyond the website designers further measures should be taken. Inclusion of an audio feature on all browsers would allow users to chose their method of interaction with the website. Of course a option such as this would necessitate a level of accessibility within websites. Maybe possibly increase awareness also!

  3. Lucy Pullicino says:

    Brian, I really don’t think this blog pushes WCAG as much as you say, or even mentions that a site will be AAA if you follow WCAG.

    I also think it’s a shame that so many people in the accessibility industry feel they have to have a poke at someone else’s approach/views when we are all in this together – trying to make the web more accessible.

    All of these points mentioned in this blog are totally valid and in the real world these ‘myths’ are raised time and time again by those who do not understand accessibility or why it’s important.

    True; that some of these ‘myths’ are quite old hat now and need to be re-researched and updated to keep up with technology and the times but at the same time they are a very good starting point for beginners and in many ways they are still valid.

    I have used them a lot in training and have found them to be a great tool to start off a discussion.

    Jonathan H’s blog does raise very interesting points too, but in my view they are for the more advanced – those who already work in this industry and have a good grasp of what the deeper accessibility issues are in a multi-media world. In fact, I would not suggest presenting them to a team who just wants to know where and how to start to make a web site or mobile app accessible – unless you want to scare them off.

    I worked with Jonathan at the BBC and money was (as with all businesses) a major consideration on every project. By making something AAA compliant for users with said cognitive disabilities would make it near impossible and certainly less enjoyable for someone with vision or hearing disabilities – thus inaccessible.

    So, you would not go down this potentially ‘expensive’ route UNLESS perhaps your site was targeted solely at users with Dyslexia or learning difficulties or literacy difficulties. OR the core proposition of your site was video.

    When you have a mixed audience you need to make sure that it’s as accessible to as many people as possible by covering the common denominators of the four disability groups (identified by WCAG et al); not favour one group over an other just because there are 4 million of them rather than 1 million.

    Implementing accessibility in the real world does not cost that much if you plan it in from the start – it costs nothing to ensure that images, links, tables, graphs, infographics are labeled correctly, as you go along. Neither does it cost to ensure that a page has a logical tab order, links are well padded, error message appear next to the error or that the colour on a page has good clear visibility. All these small basic touches can be worked in very easily.

    It’s when major things have been overlooked or ignored that expense soars. For example, implementing subtitles on a multimedia website, which has constantly updating content. The question is, do you find a solution or provide a support mechanism e.g text. The question then is ‘what is the core proposition of the site/app?’

    Nevertheless, I think you have taken Jonathan’s example out of context and it doesn’t work here.

    I am bored of this battle between WCAG and BS8878. It should not be a choice of one over the other – they are both excellent, well informed tools – how far you follow them to the word and when you use them is down to the discretion and experience of the accessibility specialist (or designer, developer, project manager etc…)

    You can never stop learning in this area and the best information always comes from the user! However, again; in the real world you need to apply all of these ‘tools’ plus common sense and business acumen to make websites/apps etc accessible.

    In conclusion, ‘Myths’ were created to introduce, explain and market the topic of accessibility to the ‘lay’ person who wants to learn – they are not something to live and die by.

    Neither are they something that should be seriously discussed beyond the classroom, in my view.

  4. Léonie Watson says:

    “I am bored of this battle between WCAG and BS8878. It should not be a choice of one over the other – they are both excellent, well informed tools – how
    far you follow them to the word and when you use them is down to the discretion and experience of the accessibility specialist (or designer, developer,
    project manager etc…)”

    Good point Lucy.

    When we wrote BS8878 it was to create a standard that focused on organisational strategy and process. It was never intended to compete with WCAG, and in fact BS8878 references the W3C guidelines in several places.

  5. Thanks, this was a useful list. But I think an uninformed developer will still find this too much of a burden. I’ve been working with developers on accessible websites and in every single case, they started by saying they produce accessible websites, and it was a LOT of work to get them to a point to become start working accessibly at the basic level.

    The problem is that WCAG is at the same time too much and not enough. It spend a lot of time and space on issues that medium-size websites won’t be able to comply with like transcripts for video and audio, and things they won’t comply with like color contrast. So basic rules about structured documents, putting labels on forms and sensible ALT attributes are lost in the noise. So developers spend a lot of time checking boxes without knowing which bits are important. As a result you end up with sites that are inaccessible in areas where no extra coding effort was required if they started with the right mind site but that have invested a lot into WCAG voodoo widgets that just get in the way. The http://www.sightandsound.co.uk/ website even doesn’t get it right in some key areas.

    The point about accessibility for cognitive impairments by Brian is a tricky one. Ultimately, you could end up saying, that something is inaccessible because it is in English. So even hinting that headline writers will have to avoid puns and figurative language is going to be a turn off. As a linguist, I study how cultural background affects understanding, and it is much more pervasive than seeing the right films. So if an author would have to pay attention to this, they would never end. But, there are many more easy and helpful tips that will make anybody’s writing better for everyone. Such as using more bullets for summary, putting the important information first, etc. Also formatting text the right way with more line spacing and left alignment will make more of a difference for more people than worrying about puns.

  6. Madeleine says:

    It’s not just developers – writers and editors have a role to play too. There are still to many badly formatted pages and click here’s littering websites which also affect the accessibility of a page..

    Here’s a guide to accessible web content:


Add a comment

Fields marked with an asterisk (*) are mandatory.

Comment details