28 (29)
5.3.4 Choose Descriptive Card Titles
It is very useful to give a descriptive name to the card. It might be a good idea to start the title with
your service’s name and keep the total length of the title short.
It also pays to use meaningful URLs since the user sees the URL of the currently selected link on the
screen and can use it as a navigational aid, especially when images have not been loaded.
5.3.5 Pay Attention to the First Screen
The first (topmost) screen of any page is the most important one. All of the often-used navigational
links, search fields, login screens, and the bulk of the information should reside there if at all possible.
The user is then able to navigate forward before the rest of the card has been loaded, and the user
does not have to scroll through the card.
Avoid wasting the top of the page on banner advertisements or non-informative graphics. It is better
to place the advertisements at the left or right edges than on the top.
5.3.6 Do not Use Absolute Values for the Screen Size
When using images the use of absolute values (in pixels) is not recommended. Sizes should be specified
as percentages of their total width or height.
5.3.7 DO-elements Usage
Always use descriptive and short labels for all DO-elements. Favour local DO-elements instead of
anchored links that are out of context. Global DO-elements should be used only when especially
needed at the end of the card. Always include the prev element in every card to enable backward
navigation.
5.4 Pictures, Tables and Colour
5.4.1 Avoid Useless Images
Downloading of images takes time, and many users may switch the loading of images off for more
speed. Try to optimize the size of the images. If you have large pictures on your site, consider using
thumbnails for the image index.
Always give an alternative text (using the ALT attribute of the IMG element) for images that convey
information. Always use a null alternative text (ALT=””) for images which do not convey information, or
are used for page layout or decorative purposes only.
5.4.2 Use Reasonable Tables Sizes
If the table size exceeds the maximum width of the application screen due to the number of columns
the table size will be scaled down to fit the screen. To keep the cell content readable, special attention
should be paid to the table structuring.
5.5 Take care of backward navigation
Due to the differences in the processing of the History between WAP and WEB, only the history
processing described in the WML specifications is followed. This means that the service provider has to
take care of the navigation as a whole!
To Next Page
Loading...
Need help?
General
