12:54:44 <RRSAgent> RRSAgent has joined #dpub-aria
12:54:44 <RRSAgent> logging to http://www.w3.org/2015/08/27-dpub-aria-irc
12:55:06 <tzviya> title: DPUB-ARIA TF Weekly
12:55:12 <tzviya> chair: Tzviya Siegman
12:55:27 <tzviya> present+ Tzviya_Siegman
12:55:48 <janina> janina has joined #dpub-aria
12:56:17 <tzviya> agenda: https://lists.w3.org/Archives/Public/public-dpub-aria/2015Aug/0031.html
13:05:16 <richardschwerdtfeger> richardschwerdtfeger has joined #dpub-aria
13:09:22 <tzviya> tzviya: DPUB will sent feedback on http://www.w3.org/2015/08/extended-description-analysis to Michael (if any) by Monday
13:10:54 <tzviya> rich: ongoing conversations with MS about Edge a11y issues
13:12:47 <tzviya> ...there is no investment in IE11. It is being deprecated. ARIA is dropping column mapping to IE11.
13:13:24 <tzviya> Rich: there is a combo of MS active a11y and UI Automation in IE
13:13:44 <tzviya> ...Edge uses UI Automation as there mobile browsers does
13:13:50 <tzviya> s/does/do
13:14:24 <tzviya> ...UIAA has client side and server side
13:14:59 <richardschwerdtfeger> s/UIAA/UIA/
13:16:06 <tzviya> rich: I will work on DPUB-AAM with Joseph
13:16:57 <tzviya> janina: question about matrix http://www.w3.org/2015/08/extended-description-analysis
13:18:08 <tzviya> ...george asked to include item about implementation complexity / what publishers will not accept
13:18:39 <tzviya> rich: it seems that publishers will not accept scripting, but they do for assessments. Why?
13:21:16 <tzviya> tzviya: publishers are not the ones that do not support scripting. It is specific platforms that will not accept scripting.
13:22:53 <tzviya> ...Text book platforms are more likely to support scripting. General reading systems are far less likely.
13:23:25 <tzviya> ...Examples: ibooks supports limited scripting. Kindle supports no scripting. All related to security issues.
13:24:04 <tzviya> ...Many systems are working toward more scripting support. The security concerns are not going away.
13:25:15 <tzviya> Janina: Is it clear from the matrix what works without AT involvement, what works natively?
13:25:31 <tzviya> tzviya: I don't think that's clear
13:26:40 <ivan> q+
13:26:40 <tzviya> Janina: if we do coalesce on <details>, we do have an extension mechanism that would get this in before HTML 5.1
13:26:44 <tzviya> ack iv
13:27:34 <tzviya> ivan: would be very good to include a column that indicates whether AT is needed as well as a column indicating whether JS is needed
13:31:04 <tzviya> janina: all need for extension is a second implementation
13:34:24 <tzviya> http://rawgit.com/w3c/aria/master/dpub-aam/dpub-aam.html#role-map-chapter
13:35:26 <tzviya> Rich: may run into problems when exposing strings
13:36:25 <tzviya> ...now, we indicate "Expose as text string 'chapter' in AriaRole." the string "chapter" could present conflicts
13:36:59 <tzviya> ... if we put the string "dpub-chapter", would want "dpub" disregarded
13:37:40 <tzviya> ...could also affect navigation
13:38:16 <tzviya> Rich: We also need to know if will use posinset, etc from ARIA
13:38:27 <tzviya> ...not all components will be in DOM all the time
13:41:05 <tzviya> MAtt: could be useful, don't know how widely it will be used
13:41:27 <tzviya> RIch: if it's optional, what happens if it's not in place?
13:41:40 <tzviya> tzviya: how is that usually handled in ARIA?
13:42:10 <tzviya> rich: UA computes it, which could be problematic
13:42:31 <tzviya> ...because it is based on DOM
13:42:47 <tzviya> Matt: it will always be position 1 or 1
13:43:10 <tzviya> rich: so, this could be detremental
13:43:20 <tzviya> tzviya: what is next step?
13:43:39 <tzviya> rich: trying to lock down several things by end of year
13:44:26 <tzviya> ...let's lock down the roles in DPUB ARIA
13:44:50 <tzviya> http://www.w3.org/TR/2015/WD-dpub-aria-1.0-20150707/
13:45:31 <tzviya> tzviya: we will add 10 or so roles to DPUB-ARIA
13:45:43 <tzviya> Rich: is there anything to add to master spec?
13:46:12 <tzviya> ivan: if we do that, won't we open ourselves up to the same issues that we faced a few months ago?
13:48:48 <tzviya> rich: is it confusing to publishers to have some terms with prefix, some terms without?
13:50:57 <tzviya> tzviya: based on past discussion, i think markus would prefer to avoid fracturing the vocabulary
13:51:42 <tzviya> rich: there is nothing to prevent people from using dpub- on a website
13:52:24 <tzviya> janina: the worst that will happen is that dpub-glossary works the same as glossary
13:54:30 <tzviya> tzviya: we are trying to avoid people looking at 3 different specs when preparing files
13:55:42 <tzviya> tzviya: by next week we will get back to this group about whether to move some terms to core, get started on additional terms to ARIA
13:56:03 <tzviya> ...and we are targeting end of year for DPUB-ARIA and DPUB AAM
13:56:44 <ShaneM> ShaneM has joined #dpub-aria
13:58:10 <tzviya> rrsagent, make logs public
13:58:16 <tzviya> rrsagent, make minutes
13:58:16 <RRSAgent> I have made the request to generate http://www.w3.org/2015/08/27-dpub-aria-minutes.html tzviya
15:56:56 <ShaneM> ShaneM has joined #dpub-aria
16:36:59 <ShaneM> ShaneM has joined #dpub-aria
16:59:45 <Zakim> Zakim has left #dpub-aria