Table of contents

Table of contents
1. Capabilities
1.1. Network capabilities
1.1.1. GSM CSD
1.1.2. GPRS
1.1.3. HSCSD
1.1.4. Conclusion
1.2. Device capabilities
1.2.1. Introduction
1.2.2. Palm Palm m100 Palm IIIc
1.2.3. Windows CE powered mobile devices Windows CE 3.0 Pocket PC Compaq iPaq 3630 Hewlett-Packard Jornada 545/548 Casio E-115/125 Casio EM-500 Handheld PC Hewlett-Packard Jornada 720 Intermec Technologies Corporation 6651
1.2.4. Psion
1.2.5. Sony CMD-Z5
1.3. Browser capabilities
1.3.1. AvantGo
1.3.2. Browsers for PalmOS Palmscape 3.0 Pendragon Browser 2.0 DPWeb Palm Web Clipping
1.3.3. Browsers for EPOC Psion Message Suite Opera 3.62 for EPOC
1.3.4. Browsers for Windows CE MIME types Security types URL types Scripting languages HTML and Object Model Reference Detecting the Pocket Internet Explorer on the web server Features of the Pocket Internet Explorer Pocket IE 1.x Pocket IE 2.0 Pocket IE 3.0 H/PC Pro Pocket IE 3.0 PPC Multiple windows Supported fonts Correct tag matching Animated GIF ActiveX controls Java applets Security XML support Internet Explorer 4.0 for H/PC 2000 More information
1.3.5. Microsoft Mobile Explorer
1.4. Application protocol capabilities
1.4.1. A typical HTTP session
1.4.2. Persistent connections in HTTP/1.1
2. Guidelines for mobile browsers
2.1. Usability
2.1.1. What is usability?
2.1.2. Page design Separate content segments by whitespaces Visualize a page's context with regard to the whole web site Enable browsers to optimize the display Optimum font size Graphics Text in graphics Page performance Page retrieval process of web browsers Reuse graphics multiple times Hyperlinks to high-volume objects Tips from other sources
2.1.3. Content design
2.1.4. Site design
2.2. Visual user interface design
2.3. Overview about technical guidelines
2.3.1. Web Content Accessibility Guidelines 1.0
2.3.2. HTML 4.0 Guidelines for Mobile Access
2.3.3. CSS Mobile Profile 1.0
2.3.4. Designing Web Sites for the Internet Explorer for Pocket PC General design guidelines Forms design for the Pocket Internet Explorer Design guidelines for information sites Frames Background sound Text fields and text areas Buttons Tables Graphics and images Image detail Image colour Image design Alt tags Image maps
2.4. General guidelines
2.4.1. Low-volume web pages
2.4.2. Minimum number of objects per web page
2.4.3. Guidelines for HTML General Presentation design No frames
2.4.4. Guidelines for images
2.4.5. Guidelines for applets and scripts
2.4.6. Guidelines for multimedia
2.4.7. Unintentional redirection
2.5. W3C Web Content Accessibility Guidelines in practice
2.5.1. General Priority 1 Provide a text equivalent for every non-text element Ensure that all information conveyed with color is also available without color, for example from context or markup Organize documents so they may be read without style sheets Until user agents allow users to control flickering, avoid causing the screen to flicker. Use the clearest and simplest language appropriate for a site's content. Priority 2 Ensure that foreground and background color combinations provide sufficient contrast when viewed by someone having color deficits or when viewed on a black and white screen When an appropriate markup language exists, use markup rather than images to convey information. Create documents that validate to published formal grammars. Use style sheets to control layout and presentation Use relative rather than absolute units in markup language attribute values and style sheet property values. Use header elements to convey document structure and use them according to specification. Mark up lists and list items properly. Mark up quotations. Do not use quotation markup for formatting effects such as indentation. Ensure that dynamic content is accessible or provide an alternative presentation or page. Until user agents allow users to control blinking, avoid causing content to blink (i.e., change presentation at a regular rate, such as turning on and off). Until user agents provide the ability to stop the refresh, do not create periodically auto-refreshing pages. Until user agents provide the ability to stop auto-redirect, do not use markup to redirect pages automatically. Instead, configure the server to perform redirects. Until user agents allow users to turn off spawned windows, do not cause pop-ups or other windows to appear and do not change the current window without informing the user. Use W3C technologies when they are available and appropriate for a task and use the latest versions when supported. Avoid deprecated features of W3C technologies. Divide large blocks of information into more manageable groups where natural and appropriate. Clearly identify the target of each link. Provide metadata to add semantic information to pages and sites. Provide information about the general layout of a site (e.g., a site map or table of contents). Use navigation mechanisms in a consistent manner. Priority 3 Specify the expansion of each abbreviation or acronym in a document where it first occurs. Identify the primary natural language of a document. Create a logical tab order through links, form controls, and objects. Provide keyboard shortcuts to important links (including those in client-side image maps), form controls, and groups of form controls. Until user agents (including assistive technologies) render adjacent links distinctly, include non-link, printable characters (surrounded by spaces) between adjacent links. Provide information so that users may receive documents according to their preferences (e.g., language, content type, etc.) Provide navigation bars to highlight and give access to the navigation mechanism. Group related links, identify the group (for user agents), and, until user agents do so, provide a way to bypass the group If search functions are provided, enable different types of searches for different skill levels and preferences. Place distinguishing information at the beginning of headings, paragraphs, lists, etc. Provide a means to skip over multi-line ASCII art. Supplement text with graphic or auditory presentations where they will facilitate comprehension of the page Create a style of presentation that is consistent across pages
2.5.2. Tables Priority 1 For data tables, identify row and column headers For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells. Priority 2 Do not use tables for layout unless the table makes sense when linearized. Otherwise, if the table does not make sense, provide an alternative equivalent (which may be a linearized version). If a table is used for layout, do not use any structural markup for the purpose of visual formatting. Priority 3 Provide summaries for tables. Provide abbreviations for header labels. Until user agents (including assistive technologies) render side-by-side text correctly, provide a linear text alternative (on the current page or some other) for all tables that lay out text in parallel, word-wrapped columns.
2.5.3. Forms Priority 2 Until user agents support explicit associations between labels and form controls, for all form controls with implicitly associated labels, ensure that the label is properly positioned. Associate labels explicitly with their controls. Priority 3 Until user agents handle empty controls correctly, include default, place-holding characters in edit boxes and text areas.
2.5.4. If all else fails Priority 1 If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
3. Best fitting document type
3.1. Introduction into HTML 4.01 Strict
3.2. Introduction into XHTML™ Basic
3.3. HTML vs. XHTML in general
3.3.1. The user's perspective
3.3.2. The web author's perspective
3.4. HTML 4.01 Strict vs. XHTML Basic
4. Authoring solutions
4.1. Content selection and negotiation
4.1.1. Content selection by links
4.1.2. Content selection by markup
4.1.3. Content selection by automatic content negotiation Language versions Media types
4.1.4. Composite Capabilities/Preference Profiles
4.1.5. Special Case: Internet Explorer for Pocket PC
4.2. Web authoring solutions
4.2.1. Static web pages Using XSLT for static web pages Support for different browser types Automatic selection Redirection Sample Perl code Reading the file from disk Manual selection Web editors for "mobile aware" web pages A single XML document for the whole web site
4.2.2. Dynamic content creation Server Side Includes SSI commands SSI server configuration How to benefit from SSI JavaServer Pages™ Active Server Pages ASP.NET PHP 4 Application servers WebObjects by Apple Cold Fusion Cocoon by the Apache Project Native applications using XML and XSLT processors Pocket Explorer's built-in support for XML and XSLT Native applications whichever technique they use
4.2.3. Automatic content reformatting
4.2.4. Conversion from HTML to XHTML HTML Tidy: Converter for HTML to XHTML
5. Special web site services for mobile devices
5.1. Printing and storing of web pages
6. Testing
7. Conclusions
8. Abbreviations
9. References
9.1. [1] - [20]
9.2. [21] -
10. Further reading
11. Web goodies for mobile browsers
12. About the authors
A. Appendix
A.1. Cellular phones with web browsers
A.2. DTD for web publishing
A.3. Examples of 'user-agent' identifications
A.4. XML editors
A.5. XSLT processors

View the short table of contents.

Copyright © 2001-2003 by Rainer Hillebrand and Thomas Wierlemann