Appendix O

In EDU 577, I developed the framework for my Professional Portfolio web page and developed my classroom web page. I used several sites to determine the areas in which my web design could include, and implemented them to improve my portfolio. The data and results of this are shown below. The use of these sites shows my understanding of the following elements from the NETS-T, CTTC, and CCCT.

NETS-T – I.a, II.b, V.a, V.b

CTTC – I.c, II.c, II.d

CCCT – 2.4, 3.3

Robert H. Ives, Jr.

6/8/07

EDU 577

A4-Accessibility Testing

In an effort to improve my online Professional Portfolio, I accessed several sites that would offer suggestions for improving my web page. These proved very important and provided wonderful feedback that I’ve used to make my web site better.

The first site I visited is named WebXACT and is provided by the Watchfire Corporation (2007). This site analyzes web pages in terms of q ality, accessibility, and privacy. It first came up with an error that said my page lacked a DOCTYPE statement. I also received an error about my page not identifying the language of the text. The last error I received commented on my failure to provide a summary for the tables contained within my page. I found the first two errors intriguing, and noted them so I could further investigate through other accessibility testing sites. The last error was not relevant to my page, because the table was used only for layout, not as a data table.

The second site I visited was at hermish.com. First, it validated the input from the previous site by stating that my site failed to indicate a document type. It also issued a warning, stating that I should check the contrast between my foreground and background colors. I noted this as something to check further into. Hermish.com also noted that I failed to specify the prime language of the document (Slinn, 2007).

In an attempt to gain further information about the color scheme of my site, I visited a site called AccessColor (2007). According to this site, both color difference and color brightness standards were not being met. The differences between my background and foreground colors were not significant enough and the site could be difficult to view, especially by those with visual handicaps.

Aware that I needed to address the color issues of my site, I next used a site called Accessibility Color Wheel by Giacomo Mazzocato. By plugging in the foreground and background colors of my site, I was able to see how my site would appear to those with visual difficulties. I was also able to tweek the colors until a big “OK” appeared on the screen. This indicated that the colors would now meet standards and be visually attractive to any that viewed the site. I could then make note of the new color codes and enter them into my html code to make my site more visually attractractive.

I was able to use the advice given to me by these tools to revise my web site. First, I indicated a DOCTYPE in my html, fixing that problem. Secondly, I entered code specifying the prime language of the document. Thirdly, I changed the colors of all the text in my online portfolio so they met visual standards. After fixing the color scheme, I immediately noticed a change for the better. Lastly, I wrote a caption for the picture on the index page. I changed the address of the new index page slightly so you could compare it to my original and see the changes that were made. My new and improved page is at www.woodstockschools.net/ives/ProfessionalPortfolio.htm.

References:

Slinn, G. (2007). Hermish: Tools for Better Web Pages. Retrieved June 7, 2007, from http://www.hermish.com/

Watchfire Corporation. (1996-2007). WebEXACT. Retrieved June 7, 2007, from http://webxact.watchfire.com/

Access Keys. (2007). AccessColor - Online Tool for Colour Contrast. Retrieved June 7, 2007, from http://www.accesskeys.org/tools/color-contrast.html

Mazzocato, G. (2007). Accessibility Color Wheel. Retrieved June 7, 2007, from http://gmazzocato.altervista.org/colorwheel/wheel.php