In-Class Exercise: Assessing Accessibility (posted 8 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). Make note of all of the priority 1, 2, and 3 problems identified.
- Now, 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 you had to change on your site, and what level of accessibility compliance you were able to achieve.
I'm pleased to see that 'my' school district passed with flying colors. The RNEWS site did well, also.
Posted by: Anne Buck on December 8, 2003 06:58 PM | Permalink to CommentMy page passed. Other folks' sites that I visited were missing the doctype and did not have text elements for graphic images.
Posted by: Curt Markham on December 8, 2003 07:10 PM | Permalink to CommentHi,
I checked for priority 1 for the blog page that was created in the first class. That didn't show any problem.
Checking my own homepage showed the priority1 in section 12.1 where it was required to have title to each of the frames that was included in the frameset.
After including the title, it passed the check with no probs.
Namgyal
Posted by: Namgyal Dolker on December 8, 2003 07:18 PM | Permalink to CommentIt hated my Javascript based navigation system, for a variety (many, many) reasons. Some of the problems were that I didn't have accessability provisions in the code itself, and some problems related to the fact that the images in the navigation didn't have ALT attributes, and they were colored. The JScript navigation also died in Mozilla, so I just blew it away. Time to go back to simple text based links. at least they pass.
Posted by: Aaron Sanders on December 8, 2003 07:26 PM | Permalink to CommentSince everything I ever did failed the www.cynthiasays.com site miserably, I created a "clean" HTML page (empty), and voila, it passed. Now I'm adding elements one-by-one and watching the reports. This is like driving school; you have to navigate between the orange cones.
Posted by: Robert on December 8, 2003 07:33 PM | Permalink to CommentMy page passed. But, one of my other websites failed due to missing code for the images such as "alt." So I added "alt" to the image code and then re-tested it. Finally, it passed.
Posted by: Bakhtiar on December 8, 2003 07:34 PM | Permalink to CommentI tried to view one of the pages I created last quarter in 741, but the max allowed url submission for rit sites had been reached. I used a page that I created a couple of years ago with Dreamweaver and Cynthia had it for dinner. My priority 1 errors were that there was no Doc Type statement, none of my images had alt statements, and I had no NOSCRIPT option for viewers that didn't have the supporting software. My priority 2 error was that I used deprecated elements and/or attributes. My priority 3 error was that I had no language attribute. I unfortunately was not able to correct these errors because i no longer have access to my UD account.
It's amazing that the page can be so flawed but still be viewable on most browsers.
Posted by: Christian Crews on December 8, 2003 09:02 PM | Permalink to CommentChristian-
Remember, these are accessibility guidelines, not just HTML standards. That means that although the page is "viewable on most browsers," and may even be valid HTML, the content would be inaccessible to many disabled users.
Posted by: Liz Lawley on December 8, 2003 09:57 PM | Permalink to CommentI checked this page first. This one failed priority 1, 2, and 3. The modifications I made to fix the priorty 1 problem is this. I made the change after I did the accessibility simulation...so I tried to make the longdsc informative. (By the way, the simulation was just too hard. People who can navigate through sites that way have some skills!!!)
The second page I run the check was this. Initially, this had priority 2 and 3 failures such as not specifying language type in HTML root and not including DOCTYPE. After struggling for hours to get rid of table format AND make them compliant with the standard, I'm just glad that I got it done.
I was thinking of adding a Javascript to the first assignment...but now I'm scared that I need to spend hours satisfying the standards.
My thought on the in-class assingment is simplicity seems to make the site more accessible to wider range of viewers. However, simplistic designs seem to bore many of them as well. I suppose there needs to be a balance. I can understand that conceptually, but very difficult to come up with the actual design.
(Detailed report on Cynthia Says is posted on my course blog.
Posted by: Fuyuko Takegawa on December 9, 2003 01:24 AM | Permalink to CommentI also had a page fail because it was missing the alt attribute in all of the images. I've found this to be very enlightening because I never realized how difficult this is for people with disabilities. I have read about it many times but disregarded much of it because I didn't realize the impact it had on those with handicaps. I'm embarrassed I didn't take it more seriously. Seeing a report stating there were problems on a page I created can't be overlooked like reading a brief article about why it's important to make sites accessible.
Posted by: Vince Falbo on December 10, 2003 10:32 PM | Permalink to Comment
Trackback Link: http://www.it.rit.edu/~ell/mt/mt-tb.cgi/644