I can quite easily imagine the scenario, but that is not really my point. I am talking Germany here, and they are very strict with us and the local regulations (and have paid us for enhancements that make things comply with German law).
Either:
1) They do not employ disabled people (not likely, but possible)
2) Their disabled people can still use the application, despite Javascript being enabled
3) Their disabled people cannot use the application with Javascript enabled
My assumption is the answer is 2) - because if it was 3) they would be down on us like a ton of bricks.
Now you are faced with the question - should you build the application in a progressive way or not? Possibly you should, but then if it is a bespoke application, would you do so at you own expense if the customer is not interested in having it? One thing is for sure, the customer won't pay for something they don't deem is necessary.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Maurice O'Prey
Sent: 29 January 2013 13:42
To: 'Web Enabling the IBM i (AS/400 and iSeries)'
Subject: Re: [WEB400] DB Maintenance Design Patterns
Kevin
So imaging you are a person with a disability and you apply for a job. You told you cannot have the job because you cannot use the DB administration system.
True, some employers have a long way to go but just because it is an Intranet application doesn't make it OK.
- Maurice
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Kevin Turner
Sent: 29 January 2013 13:28
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] DB Maintenance Design Patterns
Ahh ok - I thought you meant that those libraries had built in progressive features that we have not come across (rather than the ease with which you can transform elements into widgets when it is enabled).
It is an interesting side topic - but I wonder how much effort we would put into it given that we are not developing internet websites, but rather intranet applications. I would have thought that our customers would have complained long ago if we were developing things that their disabled employees could not use.
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Maurice O'Prey
Sent: 29 January 2013 13:20
To: 'Web Enabling the IBM i (AS/400 and iSeries)'
Subject: Re: [WEB400] DB Maintenance Design Patterns
Kevin
As we use jQuery and jQueryUI extensively, I am still quite interested
in
your assertion that they are fine examples of how to develop your website.
It could be that we are not taking advantage of some compliant things we could so it would be useful to know - but just how to you do that when Javascript is turned off? jQuery and jQuery UI won't load and therefore none of the features there-in work.<<
The approach is to build the site without JavaScript first then introduce it progressively. Clearly JQuery does not load if JavaScript is turned off. So your basic site has buttons and links to make it work as it would in the good old days (when javaScript was the much hated language it isn't today).
Then if JavaScript is enabled (you don't even need to check) you remove those and replace them with fancier widgets etc. by adding the new objects to the DOM or manipulating CSS classes (piece of cake with jQuery)
Here is a perfect example on the human rights web site. With JavaScript enabled the user can click the plus sign to expand the accordion and the relevant content is displayed (this could even be grabbed from a page further down using an Ajax call). If JavaScript disabled the page renders the normal list of hyperlinks that where there in the first place (perfect).
http://www.equalityhumanrights.com/advice-and-guidance/new-equality-act-guid
ance/equality-act-guidance-downloads/
I confess I am not perfect but I learn more about what the site needs to do by trying to do it this way (rather than being left with the knowledge that this ain't going to work for some people) and it does give a great sense of satisfaction. In fact the site just "feels" more complete IMHO
Nice to know all visitors to your site can use it!
- Maurice O'Prey
NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected.
--------------------------------------------------------------------------------
CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT
Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.
midrange.com
