1. Today’s objectives  Review Design precepts  Big concepts – Robbins textbook  Semantic HTML markup

2. Common principles to show Relationships  Size  Color  Contrast shows relative important. Dramatic shifts in text-size or color will impart a message that something is different.  Alignment - creates order between elements.  Repetition - assigns relative meaning. If all important words are Blue, a blue word is important.  Proximity - separates elements from each other and creates sub-hierarchies.

3. Size and hierarchy – bigger is important and gets attention

4. Color- schemes (e.g., Greyscale With Bright Accents). Few colors to attract attention, to differentiate important information and elements.

5. Contrast shows relative important. Dramatic shifts in text-size or color will impart a message that something is different. Contrast - ColorContrast - Size

6. Alignment - creates order between elements.

7. Information in columns is distinct.

8. Source: http://www.fuelyourcreativity.com/the-lost-principles-of-design/ Repetition - assigns relative meaning. Recurrence of a design element provides continuity, flow, direction forces etc.

9. Proximity – objects near to one another are related. Separates elements from each other and creates sub-hierarchies.

10. Big Concepts - Robbins Textbook Way back in 2007,  relatively certain users visited our sites with desk-top computers, large monitor, speedy Internet connection.  960 pixels was a popular page width.  Main concern was different browsers (e.g., IE, FireFox).

11. Big Concepts  Introduction of iPhone and Android smartphones and widespread 3G network caused huge shift in how, when, and where people surf web.

12. Big Concepts  What does this mean for us?  Designers must resist making assumptions about network speed and context based on the screen size.

13. Big Concepts  While viewing our designs on desktop machine is nice, it is not how they will likely be experienced by users. 2007TomorrowToday

14. So how do we deal with this diversity? Standards  Follow HTML, CSS, and JavaScript standards as documented by the World Wide Web Consortium (W3C) http://www.w3.org/http://www.w3.org/  Web standards helps ensure site is  consistent as possible on all standards-compliant browsers (about 99% of browsers in current use).

15. Source: Michael T. Travels http://michaelwtravels.boardingarea.com/2012/01/world-electrical-outlets-guide/#sthash.NimQtHNp.dpbs Web standards help ensure site is consistent as possible on all standards-compliant browsers (about 99% of browsers in current use). The way browsers, devices handle CSS, JS, etc. may vary. Similar to the way electrical specifications vary internationally.

16. Progressive Enhancement  We are faced with a range of browser capabilities—from basic HTML support to all the bells and whistles.  Progressive enhancement is one strategy for dealing with unknown browser capabilities.

17. Progressive Enhancement  Start with a baseline experience that makes the content or functionality available to most rudimentary browsers or assistive devices.  From there, you layer on more advanced features for the browsers that can handle them.  As Clark says, working from content out… Good book: Designing with Progressive Enhancement Todd Parker, Patty Toland, Scott Jehl, and Maggie Costello Wachs

18. Progressive Enhancement Authoring strategy  HTML document written in logical order.  Elements marked up in a meaningful way.  Document is usable on the widest range of browsing environments, including old browsers, future browsers, and mobile and assistive devices  Clean HTML document with elements accurately and thoroughly described.

19. Progressive Enhancement Styling strategy  Create layers of experience by taking advantage of the way browsers use style sheet rules.  E.g., Write style rules for enhanced and unenhanced browsers.

20. Progressive Enhancement Scripting strategy  JavaScript scripting language that makes web pages interactive and dynamic.  Make sure basic functionality is intact even when JavaScript is off.

21. Responsive Web Design  Responsive web design (RWD) a strategy for  providing custom layouts to devices  based on the size of the viewport (browser window).  RWD  serve a single HTML document to all devices,  applies different style sheets based on the screen size to provide optimized layout for that device.  A primary tool to cope with unknown viewport size.

22. Responsive Web Design  Ethan Marcotte first wrote about RWD and coined the phrase in his article “Responsive Web Design” on A List Apart in 2010 ( www.alistapart.com/articles/responsive-web-design/ ).  Media Queries  @media screen and (max-width:320px) {/* Styles */}  @media only screen and (min-device-width : 768px) and (max-device-width : 1024px) { /* Styles */ }

23. Breakpoints: 320px | 480px | 768px | 1024px

24. @media screen and (max-width:320px) { /* Styles */ }

25. Responsive Web Design  Some contend that RWD based on viewport size is limited.  Viewport sizes will continue to change.  Start with a small screen. Every time the width of the main content grows wider than either 75 characters or 10 words, something should happen. These are your breakpoints. @media (max-width: 22em) { body { font-size:.9em; padding: 0 1.5em; } } Vasilis van Gemert http://www.smashingmagazine.com/2013/03/01/logical-breakpoints-responsive-design/

26. Accessibility  People access the Web in many different ways:  screen readers,  Braille output,  magnifiers,  Joysticks, and so on.  Build pages that create fewest barriers to getting information, regardless of the user’s ability and the device used to access the Web.

27. Accessibility  W3C started Web Accessibility Initiative (WAI) to address the need to make the Web usable for everyone.  WAI site (www.w3.org/WAI) is an good starting point for learning more about web accessibility.www.w3.org/WAI  Web Content Accessibility Guidelines (WCAG and WCAG 2.0). www.w3.org/WAI/intro/wcag.php.www.w3.org/WAI/intro/wcag.php

28. Accessibility: things we can do  Provide text alternatives for any non-text content.  Provide alternatives for time-based media.  Make all functionality available from a keyboard.  Provide users enough time to read and use content.  Do not design content in a way that causes seizures.  Provide ways to help users navigate, find content, and determine where they are.  Make text content readable and understandable.  Make Web pages appear and operate in predictable ways.  Help users avoid and correct mistakes. http://www.w3.org/WAI/WCAG20/quickref/

29. Site Performance  Users expect a site to load in under two seconds, and nearly a third of your audience will leave your site for another if it doesn’t (Robbins, 2012).  Tolerable wait times have decreased to just 2 seconds (Fiona Fui-Hoon Nah).  Amazon.com found reducing page load times by 100ms resulted in a 1% increase in revenue.

30. Site Performance Akamai (2009)  47% expect a page to load in 2 seconds or less.  40% abandon page if takes more than 3 seconds to load.  52% of online shoppers claim quick page loads are important for their loyalty. http://munchweb.com/effect-of-website-speed

31. Site Performance: What you can do. 1. Optimize images - small file size without sacrificing quality. 2. Minimize HTML and CSS documents - remove extra character spaces and line returns. 3. Keep JavaScript to minimum. 4. Don’t load unnecessary assets (such as images, scripts, or JavaScript libraries). 5. Reduce HTTP requests - number of times the browser makes requests of the server.

32. MEANINGFUL MARKUP

33. How can this content be structured? Page of text with an image.

34. How can this content be structured? How to tell browser what type of content is here.

35. … <font size=“2“ color="#0066CC">… …

36. …

38. Possible tags http://www.w3schools.com/tags/default.asp