[Skip navigation links]

Site Report

This tab shows general usability issues, indicating navigation problems for all users.

This tab is available in SortSite Professional, SortSite Developer and OnDemand, but not in SortSite Standard edition.

  • FailureUsability.gov Guidelines - Some pages violate these guidelines.
  • FailureW3C Best Practices - Some pages violate these guidelines.
  • SuccessReadability - No issues found.
PriorityDescription and URLGuideline and Line#Count

Priority 1

1 issues on 3 pages

CriticalUsers should be able to quickly look at each link and tell where it goes. Usability.gov 10:1 3 pages
Don't use generic link labels like "click here" or "read more" because they're hard to tell apart when users scan a page.
Link text: Read More... Read More... Click here Click here
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 300 300 320 341
Link text: Click here Click here Read More... Read More...
https://www.w3.org/WAI/demos/bad/before/home.html
Line 433 435 475 507
Link text: Read more... Read more...
https://www.w3.org/WAI/demos/bad/before/template.html
Line 187 208

Priority 2

4 issues on 11 pages

Very ImportantAvoid underlined text - people will click on it and think it's a broken link. Usability.gov 10:4 1 pages
Use something other than underlining for highlighting text, because it looks like a link, and users become frustrated when the "link" does not work.
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 270
Very ImportantOmitting img width or height attributes makes the page layout jump about as images load. Usability.gov 14:3 W3C 11 pages
This makes the page very hard to read or click while it's loading. Fix by adding width and height attributes to the img tag matching the image dimensions. In responsive layouts, specifying width and height prevents layout jumping because the browser can pre-calculate the final image size when CSS like this is used: img { max-width: 100%; height: auto }
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 176 180 355 359 495 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 165 218 226 531 539 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 76 80 263 267 296 ...
https://www.w3.org/WAI/demos/bad/before/reports/home.htmlLine 32 181 257 320 376 ...
This issue was found on another 7 pages. The trial version is limited to showing issues on 4 pages.
Very ImportantThe img width and height attributes don't match the actual image size. This means the image will be distorted or resize during loading. W3C 6 pages
Image https://www.w3.org/WAI/demos/bad/before/img/blank_5x5.gif actual dimensions: 5 x 5 pixels.
https://www.w3.org/WAI/demos/bad/before/annotated/home.html
Line 275 303
Image https://www.w3.org/WAI/demos/bad/before/img/blank_5x5.gif actual dimensions: 5 x 5 pixels.
https://www.w3.org/WAI/demos/bad/before/home.html
Line 377 443
Image https://www.w3.org/WAI/demos/bad/before/img/blank_5x5.gif actual dimensions: 5 x 5 pixels.
https://www.w3.org/WAI/demos/bad/before/news.html
Line 175 200 221
Image https://www.w3.org/WAI/demos/bad/before/img/blank_5x5.gif actual dimensions: 5 x 5 pixels.
https://www.w3.org/WAI/demos/bad/before/tickets.html
Line 170
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
Very ImportantUse background images sparingly and make sure they are simple, especially behind text. Usability.gov 14:1 6 pages
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://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 175 176 177 180 355 ...
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 214 217 220 225 530 ...
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 75 77 80 214 263 ...
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 70 71 72 75 282 ...
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.

Priority 3

4 issues on 6 pages

ImportantUse at least a 12-point font on all web pages. Usability.gov 11:8 6 pages

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://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 216 311 332 352
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 279 458 493 524
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 116 218 260
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 21 111 279
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
ImportantUse bold text sparingly - for one or two words or a short phrase. Usability.gov 11:5 1 pages
Keep runs of bold text to less than 70 characters.
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 270
ImportantUse italic text sparingly - for one or two words or a short phrase. Usability.gov 11:10 1 pages
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://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 420
ImportantUse option groups when a drop down list has more than 10 items. Usability.gov 13:12 6 pages
Group related options using optgroup elements.
https://www.w3.org/WAI/demos/bad/before/annotated/home.htmlLine 189
https://www.w3.org/WAI/demos/bad/before/home.htmlLine 248
https://www.w3.org/WAI/demos/bad/before/news.htmlLine 89
https://www.w3.org/WAI/demos/bad/before/tickets.htmlLine 84
This issue was found on another 2 pages. The trial version is limited to showing issues on 4 pages.
Expand all 9 issues