1 / 13

Designing for All Browsers

Designing for All Browsers. Chapter 8 Briana Morrison From Jonathan Lazar. Topics. The Browser Challenge Standardization Common Browser Incompatibility Problems Designing fro Different Browsers Need for Testing. The Browser Challenge.

yori
Download Presentation

Designing for All Browsers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Designing for All Browsers Chapter 8 Briana Morrison From Jonathan Lazar

  2. Topics • The Browser Challenge • Standardization • Common Browser Incompatibility Problems • Designing fro Different Browsers • Need for Testing

  3. The Browser Challenge • Different browsers can interpret the HTML differently • Different versions of each browser can respond to HTML differently • Same browser on different platforms can act differently.

  4. Consider Disabilities • Web site should support a wide variety of users, including those with disabilities • Be wary of graphics, use textual descriptions • Set of guidelines at http://www.w3.org/WAI/

  5. Browser Incompatibility • Users do not frequently upgrade their browsers • Unacceptable to require that the user has the latest browser since • They might not know how to upgrade browser • They might not feel comfortable upgrading browser • They might not be allowed to do personal installation of software

  6. Standardization • Set of standards for languages and protocols used on web does exist: http://www.w3.org • Validator service also exists: http://validator.w3.org • However, major browser companies design their browsers to be different and not all browsers handle all the standards

  7. Universal Usability • Concept of making informational systems that anyone can use from any platform, any screen size, any browser, any location, and with any disability is call universal usability. • Conference on universal usability: http://www.acm.org/sigs/sigchi/cuu/

  8. Browser Usage Data • Information, statistics on browser usage: http://browserwatch.internet.com http://www.browser.com

  9. Common Browser Incompatibility Problems • Missing End Tags (IE okay, Netscape, leaves whole table, etc. out) • Incorrect Nesting of Tags (Navigator requires HTML formatting tags to be nested correctly) • Link Titles (Navigator ignores the link title attribute, but you should use) • JavaScript, CSS, DHTML should be used with caution as user may disable

  10. Unique Browser Features • <multicol> supported only by Navigator • <marquee> supported only by IE • Some features supported by W3 HTML standards but not supported by both major browsers • Navigation should be provided with text, not Java applets

  11. How to Design for Different Browsers • Best policy is to design web pages that will appear properly regardless of browser and will provide maximum flexibility to the user. • If you must use HTML tags that are specific to a browser: • Make very clear on web site that for maximum user experience, user must use a specific browser. Link to download browser should be included • Click and select from two or three different web sites (with/without frames) • Write JavaScript code that will automatically deliver the appropriate web page to user

  12. Example <script> If (navigator.appName==“Netscape”) { Top.location.href=‘nnhome.html’ } Else { Top.location.href=‘iehome.html’ } </script>

  13. The Need for Testing • Avoid Browser Incompatibilities • During requirements gathering, collect information on what browser are being used by the target user population • Make sure browser-specific features are not included in conceptual design • Test for Browser Incompatibilities • Test thoroughly for browser incompatibilities • Test for browser compatibility: http://www.netmechanic.com/

More Related