On this page
Supported browser approval
Introduction
Browser support determines which bug reports are accepted. It also determines which third party libraries are adopted and influences when those libraries are removed.
Trend data is used because the decision about third party libraries is made months or years in advance of a major release.
The final decision for dropping or adding support for a browser is made in a core issue that includes the relevant data and links that show the conditions have been met.
Dropping a browser
Support for a browser is dropped when the following conditions are met.
- The browser is on course to drop below 1% global usage before the next major release.
- The browser has insignificant screen reader usage or a solid downward usage trend as shown by the latest webaim screen reader survey.
- If the browser is disproportionally included in the latest webaim screen reader survey (e.g. more than 10-15% stable usage when global usage on statcounter is under 1%), then it should not be providing a specific technical reason that makes it better for accessibility.
- If the browser has high usage in a specific region and its usage is on course to be below 5-10% in the countries of that region before the next major release.
Support is removed in advance of the next major release. This allows dependencies and core code to operate on the browsers that will be supported for the duration of that release.
Adding a browser
A browser is added when any of the following conditions are met.
- It is on course to increase above 1% global usage, has significant (>30%?) market share in particular geographic areas.
- It is disproportionately and steadily or increasingly used by screen readers,
- If the browser is disproportionally included in the latest webaim screen reader survey, then it should be providing a specific technical reason that makes it better for accessibility.
References
The following are used to evaluation browser adoption.
- caniuse
- statcounter including the regional filters
- lastest webaim screenreader survey
Help improve this page
You can:
- Log in, click Edit, and edit this page
- Log in, click Discuss, update the Page status value, and suggest an improvement
- Log in and create a Documentation issue with your suggestion