As a web application developer whose bootstrapped startup needs every user it can get, let me just say: I am perfectly willing to forgo all IE6 traffic.
As a web application developer whose bootstrapped startup needs every user it can get, let me just say: I am perfectly willing to forgo all IE6 traffic.
IE6 is a bad low standard. But it remains a target which in accommodating it also addresses many other low-capability browsers.
I don't use IE6 myself (though had, some years back on Linux, to access work-related and Intranet sites on occasion). Currently my main beef is that my, yes, ancient, Android 2.2 browser is utterly normed on many sites. Including no font downloads, so no text at all, on far too many websites. Wired and Medium among many others. Obscuring sidebars elsewhere.
Really annoying.
TBL's original HTML docs remain quite accessible however.
You actually should bend over backwards to cater to as many users as possible, especially if you are getting paid to build websites for users.
Some countries require sites to be accessible to the disabled. If you design sites for the US government, they should also be accessible to 0.1% of blind or no-script users.
Sure, IE6 as a baseline is very progressive, but it is certainly doable. Less so, if you start with an inaccessible website and catering to as many users as possible is an annoying time-consuming afterthought.
If you can not muster an accessible progressive enhanced website, then you can not muster a js-only ARIA compliant website either. Your only hope is to make something profitable. That's being a marketeer or business man with a little HTML skills, not being a solid web dev.