Supported Browsers

SVTs web sites should work on a broad range of devices and browsers, but it is also important that we can use modern web technology to build the best experiences possible for our users with newer devices and browsers.

To reflect the dilemma of being modern while supporting old devices and browsers, SVT has two different levels of supported browsers; Minimum Browser Requirements and Browser Recommendations. These are explained in-depth in later sections.

Setting the expectations

The main purpose of these requirements is to communicate expectations about level of service to our users. The secondary purpose is being an internal tool for focusing and aligning our testing and development, bug fixing and workarounds on a manageable subset of the huge number of combinations of browser versions and operating systems that exists.

We strive to develop our web sites in a way so that they should work in all fairly modern standards compliant web browsers and often they work in browsers other/older than those specified in the requirements. These requirements should be seen as a starting point when building new services, but existing services with existing users might choose to actively support older browsers.

 Minimum Browser RequirementsBrowser Recommendations
iOS[1]Safari 10+Safari 12+
AndroidSamsung Internet 11+Samsung Internet 12+
WindowsInternet Explorer 11
Mac OSXSafari 10+Safari 12+
Linux[2] Chrome

[1] On iOS all browsers are still using the Safari rendering engine. So other browsers such as Chrome or Firefox should also work

[2] Linux is not tested explicitly – however a recent version of Chrome or Firefox should work as the functionality is the same on all platforms

Minimum Browser Requirements

These are the browsers that we target when we build the foundation for our sites. This baseline should be feature complete and we should put love into it, both in regard to performance, design and UX. It is allowed to use the Cutting the Mustard approach for browsers at this level and provide a site with no, or only a limited amount of JavaScript.

If well motivated, it might be okay to skip certain minor functionality at this level, but these exceptions should be very uncommon and never apply to main functionality. Any skipped functionality must not appear broken or missing, but be handled in a good way regarding user experience.

  • All content MUST be accessible and usable
  • All navigation MUST work
  • All main functionality MUST work
  • All secondary functionality SHOULD work
  • Visual appearance SHOULD look good

Browser Recommendations

The recommended level is where we try to leverage the latest browser technology to provide the greatest experience for our users. This should be seen as a progressive enhancement on the minimum level and not introduce new content or features. Usually several browsers at the minimum level will have the same functionality and behaviour.

All enhancements should be implemented fairly consistent over all browsers in this level and not pick one browser and focus solely on that.

  • All content MUST be accessible and usable
  • All navigation MUST work
  • All functionality MUST work
  • Visual appearance MUST look good
  • Variation in appearance and behaviour SHOULD be minimized

Selection Criteria

When deciding upon which browsers to support we take several aspects into considerations:

  • Statistics
  • Vendor support
  • Vendor diversity
  • Digital exclusion aspect
  • Strategic platforms
  • Technical considerations