See also: IRC log
<trackbot> Date: 24 October 2013
<scribe> scribe: allanj
js: notes at beginning, question
1. there are 2 other locations where we start Guidelines with
... can I leave them for purposes of LC
Resolution: leave notes at beginnings of Guidelines as needed
<jeanne> 1.8.9 Allow Viewport Resize:
<jeanne> The user can resize viewports within restrictions imposed by the platform, overriding any values specified by the author. (Level AA)
js: add 'if the user has reflowed
to 1 column (1.8.7) and resize viewport, then you don't loose
... how frustrating, if everytime you resize the viewport, the browser resets the reflow.
ja: done see UA doing this now
<kford> I am back, sorry for the delay
jr: agree with greg its already covered.
gl: no problem with a note on
1.8.9. rather have note, than making the SC longer
... more important to maintain point of regard.
... craft a note that covers important things that need to be retained.
<jeanne> Note: If the user has used features in 1.8.7 to reflow the viewport to one column, and the user resizes the viewport, the reflowed page has one column and maintains the original point of regard (x.x.x)
ja: maintain PoR on reflow, and scale text, and resize viewport
gl: reflow should happen on any viewport resize, not just the One Column
<jeanne> 1.8.6 is Maintain point of regard
<jeanne> Note: When the user resizes the viewport, prior user selections are respected.
ja: do we need a top level comment, that combinations of SCs still need to be met
gl: perhaps under conformance applicability notes
kp: use note that JS just wrote with expanded e.g.
<jeanne> Note: When the user resizes the viewport, prior user selections are respected (e.g if the user chose to display the content in one column, when the viewport is resized, the content is still displayed in one column, the font customizations are maintained and the point of regard is maintained. )
<jeanne> UAAG 2.0 Guidelines
<jeanne> The success criteria and applicability notes are normative. Guideline summaries are informative.
gl: what about other Notes?
js: remove the word "applicability"
<jeanne> The success criteria, their notes, and applicability notes are normative. Guideline summaries are informative.
gl: we have notes and
applicability notes, note sure of the distinction
... should call them both out as normative
... applicability note are only in one place in the doc.
<Jan1> The success criteria and applicability notes are normative. Guideline summaries are informative. --> The success criteria and conformance applicability notes are normative. Guideline summaries are informative.
all discussion of Notes and normativeness
jr: in this section only Guideline summaries are informative
<jeanne> The guidelines, success criteria, their notes, and the conformance applicability notes are normative
gl: not sure what This Section means. not visually distinguishable
<Jan1> +1 to Jeanne's
+1 to jeanne;s
<KimPatch> +1 to Jeanne's
jr: nothing in implementing guide is normative
<jeanne> The guidelines, success criteria, their notes, and the conformance applicability notes are normative. Guideline summaries are informative.
above is only in guidelines and not in implementing docs
jr: statement: SC are not
... statement: SC are not mutually exclusive.
the ua should respect other settings
gl: the UA should comply with the SCs at the same time, unless they are mutually exclusive.
ja: do other guideline documents state this general assumption?
<Greg> Under Conformance Applicability Notes, something like 4. Users should have access to all behaviors required by this document at the same time, except where those behaviors are mutually exclusive.
<jeanne> 4. Users can access all behaviors required by this document at the same time, except where those behaviors are mutually exclusive.
e.g. When the user resizes the viewport, prior user selections are respected (e.g if the user chose to display the content in one column(1.8.7), when the viewport is resized (1.8.9), the content is still displayed in one column, the font customizations(1.4.1-6) are maintained and the point of regard is maintained. (1.8.6)
<Greg> (e.g. when the user resizes the viewport per 1.8.9, content is reflowed per 1.8.6)
<jeanne> Users can access all behaviors required by this document at the same time (e.g. when the user resizes the viewport per 1.8.9, content is reflowed per 1.8.6), except where those behaviors are mutually exclusive.
kf: link to RFC2119
... 2 and 4 in conformance applicability note...this document, should say UAAG20,
<Jan1> What do we think of adding stems for the conformance applicability notes, like ATAG2...
<Jan1> Recognized content only:
<Jan1> Oprional preference settings:
<Jan1> RFC 2119 language not used:
<Jan1> Simultaneous satisfaction of success criteria:
issue: add something in implementing document, about Simultaneous satisfaction of success criteria
<trackbot> Created ISSUE-98 - Add something in implementing document, about simultaneous satisfaction of success criteria. Please complete additional details at <http://www.w3.org/WAI/UA/tracker/issues/98/edit>.
<Greg> I was just questioning on whether "global" and "element type" should be emphasis (italics) instead of strong (bold) in "Note 1: Success criteria 1.4.1, 1.4.3, and 1.4.6 address configuration at a global level, that is, it changes all of the text. Success criteria 1.4.2 and 1.4.5 are at an element type level, such as configuring just the heading text.", because we elsewhere use bold only for...
polling group: any issues, blocks, etc. for going to Last Call
6 week comment time
<Greg> The link "Implementing 2.11.6" is *before* 2.11.6 rather than after it.
assuming publishing Nov 4, 6 weeks is Dec. 8
<Greg> Appendix D has one list with bullets, two without.
<Greg> Under References, the dt for [UAAG10] is marked with <strong>.
<Jan1> 3.3.2 Describe Accessibility Features.. a,b,c list each strong needs...class="handle"
1.6.4 & 5 is AA, it is in the AAA section, should be in AA section, need renumbering
<Greg> 1.1.6 there's a space before the anchor tag.
<jeanne> 1.6.1, 1.6.2 & 1.6.3 share an IER, which messes up the numbering.
Fastest Search :: Add-ons for Firefox - Mozilla Add-ons
<jeanne> Jeanne pinged Shawn in IRC to look at the change to the Applicability Notes as a solution to 1.8.9 adding reflow. She agreed to our change.
<jeanne> +1 for publishing Last Call
+1 for last call
<Jan1> +1 for publishing Lasdt call
<Greg> +1 for publishing Last Call
<jeanne> +1 for publishing Last Call
eric: +1 for last call
<kford> +1 for last call
<KimPatch> +1 for publishing Last call
resolution: UAWG going to last call (UAAG20) with 6 week review period.
This is scribe.perl Revision: 1.138 of Date: 2013-04-25 13:59:11 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/Lasdt/Last/ Found Scribe: allanj Inferring ScribeNick: allanj Default Present: Jeanne, kford, Greg_Lowney, Jim_Allan, Kim_Patch, Jan Present: Jeanne kford Greg_Lowney Jim_Allan Kim_Patch Jan Regrets: eric WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 24 Oct 2013 Guessing minutes URL: http://www.w3.org/2013/10/24-ua-minutes.html People with action items:[End of scribe.perl diagnostic output]