WAI AU -- 05 Jan 2009

<jeanne> zakim who is here?

http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/0083.html

Actual link to attachment: http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/att-0083/ATAG_Glossary_Review.doc

Glossary review

<AndrewR> JR: first term abbreviation. adding "adapted from" WCAG 2.0 in the brackets

<AndrewR> JR: agreed at F2F in Redmond to not follow WCAG 2.0s style exactly

http://www.w3.org/TR/WCAG20/#glossary

<jeanne> http://www.w3.org/WAI/AU/2008/WD-ATAG20-20081202/#glossary

<AndrewR> JS: "enhance" seems to be indicate an "improvement". "engineer" may be a better word

<AndrewR> JS: "provide" would be suitable

A programmatic interface that is specifically engineered to provide communication between mainstream applications and assistive technologies (e.g., UIA, MSAA and IAccessible2 for Windows applications, AXAPI for MacOSX applications, Gnome Accessibility Toolkit API for Gnome applications, Java Access for Java applications, etc.). On some platforms it may be conventional to enhance communication furt

her by implementing a document object.

<jeanne> ACTION: JS to update the document with new text for Platform Accessibility Architecture [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action01]

<trackbot> Created ACTION-68 - Update the document with new text for Platform Accessibility Architecture [on Jeanne Spellman - due 2009-01-12].

<AndrewR> JR: could remove "severity" from the sentence

accessibility problem

ATAG 2.0 refers to two types of accessibility problems:

1. authoring tool user interface accessibility problem: An aspect of an authoring tool user interface that does not meet one of the success criteria in Part A.

2. Web content accessibility problem: An aspect of Web content that does not meet a WCAG success criteriaon.

1. authoring tool user interface accessibility problem: An aspect of an authoring tool user interface that does not meet a success criterion in Part A.

accessibility problem

ATAG 2.0 refers to two types of accessibility problems:

1. authoring tool user interface accessibility problem: An aspect of an authoring tool user interface that does not meet a success criterion in Part A.

2. Web content accessibility problem: An aspect of Web content that does not meet a WCAG success criterion.

<jeanne> ACTION: JS to update the document with new text for "accessibility problem" [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action02]

<trackbot> Created ACTION-69 - Update the document with new text for \"accessibility problem\" [on Jeanne Spellman - due 2009-01-12].

accessibility information

Any information that is necessary for undertaking an accessible authoring practice (e.g., text descriptions of images, role and state information, relationships within complex tables).

<jeanne> +1

<scribe> ACTION: JR - take another try at: "accessibility information" ... make it more direct [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action03]

<trackbot> Created ACTION-70 - - take another try at: \"accessibility information\" ... make it more direct [on Jan Richards - due 2009-01-12].

accessible content support features

Any features of an authoring tool that directly support authors in increasing the accessibility of the content being edited (i.e., in meeting any of the success criteria in Principle B.2).

assistive technology [adapted from WCAG 2.0]

Software and/or hardware that provides functionality to meet the requirements of users with disabilities that goes beyond direct accessibility features offered by mainstream applications. Assistive technology functionality includes alternative presentations (e.g., as synthesized speech or magnified content), alternative input methods (e.g., voice), additional navigation or orientation...

scribe: mechanisms, and content transformations (e.g., to make tables more accessible). Examples of assistive technologies that are important in the context of this document include the following:

<jeanne> ACTION: JS to update the document with new text for accessible content support features [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action04]

<trackbot> Created ACTION-71 - Update the document with new text for accessible content support features [on Jeanne Spellman - due 2009-01-12].

• screen magnifiers, and other visual reading assistants, which are used by people with visual, perceptual and physical print disabilities to change text font, size, spacing, color, synchronization with speech, etc. in order improve the visual readability of rendered text and images;

• screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;

• text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;

• speech recognition software, which may be used by people who have some physical disabilities;

• alternative keyboards, which are used by people with certain physical disabilities to simulate the keyboard (including alternate keyboards that use head pointers, single switches, sip/puff and other special input devices);

• alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.

http://lists.w3.org/Archives/Public/w3c-wai-au/2008OctDec/att-0083/ATAG_Glossary_Review.doc

assistive technology [adapted from WCAG 2.0]

scribe: mechanisms, and content transformations (e.g., to make tables more accessible). Examples of assistive technologies that are important in the context of this document includes but are not limited to the following:

scribe: mechanisms, and content transformations (e.g., to make tables more accessible). Note: Examples of assistive technologies that are important in the context of this document includes but are not limited to the following:

• screen readers, which are used by people who are blind to read textual information through synthesized speech or braille;

• text-to-speech software, which is used by some people with cognitive, language, and learning disabilities to convert text into synthetic speech;

• speech recognition software, which may be used by people who have some physical disabilities;

• alternative pointing devices, which are used by people with certain physical disabilities to simulate mouse pointing and button activations.

Note: Examples of assistive technologies include, but are not limited to, the following:

<jeanne> +1

audio [adapted from WCAG 2.0]

The technology of sound reproduction. Audio can be created synthetically (including speech synthesis), recorded from real world sounds, or both.

<jeanne> ACTION: JS to update the document with new text for assistive technologies [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action05]

<trackbot> Created ACTION-72 - Update the document with new text for assistive technologies [on Jeanne Spellman - due 2009-01-12].

authoring action

Any action that authors can take using the authoring tool user interface that results in editing content (e.g., typing text, deleting, inserting an element, applying a template). Most authoring tool user interfaces also enable actions that do not edit content (e.g., setting preferences, viewing documentation).

<jeanne> ACTION: JS to update the document to add to the introduction of the Glossary section to add the text "definitions are normative, examples are informative." [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action06]

<trackbot> Created ACTION-73 - Update the document to add to the introduction of the Glossary section to add the text \"definitions are normative, examples are informative.\" [on Jeanne Spellman - due 2009-01-12].

Any action that authors can take using the authoring tool user interface that results in creating or editing content (e.g., typing text, deleting, inserting an element, applying a template). Most authoring tool user interfaces also enable actions that do not edit content (e.g., setting preferences, viewing documentation).

<jeanne> +1 to new definition. More brief, more clear.

authoring outcome

The content modifications that result from authoring actions. The scope of authoring outcomes range from narrow (e.g., inserting a link) to wide (e.g., adding a site-wide navigation system). Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given title).

<jeanne> ACTION: JS to update the document with new text for audio [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action07]

<trackbot> Created ACTION-74 - Update the document with new text for audio [on Jeanne Spellman - due 2009-01-12].

<jeanne> ACTION: JS to update the document with new text for authoring action [recorded in http://www.w3.org/2009/01/05-au-minutes.html#action08]

<trackbot> Created ACTION-75 - Update the document with new text for authoring action [on Jeanne Spellman - due 2009-01-12].

The content modifications that result from authoring actions (e.g., inserting a link, adding a site-wide navigation system). Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given a title).

The content or content modifications that result from authoring actions (e.g., inserting a link, adding a site-wide navigation system). Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given a title).

The content or content modifications that result from authoring actions. Authoring outcomes are cumulative (e.g., text is entered, then styled, then made into a link, then given a title).

<jeanne> JS to update the document with new text for authoring actions

- DRAFT -

WAI AU

05 Jan 2009

Attendees

Contents

Glossary review

Summary of Action Items

Scribe.perl diagnostic output