Nathan
My concern about your interface is that it relies "totally" on JavaScript
being enabled, it will do nothing at all if JavaScript is disabled. This
flies totally in the face of building accessible sites using progressive
enhancement. Indeed I have to wonder why you chose that particular route as
it simply isn't necessary? As a technical exercise I concede it shows some
merit and that is probably how you came to choose it.
I also have to point out that I have not seen the vast majority of other
offerings which appear primitive when compared against it (but then I'm not
out in the wild!).
- Maurice
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On
Behalf Of Nathan Andelin
Sent: 29 January 2013 04:28
To: Web Enabling the IBM i (AS/400 and iSeries)
Subject: Re: [WEB400] DB Maintenance Design Patterns
From: Maurice O'Prey
Some do care a lot about accessibility (jQuery with jQueryUI and
jQueryMobile to name but one) and it's great when you do come across
them!
I care about accessibility and do provide keyboard alternatives to mouse
events, but is there something about my user interface that triggered your
concern? My original premise was to show something that was usable and
accessible.
-Nathan
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: WEB400@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/web400.
midrange.com
