Digital Services. Supported Browser categories. 1 P a g e

Size: px

Start display at page:

Download "Digital Services. Supported Browser categories. 1 P a g e"

Regina Turner
5 years ago
Views:

1 Digital Services ed Browser categories 1 P a g e

2 Contents SUPPORTED BROWSER CATEGORIES Definition Document Authors: Governance Approval Summary Strategic Deprecated Contained Retired Document History... 5

3 1 Definition Document This document provides a definition of the supported browser categories in place within the OU for externally facing websites. 1.1 Authors: Browser Standards Working Group Digital services 1.2 Governance Approval Approval is required from both IT and the business. Each time the standard is updated, both the Technical Design Authority and the Browser Standards Working Group will be required to sign off this definition. This definition and appendices will be revisited every six months, in May and November, to ensure it is still considered in-line with current browser technology. This document is published on the Web standards site at 2 Summary We have a need to define the browsers which will be supported so that we can ensure that the OU will continue to deliver high quality and consistent web-based content. More importantly we also need to identify at what point browsers will cease to be supported so that we can eliminate the need to test against browser technology which is no longer used by a significant number of our users. Note: there may be limitations relating to some technologies used for online learning, meaning that the technology may not meet this standard completely. Open University students should check their module computing requirements for more specific information. It is proposed that we have 4 categories of support, much in the same way that systems are managed within the architectural governance structure. These categories are defined as: 2.1 Strategic Testing Strategy We fully support this browser version for new and legacy applications All content must be readable and accessible, and display and function as per the design, providing an optimal experience across all browsers considered to be at a strategic level of support, i.e. all browsers work and look the same (not necessarily pixel perfect) and conform to the design and functional specification. Strategic browsers will conform to modern web standards for usability and security. Tested against new development and any maintenance releases. New browsers will not routinely be regression tested, i.e. when a new browser version comes along we will not test it against the whole of our estate, rather we will test any maintenance and strategic code releases against the latest browsers. Internet Explorer / Edge (Windows) see Chrome (Windows)

4 Firefox (Windows) Safari (Mac) Device IoS Latest Safari and Chrome Android Latest Chrome 2.2 Deprecated Device We support this browser version for functionality but not look and feel All core content must be readable, usable and function as per the functional specification. Look and feel may not be optimal. It must be possible to use the website or application to perform its primary objective but ancillary elements may not need to be supported at a functional or visual level. The exact acceptance criteria should be defined by the product owner on a case by case basis given the appetite for risk for the site being developed. e.g. Happy Path must be achievable but not necessarily styled as expected, validation messages; popups etc. do not need to be displayed in line with the current digital framework guidelines. Deprecated browsers would be Retired were it not for the significant levels of usage. which no longer have any security support should not be on the strategic list Identified problems are a fixed on a case by case basis based on their severity Any version older than latest and one previous, whose usage is at least 1% of overall traffic. Version previous to latest version. 2.3 Contained Device We support this browser but only for specific applications The specific website or application must function, to the levels specified in acceptance criteria, for a specific browser for which support is required, i.e. we support a specific version of a specific browser for a specific application for a specific audience. The support documentation for the website or application will list any contained browsers that are supported, so that support staff are aware. Contained browsers would be Retired were it not for the specific audience need. Testing will only take place for specific applications where support is required. Tested against new development and any maintenance releases for the specific application only. Assessed on a case by case basis. Assessed on a case by case basis.

5 2.4 Retired Device We no longer support this browser version None No testing will be carried out. Any browser which is not categorised as Contained, Deprecated or Strategic. Any browser which is not categorised as Contained, Deprecated or Strategic. 3 Document History Version Date Author Description 0.1 December 2014 Richard Miller First draft 0.2 December 2014 Sarah Allen, Richard Amendments Miller 0.3 December 2014 Richard Miller Incorporated changes from test team, added section for browser states Jan January 2015 Sarah Allen Incorporated comments from product owners 0.5 January 2015 Richard Miller Updated with latest browser stats 0.6 January 2015 Richard Miller Small wording changes from Design Working Group 0.7 January 2015 Richard Miller Update of January browser categories for devices 1.0 February 2015 Sarah Allen FINAL DRAFT all changes accepted. 1.1 February 2015 Richard Miller Update around Firefox ESR and Beta browsers 1.2 July 2015 Sarah Allen Modifications following consultation with LTS. Added note to Summary; removed final section Browser categories January 2015; removed reference to Opera due to insufficient usage. 2.0 September 2016 Caroline Jeffreys Reviewed and amended by Browser Categories working group 3.0 October 2017 Caroline Jeffreys Reviewed and amended by Browser Categories working group 4.0 October 2018 Caroline Jeffreys Amended to reflect OU Brand

UNIT ASSESSMENT SYSTEM DOCUMENTATION FACULTY

UNIT ASSESSMENT SYSTEM DOCUMENTATION FACULTY November 2013 The purpose of UAS is to collect and measure assessment data for select courses. 1 Accessing the Unit Assessment System Application 2 Browser