How to Avoid IE-Specific WWW Development?

IE-less asks: "Can any Slashdot readers help me gather evidence to support the notion that developing an IE-specific WWW site is a bad thing? A state-level US-gov't organization we are contracted with (hence the anonymity) is about to embark on converting a Citrix-based application to a browser-based application, but in order to do so will make it IE Only. Our repeated screams of, 'No! Consider the standards!' have fallen on deaf ears. One of the few things we have found that helps is the Department of Homeland Security's recommendation that people switch browsers (look for 'Use another browser') care of the Get Firefox site. That's the sort of comment that makes people pay attention. The departments in question do not care about monopolies, non-Windows users, closed source expenses, etc. They will pay attention, though, to statements from powerful sources...such as the aforementioned. Anyone else find anything that works?"

Comments

AJAX

[pokka]

Well, you could simply explain that client-side scripting has matured in modern browsers over the last five years or so, and therefore it's much easier to develop an application that works consistently with modern browsers. Point them to articles about AJAX (such as this one) and explain that it's becoming the rule, rather than the exception. You could point out that most modern web apps (such as almost everything Google develops) use the technologies mentioned above and work well with almost any modern, standards-compliant browser.

Re:AJAX

[WebCrapper]

The main problem is that the government uses IE on almost every single computer on their network. You're lucky to get other types of browsers anywhere in the gov. On top of that, you're even luckier to get your home computer to connect to something that is even half important to anything...

They get discounts on MSFT products, therefor use IE specific development programs (IE: Word/Frontpage).

Now, on the other side of things, I have started seeing a move in GS postings towards Handwritting code and using non-Frontpage programs like Dreamweaver.

Americans with Disabilities Act

[Clueless Moron]

Stick that in their stupid faces: If it won't work with lynx, it ain't no good.

I really like that Act, not because I'm disabled, but because it forces MORON web designers to actually write web pages to be media-neutral, which was the entire goddamned point of the web to begin with.

I use Firefox, IE, Opera on my 640x480 Zaurus, lynx when I'm ssh'ing, and on occasion I even google via my cellphone. Sites like BBC really shine there. Even slashdot works out as long as you use the "light" rendering option.

Look at existing logs

[dreamer-of-rules]

Look at existing logs from their website, or similar (friendly) websites. If they are building for a controlled audience (their employees), then they can do whatever works.

However, if the logs show access from non-IE browsers, then they have to justify why they are refusing to serve those people.

Good luck.