Site Report
This tab shows general usability issues, indicating navigation problems for all users.
This tab is available in SortSite Professional and OnDemand, but not in SortSite Standard edition.
| Status | Summary | | |
|---|
 | Usability.gov Guidelines - Some pages violate these guidelines. | | |
 | W3C Best Practices - No issues found.
| | |
| Readability - No issues found.
| | |
| Priority | Description and URL | Guideline and Line# | Count |
|---|
Priority 26 issues on 9 pages | |
 | Omitting img width or height attributes means page text jumps about as images load. | Usability.gov 14:3 | |
|
This makes the page very hard to read while it's loading, and the user may click on the wrong link if it moves as it's being clicked.
Add width and height attributes to the img tag matching the image dimensions. Authoring tools
like Dreamweaver can automate this process. | | |
| https://dismissed.moadoph.gov.au/ | Line 166 173 | |
| https://dismissed.moadoph.gov.au/act-one.html | Line 324 335 346 | |
| https://dismissed.moadoph.gov.au/act-two.html | Line 302 313 | |
| https://dismissed.moadoph.gov.au/prologue.html | Line 516 527 538 549 560
...
| |
| This issue was found on another 4 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | Provide a search option on each page of content-rich web sites. | Usability.gov 17:4 | |
|
A search option should be provided on all pages where it may be useful - users should not have to return to the homepage to conduct a search. Search engines can be helpful on content-rich web sites, but do not add value on other types of sites. | | |
| https://dismissed.moadoph.gov.au/ | Line 1 | |
| https://dismissed.moadoph.gov.au/act-one.html | Line 1 | |
| https://dismissed.moadoph.gov.au/act-three.html | Line 1 | |
| https://dismissed.moadoph.gov.au/act-two.html | Line 1 | |
| This issue was found on another 1 pages.
The trial version is limited to showing issues on 4 pages.
| | |
| | This page title is not unique. Each page should have a descriptive and meaningfully different title. | Usability.gov 9:2 | |
|
Title refers to the text displayed on browser tabs, favorites, and in search engines results pages. If two or more pages have the same title, they cannot be differentiated by users or the Favorites capability of the browser. | | |
| '
#Dismissal1975 ยท Dismissed! at the Museum of Australian Democracy' is also used on https://dismissed.moadoph.gov.au/hashtag-dismissal-1975.html
https://dismissed.moadoph.gov.au/hashtag-dismissal-1975/tweet_timeline.html | Line 28 | |
| | Use background images sparingly and make sure they are simple, especially behind text. | Usability.gov 14:1 | |
|
Background images can make it difficult for users to read foreground text. A single, large, complex background image (including a picture) can substantially slow page download rates. | | |
| https://dismissed.moadoph.gov.au/stylesheets/application.css | Line 205 470 | |
| | Use color changes to indicate to users when a link has been visited. This page sets identical colors for visited and unvisited links. | Usability.gov 10:7 | |
|
Generally, it is best to use the default text link colors (blue as an unvisited location/link and purple as a visited location/link). Link colors help users understand which parts of a Web site they have visited. | | |
| https://dismissed.moadoph.gov.au/stylesheets/application.css | Line 234 | |
| | Use text links rather than image links. In general, text links are more easily recognized as clickable. | Usability.gov 10:6 | |
|
Text links usually download faster, are preferred by users, and should change colors after being selected. It is usually easier to convey a link's destination in text, rather than with the use of an image.
Users often find it hard to tell which images are clickable without moving the cursor over them ('minesweeping').
Another benefit to using text links is that users with text-only and deactivated graphical browsers can see the navigation options. | | |
| https://dismissed.moadoph.gov.au/ | Line 166 173 | |
| https://dismissed.moadoph.gov.au/act-one.html | Line 324 335 346 | |
| https://dismissed.moadoph.gov.au/act-two.html | Line 302 313 | |
| https://dismissed.moadoph.gov.au/prologue.html | Line 516 527 538 549 560
...
| |
| This issue was found on another 3 pages.
The trial version is limited to showing issues on 4 pages.
| | |
Priority 32 issues on 3 pages | |
 | Use at least a 12-point font on all web pages. | Usability.gov 11:8 | |
|
For users over age 65, it may be better to use at least fourteen-point fonts.
Never use less than nine-point font on a Web site.
The following are all smaller than 12 point:
- <p style="font-size: 11pt;" >
- <p style="font-size: 15px;" >
- <p style="font-size: small;" >
- <font size="2" >
- <font size="-1" >
| | |
| https://dismissed.moadoph.gov.au/ | Line 7 | |
| https://dismissed.moadoph.gov.au/stylesheets/application.css | Line 727 1344 1530 1735 1745
...
| |
| | Use italic text sparingly - for one or two words or a short phrase. | Usability.gov 11:10 | |
|
Keep runs of styled text to less than 70 characters.
When used well, styled text draws attention to important words, but also decreases reading speed by almost twenty percent. | | |
| https://dismissed.moadoph.gov.au/hashtag-dismissal-1975.html | Line 833 | |
Priority 41 issues on 1 pages | |
 | Use site maps for web sites that have many pages. | Usability.gov 7:10 | |
|
Site maps provide an overview of the Web site. They may display the hierarchy of the Web site, may be designed to resemble a traditional table of contents, or may be a simple index. | | |
| https://dismissed.moadoph.gov.au/ | Line 1 | |
| Expand all 9 issues | | |
