See also: IRC log
http://www.w3.org/WAI/AU/2009/ATAG20-20090112-ED/
<scribe> scribe:jeanne
<Greg> +1 on attachment
<JR> http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0037.html
<JR> accessibility information
<JR> Any information that is added to Web content for the purpose of conformance with WCAG (e.g., text descriptions of images, role and state information, relationships within complex tables).
GP: Shouldn't it be "text alternatives"?
<JR> accessibility information
<JR> Any information that is added to Web content for the purpose of conformance with WCAG (e.g., text alternatives for images, role and state information, relationships within complex tables).
JR: it is an e.g. so text alternatives for images is ok.
<scribe> ACTION: JS to update the glossary with new definition of "accessibility information" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action01]
<trackbot> Created ACTION-111 - Update the glossary with new definition of \"accessibility information\" [on Jeanne Spellman - due 2009-03-02].
<JR> developer
<JR> Any entities or individuals responsible for programming the authoring tool. This includes the programmers of any additional software components included by the Claimant in the conformance claim. In some cases, development of the authoring tool is complete before the author uses it. However in other cases (e.g., some Web-based authoring tools), the developer may continue to modify the...
<JR> ...authoring tool after content is published by the author such that the Web content experienced by the end user is modified.
<scribe> ACTION: JS to update the glossary with the revised definition of "developer" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action02]
<trackbot> Created ACTION-112 - Update the glossary with the revised definition of \"developer\" [on Jeanne Spellman - due 2009-03-02].
<JR> direct accessibility features
<JR> Features in applications that are not assistive technologies that augment accessibility by people with disabilities (e.g., keyboard navigation, zoom functions, text-to-speech).
JR: removed the word "mainstream".
GP: saying that they are not assistive technologies, is confusing - a self-voicing application would not need the AT but are acting as an AT. They may not be as fully featured as an AT, but they are performing an AT function.
JR: the term is used in the definition of assistive technology
GP: features that supply accessibility without relying on external assistive technology
JT: @@
... Maybe we need to relook at definition of assistive
technology and drop it from there.
GP: I like the strategy. It is
something that people can invoke.
... We see it as "Do you have to rely on external
accessibility, or is it a built-in feature of the program?". it
may not be the best, but it will do.
JR: We all know what we are talking about and just need to find the right words.
GP: I don't want to see the concept of "direct accessibility" disappear.
<JR> ACTION: JR, GP: Rework Assistive Technology and Direct Accessibility to remove the big negative in Direct Access [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action03]
<trackbot> Sorry, couldn't find user - JR,
<JR> element
<JR> A pair of markup tags and their content or an “empty tag” (one that requires no closing tag or content).
<scribe> ACTION: JR to JR and GP to rework Assistive Technology and Direct Accessibility to remove the big negative in Direct Access [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action04]
<trackbot> Created ACTION-113 - JR and GP to rework Assistive Technology and Direct Accessibility to remove the big negative in Direct Access [on Jan Richards - due 2009-03-02].
<JR> markup language
<JR> A system of text annotations (e.g., elements in HTML) and processing rules that may be used to specify the structure, presentation or semantics of content. Examples of markup languages include HTML and SVG. The markup of some content is the set of annotations that appear in the content.
TB: Are we defining element as if it were an XHTML element?
GP: It's not always a pair of tags. Many don't require end tags.
JR: That is covered by "empty tag"
GP: It is content that is the element, not the pair itself.
JR: The semantics?
... philosophical differences. Does it interfere with the
understanding of the document?
... practical usage, not semantic usage.
<JR> element
<JR> A pair of markup tags and its content or an “empty tag” (one that requires no closing tag or content).
GP: A pair and its content is correct usage.
<JR> ACTION: JS to use the new version of "element" and "markup language" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action05]
<trackbot> Created ACTION-114 - Use the new version of \"element\" and \"markup language\" [on Jeanne Spellman - due 2009-03-02].
<JR> user agent [adapted from WCAG 2.0]
<JR> Any software that retrieves, renders and facilitates end user interaction with Web content. Examples include Web browsers, browser plug-ins, and media players.
this removes "assistive technology" and brings it in line with the UAAG revision of the definition.
<JR> ACTION: JS to use the new version of "user agent" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action06]
<trackbot> Created ACTION-115 - Use the new version of \"user agent\" [on Jeanne Spellman - due 2009-03-02].
<JR> Guideline A.3.3 [For the authoring tool user interface] Help authors avoid flashing that could cause seizures.[Techniques]
<JR> Rationale: Flashing can cause seizures in people with photosensitive epilepsy.
<JR> A.3.3.1 Static View: If an editing view renders content (e.g., WYSIWYG) then the author has the global option of a static view in which time-based content appears in a fixed state. (Level A)
<JR> ACTION: JS to remove "flash","general flash and red flash thresholds", "relative luminance" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action07]
<trackbot> Created ACTION-116 - Remove \"flash\",\"general flash and red flash thresholds\", \"relative luminance\" [on Jeanne Spellman - due 2009-03-02].
<JR> collection of software components
<JR> Any software programs that are used either together (e.g., base tool and plug-in) or separately (e.g., markup editor, image editor, and validation tool), regardless of whether there has been any formal collaboration between the developers of the programs.
no concerns. Keep as is.
<JR> label [adapted from WCAG 2.0]
<JR> Text or other component with a text alternative that is presented to users to identify a component. A label is presented to all authors whereas the name may be hidden and only exposed by assistive technology. In many (but not all) cases the name and the label are the same.
JS: Makes more sense with users instead of authors.
<JR> ACTION: JS to use new "label" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action08]
<trackbot> Created ACTION-117 - Use new \"label\" [on Jeanne Spellman - due 2009-03-02].
<JR> name [adapted from WCAG 2.0]
<JR> Text by which software can identify a component to the user. The name may be hidden and only exposed by assistive technology, whereas a label is presented to all users. In many (but not all) cases, the label and the name are the same.
<JR> no concerns
<JR> keep as is
<JR> non-text content [adapted from WCAG 2.0]
<JR> Any content that is not a sequence of characters that can be recognized or where the sequence is not expressing something in human language. This includes ASCII Art (which is a pattern of characters), emoticons, leetspeak (which is character substitution), and images representing text.
<JR> non-text content [adapted from WCAG 2.0]
<JR> Any content that is not a sequence of characters that can be recognized or where the sequence is not expressing something in human language. This includes ASCII Art (which is a pattern of characters), emoticons, and images representing text.
<JR> ACTION: JS to use new "non-text content" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action09]
<trackbot> Created ACTION-118 - Use new \"non-text content\" [on Jeanne Spellman - due 2009-03-02].
JS: SOme group recently debated whether leetspeak belonged in the definition. Some discussion on what leetspeak is.
<JR> normative [adapted from WCAG 2.0]
<JR> Required for conformance. One may conform in a variety of well-defined ways to this document. Content identified as "informative" or "non-normative" is never required for conformance.
<JR> no concerns, leave as is
<JR> presentation [WCAG 2.0]
<JR> Rendering of the content in a form to be perceived by authors.
<JR> no concerns, leave as is
<JR> prominence
<JR> A heuristic measure of the degree to which authors are likely to notice components in the authoring tool user interface when operating the authoring tool. In this document, prominence refers to visual as well as keyboard-driven navigation. Some of the factors that contribute to the prominence of a component include:
<JR> 1. component size (large items or items surrounded by extra white space may appear to be conferred higher importance),
<JR> 2. components order (items that occur early in the "localized" reading order (e.g., left to right and top to bottom; right to left and top to bottom) are conferred higher importance),
<JR> 3. components grouping (grouping items together can change the reading order and the related judgments of importance),
<JR> 4. advanced options (when the properties are explicitly or implicitly grouped into sets of basic and advanced properties, the basic properties may gain apparent importance), and
<JR> 5. highlighting (items may be distinguished from others using icons, color, styling).
6. navigation (items that appear in nested menus are prominent when they appear at at top level)
<scribe> ACTION: JS to draft an additional item to prominence and put it on the survey for next week. [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action10]
<trackbot> Created ACTION-119 - Draft an additional item to prominence and put it on the survey for next week. [on Jeanne Spellman - due 2009-03-02].
<JR> prompt
<JR> Any authoring tool initiated request for a decision or piece of information from authors. Well designed prompting will urge, suggest, and encourage authors.
<JR> No concerns, leave as is
<JR> publishing
<JR> The point at which the authors or the authoring tool make content available to end users (e.g., uploading a Web page, committing a change in a wiki).
<JR> No concerns, leave as is
<JR> relationships [adapted from WCAG 2.0]
<JR> Meaningful associations between distinct pieces of content.
<JR> No concerns, leave as is
<JR> repairing (accessibility) [harmonized with EARL 1.0]
<JR> The process by which Web content accessibility problems that have been identified within content are resolved. ATAG 2.0 identifies three types of repairing, based on increasing levels of automation:
<JR> 1. manual: where the repairs are carried out by authors. This includes the case where the authors are aided by instructions or guidance provided by the authoring tool, but where authors carry out the actual repair procedure;
<JR> 2. semi-automated: where the repairs are partially carried out by the authoring tool, but where authors' input or judgment is still required to complete the repair; and
<JR> 3. automated: where the repairs are carried out automatically by the authoring tool without any intervention by the authors.
<JR> No concerns, leave as is
<JR> reversible actions
<JR> Authoring actions that, by their nature, can be completely undone so that the system returns to the state it was in before the action. Actions that are not reversible may include certain save and delete actions as well as actions made in a collaborative environment that another author has begun to work with.
<JR> No concerns, leave as is
<JR> role [adapted from WCAG 2.0]
<JR> Text or a number by which software can identify the function of a component within Web content (e.g., a number that indicates whether an image functions as a hyperlink, command button, or check box).
<JR> No concerns, leave as is
<JR> role [adapted from WCAG 2.0] Text or a number by which software can identify the function of a component within Web content (e.g., a string that indicates whether an image functions as a hyperlink, command button, or check box).
<JR> ACTION: JS to Use new "Role" [recorded in http://www.w3.org/2009/02/23-au-minutes.html#action11]
<trackbot> Created ACTION-120 - Use new \"Role\" [on Jeanne Spellman - due 2009-03-02].
<JR> structured element set
<JR> Content that consists of organized elements (e.g., lists, maps, hierarchies, graphs).
<JR> No concerns, leave as is
This is scribe.perl Revision: 1.133 of Date: 2008/01/18 18:48:51 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: jeanne Inferring ScribeNick: jeanne Default Present: JR, jeanne, JuttaT, Tim_Boland, Greg_Pisocky, SueAnnN Present: JR jeanne JuttaT Tim_Boland Greg_Pisocky SueAnnN Sueann_Nichols Jan Jutta Jeanne Greg Regrets: Andrew_R. Anne_M. Reed_S. Ann Reed and_Andrew Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0043.html Got date from IRC log name: 23 Feb 2009 Guessing minutes URL: http://www.w3.org/2009/02/23-au-minutes.html People with action items: accessibility assistive direct gp jr js rework technology[End of scribe.perl diagnostic output]