3 ms·
I think the best strategy is to display a message warning your site may not work on IE6 and simply stop testing IE6. If it works, great, if not -- too bad. Goin
by jsz0 17y ago
I think the best strategy is to display a message warning your site may not work on IE6 and simply stop testing IE6. If it works, great, if not -- too bad. Going out of your way to block people who very likely have no control over the browser they're using at work just seems pointless. Most IT departments aren't going to feel pressure to upgrade based on their employees wanting to use non-work related sites. A better strategy would be to include a scary warning about IE6 being unsafe. This might at least shame some IT departments into upgrading. It works... I'm being shamed into buying legit SSL certs for intranet sites because I'm sick of people complaining about the scary warnings you get from self signed certs these days.
- pemdas 17y agoIt really sucks to design for IE6 but to make purposely make a site that breaks in IE6 is so bad for accessibility. If your CSS messes things up in IE then at least just displayed unstyled semantic HTML. At least the user will be able to access the content which should be what matters most.