See also: IRC log
<trackbot> Date: 20 September 2012
take up item 3
<scribe> Scribe: KFord
JAN: This all seems good to me.
Group is in agreement.
<jeanne> resolved: add IER for 3.2.4 and 3.2.5
Group starting to review le3vels again. Starting at 1.8.3.
group agrees on level a for 1.8.3
Group agrees on level a for 1.8.3.
1.8.4 agreement on level A.
JS: If people don't do this is this really an A?
Kim: For people with hand problems, orientation is really important.
1.8.5 agreed to be level A.
JAN: Going back to 1.8.3 could that be a AA because sub-viewpoerts might not be able to comply if the environment only gives a limited amount of space.
JAN: The SC is acceptable, it is in the intent. I can take an action.
<Jan> "up to the limits of the operating environment (i.e., the operating system and/or higher level user agent)" to replace "up to the limits of the physical display screen"
Group agreement on 1.8.6 is level A.
1.8.7, agreement on staying at level A.
kford: Given the complexity I think this needs to go down to AA. I don't want to fail for someone not doing part of this.
group in agreement with some hesitation.
1.8.8 moves to AA.
JAN: This isn't a show stopper. I say move to AA.
1.8.9 moves to AA.
1.8.10 stays at AA.
1.8.11 stays at AA.
KFord: I think 1.8.12 needs to be AAA.
Kim: I see this as a work around for headings and there are a lot of documents where this will help.
<jeanne> KP: this will help a number of different disabilities
<jeanne> KF: No one does this.
<jeanne> ... how to handle dynamic pages. What you mark may be not there or totally different so you always have to look through the DOM.
<jeanne> ... it could have some serious performance impact to the page.
JAN: I can agree that the persistence part can be hard.
<jeanne> JS: would this require changing the DOM?
<jeanne> KF: no, there are a number of ways to do it, it could be the URL, or some kind of datastore.
<jeanne> Jan: I think some of the technical details of this make it tricky enough to be AAA.
<jeanne> KP: Is this one of the things that would be done if people were motivated? The George example is very important.
<jeanne> KF: I think the people that want to build this will, regardless of whether it is AA or AAA.
<jeanne> KP: So you think it is technically difficult enough that it is not in our best interests to make it AA?
<jeanne> KF: The edge cases -- especially dynamic content -- are difficult enough to justify AAA.
<jeanne> KP: We should identify this as a feature that needs to be solved.
1.8.12: Group agrees 1.8.12 goes to AAA.
<jeanne> JS: We should send this to R&D as they maintain a list of ideas for grad students wanting work
1.8.13 stays at AA.
<jeanne> ACTION: jeanne to forward a request to RDWG that they suggest that students looking for projects build an extention that allows people to put navigation marks in a page - 1.8.12 [recorded in http://www.w3.org/2012/09/20-ua-minutes.html#action01]
<trackbot> Created ACTION-759 - Forward a request to RDWG that they suggest that students looking for projects build an extention that allows people to put navigation marks in a page - 1.8.12 [on Jeanne F Spellman - due 2012-09-27].
1.9.1 stays at AA.
Group talking about 1.9.1. Does PDF have to do this?
JAN: I also don't think most peope are going to use this.
Change, 1.9.1 moves to AAA.
1.9.2 stays at AA.
KFord: I have concerns about this. It isn't well defined. Very complex to define what relationships are really meant here.
More discussion. JAN thought in page links were not covered, Jim did think they were.
1.10.1 moves to AA.
1.10.2 Moves to AAA.
2.1.1 stays at A.
<jeanne> JR: Android always has keyboard focus, windows always has it. iOS has it when Voiceover is turned on.
A little discussion around how 2.1.2 works today.
2.1.2 stays at level A.
2.1.3 stays at A.
<jeanne> ACTION: Jeanne to research whether the behavior of radio buttons staying selected is defined in HTML. [recorded in http://www.w3.org/2012/09/20-ua-minutes.html#action02]
<trackbot> Created ACTION-760 - Research whether the behavior of radio buttons staying selected is defined in HTML. [on Jeanne F Spellman - due 2012-09-27].
2.1.4 stays at A.
2.1.5 stays at A.
\2.1.6 stays at A.
2.2.1 stays at A.
2.2.2 stays at A.
2.2.3 stays at A.
Group talking about what term we mean here, document or source order.
<scribe> ACTION: JA to clarify wording in 2.2.3 [recorded in http://www.w3.org/2012/09/20-ua-minutes.html#action03]
<trackbot> Created ACTION-761 - Clarify wording in 2.2.3 [on Jim Allan - due 2012-09-27].
2.2.4 stays at AA.
<jallan> ACTION: jim to review 2.2.3 for language, do we mean tab, source, or document order? [recorded in http://www.w3.org/2012/09/20-ua-minutes.html#action04]
<trackbot> Created ACTION-762 - Review 2.2.3 for language, do we mean tab, source, or document order? [on Jim Allan - due 2012-09-27].
<jallan> close action 761
<jallan> close action-761
<trackbot> ACTION-761 Clarify wording in 2.2.3 closed
2.3.1 stays at A.
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: trackbot Inferring Scribes: trackbot WARNING: 4 scribe lines found (out of 15 total lines.) Are you sure you specified a correct ScribeNick? WARNING: No "Topic:" lines found. WARNING: No "Present: ... " found! Possibly Present: joined kford ua You can indicate people for the Present list like this: <dbooth> Present: dbooth jonathan mary <dbooth> Present+ amy WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 20 Sep 2012 Guessing minutes URL: http://www.w3.org/2012/09/20-ua-minutes.html People with action items: WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]