MozillaZine

Site Suggestions

Tuesday January 8th, 2002

A few of you have asked for us to post a news item taking your suggestions for the site, so here it is. Tell us all your ideas for what we can do to improve the site. Anything you want we'll think about, but try to keep it realistic.

Just to keep you updated, one of the things we're planning on working on is getting the ChromeZone up again, if we can find some volunteer editors to help organize themes. If you're interested, please email me and I'll get back to you sometime this week.

UPDATE! Right now we're working on dumping all the tables and other old HTML within the site to both show off Mozilla's skills, and to get our file sizes smaller. If you're using Communicator to view the site, you'll notice everything looking pretty ugly, thanks to the poor CSS support it offers. If you're using IE, it'll look a bit better, but thanks to IE's lacking CSS2 support, the sidebar will show up incorrectly. We've completely redone the homepage and talkback code, and we'll be working on the forums next.

UPDATE 2! We discovered Google's great "Search Site" feature, and have added it. Right now it has most areas of the site indexed except news item talkback pages. It will start indexing talkback today, and will hopefully add all of the old items, in addition to picking up the new ones.

UPDATE 3! We've been working hard to get as many of your suggestions as possible implemented, and we encourage you to continue the feedback. You can check this article's responses for what items we have fixed, or are working on.


#170 Keep it accessable

by kberk <kberk@bigfoot.com>

Tuesday January 15th, 2002 9:02 PM

You are replying to this message

In the rush to standards compliance, no tables, and tons of CSS, please be sure to keep the site accessable.

I suggest you validate the HTML, CSS and Accesability and put those buttons on the site to advertise compliance.

Here is todays output from Bobby and the HTML Validator:

Priority 1 Accessibility Priority 1 User Checks User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby AAA Approval requires that none of them apply to your page. Please review these 5 item(s): 1. Provide alternative content for each SCRIPT that conveys important information or functionality. 2. If style sheets are ignored or unsupported, are pages still readable and usable? 3. If you use color to convey information, make sure the information is also represented another way. (13 instances) Lines 15, 16, 23, 24, 28, 29, 30, 31, 62, 107, 148, 202, 230 4. If the submit button is used as an image map, use separate buttons for each active region. (1 instance) Line 194 5. If an image conveys important information beyond what is in its alternative text, provide an extended description. (13 instances) Lines 15, 16, 23, 24, 28, 29, 30, 31, 62, 107, 148, 202, 230 The following 3 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby AAA Approved status. 6. If you can't make a page accessible, construct an alternate accessible version. 7. Identify any changes in the document's language. 8. Use the simplest and most straightforward language that is possible.

Priority 2 Accessibility This page does not meet the requirements for Bobby AAA Approved status. Below is a list of 3 Priority 2 accessibility error(s) found: 1. Nest headings properly. (8 instances) Lines 44, 53, 62, 68, 76, 81, 89, 100 2. Make sure event handlers do not require use of a mouse. (1 instance) Line 122 3. Explicitly associate form controls and their labels with the LABEL element. (8 instances) Lines 149, 172, 212, 213, 214, 215, 216, 217 Priority 2 User Checks User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby AAA Approval requires that none of them apply to your page. Please review these 8 item(s): 1. Use style sheets to control layout and presentation wherever possible. 2. Make sure that labels of all form controls are properly placed. 3. If there are logical groupings of form controls, use FIELDSET with LEGEND on each group. (4 instances) Lines 146, 169, 186, 205 4. If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening. (1 instance) Line 132 5. Make sure header elements are not used only for bold text. 6. Check that the foreground and background colors contrast sufficiently with each other. (13 instances) Lines 15, 16, 23, 24, 28, 29, 30, 31, 62, 107, 148, 202, 230 7. If this gif image is animated, make sure it does not contain fast or distracting motion. (14 instances) Lines 15, 16, 23, 24, 28, 29, 30, 31, 62, 107, 148, 194, 202, 230 8. Mark up any quotations with the Q and BLOCKQUOTE elements. The following 7 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby AAA Approved status. 9. Make sure that all link phrases make sense when read out of context. 10. Group related elements when possible. 11. Make sure your document validates to formal published grammars. 12. Is there a site map or table of contents, a description of the general layout of the site, the access features used, and how to use them? 13. Is there a clear, consistent navigation structure? 14. Use the latest technology specification available whenever possible. 15. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML).

Priority 3 Accessibility This page does not meet the requirements for Bobby AAA Approved status. Below is a list of 3 Priority 3 accessibility error(s) found: 1. Identify the language of the text. (1 instance) Line 2 2. Include default, place-holding characters in edit boxes and text areas. (2 instances) Lines 172, 223 3. Separate adjacent links with more than whitespace. (18 instances) Lines 65, 107, 111, 112, 113, 114, 115, 116, 118, 130, 131, 161, 162, 163, 165, 166, 167, 168 Priority 3 User Checks User checks are triggered by something specific on the page; however, you need to determine whether they apply. Bobby AAA Approval requires that none of them apply to your page. Please review these 6 item(s): 1. Consider furnishing keyboard shortcuts for form elements. 2. Consider specifying a logical tab order among form controls, links and objects. 3. Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present. 4. If you have grouped links, is there a link at the beginning to bypass the group? 5. If there are logical groups of links, have they been identified? 6. Consider adding keyboard shortcuts to frequently used links. The following 5 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby AAA Approved status. 7. Is there distinguishing information at the beginning of headings, paragraphs, lists, etc.? 8. If there is a search feature, are there different types of searches for different skill levels and preferences? 9. Are there navigation bars for easy access to the navigation structure? 10. Do you allow users to customize their experience of the web page? 11. Is there a consistent style of presentation between pages?

Copyright 1996-2001, CAST, Inc. All Rights Reserved. Use of this software is subject to the CAST Software License Agreement. Send feedback to <bobbyww@cast.org>. Additional information available at the Bobby Home Page.

HTML Validation Service Results URI:

Server: Apache-ADTI/1.3.22 (Unix) mod_gzip/1.3.19.1a mod_throttle/3.1.2 PHP/4.0.6 mod_ssl/2.8.5 OpenSSL/0.9.6b Detected Character Encoding: iso-8859-1 Select Character Encoding:

Current Doctype: HTML 4.0 Strict

Select Doctype:

Options: Show Source Outline Parse Tree ...no attributes

Below are the results of attempting to parse this document with an SGML parser. ? Line 23, column 50: ? ... /image/separator.gif" width="1" height="19" align="absmiddle" alt=""> ^ Error: there is no attribute "ALIGN" for this element (in this HTML version) Sorry, this document does not validate as HTML 4.0 Strict. If you use CSS in your document, you should also check it for validity using the W3C CSS Validation Service. Gerald Oskoboiny Last modified: Date: 2001/09/14 04:13:13