Title: Discussion summary: Dropping support for IE11 Author: Héctor Prieto Published: March 25, 2021 --- [ ](https://profiles.wordpress.org/priethor/) [Héctor Prieto](https://profiles.wordpress.org/priethor/) 7:14 pm _on_ March 25, 2021 Tags: [accessibility ( 59 )](https://make.wordpress.org/core/tag/accessibility/), [browser support ( 6 )](https://make.wordpress.org/core/tag/browser-support/), [performance ( 419 )](https://make.wordpress.org/core/tag/performance/) # Discussion summary: Dropping support for IE11 As a follow-up to the very active discussion around the [proposal to drop support for IE11](https://make.wordpress.org/core/2021/03/04/discussion-dropping-support-for-ie11), there is a majority **agreement to move forward with dropping support**. The next steps are to figure out a timeline and what it means for projects/teams to drop the support. Regarding timeline, there are two upcoming milestones where support could be dropped: 5.8 and 5.9. The argument for dropping in 5.8 is to realize the change and improvement quicker, while others are inclined to wait until 5.9 to provide a longer window between the official announcement and the effective date. The decision when will be left to the release team for WordPress 5.8; this team is not formed yet as it [depends on the April go/no-go Full Site Editing merge](https://make.wordpress.org/updates/2021/03/12/full-site-editing-pre-merge-overview/). _This post was written in collaboration with [@mkaz](https://profiles.wordpress.org/mkaz/), [@annezazu](https://profiles.wordpress.org/annezazu/), and [@youknowriad](https://profiles.wordpress.org/youknowriad/)._ [#accessibility](https://make.wordpress.org/core/tag/accessibility/), [#browser-support](https://make.wordpress.org/core/tag/browser-support/), [#performance](https://make.wordpress.org/core/tag/performance/) ### Share this: * [ Threads ](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/?share=threads) * [ Mastodon ](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/?share=mastodon) * [ Bluesky ](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/?share=bluesky) * [ X ](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/?share=x) * [ Facebook ](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/?share=facebook) * [ LinkedIn ](https://make.wordpress.org/core/2021/03/25/discussion-summary-dropping-support-for-ie11/?share=linkedin) 1. ![](https://secure.gravatar.com/avatar/6f505c6be9a951929a99becb6b413dcfa583a5ca3dd0f7320766fee1481f0f82? s=32&d=mm&r=g) 2. [Jb Audras](https://profiles.wordpress.org/audrasjb/) 8:16 pm _on_ March 25, 2021 3. Thanks for summarizing the feedback received in the previous post. 4. If the decision of the 5.8 release leads is to drop IE11 support in 5.8, [@peterwilsoncc](https://profiles.wordpress.org/peterwilsoncc/) and I could definitely take care of updating the Browsehappy notice in one of the upcoming minor versions. 5. Indeed, even if the Browsehappy notice can be updated independently from CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. releases, I think it’s better to update alongside a release, to give better visibility to this change. 6. ![](https://secure.gravatar.com/avatar/5612a0b1e26e958b7cb153ad8d69325be61525b2bba4819361bb69f127ec34b4? s=32&d=mm&r=g) 7. [mrwweb](https://profiles.wordpress.org/mrwweb/) 9:29 pm _on_ March 25, 2021 8. A quick piece of feedback: It would be helpful if this post provided a summary of the discussion that included not just the majority opinion but the key pros, cons, and considerations for implementation. I think that would both increase confidence in the decision and also provide guidance for next steps. 9. ![](https://secure.gravatar.com/avatar/4fd344e387cd0febbb417ee2a2bef7db6b40c8f7ecf4265fb41dcef8e9fa8c4b? s=32&d=mm&r=g) 10. [Joe Dolson](https://profiles.wordpress.org/joedolson/) 4:45 pm _on_ March 26, 2021 11. Per conversation in the accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia. org/wiki/Accessibility) team today, we’d appreciate it if the process for removing IE11 support could include ongoing documentation of the impact of the changes on IE11, so that we can keep track of functional changes in IE11 that result from this, particularly any changes that might impact assistive technologyAssistive technology **Assistive technology** is an [umbrella term](https://en.wikipedia.org/wiki/Umbrella_term) that includes assistive, adaptive, and rehabilitative devices for [people with disabilities](https://en.wikipedia.org/wiki/Disability) and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the [technology](https://en.wikipedia.org/wiki/Technology) needed to accomplish such tasks. 12. [https://en.wikipedia.org/wiki/Assistive_technology](https://en.wikipedia.org/wiki/Assistive_technology). 13. ![](https://secure.gravatar.com/avatar/85784f579efa175aa4e9193b456ed6a19a3382147d32e97fcbb3d9fa50e871b9? s=32&d=mm&r=g) 14. [lmcdo](https://profiles.wordpress.org/lmcdo/) 3:10 am _on_ April 1, 2021 15. Please take into consideration that there are in-support Microsoft devices (Windows RT devices) that only support IE11. Those devices are supported through 2023. Obviously that is not a large percentage of the user base, but people still using RT devices may not have means to replace those devices. 16. * ![](https://secure.gravatar.com/avatar/85784f579efa175aa4e9193b456ed6a19a3382147d32e97fcbb3d9fa50e871b9? s=32&d=mm&r=g) * [lmcdo](https://profiles.wordpress.org/lmcdo/) 3:23 am _on_ April 1, 2021 * Frankly, I didn’t see the prior post. I’m a little disappointed. In my opinion, there should be major version update warnings for whichever version drops support, but both of these are startlingly early. I would hope that the default themes continue to support IE11 into the new versions, and only the adminadmin (and super admin) panel drops support. * Obviously, supporting an old web browser is no fun, which explains the large number of comments in favor of dropping support. But WordPress is too big of a percentage of the Internet to drop support for an in-support web browser on the client side. Dropping it on the admin side however is 100% fine. - ![](https://secure.gravatar.com/avatar/cd257f389c91f137dab25f343b527123e887135b01921ebb6206e40cfa2eb636? s=32&d=mm&r=g) - [Knut Sparhell](https://profiles.wordpress.org/knutsp/) 7:54 am _on_ April 1, 2021 - It seems this primarily about adminadmin (and super admin) from WP 5.8 and onwards, with blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. editor, upcoming FSE and Twenty Twenty-Two. I see no plans to massively remove support for IE11 in old coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. themes. The old themes are somewhat maintained to support new core technologies, and I guess it may be some discussions if, say, Twenty Seventeen 2.7 (next), will lose IE11 support on the front. - For the very small fraction of users who want to keep IE11 functioning in admin for some time, immediately updating WordPress, or bundled themes, to latest have never been mandatory – only strongly suggested. - The “bigness” of WordPress involves both a huge responsibility to try to keep support for whatever people use, and must use, but also to try to bring both itself and the whole www forward by not keep dragging along completely outdated things almost nobody use. That would only delay phasing out IE for the few that still clings to it. 17. ![](https://secure.gravatar.com/avatar/67da3ce68fb38529f91d8d437694ae66fbde283f6ff637f7c7c22bf2e5047cb7? s=32&d=mm&r=g) 18. [Ofer Shaal](https://profiles.wordpress.org/shaal/) 4:38 am _on_ May 20, 2021 19. Microsoft announced today the official EOL of IE11 – June 22, 2022. 20. [https://blogs.windows.com/windowsexperience/2021/05/19/the-future-of-internet-explorer-on-windows-10-is-in-microsoft-edge/](https://blogs.windows.com/windowsexperience/2021/05/19/the-future-of-internet-explorer-on-windows-10-is-in-microsoft-edge/) Comments are closed. # Post navigation [← CSS Chat Summary: 18 March 2021](https://make.wordpress.org/core/2021/03/25/css-chat-summary-18-march-2021/) [A Week in Core – March 29, 2021 →](https://make.wordpress.org/core/2021/03/29/a-week-in-core-march-29-2021/)