Per my action item, following are my attempts at completing my tasks 1 and 2 in preparation for the Glossary discussion. Task #2 is listed first, because it is shorter. Comments welcome Thanks and best wishes Tim Boland NIST NOTE: For each of the terms mentioned in Task 1, perhaps we can go down the list, and put them into one of the categories mentioned after the Task #1 designation following? Some of these terms may already be defined in ATAG2.0, but I just wanted to list the terms for completeness. Task #2: Proposed Draft Framing Text for Glossary Appendix: This appendix contains definitions for all of the significant/important/unfamiliar terms used in the normative parts of this specification, including terms used in the (link to conformance) section. Except where indicated by "[ ]", the source of these definitions is the AUWG, developed with a goal of clarity, detail, understanding, and completeness. Every attempt has been made to find appropriate definitions for these terms from other sources before such development by the AUWG. All these terms are linked at least from their first usage in the specification. Terms that have designations of "[ ]" beside them are taken ?verbatim? from the indicated "outside" specifications/versions. Where a definition so referenced is not suitable/adequate for the ATAG2.0, it may be modified as described herein. Please consult http://www.w3.org/TR/qaframe-spec/ for more information on the role of definitions in specification quality. Task #1: Terms in Normative Parts possibly either needing definition (if not already defined?) or additional explanation/examples, or further thought in relation to objective testability/conformance (consult http://www.w3.org/TR/qaframe-spec/#define-terms-inline-gp for more information on defining terms in specifications - In what follows, I list the section first, and then the terms possibly needing additional clarification): Global NOte: the "[UAAG 1.0]" designations should be linked to appropriate version/spec.. In "Definition of authoring tool" section: application Web content (link to definition?) embedded/stand-alone? (Web content) technologies In Notes on the Definition following, for #1, add "Web" in front of "content"?, and "live content authoring tool" may need definition For #2, add "authoring" in front of "tool"? Is the "Components of Web Accessibility" section normative or informative (not clear)? If normative, then after "Two Parts", "accessible authoring tools" should be underlined (not just authoring tools)? Maybe a definiton (or expansion) of "disabilities"? In "Part A", consider definitions for "authoring tool user interface", and "accessible"? Provide a link for "WCAG2.0"? Maybe "augmented display and control" definition? Also "perceive", "operate", "user interface components"? In "Part B" section, add "authoring" in front of "tool"? For #2, consider definitions for "actions" and "features"? FOr Note following #2, consider definition for "user interface accessibility"? Also definitions for "accessible authoring practices" and "functions related to accessibility"? "Success Criteria" section before "Levels of Conformance": insert "middle" after "AA"? RElationship to the WCAG: Do we want to still list "WCAG1.0" after "e.g.", since WCAG2.0 is now a rec? Do we want to provide a link to WCAG2.0 when used first? Web content technologies? accessible authoring practices? WCAG-conforming? Web content? ATAG2.0 Guidelines -> Part A -> Applicability NOtes: "chrome"? insert "Web" before "content" (two places in paragraph)? user interface (or do we want to add "authoring tool" before "user interface"? accessibility authoring tool user interface Guideline A.1.2 - > A.1.2.1 standards platform conventions Guideline 2.1 (should be A.2.1?): assistive technologies 2.1.2: user interface components name, role, state, value, description? 2.1.3: spell out "DOM" user agent 2.1.4: available programmatically (value of a?) piece of content degree of write access? 2.1.5: foreground color background color Applicability Note: user agent interface Principle A-2: Editing views? Perceivable? A.2.1.1: Alternative equivalents (or equivalent alternatives - need to decide which one and stick to it for consistency) Guideline A.2.2: Programmatic access A.2.2.1: functional purpose A.2.2.2: WYSIWYG (need to spell out?) A.2.3.1: display characteristics/preferences Principle A-3: perceivable? Guideline A-3-1: authoring features? keyboard access? A.3.1.1: key-plus-modifier-key operating environment A.3.1.2: keyboard trap keyboard focus standard sequential keyboard command direct keyboard command focusable element Applicability NOtes: keyboard navigation functions Guideline A.3.2: time-dependent-interaction A.3.2.1: server A.3.2.2: simple action A.3.2.3: moving target selectable component GUideline A.3.3 flashing seizures A.3.3.1: static view time-based content fixed state Guideline A.3.4: navigation editing content structure A.3.4.1: element, contents, sub-elements (is distinction always clear?) A.3.4.2: structured element set editing focus identical element A.3.4.3: heading/level? A.3.4.4: Doesn't above, below, preceding, etc. depend on navigation order? A.3.5.1: text search insert "Web" before "content"? textual information/text content editable? backwards, forwards, case sensistive/insensitive may be unclear? What does it mean to "perform search results"? instruction level? markup tags (difference from elements?) Guideline A.3.6: preference settings A.3.6.1: keyboard operability settings A.3.6.2: multiple sets of preferences? accessibility option-setting "wizard" A.3.7.1: help system Guideline A.4.1: users (different from authors?) A.4.1.1: irreversible A.4.1.2: setting modification A.4.1.3: (Web) content "undo" A.4.1.4: reversible authoring function Applicability Notes: "undo" function (or undo function - need to make consistent) undo history Guideline A.4.2: user interface accessibility feature A.4.2.1: documented? A.4.2.2: accessibility feature and tutorial? Part B: Applicability NOtes: #1-authoring session? #2-accessibility problems third-party feed automatically-generated CMS (spell out?) #3-accessible authoring practices technologies markup authoring tool URIs (spell out?) alternative text #4 - authoring systems software tools 3rd party (vs. third-party previous - consistency?) software accessibility checking and repair program Guideline B.1.1: Web content technology add "Web" before "content" B.1.1.1: automatically selected "can" conform (say "must conform" or just "conform"?) for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? B.1.1.2 (and 1.1.4 and 1.1.6): Web content technology options prominence accessible technology task B.1.1.5: "technology" instead of "technologies" "can" conform (say "must conform" or just "conform"?) B.1.2.1: target (or target technology?) transformation conversion recognized accessibility information B.1.2.2: add "Web" before "content"? preserved resulting conten B.1.2.3: automatic deletion GUideline B.1.3: automatically-generated content (in see also): template pre-authored content B.1.3.1, 1.3.2, 1.3.3: "Web" content or "content"? (in applicability notes)" automated behavior actions generation Principle B.2: (global change - add "Web" before "content"?) Notes: authoring tool processes what is example of non-human author? why do we add "human" here but nowhere else? authoring "choices" Guideline B.2.1: accessible "Web" content (in see also): repair features author guidance (typo - "Guidelin" should be "Guideline") B.2.1.1 (2.1.3 and 2.1.5 - misnumbered - should be B.2.1.2 and B.2.1.3): prompt(ed) information (difference from "Web" content) Guideline B.2.2: accessibility problems B.2.2.1: individual check for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? (tool does not modify a WCAG success criterion - awkward wording?) B.2.2.2: checking workflow (available to whom? the author? user of the authoring tool?) B.2.2.3: check author judgement potential accessibility problem relevant "Web" content (this text is confusing to me - "identified" used twice in different contexts?) B.2.2.4: decide (What?) B.2.2.5: individual check for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? (tool does not modify a WCAG success criterion - awkward wording?) B.2.2.6: accessibility problems authoring session B.2.2.7: (repair) assistance checking option? B.2.2.8: accessibility status metadata resource discovery end users (same as authors?) option? "Web" content? B.2.2.9: individual check for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? (tool does not modify a WCAG success criterion - awkward wording?) Applicability Notes: authoring experience authoring process accessibility problems Guideline B.2.3: accessibility problems B.2.3.1, 2.3.2, 2.3.3: identifiable repair assistance for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? Applicability Notes: authoring experience authoring process accessibility problems Guideline B.2.4.: (doesn't "manage" include both "edit" and "reuse" as subcategories?) equivalent alternative non-text object B.2.4.2: for a type of?? Is this needed? B.2.4.3: equivalent alternative object database null equivalent alternative pure decoration (CART - spell out acronym?) automatic analysis? B.2.4.4: author-assigned plain text (stores) directly vs. (stores) as (URIs - spell out acronym) (Note: what is an "unreliable source"?) Guideline B.2.5: accessible template pre-authored (Web?) content B.2.5.1: automatically (selects) for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? used? B.2.5.2: accessible template options template uses B.2.5.3: accessibility status accessible template options selection mechanism B.2.5.1: automatically (selects) for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? used? B.2.5.5: new (template) B.2.5.6: repository of templates recorded (accessibility status) B.2.5.7: selection mechanism pre-authored content B.2.5.8: repository of pre-authored content (Web?) content objects recorded (accessibility status) B.2.5.9: automatically (selects) for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? used? (Note is confusing to me - acessibility of template vs. accessibility of (Web) content produced? - what is "final" technology?) Principle B.3: accessibility solution promoted integrated Guideline B.3.1: accessible authoring actions prominence B.3.1.1 terms are underlined whereas B.3.1.2 similar terms are not? Guideline B.3.2: seqential authoring processes accessible authoring practices B.3.2.1: "Functionality" instead of "function"? relevant to (how measured?) "complete" the "function" - awkward? B.3.2.2: sequence relevant to (how measured?) "complete" the "sequence" Guideline B.3.3: features accessible (Web) content available to whom? author? B.3.3.1: active B.3.3.2: deactivate/reactivate a feature? B.3.3.1 terms are underlined whereas similar terms in B.3.3.2 are not.. B.3.3.3: (Web) content accessibility problem B.3.3.4: comparable features Guideline B.3.4: features documented B.3.4.1: instructions B.3.4.2: accessible authoring process Guideline B.3.5: authoring practices documentation accessible B.3.5.1: for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? (WYSIWYG - spell out acronym) B.3.5.2: for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? Conformance: version published document for "WCAG" say "WCAG2.0" or provide link to latest WCAG spec? URI - spell out acronym (Note - for the last bullet, do we still want people to point to ATAG1.0?) what does "available" mean in this context? component Web-based user interface functionality non-user agent platform