12 Q1 2014 Executive summary Support does not mean that everyone gets exactly the same thing Instead every user should be able to consume as much as their browser can technically support Grades ID: 1009087
Download Presentation The PPT/PDF document "Graded Browser Support Version" is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
1. Graded Browser SupportVersion 1.2 Q1 2014
2. Executive summarySupport does not mean that everyone gets exactly the same thingInstead, every user should be able to consume as much as their browser can technically supportGrades give us a framework to prioritize our supportInitial scope includes all WCMS websites excluding the uwaterloo.ca homepageA-Grade browsers are:Chrome (latest stable desktop)Firefox (latest stable desktop, LTS build, UWaterloo distributed)Internet Explorer (8.0 – latest stable desktop)Safari (latest stable desktop)University of Waterloo GBS V1.2
3. PurposeTo provide a broader and more reasonable definition of “support”Introduce the notion of “grades” of supportTo document our expectations of browser support for the UniversityUniversity of Waterloo GBS V1.2
4. What does “support” meanDoes not mean that everyone gets the same thingRequiring the same experience for all creates an artificial barrier to participationAvailability and access to content should be our priorityEvery user should be able to consume as much as their environment can supportProgressive enhancementUniversity of Waterloo GBS V1.2
5. Progressive enhancement v. graceful degradationBoth are approaches to the engineering of “fault tolerance”GD prioritizes presentation and permits less widely-used browsers to receive lessPE puts content at the center, allows most browsers to receive morePE is a healthier and more forward-looking approach and a core concept of GBSUniversity of Waterloo GBS V1.2
6. What are grades of support?While an inclusive definition of browser support is necessary, the support continuum does present design, development and testing challengesIf anything goes, how do we know when the experience is broken?To address this question and restore sense of order to the system we define “grades” of supportUniversity of Waterloo GBS V1.2
7. Initial ScopeWCMS websitesExcludes uwaterloo.ca homepageExcludes authoring interfaceThis will change over timeUniversity of Waterloo GBS V1.2
8. DefinitionUniversity of Waterloo GBS V1.2 X-gradeA-gradeB-gradeC-gradeFunctional siteFullFullEnhancedBasicUsageRareCommonRareRareAgeModernModernModern - OutdatedAntiquatedStandardsCapableCapableMostly capableIncapableCSS3FullFullPartial to fullLimited to partialSupport by teamNoneFullNoneNoneTest by teamNoFull (before release)Not automaticNot automaticBug fix by teamNoYes (ASAP)Yes (soon)Maybe (when possible, if simple or hyper-critical)
9. GBS chartX-gradeA-gradeB-gradeC-gradeAndroid----4.x3.x and earlierBlackBerry----10.x,7.x6.x and earlierChromeChrome CanaryLatest stable (desktop)Latest stable (mobile/tablet)--FirefoxFireFox NightlyLatest stable (desktop), LTS build, UWaterloo distributedLatest stable (mobile/tablet)--Internet Explorer--8.0-latest stable (desktop)7.0, Windows RT, mobile/tablet6.0 and earlier, mobileSafari--Latest stable (desktop)6.x (desktop),iOS 7.x,iOS 6.x5.x and earlier (desktop and iOS)OtherNightly Webkit builds----Opera, Opera Mini, Maxthon, any others not mentionedUniversity of Waterloo GBS V1.2
10. Requirement levelsUniversity of Waterloo GBS V1.2 X-gradeA-gradeB-gradeC-gradeNo coding to specifically target X-grade browsers except for new standards-compliance or extreme circumstancesMust work without hacks (browser detection, reliance on parsing bugs) or shims; should work without JavaScript when possible; cannot require FlashCan use shims, which may require JavaScript and/or FlashCan use shims, but may be untested; can require JavaScript and/or Flash for certain functions
11. Special considerationsUniversity of Waterloo GBS V1.2 BROWSERISSUEOUR SOLUTIONIE8 and belowNo support for media queriesJS must be enabled for RWD experienceIE8 and belowNo support for HTML5 doctype and elementsJS must be enabled (shim) reference: http://www.paulund.co.uk/turn-on-html5-in-ie8-or-lowerIE8Incomplete support for :before and :after (http://css-tricks.com/browser-support-pseudo-elements/)Careful coding; shims may be availableIE7 and belowNo support for :before and :after (http://css-tricks.com/browser-support-pseudo-elements/)Careful coding; shims may be available
12. Special considerationsUniversity of Waterloo GBS V1.2 BROWSERISSUEOUR SOLUTIONAnyTo be determined (http://caniuse.com)Careful coding; shims may be availableIE8 and belowNo support for SVGShim or alternative contentIE7-8Issues with transparent PNGs and opacityAdd filter to CSS for IE7-8, see: http://www.jacklmoore.com/notes/ie-transparency-problems/
13. University of Waterloo GBS V1.2 *Source: all Uwaterloo traffic except for departments and facultiesAnalyticsFor q1 2014
14. Device overviewUniversity of Waterloo GBS V1.2
15. Operating system + browserUniversity of Waterloo GBS V1.2
16. Browser + Device categoryUniversity of Waterloo GBS V1.2
17. Screen resolutionUniversity of Waterloo GBS V1.2
18. Mobile device + browserUniversity of Waterloo GBS V1.2
19. Internet explorer breakdownUniversity of Waterloo GBS V1.2
20. Appendix 1Authoring interface requirementsUniversity of Waterloo GBS V1.2 Much stricter requirements:Only A-grade browsers are supported, with the exception of Internet Explorer, which is unsupportedSome aspects may require JavaScriptCreation of certain types of content is prohibitede.g. CSS, JavaScript, iFrames
21. Appendix 2Standards and restrictionsUniversity of Waterloo GBS V1.2 All system-generated code and, as much as possible, all user-entered information must meet accessibility standards (https://uwaterloo.ca/web-resources/resources/accessibility) and use semantic markupVideos and sound must never automatically begin playingAny pop-ups or “lightboxes” must require a click (or keyboard equivalent) to activatePrimary site navigation must never lead directly off-siteUsers must always have a way to navigate within the siteNo “breaking the back button”Intro/clickthrough pages are prohibited