WordPress.org

Making WordPress.org

Opened 3 weeks ago

Last modified 2 days ago

#4863 new defect

Adding a notice do discourage IE11 usage

Reported by: youknowriad Owned by:
Milestone: Priority: normal
Component: Browse Happy Keywords:
Cc:

Description

I initially created this as Core ticket but I have been told it should be raised here instead. https://core.trac.wordpress.org/ticket/48743

For PHP upgrades, nudging users to update their PHP version proved to be successful.

Maintainability cost of IE11 (In terms of time, bundle size and a lot more) is very high and IE11 is approaching the 1% threshold in its usage worldwide https://caniuse.com/usage-table

I think we should consider adding a notice to discourage its usage.

Change History (5)

#1 @afercia
3 weeks ago

Worth noting that when it comes to assistive technologies, browsers usage is pretty different.

WebAIM runs (almost yearly) a survey targeted to screen reader users. The most recent survey ran between August - September 2019 with 1224 respondents. See https://webaim.org/projects/screenreadersurvey8/

Specifically, two data are relevant: the list of most used browsers and the most used Screen Reader / Browser Combinations.

Most used browsers:
Internet Explorer 11: 10.9%
https://webaim.org/projects/screenreadersurvey8/#browsers

Most used Screen Reader / Browser Combinations:
JAWS with Internet Explorer: 11.5%
NVDA with Internet Explorer: 1.2%
https://webaim.org/projects/screenreadersurvey8/#browsercombos

Not to mention some users reported they use Internet Explorer versions older than 11.

It's a significantly higher IE usage than among the overall population and can be explained with the pretty high cost of updating to a more modern laptop with a most recent Windows version plus a new (pretty expensive) JAWS license.

The good news is that comparing with the previous survey, usage of Internet Explorer continues to decline.

Also worth noting the usage of Internet Explorer is much higher in North America than elsewhere in the world.

Personally, I wouldn't be opposed to encourage users to switch to a more modern browser via the wp_dashboard_browser_nag() powered by browsehappy. However, ending support for Internet Explorer 11 entirely is something that should be considered carefully and would need a clearly established roadmap with a firm date and an appropriate period of notice.

This ticket was mentioned in Slack in #accessibility by nrqsnchz. View the logs.


2 weeks ago

#3 follow-up: @joedolson
2 weeks ago

After discussion in the accessibility meeting 29 Nov 2019, we agree that this it is a good idea to encourage this - we're happy to encourage people off IE 11 if they have the option to change.

However, we want to be sure that this is separate from our ending support for IE 11. IE 11 is a required platform for government clients as long as it's still supported by Microsoft, and is still in use relatively heavily by screen reader users.

Nag needs to take into consideration that people may not have the option to change, be permanently dismissible, and be filterable.

The support question should be a separate issue.

#4 in reply to: ↑ 3 @nerrad
2 days ago

Replying to joedolson:

IE 11 is a required platform for government clients as long as it's still supported by Microsoft, and is still in use relatively heavily by screen reader users.

I've heard this mentioned here and there in a few places. I'm interested in knowing if this is documented somewhere and what this means exactly. I could understand there being application requirements for a certain browser used in a corporate or government environment, but does that also mean employees are restricted from using other browsers for things not involving those legacy applications?

#5 @joedolson
2 days ago

As I understand it, it's a support requirement for development agencies providing services to those government agencies. It's most likely contractual language, and relates to other required platforms for that government agency - it's not a matter of federal policy or law, at any rate.

E.g., you've been contracted to build a platform for the IRS, and since the IRS promises support for IE 11, you need to promise that support in your contract.

But I only know this from second-hand references; it's not an experience I've had myself.

Note: See TracTickets for help on using tickets.