16:19:56 RRSAgent has joined #ua 16:19:56 logging to http://www.w3.org/2014/09/04-ua-irc 16:19:58 RRSAgent, make logs public 16:19:58 Zakim has joined #ua 16:20:00 Zakim, this will be WAI_UAWG 16:20:00 ok, trackbot; I see WAI_UAWG()1:00PM scheduled to start in 40 minutes 16:20:01 Meeting: User Agent Accessibility Guidelines Working Group Teleconference 16:20:01 Date: 04 September 2014 16:20:17 chair: JimAllan, KellyFord 16:20:30 rrsagent, set logs public 16:20:41 rrsagent, make minutes 16:20:41 I have made the request to generate http://www.w3.org/2014/09/04-ua-minutes.html allanj 16:27:22 agenda+ Action 1029 Fleshout note for conformance of nested ua user interfaces 16:27:24 agenda+ Publishing doc. 16:27:25 agenda+ Final pass on document. 16:27:46 agenda+ MS04 Note 16:57:58 WAI_UAWG()1:00PM has now started 16:58:05 +Jeanne 17:00:47 allanj has joined #ua 17:01:15 +Jim_Allan 17:01:57 zakim, agenda? 17:01:57 I see 4 items remaining on the agenda: 17:01:58 1. Action 1029 Fleshout note for conformance of nested ua user interfaces [from allanj] 17:01:58 2. Publishing doc. [from allanj] 17:01:58 3. Final pass on document. [from allanj] 17:01:58 4. MS04 Note [from allanj] 17:02:40 Jan has joined #ua 17:02:48 +Greg_Lowney 17:02:48 zakim, code? 17:02:49 the conference code is 82941 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), Jan 17:02:58 Greg has joined #ua 17:03:22 +[IPcaller] 17:03:45 zakim, [IPcaller] is really Jan 17:03:45 +Jan; got it 17:06:11 agenda+ TPAC meetings with other groups? 17:08:25 scribe: allanj 17:08:44 agenda ? 17:09:09 zakim, open item 5 17:09:09 agendum 5. "TPAC meetings with other groups?" taken up [from jeanne2] 17:09:17 https://www.w3.org/wiki/TPAC2014/ad-hoc-meetings 17:10:18 js: optional meeting 11-3 meeting time for adhoc meetings both days 17:10:51 ... schedule between groups 17:13:49 zakim, close item 5 17:13:49 agendum 5, TPAC meetings with other groups?, closed 17:13:50 I see 4 items remaining on the agenda; the next one is 17:13:50 1. Action 1029 Fleshout note for conformance of nested ua user interfaces [from allanj] 17:14:05 zakim, open item 2 17:14:05 agendum 2. "Publishing doc." taken up [from allanj] 17:17:09 perhaps next week, with 3 week turn around, handle comments. then publish again right before TPAC 17:18:56 discussion on clean up particulars 17:19:37 +[Microsoft] 17:19:38 zakim, close item 2 17:19:39 agendum 2, Publishing doc., closed 17:19:39 I see 3 items remaining on the agenda; the next one is 17:19:39 1. Action 1029 Fleshout note for conformance of nested ua user interfaces [from allanj] 17:19:55 KimPatch has joined #ua 17:20:10 zakim, open item 1 17:20:10 agendum 1. "Action 1029 Fleshout note for conformance of nested ua user interfaces" taken up [from allanj] 17:21:15 +Kim_Patch 17:22:03 zakim, [Microsoft] is really Kelly 17:22:03 +Kelly; got it 17:22:23 rrsagent, make minutes 17:22:23 I have made the request to generate http://www.w3.org/2014/09/04-ua-minutes.html allanj 17:23:11 http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0080.html 17:24:08 kford has joined #ua 17:29:42 Proposed: insert into UAAG 2.0 Conformance Applicability Notes 17:30:11 Note: In this document the term user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user interface. The media... 17:30:13 ...player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:31:52 Note: In this document the term UA user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user interface. The media... 17:31:54 ...player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:32:14 Embedded user agents: The term user agent (UA) user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user interface. The 17:32:15 media player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:35:41 discussion of UA user interface and the conformance 17:37:18 gl: this note is about the scope of the term UA user interface 17:37:35 Scope of User Agent User Interface: Embedded user agents: The term user agent (UA) user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with 17:37:35 its own unique user interface. The media player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:37:59 Scope of User Agent User Interface: The term user agent (UA) user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user 17:37:59 interface. The media player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:38:39 Scope of User Interface: The term user agent (UA) user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user interface. 17:38:39 The media player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:40:54 Scope of User Interface: The term user interface is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user interface. 17:40:55 The media player would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:41:00 Scope of User Interface: The term "user interface" is reserved only for controls and mechanisms of the user agent that is being considered for conformance. It does not include controls and mechanisms created by content or other user agents. For example a desktop user agent displays a page containing a media player. The media player is a user agent with its own unique user interface. The media player 17:41:00 would have its own unique conformance claim, just as the parent user agent has its own conformance claim. 17:43:09 action: jeanne to update document to add Conformance Applicability Note above and link to the conformance note from the definition of user interface. Standardize all SCs to use term "user interface" linked to the definition. 17:43:09 Created ACTION-1032 - Update document to add conformance applicability note above and link to the conformance note from the definition of user interface. standardize all scs to use term "user interface" linked to the definition. [on Jeanne F Spellman - due 2014-09-11]. 17:44:48 I'd lean towards relegating the examples to the glossary entry for embedded user agents, but I'll defer to the group. 17:47:04 -Kim_Patch 17:47:26 zakim: close item 1 17:47:34 zakim, close item 1 17:47:34 agendum 1, Action 1029 Fleshout note for conformance of nested ua user interfaces, closed 17:47:36 I see 2 items remaining on the agenda; the next one is 17:47:36 3. Final pass on document. [from allanj] 17:47:36 +[Microsoft] 17:47:38 -Kelly 17:48:06 zakim, [Microsoft] is really Kelly 17:48:06 +Kelly; got it 17:48:16 agenda ? 17:48:32 zakim, open item 4 17:48:32 agendum 4. "MS04 Note" taken up [from allanj] 17:49:02 MS04 (be clear what is user interface and what is rendered content) 17:49:04 We fixed our definitions, but MS04 also pointed out SC where we were not 17:49:05 specific which applied. I propose the following: 17:50:14 3.2.2 Back button. Added sentence to Intent "The Back feature is a part of the user agent user interface instead of the rendered content, however, authors should not "break" the Back button by disabling it, or creating sequences of web pages that would cause an error if the Back button were used. " 17:50:18 kford has joined #ua 17:52:40 Greg's http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0087.html 17:53:33 http://jspellman.github.io/UAAG-LC-Comment/ 17:56:16 gl: need to smith the intent of 3.2.2 back, forward, navigate within history 17:56:32 ... ideally change the SC but willing to defer 17:57:19 I don't feel the SC needs any change to clarify whether it's related to UA UI or to content, but I would like to (ideally) see the SC reworded slightly to avoid focusing entirely on the terms "reverse" and "back". Per the second paragraph of my email, it should be about more than that. However, if people want to postpone this until UAAG3, I'll understand. 17:58:09 Original numbering: 3.2.2 Back Button 17:58:27 2.3.4 Present Direct Commands in User Interface 17:58:40 discussion of meaning of the comment 17:59:03 2.2.1 Sequential Navigation Between Elements: The user can move the keyboard focus backwards and forwards through all recognized enabled elements in the current viewport. 17:59:21 -Kelly 17:59:32 3.2.3 Spell Check: User agents provide spell checking functionality for text created inside the user agent. 17:59:45 I was just asking what 3.2.2.said exactly. 18:00:22 +[Microsoft] 18:01:21 I know that the ask on this item was to be very explicit about this discinction. 18:01:25 zakim, [Microsoft] is Kelly 18:01:25 +Kelly; got it 18:01:48 I know the ask was to be very expliciti on this point. 18:03:22 jr: need to be more explicit about rendered content. 18:03:31 We can for example address it by adding this explicitedly or say that context should in general make this obvious. 18:04:33 UAAG 1.0 used to call this out explicitly ("Conformance detail") http://www.w3.org/TR/WAI-USERAGENT/guidelines.html#Guidelines 18:04:42 I am also saying that we can say that we don't agree with the comment and such. 18:05:06 I am saying we could respond that way. 18:05:46 ja: should we take a pass at finding any SC that need explicit rendered content? 18:06:33 jr: perhaps add an applicability note about rendered content. or if some one wants to know they can dril down and follow definitions, or read the reference document 18:08:23 s/dril/drill 18:09:16 jr: add "applies to: rendered content, or uaui, or both" for each SC in the reference document 18:10:07 js: then this must be done by next thurs. 18:11:12 jr: this seems easier than rewording SCs 18:11:39 js: the work is easy, making the decision is difficult 18:12:01 jr: should not be hard, if it is hard then the comment is really valid 18:15:05 jr: will take a pass at the reference document. 18:15:31 Topic: 3.2.3 spell check 18:15:52 http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0088.html 18:16:23 gl: editorial 'user agents provide' vs 'the user can' 18:16:41 gl: I’m leery of the phrase "text created inside the user agent" 18:16:56 ... only refer to editable stuff in content 18:17:16 ... regardless of where content is created 18:19:49 gl: don't want to require spell check in the UAUI 18:20:52 My comment comes down to the fact that the current SC wording risks accidentally (a) applying to text entered into the UA UI, such as a Find field or File Open dialog, and (b) NOT applying to text that's pasted into a form field, since that's not technically "created inside the user agent". 18:22:40 ja: text inside viewport 18:22:59 js: no, not all words in

and etc. 18:23:08 I'd like to see something like "The user can have spelling and grammar assistance for any text in a text input field [or control] in content." 18:24:14 Or "The user can have spelling and grammar assistance for text in text input fields [or controls] in content." 18:24:44 ja: no UA has grammar checking 18:24:56 gl: MS Word does 18:25:19 gl: extension - grammarly lite, grammar base 18:25:22 Lots of extensions for various browsers add grammar checking. 18:25:51 But as I said in my email I'm okay with relegating grammar assistance to a recommendation in the Reference document. 18:26:06 3.2.3 The user can have spelling for text in text input fields [or controls] in content. 18:26:31 Or "The user can have spelling and grammar assistance for editable text in in content." 18:26:40 s/in in/in/ 18:27:12 "The user can have spelling assistance for editable text in content." 18:28:28 "The user can have spelling assistance for editable text in rendered content." 18:28:56 action: jeanne to update 3.2.3 to be "The user can have spelling assistance for editable text in rendered content." 18:28:56 Created ACTION-1033 - Update 3.2.3 to be "the user can have spelling assistance for editable text in rendered content." [on Jeanne F Spellman - due 2014-09-11]. 18:30:09 I can work on adapting my 1st and 3rd paragraphs for inclusion into the Intent. 18:30:48 rrsagent, make minutes 18:30:48 I have made the request to generate http://www.w3.org/2014/09/04-ua-minutes.html allanj 18:32:11 http://lists.w3.org/Archives/Public/w3c-wai-ua/2014JulSep/0089.html 18:33:52 gl: need a better definition of element and element type 18:33:58 current def 18:34:02 element, element type 18:34:04 Primarily, a syntactic construct of a document type definition (DTD) for its application. This is the sense employed by the XML 1.0 specification ([XML], section 3). This sense is also relevant to structures defined by XML schemas. UAAG 2.0 also uses the term "element" more generally to mean a type of content (such as video or sound) or a logical construct (such as a header or list). 18:34:05 enabled element: An element with associated behaviors that can be activated through the user interface or through an API. The set of elements that a user agent enables is generally derived from, but is not limited to, the set of elements defined by implemented markup languages. 18:34:07 disabled element: A potentially enabled element that is not currently available for activation (e.g. a "grayed out" menu item). 18:34:56 element type is used in 1.4.2 18:35:58 -Jan 18:36:00 -Kelly 18:36:08 -Jeanne 18:36:10 action: greg to send to jeanne new definition for 'element' and 'element type' 18:36:10 Created ACTION-1034 - Send to jeanne new definition for 'element' and 'element type' [on Greg Lowney - due 2014-09-11]. 18:36:50 -Greg_Lowney 18:36:51 rrsagent, make minutes 18:36:51 I have made the request to generate http://www.w3.org/2014/09/04-ua-minutes.html allanj 18:37:02 zakim, please part 18:37:02 leaving. As of this point the attendees were Jeanne, Jim_Allan, Greg_Lowney, Jan, Kim_Patch, Kelly 18:37:02 Zakim has left #ua 18:37:09 rrsagent, make minutes 18:37:09 I have made the request to generate http://www.w3.org/2014/09/04-ua-minutes.html allanj 18:37:25 rrsagent, please part 18:37:25 I see 3 open action items saved in http://www.w3.org/2014/09/04-ua-actions.rdf : 18:37:25 ACTION: jeanne to update document to add Conformance Applicability Note above and link to the conformance note from the definition of user interface. Standardize all SCs to use term "user interface" linked to the definition. [1] 18:37:25 recorded in http://www.w3.org/2014/09/04-ua-irc#T17-43-09 18:37:25 ACTION: jeanne to update 3.2.3 to be "The user can have spelling assistance for editable text in rendered content." [2] 18:37:25 recorded in http://www.w3.org/2014/09/04-ua-irc#T18-28-56 18:37:25 ACTION: greg to send to jeanne new definition for 'element' and 'element type' [3] 18:37:25 recorded in http://www.w3.org/2014/09/04-ua-irc#T18-36-10 18:37:31 exit 18:37:35 bye