17:01:16 <RRSAgent> RRSAgent has joined #aria
17:01:16 <RRSAgent> logging to http://www.w3.org/2014/09/22-aria-irc
17:01:18 <trackbot> RRSAgent, make logs member
17:01:18 <Zakim> Zakim has joined #aria
17:01:20 <trackbot> Zakim, this will be WAI_PF
17:01:20 <Zakim> ok, trackbot, I see WAI_PFWG(ARIA)1:00PM already started
17:01:21 <trackbot> Meeting: Protocols and Formats Working Group Teleconference
17:01:21 <trackbot> Date: 22 September 2014
17:01:46 <Zakim> +[GVoice]
17:01:57 <clown> zakim, GVoice is Joseph_Scheuhammer
17:01:57 <Zakim> +Joseph_Scheuhammer; got it
17:02:03 <janina> zakim, who's on the phone?
17:02:03 <Zakim> On the phone I see +49.322.110.8.aaaa, ??P14, Joseph_Scheuhammer
17:02:19 <Zakim> +Fred_Esch
17:02:23 <clown> zakim, I am Joseph_Scheuhammer
17:02:23 <Zakim> ok, clown, I now associate you with Joseph_Scheuhammer
17:02:23 <jongund> jongund has joined #aria
17:02:29 <richardschwerdtfeger> richardschwerdtfeger has joined #aria
17:02:32 <janina> zakim, ?PP14 is me
17:02:32 <Zakim> sorry, janina, I do not recognize a party named '?PP14'
17:02:42 <janina> zakim, who's on the phone?
17:02:42 <Zakim> On the phone I see +49.322.110.8.aaaa, ??P14, Joseph_Scheuhammer, Fred_Esch
17:02:44 <Zakim> +James_Nurthen
17:02:50 <jamesn> jamesn has joined #aria
17:02:50 <janina> zakim, ??P14 is me
17:02:50 <Zakim> +janina; got it
17:02:57 <janina> zakim, aaaa is Stefan
17:02:57 <Zakim> +Stefan; got it
17:02:58 <Zakim> +Jon_Gunderson
17:03:11 <Zakim> +Rich_Schwerdtfeger
17:03:40 <Zakim> +Joanmarie_Diggs
17:03:57 <joanie_> Zakim, I am Joanmarie_Diggs
17:03:57 <Zakim> ok, joanie_, I now associate you with Joanmarie_Diggs
17:04:05 <richardschwerdtfeger> chair: Rich
17:04:15 <joanie> Zakim, I am Joanmarie_Diggs
17:04:15 <Zakim> ok, joanie, I now associate you with Joanmarie_Diggs
17:04:20 <richardschwerdtfeger> meeting: W3C WAI-PF ARIA Caucus
17:04:26 <richardschwerdtfeger> RRSAgent, make log public
17:04:57 <Zakim> +??P7
17:05:54 <richardschwerdtfeger> http://lists.w3.org/Archives/Public/public-pfwg/2014Sep/0079.html
17:07:40 <jamesn> scribeNick: jamesn
17:08:05 <jamesn> agenda?
17:08:29 <clown> action-1349?
17:08:29 <trackbot> action-1349 -- James Craig to Patch issue-561: we need @aria-placeholder as backup for @placeholder in custom fields. -- due 2014-09-22 -- OPEN
17:08:29 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1349
17:08:56 <jamesn> RS: Don't see anything listed in here. Punt to next week
17:09:04 <jamesn> action-1355?
17:09:04 <trackbot> action-1355 -- Richard Schwerdtfeger to Propose specific edit for issue-588: clarify rowheader and columnheader selection -- due 2014-09-22 -- PENDINGREVIEW
17:09:04 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1355
17:09:17 <richardschwerdtfeger> http://lists.w3.org/Archives/Public/public-pfwg/2014Sep/0071.html
17:09:24 <jamesn> RS: I have a proposal here. This is important. There is a subtle thing which will impact the guide
17:09:29 <fesch_> fesch_ has joined #aria
17:09:36 <jamesn> q+
17:10:00 <jamesn> RS: it really only happened if the multiselectable state is set.
17:10:22 <jamesn> RS: that means that if not in the multiselectable state then only the column header can be selected.
17:11:11 <MichaelC> rrsagent, make minutes
17:11:11 <RRSAgent> I have made the request to generate http://www.w3.org/2014/09/22-aria-minutes.html MichaelC
17:13:06 <Zakim> +Matt_King
17:13:32 <jamesn> JN: discussing pivot tables and other places where selecting a column header does not select all the cells in the column
17:14:02 <Zakim> -James_Nurthen
17:14:16 <Zakim> +James_Nurthen
17:14:48 <Zakim> +Bryan_Garaventa
17:15:00 <jamesn> RS: If the author wanted to have the whole column selected and they are only navigating to the column header then they wouyld have to propogate the changes
17:15:18 <jamesn> RS: do people agree that we do not propogate the selection
17:15:22 <jamesn> MK: I agree with that
17:15:33 <jamesn> RS: don't know what else we need to add to that
17:15:39 <Zakim> +Cynthia_Shelly
17:15:46 <clown> issue-588?
17:15:46 <trackbot> issue-588 -- Clarify rowheader and columnheader selection (editorial) -- open
17:15:46 <trackbot> https://www.w3.org/WAI/PF/Group/track/issues/588
17:15:51 <mattking> mattking has joined #aria
17:15:54 <bgaraventa1979> bgaraventa1979 has joined #aria
17:15:54 <jamesn> JS: what issue caused this? Issue 588
17:16:13 <bgaraventa1979> zakim, I am Bryan_Garaventa
17:16:13 <Zakim> ok, bgaraventa1979, I now associate you with Bryan_Garaventa
17:16:18 <jamesn> MK: where did it come from?
17:16:33 <jamesn> RS: decision came that we should modify this text.
17:17:18 <jamesn> RS: should we specify in the spec to state that this doesn't select everything in the column
17:17:46 <jamesn> MK: we don't go around the spec and anticipate all the odd things that a browser developer might do and try to prevent them
17:18:06 <jamesn> RS: It was asked what does it mean if i select a row or a column header?
17:18:33 <jamesn> MK: we don't know if the question is raised based on a UA or an application.
17:18:54 <Zakim> +[IPcaller]
17:18:56 <clown> http://rawgit.com/w3c/aria/master/spec/aria.html#aria-selected
17:19:19 <jamesn> MK: I have this feeling that writing text like that is a bit of a rabbit hole. If we go through doing stuff like that is would baloon
17:19:26 <clown> http://rawgit.com/w3c/aria/master/spec/aria.html#columnheader
17:19:45 <clown> http://rawgit.com/w3c/aria/master/spec/aria.html#rowheader
17:19:56 <jamesn> MK: where does it describe what it would do if the application puts aria-selected on the row of the grid
17:20:07 <clown> http://rawgit.com/w3c/aria/master/spec/aria.html#row
17:20:19 <jamesn> MK: do we address aria-selected on the grid row?
17:20:36 <jamesn> RS: we don't have a solumn construct in 1.0
17:20:53 <richardschwerdtfeger> gridcell elements with the aria-selected attribute set can be selected for user interaction, and if the aria-multiselectable attribute of the grid is set to true, multiple cells in the grid may be selected. Grids may be used for spreadsheets like those in desktop spreadsheet applications.
17:20:58 <Lisa_Seeman> Lisa_Seeman has joined #aria
17:21:02 <jamesn> RS: we talk about multiselction in the definition of the grid
17:21:29 <bgaraventa1979> +q
17:22:12 <jamesn> RS: If you put aria-selected on the row header or the columnheader of the gris then it does not auto-select all the things in the column
17:22:39 <jamesn> RS: I want to get this closed
17:23:09 <jamesn> BG: If you have a column and it selects the entire column then if you unselect something then what happens?
17:23:22 <jamesn> RS: the author should alwys be able to override things
17:24:58 <richardschwerdtfeger> Applying the aria-selcted state on a rowheader or columnheader does not automatically set the aria-selected stated to all the cells in the corresponding row or column. The setting of these additional aria-selected states is application dependent.
17:25:17 <MichaelC> agenda: http://lists.w3.org/Archives/Public/public-pfwg/2014Sep/0079.html
17:25:26 <MichaelC> regrets: James_Craig, Léonie_Watson
17:25:40 <jamesn> JS: where are you puttin it?
17:25:47 <jamesn> RS: on row and column header
17:26:03 <jamesn> RS: let me go into the action
17:27:08 <jamesn> MK: application could be problematic
17:27:44 <clown> http://rawgit.com/w3c/aria/master/spec/aria.html#managingfocus
17:29:28 <jamesn> <dicussing wording>
17:30:35 <mattking> Applying the aria-selected state on a rowheader or columnheader does not cause the user agent to automatically propogate the aria-selected state to all the cells in the corresponding row or column.
17:32:43 <mattking> Applying the aria-selected state on a rowheader or columnheader SHOULD not cause the user agent to automatically propogate the aria-selected state to all the cells in the corresponding row or column.
17:33:09 <richardschwerdtfeger> Applying the aria-selected state on a rowheader or columnheader MUST not cause the user agent to automatically propogate the aria-selected state to all the cells in the corresponding row or column.
17:33:11 <mattking> Applying the aria-selected state on a rowheader or columnheader MUST not cause the user agent to automatically propogate the aria-selected state to all the cells in the corresponding row or column.
17:34:02 <mattking> An author MAY choose to propogate selection in this manner for a specific application.
17:34:33 <clown> An author MAY choose to propogate selection in this manner depending on the specific application
17:35:23 <richardschwerdtfeger> Propagation of aria-selected to the individual gridcells is application dependent.
17:35:50 <clown> An author MAY choose to propogate selection in this manner depending on the specific application.
17:37:39 <richardschwerdtfeger> RESOLUTION: James Craig to add this text to the rowheader and columnheader specification sections: Applying the aria-selected state on a rowheader or columnheader MUST not cause the user agent to automatically propogate the aria-selected state to all the cells in the corresponding row or column. An author MAY choose to propogate selection in this manner depending on the specific application.
17:38:00 <jamesn> action-1423?
17:38:00 <trackbot> action-1423 -- Cynthia Shelly to Ask developers about group, none, and generic roles and whether it would be helpful for implementatation of e.g., narrator -- due 2014-09-22 -- OPEN
17:38:00 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1423
17:38:10 <clown> action-1423?
17:38:10 <trackbot> action-1423 -- Cynthia Shelly to Ask developers about group, none, and generic roles and whether it would be helpful for implementatation of e.g., narrator -- due 2014-09-22 -- OPEN
17:38:10 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1423
17:38:45 <jamesn> CS: I expect to be working more closely with them in the future so should get done soon. Give me another week
17:39:19 <clown> action-1423?
17:39:19 <trackbot> action-1423 -- Cynthia Shelly to Ask developers about group, none, and generic roles and whether it would be helpful for implementatation of e.g., narrator -- due 2014-09-29 -- OPEN
17:39:19 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1423
17:39:29 <clown> action-1461?
17:39:29 <trackbot> action-1461 -- Michael Cooper to Ask an html-aapi editor to bring question of @inert to html a11y tf -- due 2014-09-22 -- PENDINGREVIEW
17:39:29 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1461
17:39:29 <jamesn> action-1461?
17:39:30 <trackbot> action-1461 -- Michael Cooper to Ask an html-aapi editor to bring question of @inert to html a11y tf -- due 2014-09-22 -- PENDINGREVIEW
17:39:30 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1461
17:39:31 <MichaelC> ack me
17:39:40 <jamesn> ack me
17:40:05 <jamesn> MC: rushed to do it. put it in pending review state.... was tossing it over the wall.
17:40:24 <jamesn> MC: in pending review state - but nothing to review
17:40:57 <jamesn> MC: if can get the property to be reinstated then would be good for aria
17:41:04 <MichaelC> ackme
17:41:05 <MichaelC> ack me
17:41:31 <jamesn> action-1462?
17:41:31 <trackbot> action-1462 -- Cynthia Shelly to Discuss computed role with ie team -- due 2014-09-22 -- OPEN
17:41:31 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1462
17:41:31 <clown> action-1462?
17:41:31 <trackbot> action-1462 -- Cynthia Shelly to Discuss computed role with ie team -- due 2014-09-22 -- OPEN
17:41:32 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1462
17:41:45 <jamesn> CS: move this one out too
17:42:30 <jamesn> action-1497?
17:42:30 <trackbot> action-1497 -- Richard Schwerdtfeger to Write a glossary item for accessible description -- due 2014-08-18 -- OPEN
17:42:30 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1497
17:42:57 <jamesn> RS: put a proposal out which JC modified. Was fine with those mods./
17:43:19 <richardschwerdtfeger> http://lists.w3.org/Archives/Public/public-pfwg/2014Sep/0083.html
17:43:36 <richardschwerdtfeger> The accessible description provides help information about an interface
17:43:36 <richardschwerdtfeger> element or about how it is used. The value of the accessible description
17:43:38 <richardschwerdtfeger> may be derived from a reference to visible or invisible content within a
17:43:39 <richardschwerdtfeger> web page, or the accessible description may be defined by host language
17:43:39 <richardschwerdtfeger> features, such as the <desc> element in SVG.
17:43:49 <Lisa_Seeman> q+
17:44:11 <jamesn> RS: people ok with that?
17:44:15 <jamesn> LS: I'm not
17:44:42 <jamesn> LS: I wrote to the list. There is a whole issue here and will be creating a mess with this
17:45:00 <jamesn> LS: My suggestion would be for screen reader help, alternate interface help etc.
17:45:33 <jamesn> LS: something we want to put in place for the cognitive task force is to put in mechanisms for help for users who require it
17:45:56 <jamesn> LS: it is a user group whose accessible experience would be detracted from by screen reader information
17:46:14 <mattking> q+
17:46:19 <jamesn> LS: It is very important that we specify who is the intended audience
17:47:21 <jamesn> LS: sould be a text box where need to edit comments. there could be somthing with a button to move to the toolbar. For someone with cognitive decline the worst thing to do would be to add something with some complex keystoke
17:47:38 <jamesn> LS: we need to accept that this is not a blanket accessible description
17:47:52 <jamesn> LS we don;t overuse terms like accessibility to mean one user group
17:48:07 <jamesn> RS: there is nothign thgat says anything specific about any user type
17:48:15 <jamesn> LS: I would like to make it specific
17:48:34 <jamesn> LS: I don't want the same tag for screen reader users as for cognitive users
17:49:15 <jamesn> LS: If soemthing is needed for screen reader users then it should only be for them and not for congnitive users
17:49:25 <richardschwerdtfeger> q?
17:49:27 <jamesn> LS: the description doesn't state who it is for.
17:49:34 <jamesn> ack Bryan
17:49:40 <jamesn> ack Lisa
17:50:16 <jamesn> MK: RS - was this intended to be accessible description as something that is meant to accompany aria-describedby
17:50:24 <jamesn> RS: yes
17:51:20 <jamesn> MK: we use aria-describedby to point to standard help which is available to all users and just associates it. aria-describedby can be used for screen reader specific help.
17:51:36 <jamesn> MK: aria-describedby is completely generic and needs to stay that way
17:51:48 <fesch_> q
17:51:59 <jamesn> MK: what makes it accessible is that it is related to a specifc element and is relatyed to that element.
17:51:59 <clown> q+
17:52:03 <joanie> q+
17:52:07 <mattking> q-
17:52:37 <jamesn> RS: getting relationships supported in browesers has been a challenbge at times. If we have to create =something with a nother relation then this is going to be evben harder
17:53:08 <jamesn> RS: if there was some sort of indication in that description if there were some support for certain user groups then this could be used.
17:53:14 <richardschwerdtfeger> q?
17:53:20 <Lisa_Seeman> q+
17:53:27 <jamesn> JS: wanted to give a little background
17:53:46 <clown> http://rawgit.com/w3c/aria/master/spec/aria.html#dfn-accessible-name
17:54:16 <jamesn> JS: I was working on the accessible name computation and there were all sorts of refs to accessible name and accessible description and had links toi the glossary. But there was no glossary description for accessible description.
17:54:38 <clown> q-
17:54:43 <jamesn> JS: Rich took the task to create one. How that accessivble name or description gets used is up to the application
17:54:46 <richardschwerdtfeger> ack Joseph
17:55:23 <richardschwerdtfeger> ack joan
17:55:24 <jamesn> JD: Matt said it is generic. Should be bigger than a name but smaller than a long description. This is something that is not helk
17:56:07 <mattking> q+
17:56:08 <jamesn> JD: when I look at the draft text it looks specifc to help information.
17:56:47 <jamesn> LS: back to the wording. "provides help infromation" should be generic information and not stuff that is specific to modality.
17:57:09 <jamesn> LS: I think it should be generic and not specific to any modality
17:58:02 <jamesn> LS: equivalent to aria-describedby and you point to the "make sure you have 7 digits in your code"
17:58:36 <jamesn> LS: it is not modality specific. It should be plain language. If people are going to use it for other stuff then we can't use it for cognitive
17:58:38 <jamesn> q+
17:59:05 <jamesn> CS: these fields already exist
17:59:15 <jamesn> CS: sometimes they have other stuff in too.
17:59:16 <richardschwerdtfeger> ack cynthia
17:59:42 <jamesn> CS: trying to redefine this isn't a good idea. We should use what they are used forf now
17:59:56 <jamesn> CS: redifining is not a good idea
18:00:15 <jamesn> RS: had an aria1.1 now in 2.0 issue for keybaord support
18:00:26 <jamesn> RS: the intent wasn't to lump it in here
18:00:38 <richardschwerdtfeger> q?
18:00:47 <richardschwerdtfeger> ack Lisa_Seeman
18:00:59 <Zakim> -James_Nurthen
18:01:32 <jongund> RS: Matt
18:01:42 <jongund> RS: Matt King?
18:01:57 <jongund> MK: I had to step away
18:02:00 <clown> scribenick:  jongund
18:02:07 <jongund> RS: You are on que
18:02:24 <clown> q+
18:02:38 <jongund> RS: We were talking about changing the text for accessible description
18:03:22 <jongund> MK: I started to edit the description, the description should not say anything about what should go in the description
18:03:43 <jongund> MK: We should say a lot less about what should be in the description
18:03:53 <Zakim> -Cynthia_Shelly
18:04:02 <jongund> MK: The accessible description is just not a string, it can also be a pointer
18:04:05 <richardschwerdtfeger> The accessible description provides help information about an interface
18:04:06 <richardschwerdtfeger> element. The value of the accessible description
18:04:07 <richardschwerdtfeger> may be derived from a reference to visible or invisible content within a
18:04:08 <richardschwerdtfeger> web page, or the accessible description may be defined by host language
18:04:09 <richardschwerdtfeger> features, such as the <desc> element in SVG.
18:04:18 <jongund> RS: It is ultimately a string
18:04:45 <jongund> MK: It could be a description of a picutre, so it could be considered more help...
18:05:00 <jongund> MK: Don't want to use the word description in the def
18:05:20 <jongund> Clown: More than a name and less than a long description
18:05:46 <jongund> MK: Any kind of information that is directly related to an element
18:06:12 <richardschwerdtfeger> The accessible description provides additional information about the element that the author feels pertinent to convey to the users. The value of the accessible description
18:06:13 <richardschwerdtfeger> may be derived from a reference to visible or invisible content within a
18:06:14 <richardschwerdtfeger> web page, or the accessible description may be defined by host language
18:06:15 <richardschwerdtfeger> features, such as the <desc> element in SVG.
18:06:16 <jongund> RS: How about this..
18:06:33 <jongund> LS: Yes
18:07:35 <jongund> MK: There are some cases where you have some information that is part of the screen, it is clearly related to the element... don't like the "author" clause..
18:07:48 <jongund> Clown: Additional information about the element period
18:08:12 <jongund> MK: It doesn't have to be... additional information related to the element
18:08:27 <jongund> Fred: What does related to add?
18:09:13 <jongund> MK: When you use the word about .... in a dialog we use aria-describedby ... the text is related to the dialog, but not dialog..
18:09:23 <Lisa_Seeman> q+
18:09:47 <richardschwerdtfeger> The accessible description provides additional information relating to the interface element. The value of the accessible description
18:09:48 <richardschwerdtfeger> may be derived from a reference to visible or invisible content within a
18:09:49 <richardschwerdtfeger> web page, or the accessible description may be defined by host language
18:09:49 <richardschwerdtfeger> features, such as the <desc> element in SVG.
18:09:57 <jongund> LS: My confusion is the link to invisible content, it can ref invisible and visible content, reference to content in the web page
18:10:09 <jongund> LS: Invisible content is always very ....
18:10:19 <jongund> MK: that is a valid use of aria-described by
18:10:30 <jongund> RS: Visible and invisible content covers it all
18:10:52 <jongund> MK: Information that is not visually present on the page
18:11:12 <jongund> MK: Information to me is visible, even though sighted users cannot see it
18:11:29 <jongund> MK: We talk about screen reader visibility
18:11:38 <jongund> Fred: Perceivable..
18:11:57 <jongund> MK: Visually perceivable, may not be visually perceivable
18:11:57 <richardschwerdtfeger> The accessible description provides additional information relating to the interface element. The value of the accessible description may not be visually perceivable.
18:12:20 <clown> s/Fred: Perceivable/Bryan: Perceivable/
18:13:04 <jongund> MK: Complements accessible name
18:13:10 <jongund> LS: I like that
18:13:20 <jongund> RS: Write it in MK
18:13:34 <jongund> RS: I have never spent this much time on a gloaary def
18:13:44 <jongund> JS: Definitions are important
18:13:58 <jongund> RS: Thank you for raising this LS
18:14:35 <mattking> The accessible description provides additional information that complements the accessible name and is related to an interface element. The value of the accessible description may not be visually perceivable.
18:15:33 <jongund> additional word smithing .....
18:15:55 <jongund> MK: May not gives a "should not" flavor
18:16:29 <jongund> MK: May not necessarily be visual perceivable
18:16:34 <richardschwerdtfeger> The accessible description provides additional information, about an interface element,  that complements the accessible name. The accessible description may not be visually perceivable.
18:16:37 <jongund> RS: Say the accessible description
18:17:14 <mattking> An accessible description provides additional information that complements the accessible name and is related to an interface element. The accessible description may or may not be visually perceivable.
18:17:40 <richardschwerdtfeger> An accessible description provides additional information that complements the accessible name and is related to an interface element. The accessible description might or might not be visually perceivable.
18:17:46 <mattking> An accessible description provides additional information that complements the accessible name and is related to an interface element. The accessible description might or might not be visually perceivable.
18:17:50 <jongund> RS: Ok with that?
18:18:03 <jongund> Clown: MK said something too
18:18:21 <jongund> ... more editing ....
18:18:33 <jongund> Clown: The glossary needs it
18:19:02 <richardschwerdtfeger>  An accessible description provides additional information, related to an interface element, that complements the accessible name. The accessible description might or might not be visually perceivable.
18:19:19 <clown> +1
18:19:25 <mattking> +1
18:19:27 <joanie> +1
18:19:33 <jongund> +1
18:19:33 <fesch_> +1
18:19:37 <Lisa_Seeman> +1
18:19:49 <richardschwerdtfeger> RESOLUTION: new glossary definition for accessible description is: An accessible description provides additional information, related to an interface element, that complements the accessible name. The accessible description might or might not be visually perceivable.
18:19:58 <jongund> RS: Colwn can you put it in?
18:20:08 <jongund> Clown: It is nt that big of deal
18:20:20 <jongund> Clown: Just reassign it to me
18:20:26 <jongund> 1497
18:20:35 <jongund> Action 1497
18:20:45 <jongund> Clown: Put the definition in a note
18:21:26 <jongund> CLown: The glossary goes into all the document
18:21:38 <jongund> Clown: "Important Terms"
18:21:55 <clown> s/into all the document/into all the documents/
18:22:11 <jongund> MK: Is this the first definition of "description??
18:22:27 <jongund> RS: This is not the only place where we have had these jems
18:23:01 <jongund> RS: 8 minutes left, let me go to the top of the agenda
18:23:38 <fesch_> http://lists.w3.org/Archives/Public/public-pfwg/2014Sep/0079.html
18:23:56 <jongund> RS: Lets go through open actions and issues and get dates assigned
18:24:15 <Zakim> -Joseph_Scheuhammer
18:24:36 <Zakim> +[GVoice]
18:24:42 <clown> zakim, GVoice is Joseph_Scheuhammer
18:24:42 <Zakim> +Joseph_Scheuhammer; got it
18:24:48 <jongund> RS: These are all ....
18:24:50 <clown> zakim, I am Joseph_Scheuhammer
18:24:50 <Zakim> ok, clown, I now associate you with Joseph_Scheuhammer
18:24:55 <Zakim> -Fred_Esch
18:25:08 <jongund> RS: Issue 561
18:25:18 <clown> action-1426?
18:25:18 <trackbot> action-1426 -- Joanmarie Diggs to Patch issue-561: @aria-placeholder -- due 2014-04-21 -- OPEN
18:25:18 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1426
18:25:27 <richardschwerdtfeger> https://www.w3.org/WAI/PF/Group/track/actions/1426
18:25:42 <jongund> Joanie: Something that is appropriate to use an object attribute, we already do this, I am not sure why assigned to me
18:25:47 <jongund> RS: Let me go back
18:26:03 <clown> issue-561?
18:26:03 <trackbot> issue-561 -- We need @aria-placeholder as backup for @placeholder in custom fields. -- open
18:26:03 <trackbot> https://www.w3.org/WAI/PF/Group/track/issues/561
18:26:17 <Zakim> +Fred_Esch
18:26:49 <Zakim> -[IPcaller]
18:26:59 <jongund> RS: Just respond saying this would be best be done with an object attribute
18:27:10 <jongund> RS: I am going to close action for Joanie
18:28:54 <jongund> RS: 2 minutes left
18:29:04 <jongund> RS: Joanie this is you again
18:29:38 <Zakim> -Michael_Cooper
18:29:42 <jongund> MK: Is region role treated as a landmark?
18:30:10 <jongund> RS: Technically region is not a landmark, but IBM and Jaws treat them as a region
18:30:12 <clown> action-1440?
18:30:12 <trackbot> action-1440 -- Joanmarie Diggs to landmarks section uses "region of page" in prose even though "region" is not a landmark -- due 2014-09-30 -- OPEN
18:30:12 <trackbot> https://www.w3.org/WAI/PF/Group/track/actions/1440
18:30:21 <jongund> MK: How it is used in the prose
18:30:52 <jongund> Joanie: I will add that to my list, Joseph assigned me some other things...
18:31:03 <jongund> RS: That is a wrap
18:31:14 <jongund> rrsagent, draft minutes
18:31:14 <RRSAgent> I have made the request to generate http://www.w3.org/2014/09/22-aria-minutes.html jongund
18:31:16 <Zakim> -Rich_Schwerdtfeger
18:31:17 <Zakim> -Joanmarie_Diggs
18:31:17 <Zakim> -Bryan_Garaventa
18:31:18 <clown> s/Joseph assigned me/James assigned me/
18:31:18 <Zakim> -Matt_King
18:31:19 <Zakim> -janina
18:31:20 <Zakim> -Fred_Esch
18:31:24 <Zakim> -Stefan
18:31:25 <Zakim> -Joseph_Scheuhammer
18:31:26 <Zakim> -Jon_Gunderson
18:31:27 <Zakim> WAI_PFWG(ARIA)1:00PM has ended
18:31:27 <Zakim> Attendees were +49.322.110.8.aaaa, Joseph_Scheuhammer, Fred_Esch, James_Nurthen, janina, Stefan, Jon_Gunderson, Rich_Schwerdtfeger, Joanmarie_Diggs, Michael_Cooper, Matt_King,
18:31:27 <Zakim> ... Bryan_Garaventa, Cynthia_Shelly, [IPcaller]
18:35:43 <RRSAgent> I have made the request to generate http://www.w3.org/2014/09/22-aria-minutes.html clown
18:51:49 <clown> clown has joined #aria
20:33:13 <Zakim> Zakim has left #aria
20:51:54 <clown> clown has left #aria
20:58:11 <newtron> newtron has joined #aria
21:05:40 <newtron_> newtron_ has joined #aria
22:15:14 <newtron> newtron has joined #aria
22:37:05 <newtron> newtron has joined #aria
23:32:01 <newtron> newtron has joined #aria