The Mythical cost of Accessibility

Recently I had a conversation with a web developer who was working for one of Sydney’s larger web development houses, and brought up the subject of web-standards and accessibility.
I was very interested to find out this persons’ view of and exposure to this subject. The answer I received has been indicative of most of the similar conversations I’ve had since, and is what made me finally decide that it was time to put the record straight.

According to this web developer, accessibility was a do-able, but complicated (almost mystical) additional function that would cost the client “3 times the amount of a normal site”, and would “look terrible anyway”. All of a sudden, the client decides accessibility should not really be such a big priority after all.

This view, that seems to be commonly held amongst the web development community, leaves me quite astonished as it is entirely erroneous. Let me clarify:

  1. Accessibility costs no more than a normal site because it’s not about adding extra code. It does not require an additional effort, it just requires the usual effort be administered using a different approach to designing/coding.
  2. Accessibility is not synonymous with unnattractive design. A developer with expertise in style sheet design can eliminate the prospect of an accessible site being complete design ‘faux pas’.

There is a lack of design houses in Australia that boast the inhouse skills to create a fully accessible web site that will maintain the same quality of ‘look and feel’ as a traditional web site. This most likely accounts for the often exorbitant costs applied. Accessibility 1st, with every project, aims to reduce the experience gap by passing on our enthusiasm and knowledge in designing and coding with web-standards, this means that when we leave, that might be the last time you need to see us.

At Accessibility 1st we highly recommend that you start any web based project with accessibility in mind at the outset. This will future proof you or your business from any future legal prosecution, the HREOC recommended in 1998, that attaining WCAG Priority 1 — is a must, 2 — you really should and 3 — would be nice.
What was acceptable 1 year ago, let alone 5, may now no longer be acceptable, when Accessibility 1st creates a site, we aim to attain Priority 3 (AAA) rating.

When designing with web-standards the savings to be made are phenomenal. For example, because the code is valid, the browser doesn’t have to think as much, therefore the browsing time is faster and lowers bandwidth and associated costs. Additionally, updating the ‘look & feel’ of a site only requires tweaking of the style sheets, not a redesign of every page, thereby enabling unbelievably fast and pain-free migration efforts and brand/style updates. As a result this means less work for the developer and less money you have to part with.

At Accessibility 1st we are sold out on the business advantages of building accessible websites, but the extra appeal is that resounds with our commitment to social justice and equal opportunities for all. Imagine for a moment that you were disabled, and you knew the power of the net as an information, services and communication hub. If you knew that websites could be built to enable full access for all wouldn’t you be disgruntled to know they weren’t due to myths and misunderstandings?

Australia has recorded that 19% of it’s population has a disability; can you afford to ignore this amount of potential customers?