Funny how the same problems come in clusters: there are several current threads that are relevent to this.
The first point is one that I have just finished answering in this thread , and my answer is not one that your boss is going to like, unless yours is an Intranet/Extranet environment.
Quite simply, javascript-dependent public websites are ILLEGAL in Europe, or rather the EU: though most web-heads do not realise it.
All of our governments have signed up to the notion of accessibility, and passed local laws to enforce the issue.
So far this has just been interpretted to mean 'accesible to people with disabilities' like impaired vision. see this articel or this article for more information.
"OK", your boss sez, "We'll provide alt text for images" etc: but that is still browser-dependent.
But what about this:
Web Content Accessibility Guidelines version 2 (WCAG2)
WCAG2 is currently being written by the WAI and is due for release late 2005. The draft guidelines group checkpoints under four main principles:
* Perceivable - all content must be perceivable i.e. provide text for non-text content
* Operable - Interface elements in the content must be operable i.e. access via a keyboard or keyboard interface
* Understandable - Content and controls must be understandable i.e. text should not be ambiguous
* Robust - Content must be robust enough to work with current and future technologies i.e. will work with old, new and future technology[/COLOR]
What you gonna do when someone comes along and sez, "I use a different technology, or an old browser, and it is not javascript complient."? How does that fit with the 'Robust' aspect?
Add that to this, (from the W3.org website)
It will also enable people to access Web content using many different devices - including a wide variety of assistive technologies.
and you have a problem.
What I'm trying to get at is that your web site MUST be accessible to the lowest common denominator if it is public. That means that it must work in text-only mode. Then, and only then, can you off-load the problem to the user and their agent. If you provide a text-complient website then it is up to them to use an agent that can convert that text to their needs.
Throw all this at your boss and tell him to get with the program: make it work at the lowest level and then use enhanced technologies like js and AJAX for those that can use them.