1194.22 Web based intranet and Internet information and applications

Criteria

WCAG 1.0 Checkpoint

Supporting Features

Remarks and explanations

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

Supporting:

Providing methods to set text equivalent with non-text element

Providing setAlt() and setLongdesc() to the non-test ZK components to allow application developers providing text equivalent information.

Sample

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

Supporting:

Providing methods to link the text equivalent, such as a transcript to the multimedia components

Using the toolbarbutton component with the transcript url to link the text equivalent.

Sample

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

Supporting:

Using ZK label to indicate the information which is conveyed with color

Use ZK label component to indicate information which is conveyed with color

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

Supporting:

ZK components style rules are set up in separate CSS files.

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

Supporting:

Using setServerSideMap(url) to indicate the location of server side map file

Sample

Note:
Read the relative criteria (f)

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

Supporting:

Providing the methods and relevant component to set image map with image

Sample

(g) Row and column headers shall be identified for data tables.

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

Supporting:

Generate scope attribute for html table based components.

Sample

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

Supporting:

Providing methods to set the frame title in iframe component

Providing a setTitle() method to allow application developers to set title for iframe

Sample

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

Supporting:

Dynamical change content by following this criteria.

Note:

Application developer should be aware that flashing or flickering elements, such as animated gifs , java-applet, flash clips should be followed this criteria.

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

Supporting:

Providing methods to set the url of text-only page for each window components

(1). Using the toolbarbutton component with text-only page url to provide the quivalent information and functionality

(2). Providing a <NOSCRIPT> option for all scripts. The message <NOSCRIPT> option can be customized by config the zk.xml. For furthur information, please refer to zk developer reference Appendix B, the device-config element.

Sample

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

Supporting: see l-1 through l-3

Since the ZK is heavily depended on dynamic content, there is a specific section for criteria(l).

(l-1) Inspect web content source to help identify presence of functional text for scripts. Some hints on how to determine what part of a script is necessary information vs. decoration:

Using WAI-ARIA roadmap to create a bridge to fix the interoperability problem.

See ZK ARIA ( Accessible Rich Internet Applications) Project Guideline

WAI-ARIA roadmap identifies some technology gaps to achieve the desired access. Some of the technologies required to fill these gaps are under development in other W3C Groups, such as the XHTML Role Attribute Module [XHTML-ROLE] being developed by the HTML Activity. The remaining gaps are planned to be filled by two companion specifications: Roles for Accessible Rich Internet Applications [ARIA-ROLE] and States and Properties Module for Accessible Rich Internet Applications [ARIA-STATE

(l-2) Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported.

Supporting:

Providing methods to set the url of text-only page for each window components

See criteria (k)

(l-3) Apply AT to make sure functional text is available. Note the use of AT as a measurement method is limited by the adequacy of algorithms and heuristic methods of the specific AT tool used. It can be used to identify problems with specific AT-E&IT interoperability but it cannot predict results with other AT or with other versions of the same AT, OS, application or accessibility architecture. AT should include the full range e.g. screen readers, screen magnifiers, alternate input devices, etc.

Using WAI-ARIA roadmap to create a bridge to fix the interoperability problem.

See ZK ARIA ( Accessible Rich Internet Applications) Project Guideline

WAI-ARIA roadmap identifies some technology gaps to achieve the desired access. Some of the technologies required to fill these gaps are under development in other W3C Groups, such as the XHTML Role Attribute Module [XHTML-ROLE] being developed by the HTML Activity. The remaining gaps are planned to be filled by two companion specifications: Roles for Accessible Rich Internet Applications [ARIA-ROLE] and States and Properties Module for Accessible Rich Internet Applications [ARIA-STATE

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

Supporting:

Providing methods to set text equivalent with non-text element

Providing setAlt() and setLongdesc() to the non-test ZK components to allow application developers providing text equivalent information.

Sample

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

Supporting:

Providing methods to set label information with its relevant input html elements.

Providing SetWaiLabel() method to allow application developers set the relative label to various inputs

Sample

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

Supporting:

Providing method to set the “ Skip Navigation Links” mark.

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

Make sure the time interval is reasonable.