Skip to content
This repository has been archived by the owner on Mar 5, 2018. It is now read-only.

Latest commit

 

History

History
67 lines (46 loc) · 3.28 KB

BROWSER-SUPPORT.md

File metadata and controls

67 lines (46 loc) · 3.28 KB
Raw

Browser support

The UI-Kit team needs to support all of our users, regardless of their device, web browser or other user agent.

Equal access to information about laws and government programs is a legal requirement under the Disability Discrimination Act (1992).

This document has drawn on analytics data from various major *.gov.au sites.

Mobile browsers

Browser Platforms Minimum version Advanced support status
Chrome Android, iOS 21 Tested (Android only)
Firefox Android, iOS 28 Untested
Safari iOS 3.2 Untested
Android browser Android 2.1 Untested
IE Windows Mobile 10 Untested

Minimum version based on support for CSS Flexible Box layout modules.

Desktop browsers

Browser Platforms Advanced support status
Chrome Windows, OS X Tested
Firefox Windows, OS X Tested
Safari OS X Tested
Opera Windows, OS X Untested
Yandex Windows, OS X Untested
Edge Windows Tested
IE 10 & newer Windows Tested
IE 9 & older Windows Tested — functional support only

All browsers listed are latest stable release, except Internet Explorer.

Unsupported browsers

We list commonly used browsers and devices and their rough test status. Other combinations may be supported but have not been extensively tested.

We are aiming for a solid HTML mobile-first foundation that provides functional support for the browsers and devices of all of our users.

Advanced support

  • All (or most) documented features.
  • Advanced functionality and behaviour.
  • Advanced design using JavaScript and CSS.

Functional support

  • Accessible content.
  • Users can complete critical tasks.
  • Basic page design and layout, based on the simplest layout available to graphical browsers.
  • Similar look and behaviour across all pages (performance will still vary across browsers).
  • JavaScript and CSS not necessarily required.

As we perform browser testing we will provide component-specific documentation. This will specify what is critical and what provides advanced functionality.

Principles

  1. Support basic access and functionality in the browsers and devices of all of our users.
  2. Build a solid semantic HTML5 foundation.
  3. Progressive enhancement over graceful degradation. Build the basic foundation for the lowest common denominator then enhance — instead of a managed degraded experience for older browsers (fault tolerance).

We define ‘support’ as:

  • making things usable before they go live
  • improving and fixing issues found in production environments.