See also: IRC log
<JR> Scribe: AnnM
<JR> http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/att-0063/ATAG2_Glossary_Review__Rev12_.doc
<JR> http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0064.html
<JR> prominence
<JR> A heuristic measure of how likely users are to notice items (E.G. single
<JR> controls, groups of controls, text messages) in a user interface that
<JR> they are operating. Prominence is affected by numerous factors,
<JR> including: the number of navigation steps required, the reading order
<JR> position, visual properties (e.g., size, spacing, color), and even the
<JR> modality of use (e.g., mouse vs. keyboard use). For purposes of
<JR> conformance to ATAG 2.0, item A is considered to be *at least as
<JR> prominent* as item B if:
<JR> * (a) both items occur in the same item container (e.g., menu for menu
<JR> items, list for list items, dialog box for text boxes)
<JR> * (b) item A is highlighted if item B is highlighted.
<JR> * (c) item A occurs higher in the reading order or immediately follows
<JR> item B.
<JR> * (b) if item B is emphasized then item A is also emphasized
<JR> http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0064.html
<JR> TB, GP: Prefer item A, item B
<JR> (2a) Rewording B.1.1.2, B.1.1.4, B.1.1.6 for clarity:
<JR> UNCHANGED FROM EARLIER PROPOSAL
<JR> B.1.1.2 Author Choice of Technologies (Level A): If the authoring tool
<JR> provides authors with Web content technology options, THEN ANY
<JR> *ACCESSIBLE technology* (WCAG Level A) options THAT ARE SUITABLE FOR THE
<JR> TASK ARE *AT LEAST AS PROMINENT* AS ANY OTHER TECHNOLOGY OPTIONS. (Level A)
<JR> ACTION: JR to Update "Technology" with "*accessible technology*" phrase [recorded in http://www.w3.org/2009/03/30-au-minutes.html#action01]
<trackbot> Created ACTION-130 - Update \"Technology\" with \"*accessible technology*\" phrase [on Jan Richards - due 2009-04-06].
<jeanne> ACTION: js to update glossary with finalized definition of Prominence from the updated glossary document [recorded in http://www.w3.org/2009/03/30-au-minutes.html#action02]
<trackbot> Created ACTION-131 - Update glossary with finalized definition of Prominence from the updated glossary document [on Jeanne Spellman - due 2009-04-06].
<JR> (3) Rewording B.2.1.1, B.2.1.2, B.2.1.3:
<JR> REWORDED TO TAKE INTO ACCOUNT WIZARD-STYLE PROMPTING ETC. - REMOVED
<JR> "PROMINENCE" CLAUSE
<JR> B.2.1.1 Guide Accessible (Level A): If THE AUTHORING TOOL AUTOMATICALLY
<JR> PROMPTS AUTHORS FOR any information as content is being added or updated
<JR> (e.g., by an image modification dialog), then AUTOMATIC PROMPTS ARE ALSO
<JR> INCLUDED for any accessibility information required for that content to
<JR> meet WCAG Level A (Level A).
<JR> ---
<scribe> ACTION: jeanne to incorporate proposal into document [recorded in http://www.w3.org/2009/03/30-au-minutes.html#action03]
<trackbot> Created ACTION-132 - Incorporate proposal into document [on Jeanne Spellman - due 2009-04-06].
<JR> No objections
<JR> (4) Rewording B.2.5.3:
<JR> UNCHANGED FROM EARLIER PROPOSAL
<JR> B.2.5.3 Template Selection Mechanism: If authors are provided with a
<jeanne> ACTION: JS to update B.2.1.1 - 3 as from the minutes of 20090330 [recorded in http://www.w3.org/2009/03/30-au-minutes.html#action04]
<trackbot> Created ACTION-133 - Update B.2.1.1 - 3 as from the minutes of 20090330 [on Jeanne Spellman - due 2009-04-06].
<JR> template selection mechanism, then (Level A):
<JR> (a) the selection mechanism indicates the accessibility status of
<JR> templates (if known), AND
<JR> (b) any accessible template options ARE *AT LEAST AS PROMINENT* AS other
<JR> TEMPLATE options.
<JR> (5) Rewording B.2.5.7:
<JR> UNCHANGED FROM EARLIER PROPOSAL
<JR> B.2.5.7 Pre-Authored Content Selection Mechanism: If authors are
<JR> provided with a selection mechanism for pre-authored content other than
no objections to proposal for B.2.5.3
<JR> templates (e.g., clip art gallery, widget repository, design themes),
<JR> then (Level AA):
<JR> (a) the selection mechanism indicates the accessibility status of the
<JR> pre-authored content (if known), AND
<JR> (b) any accessible options ARE *AT LEAST AS PROMINENT* AS other
<JR> PRE-AUTHORED CONTENT options.
no objections to proposal for B.2.5.7
<JR> (6) Rewording the rationale of B.3.1:
<JR> "IS" added
<JR> Guideline B.3.1 Rationale: When authors are learning a new authoring
<JR> tool, they may find and learn to use the first authoring action they
<JR> encounter that achieves their intended outcome. Since they may be
<JR> unaware of the issue of accessibility, it IS preferable that accessible
<JR> content be an additional unintended outcome, rather than inaccessible
<JR> content.
<JR> (7) Rewording B.3.1.1:
no objections to proposal for B.3.1
<JR> UNCHANGED FROM EARLIER PROPOSAL
<JR> B.3.1.1 Accessible Options Prominent: If authors are provided with
<JR> multiple options for an authoring task, options that will result in
<JR> content conforming to *WCAG* Level A ARE *AT LEAST AS PROMINENT* AS
<JR> OPTIONS THAT WILL NOT. (Level A)
<JR> darn
<JR> calling bacxk in'
<JR> ---
no objections to proposal for B.3.1.1
<JR> (8) Minor edit to B.3.3.4:
<JR> UNCHANGED FROM EARLIER PROPOSAL
<JR> B.3.3.4 At Least as Prominent: Accessible content support features are
<JR> *at least as prominent* [DEL] as comparable features related to other
<JR> types of Web content problems (e.g., invalid markup, syntax errors,
<JR> spelling and grammar errors). (Level AA)
no objections to proposal for B.3.3.4
<JR> no objections to new prominence defn with "emphasized" rewording
<JR> ACTION: All to Be prepared to discuss Anna's comments (incl. making proposals) [recorded in http://www.w3.org/2009/03/30-au-minutes.html#action05]
<trackbot> Sorry, couldn't find user - All
<JR> Reminder that we want to collect ARIA comment ideas on the next call (April 6)
<JR> GP: Tentative offer of Adobe's Washington DC location
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: AnnM Inferring ScribeNick: AnnM WARNING: Dash separator lines found. If you intended them to mark the start of a new topic, you need the -dashTopics option. For example: <Philippe> --- <Philippe> Review of Action Items WARNING: No "Present: ... " found! Possibly Present: AnnM GP Greg Greg_Pisocky JR Jeanne JuttaT P1 P11 P13 Tim_Boland including trackbot You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy Agenda: http://lists.w3.org/Archives/Public/w3c-wai-au/2009JanMar/0068.html Got date from IRC log name: 30 Mar 2009 Guessing minutes URL: http://www.w3.org/2009/03/30-au-minutes.html People with action items: all jeanne jr js WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]