Bobby
URL tested: http://www.couvas.com.cy/carton2.htm, April 29, 2001 8:35:34 PM GMT+00:00
Bobby Core v3.2, WAI Guidelines 1999/05/05

About this report

The Bobby report presents an accessibility evaluation grouped by the three priority levels defined by the Web Access Initiative (WAI), as well as browser compatibility and download statistics. As an automated evaluation tool, Bobby is able to detect many accessibility problems and to highlight other possible problems that must be checked. A "Bobby" hat in the original page (if displayed) indicates that Bobby was able to detect a Priority 1 problem with accessibility. A question mark indicates a Priority 1 item that needs to be checked by the user. Follow the links provided in the report to get details about any problem reported, including how to repair it, if needed. For more information on the report, please access our online documentation.

To be Bobby Approved, a page must pass all of the Priority 1 accessibility checkpoints established by the WAI.





Click on the error messages below to find out more information.

Priority 1 Accessibility

This page does not meet the requirements for Bobby Approved status. Below is a list of 1 Priority 1 accessibility errors found:

  1. Provide alternative text for all images. (4 instances)
    Line 14, Line 16, Line 21, Line 29

User Checks

User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby Approval requires that none of them apply to your page. Please review these 3 item(s):

  1. If you use color to convey information, make sure the information is also represented another way.

  2. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (3 instances)
    Line 27, Line 25, Line 56
  3. If an image conveys important information beyond what is its alternative text, provide an extended description. (4 instances)
    Line 14, Line 16, Line 21, Line 29

The following 4 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby Approved status.

  1. Ensure that descriptions of dynamic content are updated with changes in content.

  2. Use the simplest and most straightforward language that is possible.

  3. Avoid ASCII art.

  4. If you can't make a page accessible, construct an alternate accessible version.

Not Bobby ApprovedThis page does not yet meet the requirements for Bobby Approved status.


Priority 2 Accessibility

Bobby Approved status is assigned on the basis of Priority 1 items in the Web Content Guidelines. For a higher level of accessibility you may also want to examine Priority 2 and Priority 3 items. 2 Priority 2 issue(s) that Bobby has identified are presented below.

  1. Use relative sizing and positioning (% values) rather than absolute (pixels). (2 instances)
    Line 33, Line 58
  2. Avoid use of deprecated language features if possible. (3 instances)
    Line 23, Line 54, Line 58

User Checks

4 Priority 2 issue(s) that Bobby has identified are presented below:

  1. Check that the foreground and background colors contrast sufficiently with each other.

  2. Avoid using movement in images where possible. (4 instances)
    Line 14, Line 16, Line 21, Line 29
  3. Avoid using tables to format text documents in columns unless the table can be linearized. (3 instances)
    Line 27, Line 25, Line 56
  4. Add a descriptive title to links when needed.

The following 8 item(s) are not triggered by any specific feature on your page, but are still important for accessibility.

  1. Use a clear, consistent navigation structure.

  2. Make sure your document validates to formal published grammars.

  3. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).

  4. Use metadata to add computer-understandable information about the page.

  5. Group related elements when possible.

  6. Ensure that dynamic content is accessible or provide an alternate presentation or page.

  7. Offer a site map or table of contents, and provide a description of the general layout of the site, the access features used, and how to use them.

  8. Use the latest technology specification available whenever possible.


Priority 3 Accessibility

Bobby Approved status is assigned on the basis of Priority 1 items in the Web Content Guidelines. For a higher level of accessibility you may also want to examine Priority 2 and Priority 3 items. 2 Priority 3 issue(s) that Bobby has identified are presented below.

  1. Identify the language of the text. (1 instance)
    Line 2
  2. Provide a summary and caption for tables. (3 instances)
    Line 27, Line 25, Line 56

User Checks

4 Priority 3 issue(s) that Bobby has identified are presented below:

  1. Provide abbreviations for long row or column labels. (3 instances)
    Line 27, Line 25, Line 56
  2. Specify a logical tab order among form controls, links and objects.

  3. Consider adding keyboard shortcuts to frequently used links.

  4. Provided a linear text alternative for tables that lay out content in parallel, word-wrapped columns. (3 instances)
    Line 25, Line 27, Line 56

The following 9 item(s) are not triggered by any specific feature on your page, but are still important for accessibility.

  1. Create a consistent style of presentation between pages.

  2. Provide a link at the beginning of a group of related links to bypass the group.

  3. Use icons or graphics (with accessible alternatives) to facilitate comprehension of the page.

  4. Allow users to customize their experience of the web page.

  5. Use the ABBR and ACRONYM elements to denote and expand abbreviations and acronyms.

  6. Offer navigation bars for easy access to the navigation structure.

  7. Place distinguishing information at the beginning of headings, paragraphs, lists, etc.

  8. If ASCII art is present, provide a means to skip over it.

  9. Offer different types of searches for different skill levels and preferences.



Browser Compatibility Errors

The following section contains a list of 4 browser compatibility errors. Browser compatibility errors help to determine when HTML tags and their attributes are not compatible with certain web browsers or HTML specifications. Browser compatibility errors do not affect the accessibility rating of a page.
  1. Unknown attribute WIDTH in element TD. for browser(s): Lynx2.7 (1 instance)
    Line 33
  2. Unknown element name !DOCTYPE for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (1 instance)
    Line 1
  3. Required attribute ALT is missing from tag IMG for browser(s): HTML4.0 (4 instances)
    Line 14, Line 16, Line 21, Line 29
  4. Unknown attribute COLSTART in element TD. for browser(s): Lynx2.7, Explorer4.01, Navigator4.0, HTML4.0 (2 instances)
    Line 27, Line 33

Download Time

The following three-column table gives download time statistics for the images, applets, and objects on this page. The first column contains the URL of each item, the second column the item size in kilobytes, and the third column the approximate download time for each item when using a 28,800 baud modem. At the end of the report, an arbitrary delay of 0.5 seconds is added for each file to account for slow-downs caused by HTTP connection times.

URL
Size
Time (secs)
http://www.couvas.com.cy/carton2.htm 2.12 K 0.59
http://www.couvas.com.cy/cartlogo.gif 4.96 K 1.38
http://www.couvas.com.cy/cartname.gif 5.86 K 1.63
http://www.couvas.com.cy/leaders.gif 6.77 K 1.88
http://www.couvas.com.cy/no104.gif 17.39 K 4.83
Total
37.08 K
10.30
HTTP Request Delays
--
2.50
Total + Delays
--
12.80