In-Class Exercise: Assessing Accessibility (posted 9 December 2003)
- Use Cynthia Says to evaluate at least two of your own web pages (with at least one of those being on your Grace account). If you don’t have a web page of your own, or if the server is not accepting URLs from rit.edu, review a page that you visit frequently. Make note of all of the priority 1, 2, and 3 problems identified.
- If you reviewed your own web page, fix the Priority 1 problems. Remember that to pass the W3C recommendations, you must not have any Priority 1 problems. (You may find it helpful to use the WCAG checklist.)
- After you’ve fixed your Priority 1 problems, look at the other comments in the report provided. Your efforts should now be directed towards fixing any Priority 2 problems. Finally, Priority 3 problems may also be fixed to provide maximum accommodations.
Post a comment to this entry that describes what problems you found on the site that you visited. If it was your own site, what level of accessibility were you able to achieve?
Generally the pages I looked at using the "Cynthia says" tool find that most images do not have the alt info to explain what the images is. The other common problem I see is that with the pages containing frameset they don't have any other way to display the info if frames are not supported.
Posted by: Michael Ashman on December 9, 2003 08:51 AM | Permalink to CommentI ran my company's site (http://www.pbtg.com -- don't look, it's ugly, new revision on the way) through Cynthia and for a site that is 5 years old, it has few problems. The only points of failure were images that do not have alt attributes, the HTML element does not have a lang attribute, and it uses the deprecated bgcolor attribute. It is good to keep these things in mind as we work on a webpage revision.
Posted by: Sean Hannan on December 9, 2003 08:59 AM | Permalink to Commenti viewded my own site, from what i could decipher i failed to include tags, i went ahead and fixed the problem.
Posted by: jordan fripp on December 9, 2003 09:00 AM | Permalink to CommentI've run a few sites through Cynthia and it looks like the most common problem is the lack of "alt" attributes on image tags.
Posted by: Jen R on December 9, 2003 09:00 AM | Permalink to CommentOn several of the web pages I viewed, the largest problem seemed to be not having alt tags for some images. Another frequent problem was not having the DOCTYPE tag.
Posted by: Philip Charles on December 9, 2003 09:01 AM | Permalink to CommentThe page that I evaluated was www.theforce.net. The problems were mainly in the non-existance of alt tags, though I did find alt tags in at least one line that the Cynthia Says complained about. The other priority checks complained about the missing doctype and meta tags, something about depreciated tags with the body bg tag, missing lang atribute in the html tag, anchor problems, and problems with targets for the links.
Posted by: Christine Chriscaden on December 9, 2003 09:01 AM | Permalink to Commenti viewed my 409 website, i failed to include alt tags and language tags. ill fix this soon.
Posted by: jordan fripp on December 9, 2003 09:02 AM | Permalink to CommentOn legos website, the problems found mostly had to do with the lack of alt tags. There was also a problem with it having embed elements without having noembed.
Posted by: Michael Delaney on December 9, 2003 09:06 AM | Permalink to CommentI reviewed a video games web site I visit often (http://cube.ign.com)
And found a Priority 1 violation of the following WCAG guideline... Rule: 1.1.1 - All IMG elements are required to contain either the alt or the longdesc attribute.
This seems to be a fairly common error on many sites, and also a fairly easy error to fix as well. It must be frustrating for someone who cannot see the many images that exist on the web to have to hear "image" with no explanation of what it contains when using a screen reader.
I ran http://www.timecube.com through the Cynthia validator. It failed at Rule 1.1.1 because the page did not include alt or longdesc attributes for some img tags. Overall the site did very well for being quite primitive in layout.
Posted by: Erhardt Graeff on December 9, 2003 09:08 AM | Permalink to CommentI look under www.norwalklib.org. There were a lot of Priority 1 problems, the img image did not have any alt attributes. They have problems with bgcolor attributes. The other error, never included - MARQUEE in the website. Only if the users want to use it.
Posted by: Olga on December 9, 2003 09:09 AM | Permalink to CommentI went to webmonkey and the only priority 1 problem was the lack of alt tags. In priority 2 the site doesn't use the doctype tag and auto-refreshes without letting you stop it.
Posted by: brian tepfenhart on December 9, 2003 09:10 AM | Permalink to CommentI checked penny-arcade.com, and the dominant Priority 1 problem was that many images did not have text-alternatives and/or descriptions included with them in the code. Priority 2 problems included the absence of a !Doctype tag and the use of bgcolor, which I did not realize was a W3C deprecated attribute now. Finally, one Priority 3 problem was the lack of a lang tag.
Posted by: Shad Ali on December 9, 2003 09:11 AM | Permalink to CommentFrom the pages I checked using the "Cynthia says" tool ever single one failed, Usally from not adding a ALT element to the IMG tag.
Posted by: Ricky on December 9, 2003 09:11 AM | Permalink to CommentI just used two of my old IMM pages and ran those through, and I concur with the above comments on lack of alt attribs and so on.. Specifically, here's what I had to do on each page to fix the "failures" Cynthia found:
http://www.rit.edu/~scs6901/imm/index.html
1) Added !DOCTYPE tag
2) fixed use of deprecated "bgcolor" attribute in BODY tag - replaced with STYLE tag (stylesheet)
3) added lang attribute to HTML tag
http://www.rit.edu/~scs6901/imm/project3/index.html
1) added alt attribute to IMG tags
2) added lang attribute to HTML tag
3) fixed use of deprecated "bgcolor" attribute in BODY tag - replaced with STYLE tag (stylesheet)
I ran the websites for the two banks I use. www.bsbbank.com & www.us.hsbc.com. both of which had the same priority failures. Priority 1: missing alt attributes. Priority 2: not using DOCTYPE tag, identifying the target for each link, and Labels associated explicitely with their controls. Priority 3: Identify language of a document.
Posted by: Maria Morris on December 9, 2003 09:15 AM | Permalink to CommentI used Cynthia to evaluate www.yahoo.com. There were some problems with img images. They were missing alt tags or the longdesc attribute in the priority 1.
Posted by: Qing on December 9, 2003 09:19 AM | Permalink to CommentWebsite: www.umterps.com
When I ran this website to test for web content to find any errors in it. I found out that their image elements do not have any comments in alt to describe each image. In addition, the server included map is required to be used, which is missing from this website.
Another website: www.espn.com
This website do not include any comments in alt tag for each image. Also, it failures of input elements for both radio and text, and area. For the priority 2, there are some mistakes such as Meta for refresh, already use the deprecated elements or attributes which is not required, failure at anchor elements, input of text and radio, and others. Finally, the priority 3 has some warnings for this website need to be fixed. I realized that this website, "Cynthia says Report" is a good tool to check for any mistakes in your webpages. By the way, I used Microsoft 6.0 to test for both websites above.
Posted by: Nick Hawkins on December 9, 2003 10:28 AM | Permalink to Comment
Trackback Link: http://www.it.rit.edu/~ell/mt/mt-tb.cgi/647