Leave no man behind

25 April 2005


A Blue Perspective: Leave no man behind

Seems like some people don't mind seeing JavaScript only applications, some do. But irrespective of which technology we argue about (CSS, JavaScript, Flash), the inherent question is: when is it worthwhile to cater to a minority?

In some respects, the answer can often be approached scientifically:

  1. How much will it cost to cater to a particular group of people?
  2. How much benefit will we receive from this group?
  3. Is the benefit greater than the cost?

Most often the cost will be monetary – paying for programmers, designers and managers – and the benefit can also take cash form, either directly (through sales revenue) or indirectly (through good will, reputation). However, there are other priorities which can affect your decision. Take accessibility, for one.

I've never been much swayed by the argument that making your site accessible will cover its own cost through gained revenue, particularly where you're performing a retrofit of an existing website, and not building it in from the ground up. It'd be interesting to see a formal case study that tested that hypothesis. But not everything we do in life is just for money. I would count one of the strong benefits of accessibility as being a moral one – enabling access to the disadvantaged. This, I think, is the driving force behind much of the World's disability legislation, so in some respects the threat of punishment by these laws could be considered a negative cost by the particularly immoral.

When including a benefit as ephemeral as moral satisfaction it is hard to exactly quantify it against the bottom line of costs, but accessibility would certainly have a high value. If we're talking about something much more cleancut – such as the ability for a user's browser to execute JavaScript – it's far easier to draw up a balance sheet and make your decisions from there.

What the costs will be and what the benefits will be vary dramatically from project to project. It depends on what you are trying to "sell", who you're trying to sell it to and how you're trying to sell it – information which a mere outsider can only guess at. But no feature should be a given at the start of a project, they are all subject to the same cost/benefit analysis as any other. And ultimately, the market will decide whether your decisions sink or swim.




  1. 1/21

    Lea commented on 25 April 2005 @ 17:58

    I think the main justification for legislation that requires accessibility is economic - the more the disabled are empowered the greater the total GDP.

    So the macro-reason, that government can afford is economic.

    For the individual trader, I am inclined to agree - the probability that making a given website more accessible will improve its bottom line is low.

    For you, me and Joe Blow, the main motivation must be the ethical one - selfish reasons all say "don't do it".

  2. 2/21

    Ryan Brooks commented on 26 April 2005 @ 00:41

    Let's put things in perspective: 12% of the world's internet users have javascript disabled. 18-25% have flash either disabled or not installed. (These numbers were developed during my last case study, numbers may have changed)

    Javascript has evolved, and I think the stigma against javascript is a little moot. Look at how the DOM has evolved.

    The problem now becomes typing Javascript and Accessibilty together. If you have a multi-page form with javascript, it should work still without javascript enabled. (I.e. next/back buttons)

    Personally, I find that many people who go off on the 'yes it looks nice but is it accessible' rant generally are a bit extremist in their views.

    Javascript is allowing for many new applications to come to light. You know about Backbase (http://www.backbase.com/) I assume. The counter in flash is Laszlo (http://www.laszlosystems.com/) which has recently gone open source. RIA is getting a lot of attention, and it was voted Top 10 technologies to watch of 2005.

    My company uses minimal if any javascript for one reason - money.

    I think that there places, and reasons to use javascript. But let's also remember that any functional requirements done via javascript can usually be done by traditional means.

    Just my two cents.


  3. 3/21

    Charles Martin commented on 26 April 2005 @ 05:21

    Try balancing this with a company that wants an application that does most, if not all, of the data input validation before the form is submitted to the server.  The company is faced with a huge amount of bandwidth usage and is trying to improve performance on the database.  Thus, in order to reduce the number of page requests due to poor user input, it is deemed the best means of handling this is to use some javascript to validate dates, email addresses, web addresses, numerical values, etc.  Thus, the only page requests are for valid results.

    I was faced with this same situation and was told that (because the previous developer used it) it would be necessary for me to continue using it in order to provide the best performance for their servers.

    All was great until, after I'm gone, they're faced with somehow managing/creating multiple versions of said scripts to handle different international date/time/monetary formats.  More powerful handling could have been done server-side from the beginning.

    So, not only does it depend on the user.. but it depends on client requirements as well.

  4. 4/21

    Unearthed Ruminator commented on 26 April 2005 @ 22:39

    I usually try to leave no one behind for altruistic reasons (it makes me feel good to do it).

    Technically, for form validation, you should do both client-side javascript validation and server-side validation.  The client-side javascript validation can circumvent needless trips back to the server.  The server-side validation ensures that the data sent from a client is within the valid parameters (to check for valid data from clients who don't have javascript enables and to prevent someone from typing in invalid data in the browser URL line purposefully trying to break your code).

  5. 5/21

    tiffany commented on 18 May 2005 @ 01:06

    Remember that in some countries, not being accessible opens  you up to legal action.

    The cost of legal defense alone may be reason enough to do it "right" the first time.

  6. 6/21

    pgmenonky commented on 17 June 2010 @ 09:35

    LP2WXt <a href="http://revzokdhjksc.com/">revzokdhjksc</a>, [url=http://hvsobjizzizf.com/]hvsobjizzizf[/url], [link=http://vljpxwxgaqwx.com/]vljpxwxgaqwx[/link], http://yrygwnxqrynd.com/

  7. 7/21

    psrewppie commented on 7 July 2010 @ 10:38

    RdlxSe <a href="http://flboitlilbae.com/">flboitlilbae</a>, [url=http://pjdgrbonatic.com/]pjdgrbonatic[/url], [link=http://akiqgmvxmpqf.com/]akiqgmvxmpqf[/link], http://kpqmmvmoxxfu.com/

  8. 8/21

    tybxqa commented on 21 February 2011 @ 17:12

    bd9tMZ <a href="http://bwlxbaazgfbn.com/">bwlxbaazgfbn</a>, [url=http://dkgexadwtpgj.com/]dkgexadwtpgj[/url], [link=http://mlenctqrgamx.com/]mlenctqrgamx[/link], http://fxmcokyzduce.com/

  9. 9/21

    urjnimwkcvk commented on 22 March 2011 @ 17:26

    KVVRB5 <a href="http://ehdfbtfxzayp.com/">ehdfbtfxzayp</a>, [url=http://qfqkettpgawb.com/]qfqkettpgawb[/url], [link=http://lbxchrskjrwg.com/]lbxchrskjrwg[/link], http://ngloflijiten.com/

  10. 10/21

    duchaoyj commented on 23 March 2011 @ 05:51

    5zSTlk <a href="http://dkkojojaiqbq.com/">dkkojojaiqbq</a>, [url=http://ofnldfagxvvd.com/]ofnldfagxvvd[/url], [link=http://qddhcioufwsa.com/]qddhcioufwsa[/link], http://sglqpmtnbvpg.com/

  11. 11/21

    gyetqytlv commented on 23 March 2011 @ 10:42

    KeDsF7 <a href="http://rdmpunkyeacc.com/">rdmpunkyeacc</a>, [url=http://xtgeoeboheqz.com/]xtgeoeboheqz[/url], [link=http://luwahqethqpo.com/]luwahqethqpo[/link], http://ucxrhmfkgyne.com/

  12. 12/21

    Betty commented on 20 May 2011 @ 20:29

    Wow! That's a really neat anwser!

  13. 13/21

    Ethica commented on 21 May 2011 @ 02:09

    Kudos to you! I hadn't tohuhgt of that!

  14. 14/21

    Arry commented on 21 May 2011 @ 07:56

    Now we know who the sensilbe one is here. Great post!

  15. 15/21

    Lynsey commented on 21 May 2011 @ 13:19

    That saves me. Thanks for being so ssenible!

  16. 16/21

    Sherry commented on 5 July 2011 @ 15:18

    Wow! Great tinhking! JK

  17. 17/21

    Johnray commented on 26 August 2012 @ 18:17

    Thank you for writing this great ariltce! I was very much due!@Ben: look at their portfolio; the work they've done before. Then ask for their prices and remember you can always say no, thank you . It's just like any other industry: you would not hire someone to build you a house if they had never built a house before, would you?

  18. 18/21

    Ana commented on 26 August 2012 @ 20:05

    Zabezpieczają się aby nie można było podpisać kktakirolnie zamieniając tekst po plusie. W gmailu można jeszcze wstawić w dowolnym miejscu kropkę tylko wtedy trochę trudniej z katalogowaniem

  19. 19/21

    Pakdhe commented on 26 August 2012 @ 20:43

    Nice post, the problem is that its quite hard to find a good web deengisr and when you do find one they are very pricey.. Where is the best place to look for a deengisr?

  20. 20/21

    Bertil commented on 27 August 2012 @ 00:20

    Thanks. Part of the reason I did the talk is that I'm pastoinase about web accessibility and web standards. The other is that I figured that someone had to do the talk and why not me.Making website accessible does not take that much more work once you know what is neeed to be done.

  21. 21/21

    Adam commented on 27 August 2012 @ 09:21

    Thanks. Part of the reason I did the talk is that I'm pasnoisate about web accessibility and web standards. The other is that I figured that someone had to do the talk and why not me.Making website accessible does not take that much more work once you know what is neeed to be done.

  22. Leave your own comment

    Comments have been turned off on this entry to foil the demons from the lower pits of Spamzalot.

    If you've got some vitriol that just has to be spat, then contact me.

Follow me on Twitter

To hear smaller but more regular stuff from me, follow @themaninblue.

Monthly Archives

Popular Entries

My Book: Simply JavaScript

Simply JavaScript

Simply JavaScript is an enjoyable and easy-to-follow guide for beginners as they begin their journey into JavaScript. Separated into 9 logical chapters, it will take you all the way from the basics of the JavaScript language through to DOM manipulation and Ajax.

Step-by-step examples, rich illustrations and humourous commentary will teach you the right way to code JavaScript in both an unobtrusive and an accessible manner.

RSS feed