Lack of Access = Barrier to Access

August 10, 2006

Topics: Accessibility, Web standards.

This case arises out of Target’s policy and practice of denying the blind access to, including the goods and services offered by Target stores through Due to Target’s failure and refusal to remove access barriers to, blind individuals have been and are being denied equal access to Target stores, as well as to the numerous goods, services and benefits offered to the public through

First Amended Complaint, Article 24, National Federation of the Blind, et al versus Target Corporation

The point made above, from the accessibility lawsuit against Target corporation by Bruce Sexton and the National Federation for the Blind, is that Target has explicitly denied the blind access to their resources through their refusal to remove barriers to access. This is somewhat semantically different than the terminology commonly used within the accessible web development world. The common language in web development is to state that you are "adding accessibility features" to a website – I’ve certainly used this construction myself. However, it may be far more accurate to state that my actions as an accessible developer are not to "add features" but to remove barriers.

A website, in it’s simplest form, could be considered nothing more than an unorganized collection of hyperlinks and text. It is nothing but information. A web designer transforms this into a website by adding organization, images, color, and sometimes multimedia to this otherwise plaintext collection of information. In this process, it is easy to add numerous barriers to access. Unwary developers may provide an organization which is visually exciting but when read in a linearized fashion makes little sense. They may use color contrasts which are only barely visible (or not visible) to users with poor vision. Any number of problems can arise during the design of a site which a designer unversed in accessibility may be completely unaware of.

An accessible web developer’s job is to remove barriers to access, if working on an existing site, or to minimize the barriers they create when designing an original site. It is almost impossible to create a site without introducing some form of barrier – at the very least, the linearization of text will require that elements come in some order – and any order will be a barrier to the person who wants to reach a different section of the page. However, an accessible web developer can also create aids to the disabled web user. Where a barrier must be erected, an aid must be created. In the previous situation, skiplinks should be provided, which will allow the user to jump between navigation, content, and any other necessary sections of the page.

A lack of accessibility is not inherent to web design. If a site is not accessible, that is primarily the fault of the site’s developer – they have erected barriers to the user. However, a plain text equivalent is not any kind of help. I said towards the beginning of this article that "A website, in it’s simplest form, could be considered nothing more than an unorganized collection of hyperlinks and text.". This is what you get when you upload a plaintext version of your site to the web. Is this accessible? Emphatically not. It does not contain any of the barriers added by the designer, but it is not accessible.

The key which is missing from a plaintext document is organization. Removing semantic organization from a document does not add accessibility. Screen readers are capable of navigating quickly through HTML (HyperText Markup Language) headers – plain text has none. Skiplinks can provide quick navigation between sections of a document – which will be absent in a plain text version. Plain text may be more accessible than the original document, if that document is badly inaccessible, but it is a mistake to consider plain text a suitable substitute for accessible development.

But to get back to the point, if you have created an inaccessible website it is do to your own actions. It is because you have erected barriers which prevent disabled users from accessing your content. It’s not because you have failed to add accessibility; it’s because you have prevented it.

8 Comments on “Lack of Access = Barrier to Access”

  1. Great article; I love how you’ve compared a real-life case with something on the internet. That aside, I agree that website designers themselves are the ones preventing people from accessing their site due to the many complicated things that they do with it. Maybe if they could come up with a way of using only simple techniques so as not to make the website look too cluttered in its text-only version, it would work out fine.

  2. Joe you are right, everyone has an opinion on a full range of subjects from on site SEO to usability. My own opinion is to constantly work on improving conversion ratios.

  3. Differentiating between the things that matter and the things which don’t in web accessibility takes pretty careful attention to the practical, end-user experience.

    There are definitely those who seize upon minor issues and turn them into major ones — but the only people who’s opinions really matter, ultimately, are those who will use your site.

    When in doubt: ask the visitors!

  4. The main problem I’ve found in trying to make my website is the nitpicking of silly things that don’t matter. I’ve finally got my index page validated for css and html for strict, and then I started looking at accessibility. So far I’m only an A and if I want to move further along to AAA I might have to ask for help, which fills me with dread as I’ve used css to table style my page and I got knocked down the last time I asked.

    This is where the main problem lies, where style becomes more important than content, and that little people trying to build a silly, personal site are made to feel small before they’ve got their first page even up. I’m not going to give up, even if it takes a bit of time, because I think it’s worth the effort (even for a private site) to make it as accessible as possible.

  5. I think if you’ll re-read the earlier posts in the Cre8asiteforums thread on that topic, you’ll very quickly see my opinion on the issue…

    On the other question — most designers are focused on design. When it comes right down to it, they aren’t thinking about these issues or they don’t care. I don’t think it has as much to do with intent as it does with ignorance.

    As much as web standards and accessibility have a much higher profile now than they did in the earlier days of the Internet, it’s still a relatively small area of the overall web design community.

  6. Thanks Joe, you mirror my thoughts exactly. Why do you think designers fail with this issue? Is it down to time, having to quote at the low end to secure the contract or simply not understand SEO fundamentals.

    I also wonder what your thoughts are on designers adding a hyperlinking logo to clients websites, without permission.

  7. Certainly. At the bare minimum, web developers should have a thorough understanding of search engine friendly design. Any developer should know how a search engine is going to approach, navigate, and comprehend the sites they develop.

    Do they need to be capable of doing link building, managing PPC campaigns, or analyzing statistics to find marketing opportunities ? No, not really. But they should definitely be capable of developing a site which is well set-up for the implementation of these processes.

    Thanks for the question!

  8. A general question

    Do you think a web developers should have a better understanding of SEO, thus providing their clients with a more rounded product?