 |
Tweed Promotions Internet web page services |
|
|
 |
 |
 |
 |
 |
 |
|
|
|
Assignment
|
Confirm Accessibility Part A
What are the accessibility standards and who do they apply to;
Web Content Accessibility Guidelines 1.0
W3C Recommendation 5-May-1999These standards provide guidelines for the accessibility of a site so that it can be used by disadvantaged persons It provides the sites content that, when presented to the user, conveys essentially the same function or purpose as auditory or visual content.Priorities
There are three priority levels within the guidelines;
Priority one A Web developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document. Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents.
Priority two A Web developer should satisfy this checkpoint. Otherwise, one or more groups will find it difficult to access information in the document. Satisfying this checkpoint will remove significant barriers to accessing Web documents.
Priority three A Web developer may address this checkpoint. Otherwise, one or more groups will find it somewhat difficult to access information in the document. Satisfying this checkpoint will improve access to Web documents
The essential priority one standards cover the following criteria:
Web Content Accessibility Guidelines.
1 Provide equivalent alternatives to auditory and visual content
2 Don't rely on color alone
3 Use markup and style sheets and do so properly
4 Clarify natural language usage
5 Create tables that transform gracefully
6 Ensure that pages featuring new technologies transform gracefully
7 Ensure user control of time-sensitive content changes
8 Ensure direct accessibility of embedded user interfaces
9 Design for device-independence
10 Use interim solutions
11 Use W3C technologies and guidelines
12 Provide context and orientation information
13 Provide clear navigation mechanisms
14 Ensure that documents are clear and simple
The Web Accessibility Standards apply to all web designers and developers.Do you think accessibility standards are or are not important and why?
These standards are important as they draw our attention to the importance of providing aids within the web site that make web pages more accessible and usable by the disadvantaged. These standards identify areas that need to be considered during the design and development process of a web site and which otherwise may not have been included.
Give example of specific user groups with particular accessibility standards and requirements.
Groups who benefit from the accessibility standards are;
1 The visually impaired
2 People who are colour blind
3 The hearing impaired
4 Persons who may suffer seizures from visual flickering or images.
5 Those who may have memory loss
6 The Disabled who may suffer from multiple disabilities
7 Those who may suffer from mental health issuesA visually impaired user may use a text reader for their use of the site. They would benefit if the site was significantly text based or by the use of text to identify images and other features within the site. Also the use of text that can be viewed in a higher magnification.
What is an example of a general legislated accessibility standard and requirements?
Electronic and Information Technology Accessibility Standards
ARCHITECTURAL AND TRANSPORTATION BARRIERS COMPLIANCE BOARD
[Published in the Federal Register on December 21, 2000]
36 CFR Part 1194
[Docket No. 2000-01]
RIN 3014-AA25
AGENCY: Architectural and Transportation Barriers Compliance Board.
ACTION: Final Rule.
SUMMARY: The Architectural and Transportation Barriers Compliance Board (Access Board) is issuing final accessibility standards for electronic and information technology covered by section 508 of the Rehabilitation Act Amendments of 1998. Section 508 requires the Access Board to publish standards setting forth a definition of electronic and information technology and the technical and functional performance criteria necessary for such technology to comply with section 508. Section 508 requires that when Federal agencies develop, procure, maintain, or use electronic and information technology, they shall ensure that the electronic and information technology allows Federal employees with disabilities to have access to and use of information and data that is comparable to the access to and use of information and data by Federal employees who are not individuals with disabilities, unless an undue burden would be imposed on the agency. Section 508 also requires that individuals with disabilities, who are members of the public seeking information or services from a Federal agency, have access to and use of information and data that is comparable to that provided to the public who are not individuals with disabilities, unless an undue burden would be imposed on the agency.
Accessibility Assignment Part BPart One - Validity report
Response code from: http://www.oocities.org/marcus_2300/index.htm
Site evaluated by : w3c Validation service
This page is not Valid HTML 4.01 Transitional!
Response code from: http://www.rta.nsw.gov.au
Site evaluated by : w3c Validation service
This Page Is Valid XHTML 1.0 Transitional!
Part Two - Site accessibility evaluation
Site evaluated using Bobby
http://bobby.watchfire.com/bobby/html/en/index.jsp
URL tested: http://www.oocities.org/marcus_2300/index.htm, November 4, 2003
About this report
This page does not yet meet the requirements for Bobby AAA Approved status. To be Bobby AAA Approved, a page must pass all of the Priority 1,2 and 3 accessibility checkpoints established in W3C Web Content Accessibility Guidelines 1.0. For more information on the report, please read "How to Read the Bobby Report".
Priority 1 Accessibility
This page does not meet the requirements for Bobby A Approved status. Below is a list of 1 Priority 1 accessibility error(s) found:
1. Provide alternative text for all images. (8 instances)
Lines 17, 39, 40, 41, 42, 43, 44, 78
Priority 1 User Checks
User checks are triggered by something specific on the page; however, you need to determine manually whether they apply and, if applicable, whether your page meets the requirements. Bobby A Approval requires that all user checks pass. Even if your page does conform to these guidelines they appear in the report. Please review these 5 item(s):
1. If you can't make a page accessible, construct an alternate accessible version.
2. If style sheets are ignored or unsupported, are pages still readable and usable?
3. If you use color to convey information, make sure the information is also represented another way. (21 instances)
Lines 17, 21, 23, 36, 39, 40, 41, 42, 43, 44, 54, 56, 57, 70, 73, 77, 78, 119, 120
4. If an image conveys important information beyond what is in its alternative text, provide an extended description. (8 instances)
Lines 17, 39, 40, 41, 42, 43, 44, 78
5. If a table has two or more rows or columns that serve as headers, use structural markup to identify their hierarchy and relationship. (10 instances)
Lines 14, 29, 36, 47, 54, 65, 82, 62, 93, 11
The following 2 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby A Approved status.
6. Identify any changes in the document's language.
7. Use the simplest and most straightforward language that is possible
Priority 2 Accessibility
This page does not meet the requirements for Bobby AA Approved status. Below is a list of 1 Priority 2 accessibility error(s) found:
1. Use relative sizing and positioning (% values) rather than absolute (pixels). (38 instances)
Lines 11, 13, 16, 19, 23, 31, 38, 39, 40, 41, 42, 43, 44, 49, 56, 57, 62, 64, 67, 70, 73, 77, 82, 84, 93, 95, 96, 106, 111
Priority 2 User Checks
User checks are triggered by something specific on the page; however, you need to determine manually whether they apply and, if applicable, whether your page meets the requirements. Bobby AA Approval requires that all user checks pass. Even if your page does conform to these guidelines they appear in the report. Please review these 6 item(s):
1. Avoid use of obsolete language features if possible. (9 instances)
Lines 21, 23, 57, 70, 73, 96, 106, 111
2. If scripts create pop-up windows or change the active window, make sure that the user is aware this is happening. (3 instances)
Line 119
3. Add a descriptive title to links when needed.
4. Make sure BLOCKQUOTE is used only for quotations, not indentation.
5. Check that the foreground and background colors contrast sufficiently with each other. (22 instances)
Lines 10, 17, 21, 23, 36, 39, 40, 41, 42, 43, 44, 54, 56, 57, 70, 73, 77, 78, 119, 120
6. If this gif image is animated, make sure it does not contain fast or distracting motion. (8 instances)
Lines 17, 39, 40, 41, 42, 43, 44, 119
The following 7 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby AA Approved status.
7. Make sure that all link phrases make sense when read out of context.
8. Is there a site map or table of contents, a description of the general layout of the site, the access features used, and how to use them?
9. Make sure your document validates to formal published grammars.
10. Group related elements when possible.
11. Is there a clear, consistent navigation structure?
12. Use the latest technology specification available whenever possible.
13. Where it's possible to mark up content (for example mathematical equations) instead of using images, use a markup language (such as MathML)
Priority 3 Accessibility
This page does not meet the requirements for Bobby AAA Approved status. Below is a list of 3 Priority 3 accessibility error(s) found:
1. Provide a summary for tables. (10 instances)
Lines 14, 29, 36, 47, 54, 65, 82, 62, 93, 11
2. Identify the language of the text. (1 instance)
Line 2
3. Separate adjacent links with more than whitespace. (5 instances)
Lines 97, 98, 99
Priority 3 User Checks
User checks are triggered by something specific on the page; however, you need to determine manually whether they apply and, if applicable, whether your page meets the requirements. Bobby AAA Approval requires that all user checks pass. Even if your page does conform to these guidelines they appear in the report. Please review these 4 item(s):
1. If this document is part of a collection, provide metadata that identifies this document's location in the collection.
2. If this is a data table (not used for layout only), provide a caption. (10 instances)
Lines 14, 29, 36, 47, 54, 65, 82, 62, 93, 11
3. Use the ABBR and ACRONYM elements to denote and expand any abbreviations and acronyms that are present.
4. Consider adding keyboard shortcuts to frequently used links.
The following 5 item(s) are not triggered by any specific feature on your page, but are still important for accessibility and are required for Bobby AAA Approved status.
5. Is there distinguishing information at the beginning of headings, paragraphs, lists, etc.?
6. If there is a search feature, are there different types of searches for different skill levels and preferences?
7. Are there navigation bars for easy access to the navigation structure?
8. Do you allow users to customize their experience of the web page?
9. Is there a consistent style of presentation between pages?Copyright © 2002 Watchfire Corporation. All rights reserved. Use of this software is subject to the Bobby Software License Agreement.
URL tested: http://www.oocities.org/marcus_2300/index.htm, November 4, 2003 4:15:00 AM EST
Watchfire Bobby Core v4.0.1, WAI Content Accessibility Guidelines 1999/05/05, Support Level: AAA
Note: To ensure that the marked up report is readable, all stylesheets and scripts are removed. The page may not appear as expected.Source code
1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
2 <html>
3 <head>
4 <title>marcus </title>
5 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
6 <meta name="keywords" content="tweed promotions,mac,trainee,web designer,logo,tweed, promotions, kingscliff, tafe,student">
7 <meta name="description" content="this is a test site for a trainee web designer mac">
8 </head>
9
10 <body bgcolor="#FFFFee" leftmargin="0" topmargin="0">
11 <table border="0" cellspacing="0" cellpadding="0" width="760">
12 <tr>
13 <td height="945" valign="top">
14 <table width="100%" border="0" cellpadding="0">
15 <tr>
16 <td width="38%" height="164">
17 <div align="center"><img src="images/logonew.gif" width="250" height="180"></div>
18 </td>
19 <td width="62%" height="164">
20 <div align="center">
21 <p><font color="#0033FF" size="+7" face="Geneva, Arial, Helvetica, san-serif">Tweed
22 Promotions</font> </p>
23 <p><font color="#0033FF" size="5" face="Geneva, Arial, Helvetica, san-serif">Internet
24 web page services</font></p>
25 </div>
26 </td>
27 </tr>
28 </table>
29 <table width="100%" border="0" cellspacing="0" cellpadding="0">
30 <tr>
31 <td height="55">
32 <hr width="95%" align="center">
33 </td>
34 </tr>
35 </table>
36 <table width="100%" border="0" cellspacing="0" cellpadding="0" bgcolor="#FFFFee">
37 <tr>
38 <td height="87" width="59"> </td>
39 <td height="87" width="118" bgcolor="#FFFFee"><a href="index.htm"><img src="images/trIndexbutton.gif" width="100" height="85" border="0"></a></td>
40 <td height="87" width="112" bgcolor="#FFFFEA"><a href="pasttime.htm"><img src="images/trpasttime.gif" width="100" height="75" border="0"></a></td>
41 <td height="87" width="110"><a href="tafetimes.htm"><img src="images/trtafebutton.gif" width="100" height="85" border="0"></a></td>
42 <td height="87" width="110"><a href="sparetimes.htm"><img src="images/trsparebutton.gif" width="100" height="85" border="0"></a></td>
43 <td height="87" width="117"><a href="drivetime.htm"><img src="images/trdrivebutton.gif" width="100" height="85" border="0"></a></td>
44 <td height="87" width="140"><a href="links.htm"><img src="images/trlinkbutton.gif" width="100" height="85" border="0"></a></td>
45 </tr>
46 </table>
47 <table width="100%" border="0" cellspacing="0" cellpadding="0">
48 <tr>
49 <td height="52">
50 <hr width="95%" align="center">
51 </td>
52 </tr>
53 </table>
54 <table width="100%" border="1" cellspacing="0" cellpadding="0" bordercolor="#000000" height="75">
55 <tr>
56 <td bgcolor="#CCCCCC" height="69">
57 <div align="center"><font face="Geneva, Arial, Helvetica, san-serif" size="7" color="#FFFFFF">Moments
58 in Time</font></div>
59 </td>
60 </tr>
61 </table>
62 <table width="760" border="0" cellspacing="0" cellpadding="0">
63 <tr>
64 <td height="289">
65 <table border="0">
66 <tr>
67 <td width="574" height="251">
68 <blockquote>
69 <p> </p>
70 <p align="center"><font color="#0033FF" size="5">My name is
71 Mark. I am a web design student at Kingscliff TAFE NSWAustralia
72 </font></p>
73 <p align="center"><font color="#0033FF" size="5"><br>
74 Welcome to My Time</font></p>
75 </blockquote>
76 </td>
77 <td width="200" bordercolor="#000000" height="251">
78 <div align="center"><img src="images/marcusscenery.jpg" width="181" height="124"></div>
79 </td>
80 </tr>
81 </table>
82 <table width="760" border="0" cellspacing="0" cellpadding="0">
83 <tr>
84 <td height="76" valign="bottom">
85 <hr width="95%">
86 </td>
87 </tr>
88 </table>
89
90 </td>
91 </tr>
92 </table>
93 <table width="760" border="0" cellspacing="0" cellpadding="0">
94 <tr>
95 <td height="77">
96 <div align="center"> <font face="Geneva, Arial, Helvetica, San-serif" size="2"><a href="index.htm">Index</a>
97 <a href="pasttime.htm">Past Times</a> <a href="tafetimes.htm">TAFE
98 Times</a> <a href="sparetimes.htm">Spare Times</a> <a href="drivetime.htm">Drive
99 Times</a> <a href="links.htm">Links</a></font></div>
100 <div align="center"></div>
101 <div align="center"></div>
102 <div align="center"></div>
103 <div align="center"></div>
104 <div align="center"></div>
105 <div align="center"></div>
106 <div align="center"><font face="Geneva, Arial, Helvetica, San-serif" size="2"></font>
107 </div>
108 </td>
109 </tr>
110 </table>
111 <div align="center"><font size="2"> <font face="Geneva, Arial, Helvetica, San-serif"><Br>
112 Marcus Copyright © 2003</font></font></div>
113 </td>
114 </tr>
115 </table>
116 <p align="center"> </p>
117 </body>
118 </html>Comments
This index page fails to comply with several components of the accessibility standards of the W3C recommendations. To maintain an acceptable level of accessibility for disabled persons it is important that consideration be given to complying with the priority one levels of accessibility. It is also equally important to maintain a site that appropriately conveys its message to the majority of users in an informative and interesting manner. There is therefore a happy medium that needs to be reached in providing access to content.In this regard it would be most appropriate to concentrate on the level one priority level of access as determined by the W3c standards and accommodate the other levels of priority where there is no detraction to the content quality of the web site. Total compliance to all levels of W3C recommendations would initiate a very uninteresting site for the majority of users
There are several errors in the validity test that would be reasonably straight forward to rectify and with little consequence to the page content . The addition of alts and labels for all <IMG> elements is a simple process and would have considerable benefit for the accessibility of the page to disabled persons. Most of the level one validity errors would not be that difficult to rectify and would not detract form the site content and would be more accessible by disadvantaged individuals.
The W3C recommendations gives designers an insight into aspects of web design that one would not have ordinarily considered during the development stages of a web site.
The validator has also identified redundant code that can be eliminated . This is not an uncommon problem with some dedicated web page development programs. The page would benefit from cleaning up of this unnecessary code.
Index Past Times TAFE Times Spare Times Drive Times Links
Marcus Copyright © 2003