Browser support

Levels of support and usage trends

All new web pages must be tested against a relevant browser matrix. This should be appropriate for the audience of your website and the region(s) you are targeting. This section references the Abeille Assurances global standard browser matrix, which should be used as a base level of support. This is based from the usage statistics for the Abeille Assurances global and some country specific websites.

---

Support matrix

The support matrix has been created to specify what priority each browser is and which ones need to be tested against.

• The support matrix references our priority levels.
• Individual browser support levels have been defined via analysis of our online analytics data and external web guidelines.
• Note that testing a browser on various versions of the same operating system family is not required (ie. Firefox only needs to be tested on one version of Microsoft Windows, not them all). However it is recommended to test across different operating systems such as Microsoft Windows and Apple OSX.

The priority level of support for each browser

Note: These priority levels have been set using our online analytics data and should be considered a base level of support. Analytics for an individual website should be used to determine if extra support is required. For any browser where a version is not specified, support is provided for the latest version along with the version preceding that.

Browser targeting

Wherever possible browser targeting and device detection should be avoided, with feature detection being used instead. If it is necessary to use device detection the preferred method for achieving this is via server side device detection.

---

“Priority level” definitions

The rating system that defines the level of browser support has been created to define what level of testing is required.

Priority level A – Fully supported

• Testing is required.
• All content must be available.
• Layout must comply with the creative design unless there is a technical need not to do so.
• All functionality must be available and work as required.

Priority level B – Mostly supported

• Testing is required.
• All content must be available.
• Layout does not have to look identical to creative design (ie, degradation of visual appearance is acceptable).
• All functionality must be available and work as required.

Priority level C – Partially supported

• Testing is required.
• All content must be available.
• Layout does not have to look identical to creative design (ie, degradation of visual appearance is acceptable).
• Core functionality must be available and work as required, however it may function in a more basic manner and enhancements do not need to be available.

Priority level D – Not supported

• Testing is not required.

Note: “not supported” does not mean the browsers are blocked in any way, it simply means they are not tested (thus unsupported browsers could work as well as a priority A browser).

---

Test process

It is recommended that as much real world browser testing is carried out as possible using actual devices. Emulators or simulators should then be used to fill the gaps where real device testing has not been possible. Emulators or simulators must not be used as a replacement to real world testing due to their inaccuracies and the difficultly to test touch interfacing.

For lower priority web browsers a recommended strategy is to use batch testing at an interval by testing against these on a monthly basis across templates instead of isolated components.

Recommended device lists for testing are shown below along with the best options to use in BrowserStack:

Functional device list

The functional device list can be used for testing components with JavaScript interaction. This could include components such as accordions, carousels, drop down filters or any components that require the visitor/user to perform some form of action or interaction with the web page.

UI device list

The UI device list can be used to check components against different visual break points. For example, if there have been major UI code changes then we would need to check whether components on a web page are displayed correctly against different view points ie. a larger screen, smaller screen or bigger mobile and tablet screens.

---

Browser usage statistics

This usage data is collected from the Adobe Analytics tracking tags on the Abeille Assurances UK, PL and SG websites. For browsers that do not have a version number associated the figures are calculated by adding together all versions of these browsers that record a share of 0.1% or more.