Assessing Accessibility: Studio Exercise (12 January 2005)
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 the server is refuses to accept any more 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 your site. Which problems were you able to fix? Were there any you couldn't? (If you weren't able to test your site in class, do this before Thursday.)
Excerpt: I submitted both my 409 mains and midterm sites to the Cynthia Says check--both passed on the Priority 1 checklists. Both failed one of the Priority 2 items in that I used the "align" property within a table and div...
Read More: Cynthia Says, Screen Readers, and Color Blindness
Excerpt: For this studio class we had to test the accessibility of two of our sites. I couldn't connect to my RIT sites, so I used two other sites that I had created in the past, but, unfortunately, do not have...
Read More: Accessibility
Excerpt: For our first exercise today we used a web site called Cynthia Says to evaluate two of our web pages. I first evaluated my 409 site and only found one priority 3 problem. I had links next to eachother that...
Read More: Cynthia Says I Rock
Excerpt: w00t! I passed on the first try. Granted my website is FAR from complex. It really only has 3 links, but as far as Cynthia is concerned ...its meets all standards. I am very happy that I won't have to...
Read More: I Passed with Flying Colors!
Excerpt: Today's exercise. This was different. The one site with the computer voice was difficult to understand. Was able to find Founder and phone number but class schedule was hard until I looked at the visable site and found no bio...
Read More: Assesibilty sites
Excerpt: Testing my two websites went relatively smoothly. The first site I tested was my faculty website I made for this class. The url is www.rit.edu/~kmn3568/409/faculty.html. That website passed all of Cinthia's test on it's first run. The second site I...
Read More: Cinthia Says!
Excerpt: I didn't complete these exercises in class because I used the time to get help with my midterm website, but I did them this morning. For cynthia says, I tested my 409 site, my midterm site, thefacebook site, and also...
Read More: cynthia says, vischeck, etc
Excerpt: Yay! I finally did the inclass exercise from last week, and my main 409 page passes priority 1 and 2 verifications, according to Cynthia. The only thing that I have to fix is the priority 3 requirement of identifying the...
Read More: Accessibility inclass exercise
Excerpt: For this inclass, I tested both my 409 homepage and my midterm site. My homepage had one priority 2 problem regarding the use of a deprecated align element, and a (priority 3) missing primary language definition. My Midterm site only...
Read More: Cynthia Says Report
Excerpt: I ran my midterm website and my poem website through the Cynthia says tester. I got two errors on my midterm website. The first priority 2 error was that I set the border property in my navigation links to zero...
Read More: Assessing Accessibility exercise
http://www.rit.edu/~mlm4924/409 is the first site that I attempted. There was only one priority 3 problem that a language was not specified in the html tag, which was easily fixed.
http://www.rit.edu/~mlm4924/409/border/border.html was the second site that I attempted. I had 1 Priority 2 problem that said to avoid deprecated features of W3C technologies. Basically it said that I cannot use the align element inside of the IMG tag. I also encountered the same problem as before with the language, which was easily fixed.
Posted by: Matt Muoio on January 12, 2005 12:23 PM | Permalink to CommentI tested my old IMM page and 409 front page. The IMM page had one priority 1 issue - an image without alt text. It had three priority 2 issues - removing background from the body tag, adding the doctype and meta information. Both issued were fixable. The 409 page had no priority 1 or 3 issues. However, both pages had two of the same warnings in priority 2 - using the tabindex and accesskey features. I cannot fix either of those problems because I don't have anything in my pages (that I can see) that would use either tabindex or accesskey.
Other than those warnings, everything is now a-ok on both pages.
Posted by: Erin Milano on January 12, 2005 1:15 PM | Permalink to CommentI checked my 409 page with Cynthia Says. I had no Priority 1 problems. I only had one Priority 2 problem and that was because I had an align attribute inside one of my div tags. I simply deleted the align attribute and the problem was fixed. I had two Priority 3 problems. The first was that I did not have a 'lang' attribute defined in my HTML tag. I inserted lang="en-US" in my HTML tag and that solved the problem. The other Priority 3 problem was that I had several anchor elements directly adjacent to another anchor element. These were the links in my navigation bar, and I am not sure how to correct it without changing my navigation bar.
Posted by: Katie Nemmer on January 13, 2005 5:02 AM | Permalink to CommentI tested my 409 page and I didn't get any priority 1 errors. Sorry, I forgot to post it on that day.
Posted by: Jesus Janne on February 3, 2005 7:54 PM | Permalink to Comment
(Trackback link: http://www.it.rit.edu/~ell/mt/mt-tb.cgi/1215)