[1] https://webaim.org/projects/screenreadersurvey8/#browsers
[1] https://webaim.org/projects/screenreadersurvey8/#browsers
It might not be IE6 stable, but better than running nightly.
Treating security as an absolute is rarely useful because very few things are completely secure. No browser will be completely secure for the foreseeable future.
Microsoft is offering IE11 extended support until at least 2025, so I wouldn't bet on that.
Why has it taken so long for corp America to move off of IE? There are so many other better alternatives.
I still sometimes have flashbacks of having to design around and support IE6. /shudder
Oracle EBS uses NPAPI (AKA Java Plugins AKA Java Applets). Chrome dropped support for NPAPI years ago, and since then we've been using IE to whenever we need to use Oracle EBS.
I understand that the latest version of Oracle EBS might now support the cutting-edge technology of Java Web Start to continue to deliver their 1990's era grey-blah UI's with shitty layout. I don't even care to ask about upgrades.
Negotiating with the bean-counter types that have enabled Oracle to put it's slimy tentacles into every critical area of the business is a dreadful, thankless task. I expect it will keep running, at its current version, long after I leave or retire. At some point, I expect employees will need to spin up VM's to open IE to use the f-ing thing-- perhaps they can set it up in their "forever" dream OS, Windows NT with IE4?
But even if we could use the "latest version" a quick google image search for "Oracle EBS screenshots" shows that UI-wise, not much has changed. Maybe they got rid of the insipid flash-light icon? I didn't want to get too stressed by looking closely.
In two years the C-level/VP responsible has long since taken the golden parachute and his successor is stuck with the bill.
Also, any sort of internal IT stuff is exclusively seen as a cost center by the MBA bean counters. Stuff like employees leaving due to outdated IT isn't something quantifiable in impact unless you have entire departments walking away at once.
In some cases this was off the shelf software from vendors who had gone out of business. In other cases it was software built in house that would require a complete rewrite to modernize.
All of this software was tightly integrated into processes that were critical for the company to operate. While the cost of replacing the old software was a consideration, the biggest concern was the potential disruption to operations.
If a software change reduced productivity or even worse caused work to stop entirely, it meant millions in financial impact.
1) Sometimes companies go out of business or stop supporting\updating things. If you build critical processes around these outdated tools, it can be very difficult to change.
2) Users aren't savvy enough to know when to use Chrome, Firefox or IE. Some aren't even savvy enough to call things the correct names (looking at you Mozzarella Foxfire). So they just settle on on a lowest common denominator.
Granted, this is the same codebase that has an element on their login page named "acceptCredintials", so... that's the starting point.
Bottom line: Web developers should not feel obligated to keep supporting IE 11 for the sake of screen reader users.
Were you able to use other sources than Google Analytics to look at the browser population? I imagine working with the NHS that things like HTTP access logs are harder to wrangle (if they exist at all)
I say this because even though your anecdote rings true, I’ve seen many people in offices use IE 11 purely out of ignorance and comfort reasons rather than because they were forced. They had Edge, Firefox installed but stuck with IE because no one told them to stop using it.
We may be underestimating the portion of “if it ain’t broke why fix it” crowd are using IE 11 but it’s hard to say with statistical data alone.
Anyway, regardless of how it’s sliced, it’s low enough now for libraries to start dropping.
Some of these Applet-based things have been migrated to modern web, but many still haven't, since it is almost 15+ years of software development now needing to be re-written.
There have been discussions about Edge's "IE Mode" but unfortunately that only applies to domain joined machines, and they have a BYOD policy.
As with a phone, if it bothers the employees (it'd certainly bother me) have them buy a laptop for work only.
It is unlikely someone would purchase from anywhere than their home Windows PC, and I don't think many are using accessibility-related devices (the site was using a third party component that turned out to be terrible for accessibility, and it was years before anyone complained about it (and we then replaced it with one that was accessible)).
I just took a look at the logs for the past 12 months. Here are the relative numbers of successful orders by browser, normalized to Firefox on Windows 10 = 100.
On Windows 10: Chrome 602, IE11 116, Firefox 100, Edge 94.
On Windows 8: Chrome 44, Firefox 16, IE11 14, IE10 4.
On Windows 7: Chrome 76, Firefox 40, IE11 30, IE9 2.
On Vista: Chrome 8, Firefox 4.
On XP: Chrome 6, Firefox 2.
I work in healthcare, so I don't get to make lazydev excuses about time constraints and "edge cases." The people still using IE are the people who need my web sites the most.
If I were to read this statement uncharitably, I would conclude that there is plenty of money in healthcare to be wasted on supporting outdated technology, adding to the already outrageous costs of healthcare. Furthermore, if you're not lazy, you're probably creating unnecessary work.
> The people still using IE are the people who need my web sites the most.
From a holistic welfare perspective, giving these people a modern web browser would be better than maintaining their status quo.
I love working in healthcare but the hospital side is atrocious in my experience.
I will try to get the name tomorrow.
Me personally, I want my sites to be accessible from libraries, that old device in the closet you're attached to, survival centers and shelters, old kiosks stuck in the corner of a community space somewhere, and all other kinds of scenarios I haven't even imagined, but I don't want to leave those users out in the cold.
So this reflects my experience as well.
Edit: a few of the IE11 user agent strings even mention Windows NT 6.1, and no x64 or WOW/Win64, so I guess they're still running 32 bit Windows 7.
In the US the number has dropped significantly over the past five years (it was >50% but is now under 25%).