Authoring Tools Proposal 1 March 5, 2007

Editing Authoring Tools Proposal 1 March 5, 2007

• Reference: Allen's post on March 5, 2007
• When software allows creation of, or modification to information stored in a specific set of encoding formats, all accessibility attributes contained in those formats must be available to the author, and programmatic assessment and remediation of those attributes must be provided to expedite such creation or modification.
  • Note: Distinction may be needed for software (or web-based software), which is not operated by humans, but I'm not fully prepared with that language at this date.

Summary of discussion on Authoring Tools Proposal 1

• See Gregg's post on March 5, 2007.
  • Recommendation for authoring tool to add "When software allows people to create or modify...." to limit this to human authoring.
• When testing and discussing failures, I am told that the "content management system is at fault and there is no way or no known way to fix this". So, here we have a case of content being middled by software which should be tweakable?
• There is the case where server systems have tools which dynamically generate out as a result of user input or other information such as changing counts or conditions?
• Content management systems are often template or "othermark-up language" based, but in my opinion fall in to the authoring tool category. Maybe some specific words can be used to include contentmanagement systems, in the authoring tools language. Maybe just an "including content management" would due?
• Discussed at the March 14, 2007 meetings