Lab 21 Making web pages accessible

1. Use Firefox Accessibility Extension to identify the accessibility failures and warnings in http://google.com
2. Fix the failures you found.

Accessibility Extension

List of Accessibility Issues Summary

FAE Rule	Violations	Message	Class
Warn	1	The words contained in each h1 element should match a subset of the words contained in the title element. Words (%1) in h1 elements should also be in the title element.	Title
Check	1	Heading content should be concise (usually 65 or fewer characters in length).	Headings
Fail	1	Every frame element must have a title attribute with content that describes the purpose of the frame.	Frames
Warn	1	Hidden or empty frames should not be used.	Frames
Warn	1	One level of nesting. Use CSS properties instead of tables and nested tables to visually layout blocks of related content for graphical renderings.	Tables
Fail	1	Two or more levels of nesting. Use CSS properties instead of tables and nested tables to visually layout blocks of related content for graphical renderings.	Tables
Warn	1	The character encoding was not specified.	W3C Specifications
Warn	2	Each map, ul or ol element that precedes the last h1 element and appears to be a navigation bar should be immediately preceded by a heading element, preferably an h2.	Menu and Navigation Bars
Fail	3	The font and center elements must not be used for text styling, instead use structural markup should be used with CSS for styling.	Text Styling
Warn	4	Ensure that links that point to the same HREF use the same link text.	Links
Fail	6	Each page must have a lang attribute on its html element whose value or initial subtag is a valid two-character language code.	Language Changes
Warn	15	Avoid using text links that are shorter than four 4 characters in length.	Links

Date: 11/5/2012 20:14 PM
URL: http://www.google.com/



Q:請描述至少一個你做這個lab所遇到的問題，並且你是如何解決這個問題的。
A:剛開始搞不太清楚載的東西是甚麼找很久，之後發現這個功能很方便好用