17:03:27 RRSAgent has joined #aria-apg 17:03:27 logging to http://www.w3.org/2017/04/10-aria-apg-irc 17:03:35 rrsagent, make minutes 17:03:35 I have made the request to generate http://www.w3.org/2017/04/10-aria-apg-minutes.html jamesnurthen 17:03:41 rrsagent, make log world 17:03:51 meeting: ARIA APG TF 17:03:57 present+ AnnAbbott 17:04:08 present+ 17:04:10 present+ Bryan Garaventa 17:04:27 present+ matt_king 17:04:33 present + Shirisha Balusani 17:04:53 https://github.com/w3c/aria-practices/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Jan+2017+Clean+Up%22+sort%3Aupdated-desc 17:05:31 scribe: jamesnurthen 17:05:54 MK: Start at the top of the list. Walk through and work out what we are going to discuss 17:07:24 jemma has joined #aria-apg 17:09:27 https://mit.webex.com/mit/j.php?MTID=m4b54b847795d432ef8a2ba82e488fea2 17:09:33 https://github.com/w3c/aria-practices/issues/321 17:09:46 MK: will look at this with Tatiana. 17:10:11 https://github.com/w3c/aria-practices/issues/334 17:10:19 MK: assume this is still outstanding 17:10:33 mak logs public 17:10:40 make logs publick 17:10:42 make logs public 17:10:50 rrsagent, make minutes 17:10:50 I have made the request to generate http://www.w3.org/2017/04/10-aria-apg-minutes.html jemma 17:11:13 present+ JaEunJemmaKu 17:11:25 https://github.com/w3c/aria-practices/issues/144 17:11:41 MK: have to merge - there is a PR related 17:11:55 https://github.com/w3c/aria-practices/pull/340 17:13:13 merged the new PR into it 17:14:51 MK: will do final checks on 340 - feedback has been addressed 17:18:19 Logged https://github.com/w3c/aria-practices/issues/355 17:18:57 MK: 1 thing we dont have in menu examples is an example of using aria-owns rather than putting the children inside the menu item 17:19:57 arrow keyboard navigation in vertical menubar will be reverse of horizontal menubar's 17:20:08 MK: vertical menubar priority is relatively low 17:22:43 https://github.com/w3c/aria-practices/issues/325 17:24:03 http://w3c.github.io/aria-practices/#dialog_modal 17:24:08 is it 325? 17:27:54 yes 325 17:34:07 +q 17:35:06 bryan: dont understand its purpose if it is not to hide the content from at users 17:37:59 When a modal element is displayed, authors must ensure the interface can be controlled using only descendants of the modal element. In other words, if a modal dialog has a close button, the button should be a descendant of the dialog. When a modal element is displayed, authors should mark all other contents as inert (such as "inert subtrees" in HTML) if the ability to do so exists in the host language. 17:38:02 (from the spec) 17:38:53 MK: it is a screen reader's job to limit navigation to stuff inside a modal 17:39:02 MK: what makes something inert is the real issue 17:39:50 seems to me that is a screen reader user can see what is outside the dialog - it is still the author's job to ensure that activating links outside the dialog doesn't do anything. 17:48:57 MK: if you can see and operate outside the dialog should not be using aria-modal 17:52:24 JN: will work on it 17:53:13 When a modal element is displayed, authors must ensure the interface can be controlled using only descendants of the modal element. In other words, if a modal dialog has a close button, the button should be a descendant of the dialog. When a modal element is displayed, authors should mark all other contents as inert (such as "inert subtrees" in HTML) if the ability to do so exists in the host language. 17:53:22 ack me 17:53:23 https://github.com/w3c/aria-practices/issues/279 17:53:42 MK: gave Feedback in the issue 17:54:01 MK: ready to close 17:54:46 https://github.com/w3c/aria-practices/issues/224 18:00:51 18:01:01 rrsagent, make minutes 18:01:01 I have made the request to generate http://www.w3.org/2017/04/10-aria-apg-minutes.html jamesnurthen 18:05:03 It is little confusing 18:06:49 rrsagent, make minutes 18:06:49 I have made the request to generate http://www.w3.org/2017/04/10-aria-apg-minutes.html jamesnurthen 19:57:45 Zakim has left #aria-apg