|
TimeLive and Section 508 |
|
Section 508 Requirement |
Remarks |
|
|
(a) A text equivalent for every non-text element shall be provided (e.g., via "alt",
"longdesc", or in element content). |
Supported |  |
|
(b) Equivalent alternatives for any multimedia presentation shall be synchronized
with the presentation. |
Not Applicable |
Not Applicable |
|
(c) Web pages shall be designed so that all information conveyed with color is also
available without color, for example from context or markup. |
Color is not used as the sole means to convey information in TimeLive |
|
|
(d) Documents shall be organized so they are readable without requiring an associated
style sheet. |
TimeLive complies with this requirement. |
|
|
(e) Redundant text links shall be provided for each active region of a server-side
image map. |
Server-side maps are not used in TimeLive |
Not Applicable |
|
(f) 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. |
Client-side image maps are not used in TimeLive |
Not Applicable |
|
(g) Row and column headers shall be identified for data tables. |
TimeLive uses HTML data tables to display data.
All tables have row and column headers
appropriately defined. |
|
|
(h) 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. |
Table cells are associated with appropriate headers in the data tables used by TimeLive. |
|
|
(i) Frames shall be titled with text that facilitates frame identification and navigation. |
TimeLive does not use frames |
Not Applicable |
|
(j) Pages shall be designed to avoid causing the screen to flicker with a frequency
greater than 2 Hz and lower than 55 Hz. |
TimeLive complies with this requirement |
|
|
(k) 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 textonly page shall be updated
whenever the primary page changes. |
TimeLive pages meet the standards specified above, so text only equivalent pages
are not provided |
|
|
(l) When pages utilize scripting languages to display content, or to create interface
elements, the information provided by the script shall be identified with functional
text that can be read by assistive technology. |
Scripting languages are not used in TimeLive to create interface elements or content
that would require functional text. |
Not Applicable |
|
(m) When a web page requires that an applet, plug-in or other application be present
on the client 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). |
TimeLive does not make use of applets or plug-ins for functionality |
Not Applicable |
|
(n) When electronic forms are designed to be completed on-line, the form shall allow
people using assistive technology to access the information, field elements, and
functionality required for completion and submission of the form, including all
directions and cues. |
HTML forms in TimeLive use standard HTML controls and are accessible. Tab order
thorough a form is logical. |
|
|
o) A method shall be provided that permits users to skip repetitive navigation links. |
The ACCESSKEY HTML attribute can be used to provide shortcut keys in HTML pages.
However, not every control in TimeLive has a shortcut key currently assigned. |
Does not Support |
|
(p) When a timed response is required, the user shall be alerted and given sufficient
time to indicate more time is required. |
The only place where a timed response is used in TimeLive is a session timeout.
The administrator can set the session timeout (default is 20 mins) on the server.
This setting applies to all users. |
|