Page Comparison

(a)

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

Yes

Sakai provides text equivalents for images.

(b)

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

N/A

Sakai does not contain multimedia elements.

(c)

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

Yes

No

Sakai does not rely on color alone to differentiate content.

(d)

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

Yes

No

Sakai is readable without style sheets.

(e)

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

N/A

Sakai does not include 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

Sakai does not include server-side image maps.

(g)

Row and column headers shall be identified for data tables.

Yes

Data tables contain row and column headers in Sakai. Exception: Schedule tool does not associate date with day of week.

(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.

No

Schedule Tool: 12 month calendar does not associate dates with day of week and month.

( i )

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

Yes

Sakai provides title and name attributes for frames when they are present.

(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

Sakai does not include flickering images.

(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

It is not necessary for Sakai to produce a text-only version, so long as JavaScript is enabled.

(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.

No

JavaScript must be enabled for Sakai to function.

(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

Sakai does not require external plug-ins to operate.

( 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.

Yes

No

Sakai does not contain interactive forms. Form labels are associated with input fields.

(o)

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

Yes

Sakai provides skip links to worksites, tools and page content.

(p)

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

No

Sakai times out after twenty minutes of inactivity but does not notify users beforehand.