QA Checklist

Items requiring manual attention or WG consensus

• Editor credits
• Participant credits
• Documents are valid XHTML Transitional [Strict?]
• Spelling / typos
• Consistent use of approved spellings when multiple are possible

Automated

• Ensure TOC is current
• Generation of indices when sections index sub-sections
• Headings at proper levels
• Section number for headings is correct
• RDF a correct representation of the Role taxonomy
• State module correctly defines the states defined in the spec
• Show role attributes that inherit from ancestor roles
  • Supported states
  • "child presentational"
  • "required accessible name"
• Role, state, and property fields that do not have defined information are elided from the visual presentation
• Show child roles of the roles to which a state applies
• Lists sorted in meaningful way (usually alphabetically) to avoid random appearance

Semi-automated

• Document publication date is set to current date when automated tools run, has to be updated if another date is desired
• When inheritance of roles change, the states they support may change. The tools will indicate when there is a change of supported states by comparison to an earlier version of the spec. It is a manual decision whether the changes are desired or if the set of supported states needs to be updated.
• Ensure that supported state not defined if the state is also inherited
• Check that the role spec and the UML Class Diagram express the same thing
• Roles list only supported states that are defined
• States indicate applicability only to roles that are defined
• Roles and states cross reference each other: roles indicate supported states, and those states indicate applicability to those roles; discrepencies called out for manual attention