Difference between revisions of "Testing layout submissions"
Foxfirefey (Talk | contribs) m (→Tags View Regions) |
m (adding browser support policy link) |
||
| Line 92: | Line 92: | ||
At the start of every comment, post, or email you write, include the user agent you tested with, so coders can identify browser specific problems. You can find this at [http://whatsmyuseragent.com whatsmyuseragent.com]. You don't need to include your IP address. | At the start of every comment, post, or email you write, include the user agent you tested with, so coders can identify browser specific problems. You can find this at [http://whatsmyuseragent.com whatsmyuseragent.com]. You don't need to include your IP address. | ||
| − | Include any problems you happen upon, even ones not on the checklist. The designer might not solve your problem or change their design, but it's always useful to gain user experience. | + | Include any problems you happen upon, even ones not on the checklist. The designer might not solve your problem or change their design, but it's always useful to gain user experience. |
| + | |||
| + | If you have multiple browsers, see [[Browser Support Policy]] for a listing of the ones that should be tested. | ||
[[Category: Styles]] | [[Category: Styles]] | ||
Latest revision as of 06:01, 30 March 2013
Contents
Key Usability
Contrast
Can you read the words easily? Are the colors outside this recommendation? That's worth mentioning.
Text sizing
Can you read the words? If the font is too small, can you size it up without words breaking out of their bounds or overlapping?
Layout
Is content overlapping? Are there blank areas that hold content in other browsers? Are there horizontal scrollbars?
Links
Can you click on the links? Can you tell what text are links? Can you tell what links you have visited?
Checklist: Journal, Post, Read & Network View Regions
Check the five regions in order, asking the key usability questions about each area. This plan is a guide to help you, not a requirement. You don't need to test every part of the checklist every time. Just do what you fancy.
Header
- Banner
- Title
- Subtitle
Links to all views:
- Journal (user.dreamwidth.org)
- Single Post (user.dreamwidth.org/1234.html)
- Reading List (user.dreamwidth.org/read)
- Network (user.dreamwidth.org/network)
- Archive (user.dreamwidth.org/archive)
- Subjects (user.dreamwidth.org/2009/01)
- Tags (user.dreamwidth.org/tag)
Sidebars
Try the layout with one sidebar, two sidebars, and no sidebars. In each configuration, does content overlap? Do you get horizontal scrollbars? Can you click on the links?
(Probable content to look at:)
- title
- module
- links list
- page summary
- calendar table
Main Content
- subject
- date
- userpic
- post contents
- meta data:
- mood
- music
- other
- actions:
- memory entry
- share entry
- track entry
- permalink
- read # comments
- post comment
- spacers
Can you post a comment? Turn on custom comment pages. In post view, can you read the comments easily? Can you understand who is making each comment, and where it fits in the thread? If there are lots of nested comments, does the layout break?
Normally there are some skip links here. There might also be some journal credits or journal actions, like a search or an RSS subscription button.
Archive View Regions
tba
Subjects View Regions
tba
Tags View Regions
Can you view all the tags and do they look nice? Can you check to see whether they look good in the different display options, whether list, hiearchical, or cloud?
Reporting Your Findings
At the start of every comment, post, or email you write, include the user agent you tested with, so coders can identify browser specific problems. You can find this at whatsmyuseragent.com. You don't need to include your IP address.
Include any problems you happen upon, even ones not on the checklist. The designer might not solve your problem or change their design, but it's always useful to gain user experience.
If you have multiple browsers, see Browser Support Policy for a listing of the ones that should be tested.
