標籤

2012年5月7日 星期一

Lab 23 Making web pages accessible


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

Accessibility Extension

List of Accessibility Issues Summary

FAE RuleViolationsMessageClass
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 
Warn 1 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 
Warn 1 Hidden or empty frames should not be used. Frames 
Fail 1 The b element must not be used to bold text content, instead use heading (h1-h6) elements for heading text or the strong element for emphasizing words, phrases or sentences. Text Styling 
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 
Fail 2 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 5 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: 5/7/2012 21:10 PM
URL: file:///C:/Users/ELstudent/Desktop/Google.htm





2. Fix the failures you found.




沒有留言:

張貼留言