Against the 22 October 2001 version of XAG.

Checkpoint pass,fail,n/a comments
xslt xsl
1.1 Provide a mechanism to explicitly associate alternatives for content or content fragments. n/a provides way to preserve these relationships in transformation
1.2 Define flexible associations, where a given kind of relationship can link to or from objects of varying types without constraint. n/a
1.3 Reuse existing accessibility modules to indicate alternative-equivalent associations. n/a
2.1 Ensure all semantics are captured in markup in a repurposeable form. n/a
2.x Specific checkpoint for Final-form dialects. will apply to xsl:fo
2.2 Separate presentation properties using stylesheet technology/styling mechanisms. n/a
2.3 Use the standard XML linking and pointing mechanisms (XLink and XPointer). pass
2.4 Define element types that allow classification and grouping (header, section, list, etc). n/a
2.5 Provide for a full containment model with chunks of reasonable size. n/a
2.6 Define element types that identify important text content. n/a
2.7 Provide a mechanism for identifying summary / abstract / title. n/a
2.8 Don't overload the semantics of elements. pass
2.9 Reuse accessible modules from schema as originally specified / intended. n/a
2.10 Allow association of metadata with distinct elements and groups of elements. ??
3.2 Define navigable structures that allow discrete, sequential, structured, and search navigation functionalities. n/a
3.3 Use CSS or XSLT to describe a basic outline view. ??
3.4 Use a device-independent interaction and events model / module. n/a
3.5 Allow for user control of interaction timing - rate of change, external events triggering document changes, etc. n/a
4.1 Ensure human-readable documentation conforms to WCAG double A. didn't evaluate
4.2 Provide a machine-understandable means/mechanism to get from a document instance to the schema. not sure
4.3 Provide explicit human readable definitions for markup semantics. not sure
4.4 Use schema (in preference to DTD) to provide explicit documentation/annotation of element/attribute/etc semantics. not sure
4.5 Provide semantic relationships to other schema where appropriate and possible. not sure
4.6 Document accessibility features of the application. not sure
4.7 Include accessibility requirements in conformance requirements n/a??
4.8 Document techniques for WCAG, ATAG, and UAAG with respect to the XML application. not sure
4.9 Do not assume that element or attribute names provide any information about element semantics. pass
4.10 Document navigable structures. Describe how discrete, sequential, structured, and search navigation mechanisms should work n/a

$Date: 2001/10/29 20:15:28 $ Wendy Chisholm