Ok, I can see that we aren't getting the issue with accessibility. The
For me the wonder of the web is that it makes so much available to so many. The fundamental concept of the web is that it *is* available to all users of *all* devices. the future is bound to see an increase in the number of people using PDAs/phones to access the net (I've been doing this more and more recently) and we need to cater for this. There are very few reasons to rely on JavaScript. Do so at your peril.
Anyway, accessibility aside, my gripe is with Domino and the fact that its core functionality is needlessly tied to a reliance on JavaScript. I don't believe this has anything to do with WebSphere. I think it's merely because Lotus wouldn't have thought far enough ahead to envisage people wanting to do it any other way than their way. Session-based form behavious exists with the &Seq=1 thing, why can't we do this when JS is turned off!?
Ron. JS is standards-based? Are you sure?
Ok, I can see that we aren't getting the issue with accessibility. The
For me the wonder of the web is that it makes so much available to so many. The fundamental concept of the web is that it *is* available to all users of *all* devices. the future is bound to see an increase in the number of people using PDAs/phones to access the net (I've been doing this more and more recently) and we need to cater for this. There are very few reasons to rely on JavaScript. Do so at your peril.
Anyway, accessibility aside, my gripe is with Domino and the fact that its core functionality is needlessly tied to a reliance on JavaScript. I don't believe this has anything to do with WebSphere. I think it's merely because Lotus wouldn't have thought far enough ahead to envisage people wanting to do it any other way than their way. Session-based form behavious exists with the &Seq=1 thing, why can't we do this when JS is turned off!?