Skip to end of metadata
Go to start of metadata

This page details the browsers and versions that we support for all the web pages and applications which we produce.

We have documented the standards we use for writing web pages.

We provide two levels of browser support: 'full support' and 'degraded support'.

Full support is given to all browsers with more than 10% of the total number of visits from external users in a given month. You can find this information in Google Analytics.

Icon

Browser usage stats are available from the Daily Reports from Analog, and Google Analytics (external traffic, internal traffic)


Layouts, designs and functionality must be checked in all these browser versions:

Browser

Versions

Firefox

Latest stable release

Internet Explorer

9, 10, 11

Safari

Latest stable release on Mac.

Latest stable release on iPad.

Chrome

Latest stable release on Windows

In Google Analytics Safari 5.0.x and above appears as 533.16 and above

Degraded support is given to edge-case browsers where the total number of external visits may be below 10% but is still a significant number. All the information provided on the page should be accessible but it is not a requirement for the layout to work perfectly. If there is specific page functionality that does not work in these browsers then it should not be enabled and you should apply the rules for "Dynamic content/JavaScript" as documented below.

Layouts, designs and functionality must be checked in all these browser versions:

Browser

Versions

Internet Explorer

7, 8

You can check IE7 using the Legacy Browser Terminal Server.

Mobile devices

Other than devices specifically mentioned in the 'full support' table above, we provide no official support for any mobile devices, regardless of OS or browser.

Exception: We have some pages targeted directly for mobile devices, and these have been written to render in the WebKit browsers on iOS and Android which were available at that time.

Dynamic content/JavaScript

JavaScript should be used to enhance pages rather than being the only way to access page functionality - applications and pages must work fully in the absence of JavaScript; all visible content and functions should be operational.

For the same reason, a page visitor shouldn't be able to click on a button or link that does nothing!

Other browser support documents

  • No labels

2 Comments

  1. Do these browser type support and testing requirements extend to University hosted and maintained web applications, that are hosted outside your team too? I'm thinking Moodle and SAMIS in particular.

    1. Good question (smile)

      We would advise that wherever possible these standards are adhered to since they come out of the statistics of actual site visitors, but note that they're focussed on the visits from external users and the stats from the average Moodle user may well be different.

      We'll be working with the SAMIS team in the near future on some of their web apps and we'd try and apply these standards since a large proportion of users are external (registration etc.).