CSU Cal Poly Section 508 Manual Website Evaluation Worksheet

goldbashedΤεχνίτη Νοημοσύνη και Ρομποτική

15 Νοε 2013 (πριν από 3 χρόνια και 6 μήνες)

97 εμφανίσεις


Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
1

CSU Cal Poly

Section 508 Manual Website Evaluation
Worksheet

Site name:


URL
:


Requestor
:


Email address:


Reviewer:


Email address:


AccMonitor reports:


Date:


Time Spent (Review):



Use the companion
CSU Cal Poly Section 508 Manual Website Evaluati
on
Guide

when reviewing a site and for completing this worksheet which
is available at:
http://warc.calpoly.edu/accessibility/compliance_process_guide.html
.
The tools and
methods for the review are described in
the guide.
A th
orough review can not be done without the guide.

As of September 2007, all new construction or significant site redesign

must be done to best practices and include must
-
repair standards.
Web
site or Web
-
based application developers

will

use this worksheet to assist them in evaluating web pages for Section 508 compliance and
best practice guidelines.

For each checkpoint listed below, indicate whether the
pages in the website pass, fail, or are

not applic
ab
le.
Use the Comments column to
record your observations of how each checkpoint passes, fails, or is not applicable.

Developers will be asked to provide this completed worksheet when they submit a website for
an accessible compliance review
.

Send the
comp
leted worksheet to
accessibility@calpoly.edu



Pass
-
Fail
-
N/A

Comments

Cal Poly Minimum Requirements



See
http://warc.calpoly.edu/univers
ityid/elements.html



1.

Header: Cal Poly logo in upper
left

corner and links to Cal Poly
Home Page.
Nothing is to be placed above or to the left of the
Cal Poly logo. alt="Cal Poly" title="Go to Cal Poly Home".



2.

Footer:
Place on a separate line, links to

"
Cal Poly Home
"
(http://www.calpoly.edu/) and "
Cal Poly Find It
"
(http://www.calpoly.edu/cpfindit.html).



3.

Page titles:
The words "Cal Poly" should be used in al
l HTML title
coding. Recommend title tag look like the following: "page title
-

department name
-

Cal Poly".



Syntax validation



1.

Is the page valid HTML? (fix if "no") Best practice: XHTML 1.0
Strict

or Transitional
.



2.

Best practice: Do not use tables

for layout..




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
2


Pass
-
Fail
-
N/A

Comments

3.

Does the page use valid CSS? (fix if "no") Best practice: CSS
should be entirely separate from HTML code.



4.

Does site contain duplicate pages with same content? (fix if
“yes”)



5.

Are unique page titles used for each page? (fix if “no”)



Semantic validation



1.

Must repair: Does the text of each link describe where the link
goes? (fix if "no")



2.

Must repair: Do any links with the same text point to different
places such as “click here”? (fix if "yes")



3.

Do links open a new browser wind
ow? (fix if “yes”) Best
practice: Add text to end of link. Example: “Biographical
sketch (link opens new window).”



4.

Do links open a pop
-
up window? (fix if “yes”)



5.

Are e
-
document types included as part of the link description
text (e.g.
registration f
orm (PDF)
)? (fix if “no”)



6.

Best practice: Is linked text within the body content clearly
distinguishable from non
-
linked text content (e.g. are links
underlined or do they provide hover feedback) (fix if “no”)



Checkpoint A, text equivalents

A text equ
ivalent for every non
-
text element shall be provided
(e.g., via "alt", "longdesc", or in element content).



1.

Must repair: Do images that convey content have
equivalent

alt
-
text? (fix if "no")



2.

Best practice: include
title

as well as
alt

attribute (they
don't
have to be identical).



3.

Must repair: Do purely decorative images have empty alt
-
text
(alt="")? (fix if "no")



4.

Does alternate text make sense in the context of the page as
spoken? (fix if "no")



5.

Do images that convey complex content have long
desc
attributes or equivalent text content elsewhere on the page?
(fix if "no") May have to be evaluated by a domain expert.



6.

Must repair: Does text content contained in images disappear
when images are not available? (fix if "yes")




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
3


Pass
-
Fail
-
N/A

Comments

7.

Must repair: Doe
s image map area alt
-
text describe the link
destination correctly? (fix if "no") Best practice: include
title

as
well as
alt

attribute (they don't have to be identical).



Checkpoint B, multimedia equivalents

Equivalent alternatives for any multimedia pr
esentation shall be
synchronized with the presentation.



1.

Is synchronized captioning provided for all spoken content?
(fix if "no"; may require a temporary alternate means of
delivering the content)



2.

Additional review items may be provided later.



C
heckpoint C, color

Web pages shall be designed so that all information conveyed with
color is also available without color, for example from context or
markup.



1.

Must repair: Is information conveyed by color also conveyed
by context, markup, graphic codin
g, or other means? (fix if
"no")



2.

Does the contrast between foreground and background colors
have a luminosity contrast ratio of least 5:1 for both normal
vision and color blindness? (fix if "no")



3.

Is a correct contrast ratio maintained when images
are not
available? (fix if "no")



Checkpoint D, styles

Documents shall be organized so they are readable without
requiring an associated style sheet.



1.

Must repair: Are styles used to simulate headings or other
semantic markup? (fix if "yes")



2.

With
all styles disabled, is color and font information rendered
in the browser's default style? (fix if "no")



3.

With all styles disabled, are headings, paragraphs, and lists
obvious and sensible? (fix if "no")



4.

With all styles disabled, does the order of
the page content
make sense as read? (fix if "no")




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
4


Pass
-
Fail
-
N/A

Comments

5.

Best practice: With all styles disabled, is most text (other than
logos and banners) rendered in text rather than images? (fix if
"no")



6.

Best practice: With all styles disabled, does any content
ap
pear that was invisible before? (fix if "yes")



7.

Best practice: are headings properly nested by level? (fix if
"no")



8.

Best practice: do headings accurately reflect the structure of
the document content? (fix if "no")



Checkpoint E, server
-
side image

maps

Redundant text links shall be provided for each active region of a
server
-
side image map.



1.

Does this page use server
-
side image maps? (fix if "yes")
Comment: there is no reason to use these today, despite the
exception allowed in checkpoint f.



Checkpoint F, client
-
side image maps

Client
-
side image maps shall be provided instead of server
-
side
image maps except where the regions cannot be defined with an
available geometric shape.



1.

See Checkpoint A for alt
-
text requirement.



2.

Best practice: I
s there a non
-
graphic alternative to the image
map, for example a drop
-
down selection control? (fix if "no")



Checkpoint G, simple tables

Row and column headers shall be identified for data tables.



1.

Must repair: For tables containing data, are <th> el
ements
used in the first row (and/or first column, if applicable)? (fix if
"no")



2.

Must repair: Do <th> elements contain the
scope

(="col" or
="row") attribute? (fix if "no")



3.

Must repair: For tables that are used for layout only, are <th>
elements or

the
summary

attribute used at all? (fix if "yes")



4.

Best practice: don't use tables for layout only.



5.

Best practice: For tables containing data, is the
summary

attribute used to explain the meaning of the table if it is not
otherwise evident from con
text? (fix if "no")




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
5


Pass
-
Fail
-
N/A

Comments

6.

Best practice: For tables containing data, is the <caption>
element used to describe the data when the context within the
page doesn’t? (fix if “no”)



Checkpoint H, complex tables

Markup shall be used to associate data cells and
header cells for
data tables that have two or more logical levels of row or column
headers.



1.

Are the Checkpoint G items done correctly? (fix if "no")



2.

Must repair: Does each <th> element contain the
id

attribute?
(fix if "no")



3.

Must repair: Does ea
ch <td> element contain a
headers

attribute that associates it with its column and row headers?
(fix if "no")



4.

Are <thead> and <tbody> elements used to clarify the table
structure? (fix if "no")



5.

Best practice: find a simpler way to present the data
to all
readers.



Checkpoint I, frames

Frames shall be titled with text that facilitates frame identification
and navigation.



1.

Must repair: Does each <frame> element have a meaningful
title

attribute? (fix if "no")



2.

Must repair: Does the page have e
quivalent content in a
<noframes> element for user agents that do not support
frames? (fix if "no")



3.

Best practice: don't use frames.



Checkpoint J, flicker

Pages shall be designed to avoid causing the screen to flicker with
a frequency greater than
2 Hz and lower than 55 Hz.



1.

Must repair: Does any page element flicker at an unhealthy
rate? (fix if "yes")



2.

Best practice: Does any element on the page move at all? (fix
if "yes" unless the moving element conveys information
relevant to the page cont
ent, and then refer to checkpoints B,
L, and M)




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
6


Pass
-
Fail
-
N/A

Comments

Checkpoint K, text only

A text
-
only page, with equivalent information or functionality,
shall be provided to make a web site comply with the provisions of
this part, when compliance cannot be accomplished

in any other
way. The content of the text
-
only page shall be updated whenever
the primary page changes.



1.

Does this page have a text
-
only version? (fix if "yes" by
making the page compliant with the rest of the checkpoints)
Comment: there is no reason to
day to have separate versions,
despite the grudging exception contained in this checkpoint.
For quick repair, a text version
must

contain the same
information as the basic page.



Checkpoint L, scripts

When pages utilize scripting languages to display co
ntent, or to
create interface elements, the information provided by the script
shall be identified with functional text that can be read by
assistive technology.



1.

Must repair: Are HTML event handlers accessible to both
mouse and keyboard users? (fix if "
no" unless mouseovers are
purely decorative; e.g., changing color of a graphic link.) Best
practice: use CSS
:hover

in place of JavaScript and graphic
links.



2.

Must repair: Is all content and functionality generated by
scripts (including
href="javascript
:..."
) also provided to user
agents that do not support scripts? (fix if "no" unless
"functionality" is purely decorative). Best practice: Don't use
href="javascript:..."

for anything; it's not a URI!



3.

Best practice: Is modern "unobtrusive" JavaScript u
sed in
place of older coding techniques? (fix if "no") Comment: this
coding technique does
not

require the <noscript> element.



Checkpoint M, applets and plug
-
ins

When a web page requires that an applet, plug
-
in or other
application be present on the cl
ient system to interpret page
content, the page must provide a link to a plug
-
in or applet that
complies with §1194.21(a) through (l).



1.

Are links provided to any special readers or plug
-
ins that are
required to interpret page content? (fix if "no")




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
7


Pass
-
Fail
-
N/A

Comments

2.

D
o special readers or plug
-
ins comply with the requirements of
Section 508 paragraphs 1194.21(a)
-
(l), the Subpart B
technical standards for software? (fix if "no"; requires separate
evaluation)



3.

Are documents that are presented in commonly
-
supported
form
ats such as PDF and Word constructed so as to be
accessible? (fix if "no"; requires separate evaluation)



Checkpoint N, forms

When electronic forms are designed to be completed on
-
line, the
form shall allow people using assistive technology to access th
e
information, field elements, and functionality required for
completion and submission of the form, including all directions
and cues.



1.

Must repair: Does each <input> element or control (except
buttons) have an associated and visible <label> element or
title

attribute? (fix if "no")



2.

Must repair: Are all cues for filling out the form (mandatory
fields, help boxes, error messages, and so on) available to
users of assistive technology? (fix if "no")



3.

Is the tab order to reach the form and the tab ord
er between
form elements consistent with the normal order of entering
form data? (fix if "no")



4.

Are logically
-
related groups of form elements identified with
appropriate <fieldset>, <legend>, or <caption> elements?
(fix if "no")



5.

Is placeholder text,

if used, redundant or distracting to users
of assistive technology? (fix if "yes") Comment: most properly
labeled form elements no longer benefit from placeholder text.



Checkpoint O, skip links

A method shall be provided that permits users to skip rep
etitive
navigation links.



1.

Must repair: Can a user navigate over groups of links, between
multiple groups of links, and between sections of the page
content by means of section headings or visible and audible
local links? (fix if "no") Best practice: hea
dings are most
helpful for users of modern assistive technology; "skip" links
and headings can be used in combination where appropriate.




Filename:
C:
\
Program Files
\
neevia.com
\
docConverterPro
\
temp
\
NVDC
\
F450F6B6
-
9D59
-
4976
-
B560
-
2C45F1E73AE7
\
goldbashed_e956632b
-
7443
-
4f50
-
ac7f
-
de803fe0d5f8.doc

CP_manual_eval_worksheet.doc,

rev: 02/24/09

Page
8


Pass
-
Fail
-
N/A

Comments

Checkpoint P, timed response

When a timed response is required, the user shall be alerted and
given sufficient time

to indicate more time is required.



1.

Must repair: If a timed response is required, is the user
alerted and given sufficient time to indicate that more time is
required? (fix if "no"; see also next item)



2.

In a timed environment such as an examination,
are users
who need more time accommodated in an appropriate
alternative way? (fix if "no"; may be organizational rather than
technical solution)



User validation



1.

Does all text (except in banner graphics) enlarge or shrink in
response to changes in br
owser text size settings? (fix if "no")



2.

Does text enlarged with browser settings wrap within
columns? (fix if "no")



3.

Do columns, page elements, or text lines overlap each other
when text is enlarged with browser settings? (fix if "yes")



4.

Do actua
l low vision users encounter any remaining barriers?
(fix if "yes") Comment: this and the following two items may
be simulated, although actual users are best.



5.

Do actual blind users encounter any remaining barriers? (fix if
"yes")



6.

Do actual users w
ith other disabilities encounter any remaining
barriers? (fix if "yes")