Progressive enhancement

From HandWiki
Short description: Web design strategy putting emphasis web content first
The order of progressive enhancement: HTML, CSS, and JavaScript.
This article is accessible through pure HTML (first layer). Without styling (second layer) and scripts (third layer), the content is only 76 KB in size.

Progressive enhancement is a strategy in web design that puts emphasis on web content first, allowing everyone to access the basic content and functionality of a web page, whilst users with additional browser features or faster Internet access receive the enhanced version instead. This strategy speeds up loading and facilitates crawling by web search engines, as text on a page is loaded immediately through the HTML source code rather than having to wait for JavaScript to initiate and load the content subsequently, meaning content ready for consumption "out of the box" is served immediately, and not behind additional layers.[1][2][3]

This strategy involves separating the presentation semantics from the content, with presentation being implemented in one or more optional layers, activated based on aspects of the browser or Internet connection of the client. In practice, this means serving content through HTML, the "lowest common denominator" of web standards, and applying styling and animation through CSS to the technically possible extent, then applying further enhancements through JavaScript.[4] Deprecated Adobe Flash could be thought of as having shared the final spot with JavaScript while it was widely in use.[5][6] Since web browsers can load site features to the extent supported rather than failing to load the entire site due to one error or missing feature in JavaScript, a progressively enhancing site is more stable and backwards compatible.[4]

History

"Progressive enhancement" was coined by Steven Champeon and Nick Finck at the SXSW Interactive conference on March 11, 2003, in Austin,[7] and through a series of articles for Webmonkey which were published between March and June 2003.[8]

Specific Cascading Style Sheets (CSS) techniques pertaining to flexibility of the page layout accommodating different screen resolutions is the concept associated with responsive web design approach. In 2012, net Magazine chose Progressive Enhancement as #1 on its list of Top Web Design Trends for 2012 (responsive design was #2).[9] Google has encouraged the adoption of progressive enhancement to help "our systems (and a wider range of browsers) see usable content and basic functionality when certain web design features are not yet supported".[10]

Introduction

The strategy is an evolution of a previous web design strategy known as graceful degradation, wherein Web pages were designed for the latest browsers first, but then made to work well in older versions of browser software.[11][3] Graceful degradation aims to allow a page to "degrade" – to remain presentable and accessible even if certain technologies expected by the design are absent.[12]

In progressive enhancement the strategy is deliberately reversed: The web content is created with a markup document, geared towards the lowest common denominator of browser software functionality.[13][8][12] If content should be revealed interactively through JavaScript, such as a collapsible navigation menu, this would be by default and only first hidden by JavaScript itself.[3] The developer adds all desired functionality to the presentation and behavior of the page, using modern CSS, Scalable Vector Graphics (SVG), or JavaScript.[14]

Background

The progressive enhancement approach is derived from Champeon's early experience (c. 1993–1994) with Standard Generalized Markup Language (SGML), predating HTML and other Web presentation languages.[8]

Writing content with semantic markup and considering the presentation of the content separately, rather than being embedded in the markup itself, is a concept referred to as the rule of separation of presentation and content[15][16]. Champeon expressed a hope that, since web browsers provide a default presentation style for HTML content, this would result in websites with their content written as semantic HTML, leaving presentation choice to the web browser.[8] However, the needs of web designers led to the HTML standard being extended with hardcoded features that allowed HTML content to prescribe specific styles, and taking away this option from consumers and their web browsers.[8] These features forced publishers to choose between adopting a new disruptive technologies or allowing content to remain accessible to audiences that used other browsers, a dilemma between design and compatibility.[8][17][12] During the 1990s, an increasing number of websites would not work in anything but the latest of popular browsers.[12]

This trend reversed after the 1990s, once CSS was widely supported,[8][17] through grassroots educational efforts (from Eric Costello, Owen Briggs, Dave Shea, and others) showing Web designers how to use CSS for layout purposes.[citation needed]

Core principles

The progressive enhancement strategy consists of the following core principles:[8]

  • Basic content should be accessible to all web browsers.
  • Basic functionality should be accessible to all web browsers.
  • Sparse, semantic markup contains all content.
  • Enhanced layout is provided by externally linked CSS.[17]
  • Enhanced behavior is provided by externally linked JavaScript.[14]
  • End-user web browser preferences are respected.

Support and adoption

  • In August 2003 Jim Wilkinson created a progressive enhancement wiki page to collect some tricks and tips and to explain the overall strategy.[18]
  • Designers such as Jeremy Keith have shown how the approach can be used harmoniously with still other approaches to modern web design (such as Ajax) to provide flexible, but powerful, user experiences.[19][20]
  • Aaron Gustafson wrote a series for A List Apart covering the fundamentals of progressive enhancement, from the underlying philosophy to CSS approaches to how to handle JavaScript.[21][11][22][23]
  • CSS Zen Garden by Molly Holzschlag and Dave Shea, spread the adoption of the term to refer to CSS-based design strategies.[24]
  • Organizations such as the Web Standards Project (WaSP), which was behind the creation of Acid2 and Acid3 tests,[25] have embraced progressive enhancement as a basis for their educational efforts.
  • In 2006 Nate Koechley at Yahoo! made extensive reference to progressive enhancement in his own approach to Web design and browser support, Graded Browser Support (GBS).[12]
  • Steve Chipman at AOL has referred to progressive enhancement (by DOM scripting) as a basis for his Web design strategy.[26]
  • David Artz, leader of the AOL's Optimization team, developed a suite of Accessible Rendering Technologies, and invented a technique for disassembly of the "enhancement" on the fly, saving the user's preference.
  • Progressive enhancement is used in the front ends of MediaWiki-powered sites such as Wikipedia, as it is readable, navigable, and even editable using the basic HTML interface without styling or scripts, though is enhanced by such. For example, the wikitext editor's toolbar is loaded and operates through JavaScript.
  • Chris Heilmann discussed the importance of targeted delivery of CSS so that each browser only gets the content (and enhancements) it can handle.[27][28]
  • Scott Jehl of Filament Group proposed a "Test-Driven Progressive Enhancement",[29] recommending to test the device capabilities (rather than inferring them from the detected user agent) before providing enhancements.
  • Wt is an open-source server-side web application framework which transparently implements progressive enhancement during its bootstrap, progressing from plain HTML to full Ajax.

Benefits

Accessibility, compatibility, and outreach

Web pages created according to the principles of progressive enhancement are by their nature more accessible,[27] backwards compatible,[6] and outreaching, because the strategy demands that basic content always be available, not obstructed by commonly unsupported or scripting that may be easily disabled, unsupported (e.g. by text-based web browsers), or blocked on computers in sensitive environments.[14] Additionally, the sparse markup principle makes it easier for tools that read content aloud to find that content. It is unclear as to how well progressive enhancement sites work with older tools designed to deal with table layouts, "tag soup", and the like.[citation needed]

Speed, efficiency, and user control

The client (computing) is able to select which parts of a page to download beyond basic HTML (e.g. styling, images, etc.), and can opt only to download parts necessary for desired usage to speed up loading and reduce bandwidth and power consumption. For example, a client may choose to only download basic HTML, without loading style sheets, scripts, and media (e.g. images), due to low internet speeds caused by geographical location, poor cellular signal, or throttled speed due to exhausted high-speed data plan. This also reduces bandwidth consumption on the server side.

In comparison, pages whose initial content is loaded through AJAX require the client to inefficiently run JavaScript to download and view page content, rather than downloading the content immediately.

Search engine optimization (SEO)

Improved results with respect to search engine optimization (SEO) is another side effect of a progressive enhancement-based Web design strategy. Because the basic content is always accessible to search engine spiders, pages built with progressive enhancement methods avoid problems that may hinder search engine indexing, whereas having to render the basic page content through JavaScript execution would make crawling slow and inefficient.[27][30]

Criticism and responses

Some skeptics, such as Garret Dimon, have expressed their concern that progressive enhancement is not workable in situations that rely heavily on JavaScript to achieve certain user interface presentations or behaviors.[31] Laurie Gray (Information Architect at KnowledgeStorm[32]) countered with the point that informational pages should be coded using progressive enhancement in order to be indexed by search engine spiders.[33] Geoff Stearns (author of SWFObject, a popular Flash application) argued that Flash-heavy pages should be coded using progressive enhancement.[34]

Designers Douglas Bowman and Bob Stein expressed doubts concerning the principle of the separation of content and presentation in absolute terms, pushing instead for a realistic recognition that the two are inextricably linked.[35][15]

See also

References

  1. ↑ "Progressive enhancement is faster" (in en). 2013-09-03. https://jakearchibald.com/2013/progressive-enhancement-is-faster/. 
  2. ↑ Tse, Tiffany (2017-02-15). "What is Progressive Enhancement and Why Should You Care?" (in en). https://www.shopify.com/partners/blog/what-is-progressive-enhancement-and-why-should-you-care. 
  3. ↑ 3.0 3.1 3.2 Olsson, Tommy (2007-02-06). "Graceful Degradation & Progressive Enhancement" (in en-US). Accessites.org. http://accessites.org/site/2007/02/graceful-degradation-progressive-enhancement/. 
  4. ↑ 4.0 4.1 van der Sluis, Bobby (2005-04-19). "Ten good practices for writing JavaScript in 2005". http://www.bobbyvandersluis.com/articles/goodpractices.php. 
  5. ↑ Mills, Chris (8 July 2011). "Graceful degradation versus progressive enhancement". https://www.w3.org/wiki/Graceful_degradation_versus_progressive_enhancement. 
  6. ↑ 6.0 6.1 Nyman, Robert (2006-03-01). "What is Accessibility?". https://robertnyman.com/2006/03/01/what-is-accessibility/. 
  7. ↑ Steven Champeon; Nick Finck (2003-03-11). "Inclusive Web Design for the Future (SxSWi presentation)". http://hesketh.com/publications/inclusive_web_design_for_the_future/. 
  8. ↑ 8.0 8.1 8.2 8.3 8.4 8.5 8.6 8.7 Champeon, Steve (2003-03-21). "Progressive Enhancement and the Future of Web Design". Webmonkey. http://hesketh.com/publications/progressive_enhancement_and_the_future_of_web_design.html. 
  9. ↑ "15 top web design and development trends for 2012". net. January 9, 2012. http://www.creativebloq.com/features/15-top-web-design-and-development-trends-for-2012/. 
  10. ↑ Pierre Far (2014), Updating our technical Webmaster Guidelines, Webmaster Central Blog
  11. ↑ 11.0 11.1 Gustafson, Aaron (2008-10-07). "Understanding Progressive Enhancement" (in en-US). https://alistapart.com/article/understandingprogressiveenhancement/. 
  12. ↑ 12.0 12.1 12.2 12.3 12.4 Koechley, Nate (2006-02-13). "Graded Browser Support". http://developer.yahoo.com/yui/articles/gbs/gbs.html. 
  13. ↑ "101 Search Engine Optimization Tips". http://www.meta4creations.com/101-search-engine-optimization-tips.htm. "Progressive Enhancement […] means [to] build your website starting with the lowest common denominator browsers in mind." 
  14. ↑ 14.0 14.1 14.2 James Edwards; Cameron Adams (2006-03-07). "Script Smarter: Quality JavaScript from Scratch" (in en). https://www.sitepoint.com/javascript-from-scratch/. 
  15. ↑ 15.0 15.1 Stein, Bob (2000-11-17). "Separation Anxiety: The Myth of the Separation of Style from Content" (in en-US). https://alistapart.com/article/separation/. 
  16. ↑ "Separation: The Web Designer's Dilemma". A List Apart. 14 May 2004. https://alistapart.com/article/separationdilemma. 
  17. ↑ 17.0 17.1 17.2 Malicoat, Todd (2003-08-23). "Form vs. Function in Site Design". http://www.seotoday.com/browse.php/category/articles/id/321/index.php. 
  18. ↑ Wilkinson, Jim (2003), Progressive Enhancement - CSS Discuss
  19. ↑ Jeremy Keith's Adactio blog (2005), Progressive Enhancement with Ajax
  20. ↑ Keith, Jeremy (2006-06-20). "Behavioral Separation" (in en-US). https://alistapart.com/article/behavioralseparation/. 
  21. ↑ Gustafson, Aaron (2007-03-27). "Ruining the User Experience" (in en-US). https://alistapart.com/article/ruininguserexperience/. 
  22. ↑ Gustafson, Aaron (2008-10-22). "Progressive Enhancement with CSS" (in en-US). https://alistapart.com/article/progressiveenhancementwithcss/. 
  23. ↑ Gustafson, Aaron (2008-11-04). "Progressive Enhancement with JavaScript" (in en-US). https://alistapart.com/article/progressiveenhancementwithjavascript/. 
  24. ↑ Lawson, Bruce. "An interview with Dave Shea, the CSS Zen Gardener" (in en). https://www.dmxzone.com/go/5442/an-interview-with-dave-shea-the-css-zen-gardener/. 
  25. ↑ "Acid Test Results on Popular Browser". http://www.sciactive.com/main/index.php?Itemid=1&id=133&option=com_content&task=view. "The Acid 3 test is a work in progress and will be updated when The Web Standards Project releases the final version of the test." 
  26. ↑ Steven G. Chipman (2005), New Skool DOM Scripting
  27. ↑ 27.0 27.1 27.2 Heilmann, Chris (2005-02-22). "Double Vision – Give the Browsers CSS They Can Digest". Developer Shed. http://www.devarticles.com/c/a/Web-Style-Sheets/Double-Vision-Give-the-Browsers-CSS-They-Can-Digest/. 
  28. ↑ "Seven Accessibility Mistakes (Part 1)". 2006-04-12. http://digital-web.com/articles/seven_accessibility_mistakes_part_1/. 
  29. ↑ Jehl, Scott (23 September 2008). "Test Driven Progressive Enhancement". http://alistapart.com/article/testdriven. 
  30. ↑ Spencer, Stephan (2007-09-25). "PE is good for SEO". http://news.cnet.com/8301-13530_3-9782891-28.html. 
  31. ↑ Dimon, Garret (2005-08-29). "The Reality of Progressive Enhancement". http://v1.garrettdimon.com/archives/the-reality-of-progressive-enhancement. 
  32. ↑ "IA Summit 2006: Speaker Biographies". ASIS&T. http://www.iasummit.org/2006/speakers.htm#Gray. 
  33. ↑ Gray, Laurie (2006-03-27). "Web 2.0 and SEO?". Association for Information Science and Technology. http://iasummit.org/2006/blog/?p=86. 
  34. ↑ Stearns, Geoff (2006-02-27). "Using alternate content as content in Flash" (in en-US). https://blog.deconcept.com/2006/02/27/using-alternate-content-flash/. 
  35. ↑ Bowman, Douglas (2003-10-14). "Are they really separated?". https://stopdesign.com/journal/2003/10/14/separated.html. 

Further reading



Retrieved from "https://handwiki.org/wiki/index.php?title=Progressive_enhancement&oldid=3380054"