Criteria
|
Supporting Features
|
Remarks & Explanations
|
| (a) A text equivalent for every non-text element shall be provided (e.g., via “alt”, “longdesc”, or in element content). |
Supports |
“alt” text for graphics has been provided by EOS.Web OPAC Discovery. |
| (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation. |
n/a |
Multimedia files are not provided by EOS.Web OPAC Discovery. |
| (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup |
Supports |
Color is not used to convey important information in EOS.Web OPAC Discovery. |
| (d) Documents shall be organized so they are readable without requiring an associated style sheet. |
Supports |
Documents are readable without style sheets in EOS.Web OPAC Discovery. |
| (e) Redundant text links shall be provided for each active region of a server-side image map. |
n/a |
EOS.Web OPAC Discovery does not use server-side image maps. |
| (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. |
n/a |
EOS.Web OPAC Discovery does not use client-side image maps. |
| (g) Row and column headers shall be identified for data tables. |
Supports |
Row and column headers are identified for data tables in EOS.Web OPAC Discovery. |
| (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. |
Supports |
Markup to associate data cells and header cells for data tables are used in EOS.Web OPAC Discovery. |
| (i) Frames shall be titled with text that facilitates frame identification and navigation. |
Supports |
Frames are properly titled. |
| (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz. |
n/a |
There are no animations on EOS.Web OPAC Discovery, all of the pages are static. |
| (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 text only page shall be updated whenever the primary page changes. |
n/a |
At this time, all features in EOS.Web OPAC Discovery are usable with assistive technology, therefore a text-only version is not required. |
| (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. |
Supports |
Information provided by script is identified with functional text in EOS.Web OPAC Discovery. |
| (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). |
n/a |
EOS.Web OPAC Discovery does not require applets or plug-ins. |
| (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. |
Supports |
Electronic forms are designed properly in EOS.Web OPAC Discovery. |
| (o) A method shall be provided that permits users to skip repetitive navigation links. |
Supports |
EOS.Web OPAC Discovery subnavigation allows all menu items to be accessed without repetitive clicks. |
| (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required. |
n/a |
There are no timed responses required in EOS.Web OPAC Discovery. |
