86306 - mozilla.org has minor priority2 and priority3 accessibility errors

Status: RESOLVED WONTFIX

(www.mozilla.org :: General, defect)

Description

[Cormac F]

The above link validates the mozilla.org homepage using the bobby accessiblity 
validator at http://www.cast.org/bobby
Mozilla.org does quite well, but there are still one or two minor errors that 
prevent priority 2 and priority 3 compliance.

We need to comply with as many of the WAI accessibility checkpoints as 
possible, to ensure the mozilla.org site is accessible to the widest range of 
users. (including the pages available through the browser, such as 
http://www.mozilla.org/releases) 

Complying with the recommendations in the above document should be a fairly 
easy task for an individual page (when applied to the whole site, it might take 
a little bit longer, but only a matter of hours.A sitewide search/replace or 
something should make it easy)

Either way, we still have priority 1 compliance, and can place that attractive 
bobby symbol on the homepage....!

Comment 1

[Mitchell Baker]

Reassigning to Dawn, who keeps the website.  Also cc'ing Aaron.

Comment 2

[Andreas Franke (gone)]

-> [e-mail] component.

Comment 3

[James Cox]

-> taking QA contact so I don't need to watch Dawn anymore. ;)

Comment 4

[Cees T.]

I've compared outputs of www.mozilla.org and bobby.cast.org itself and these are
the only points that make mozilla.org worse:

Priority 1 User Checks
# If this is a data table (not used for layout only), identify headers for the
table rows and columns. (5 instances)
Lines 25, 77, 149, 200, 20 
# If a table has two or more rows or columns that serve as headers, use
structural markup to identify their hierarchy and relationship. (20 instances)
Lines 10, 25, 24, 23, 80, 92, 77, 72, 139, 152, 165, 149, 144, 192, 203, 214,
200, 195, 66, 20 

Priority 2 Accessibility
# Do not use the same link phrase more than once when the links point to
different URLs. (4 instances)
Lines 176, 230, 246, 256 

Priority 2 User Checks
# Add a descriptive title to links when needed.

Priority 3 Accessibility
# Provide a summary for tables. (20 instances)
Lines 10, 25, 24, 23, 80, 92, 77, 72, 139, 152, 165, 149, 144, 192, 203, 214,
200, 195, 66, 20
# Identify the language of the text. (1 instance)
Line 2 

Priority 3 User Checks
# If this is a data table (not used for layout only), provide a caption. (20
instances)
Lines 10, 25, 24, 23, 80, 92, 77, 72, 139, 152, 165, 149, 144, 192, 203, 214,
200, 195, 66, 20 
# Use the ABBR and ACRONYM elements to denote and expand any abbreviations and
acronyms that are present.

Comment 5

[Dave Miller [:justdave]]

reassigning endico's bugs to default owner

Comment 6

[Anne (:annevk)]

I seriously doubt if this bug is still relevant. I propose WORKSFORME.

Comment 7

[dolphinling]

We still fail on 

13.1 Clearly identify the target of each link.
    * Rule: 13.1.2 - All Anchor elements are required not to use the same link
text to refer to different resources.
          o Failure - Anchor Element at Line: 726, Column: 37

We get warned on not having tabindex and accesskey on all links and (most) form
elements (which IMO is pretty stupid...)

Comment 8

[Jesse Ruderman]

The links Bobby complains about:

Two links labelled "Other languages" (one for Firefox, one for Thunderbird, both
in <noscript> blocks).

Two image links with the same alt text, "Live Bookmarks icon".  The alt text
could be changed to e.g. "Announcements in RSS".

Two links labelled "Mozilla Store".  The links are the same except for tracking
information, so I think this is ok.

Comment 9

[David Boswell]

It looks like Bobby is no longer available.  Here are some other links that may have useful information to help us with accessibility testing:

http://www.w3.org/WAI/eval/Overview.html
http://www.marcozehe.de/articles/how-to-use-nvda-and-firefox-to-test-your-web-pages-for-accessibility/

Comment 10

[Chris More [:cmore]]

Closing old Mozilla.org website bugs due to them not being relevant to the new Python-based Bedrock system. Re-open if this is a critical bug and should be resolved on the new system too.

Comment 11

[Samuel Sidler (:ss)]

WONTFIX seems about right here... Unless someone cares about accessibility and can investigate?

Comment 12

[alexander :surkov (:asurkov)]

Marco, you might want to look