16:57:12 RRSAgent has joined #aria-apg 16:57:12 logging to http://www.w3.org/2016/08/08-aria-apg-irc 16:57:24 zakim, clear agenda 16:57:24 agenda cleared 16:57:51 Meeting: August 8, ARIA APG TF 16:58:02 rrsagent, make minutes 16:58:02 I have made the request to generate http://www.w3.org/2016/08/08-aria-apg-minutes.html mck 16:58:33 rrsagent, make log world 17:00:33 Agenda+ Issue#12 code review guide (Ian) https://github.com/w3c/aria-practices/issues/12 17:00:35 Agenda+ Issue#35: Adapt dev docs style for code examples? https://github.com/w3c/aria-practices/issues/35 17:00:37 Agenda+ Issue 17 - Breadcrumb design pattern (Michiel) https://github.com/w3c/aria-practices/issues/17 17:00:38 Agenda+ Issue#69: Accordion Arrow Key Navigation https://github.com/w3c/aria-practices/issues/69 17:00:40 Agenda+ Issue#29: 2.13 Grid (Simple Data Tables) - changes https://github.com/w3c/aria-practices/issues/29 17:00:41 Agenda+ Review status of current example development work https://github.com/w3c/aria-practices/wiki/Design-Patterns-Status 17:01:24 annabbott has joined #aria-apg 17:03:16 present+ Michiel_Bijl 17:03:21 regrets+ Ian_Pouncey 17:04:24 regrets+ Jon_Gunderson 17:04:33 Birkir has joined #aria-apg 17:05:18 regrets+ Byan_Garaventa 17:05:24 Is the meeting password apg or aria-apg, I tried apg in the WebEx client and got an incorrect pasword error along with the CAPTCHA. 17:05:55 present+ Birkir 17:06:25 regrets+ James_Nurthen 17:06:48 present+ AnnAbbott 17:06:49 chair: Matt King 17:07:04 present+ matt_king 17:10:42 Scribe: MichielBijl 17:11:36 zakim, drop agendum 1 17:11:36 agendum 1, Issue#12 code review guide (Ian) https://github.com/w3c/aria-practices/issues/12, dropped 17:12:10 zakim, take up agendum 2 17:12:10 agendum 2. "Issue#35: Adapt dev docs style for code examples? https://github.com/w3c/aria-practices/issues/35" taken up [from mck] 17:12:39 MK: not necessarily understand the request 17:16:44 MB: make APG more like MDN 17:16:52 MK: Not something we can do now 17:18:18 MB: So maybe something for the future? 17:18:23 MK: Yeah that could work 17:22:34 zakim, take up next item 17:22:34 agendum 3. "Issue 17 - Breadcrumb design pattern (Michiel) https://github.com/w3c/aria-practices/issues/17" taken up [from mck] 17:24:15 http://w3c.github.io/aria-practices/#breadcrumb 17:26:42 MK: Breadcrumbs aren't necessarily hierarchical 17:26:50 AA: They usually are no? 17:26:54 MB: Think they always are 17:27:23 MK: Well some pages land in different sections or categories 17:27:38 MB: True, but would still be hierarchical 17:28:47 scribe: Birkir 17:29:35 MK: Breadcrumbs are most often right aboe the main content of the page. 17:29:57 s/aboe/above 17:31:30 MK: Do we need the statement recommending ordered lists? WE generally don't recommend specific constructs unless it is particular to the interaction. 17:32:22 MB: I want to keep it in, but if you don't agree it is not necessarily necessary. 17:32:59 MK: Better to put the data structure in the examples. 17:34:10 Birkir: Most breadcrumbs I see use unordered list or div markup. 17:34:39 MB: Usually I see separators, and the lists usually use a style of bullet:none. 17:35:25 MB: The 2014 WEbAIM survey asked users to rate breadcrumb pattenrs, users prefered the ordered list one. 17:35:52 http://webaim.org/projects/screenreadersurvey5/breadcrumbs.htm 17:37:13 MK: Little difference between 1 and 2, except perhaps with Voiceover. 17:37:30 AA: More than twice as many people prefered an ordered list to an unordered one. 17:40:00 MK: WebAIM's breadcrumb examples use lists where CSS removes the bullets, which causes screen readers not to announce individual list items (though users can still navigate between them). 17:40:55 MB: I can accept removing this paragraph, rather than spending 40 minutes discussing it. ;) 17:41:15 MK: WE are not dropping the paragraph entirely, just removing the contents from the spec to the examples. 17:41:57 MB: So we agree to remove the paragraph? 17:42:27 Group agrees! MB will do the honors. 17:42:44 AA: Should we add the role="navigation"? 17:43:10 MB: Yes, put it as the first bullet under the "Aria roles and attributes" heading. 17:44:40 MK: We can create examples where breadcrumb widgets are implemented as a single tab stop. If so, refer to examples in the keyboard section. 17:45:58 Birkir: Perhasp not over recommend complex components on breadcrumb trails. 17:47:30 MK: For some scenarios (such as when we have a long breadcrumb list), a single tab stop might be beneficial. We should at least implement a plug-and-play Javascript example for a single tabstop breqdcrumb widget. 17:47:45 https://github.com/w3c/aria-practices/issues/72 17:47:53 MB: Creates issue t#72 to create one. 17:49:21 MK: We are ready to close issue 17. 17:49:32 zakim, next item 17:49:32 agendum 4. "Issue#69: Accordion Arrow Key Navigation https://github.com/w3c/aria-practices/issues/69" taken up [from mck] 17:50:53 MK: There is a problem with the code page itself, unable to see the sourcecode. 17:51:21 AA: I think designrs will push back on having the current (last) item bold. 17:51:42 MB: does not have to be bold, but should be styled different. 17:52:45 MB: Used a link here to use aria-current. 17:53:41 Birkir: Perhaps create a different breadcrumb widget where link to current page is not a link. 17:54:52 MK: Do we need multiple examples, I don't think so. 17:55:28 MB: Using aria-current gives the most information to the machine using it. 17:56:18 MK: We could sovle this by adding a note that if the last link (to current page) is implemented as static text, aria-current is not required. 17:58:01 Group agrees to add a note to current examples explaining the static text option. This should be added to the APG itself. 18:00:00 Note has been aded, courtessy of MB. 18:04:13 Onto issue 69 (item 3), the group had a detour. 18:08:41 TOPIC: nOW WE ARE DISCUSSING ISSUE 69 FOR REAL! 18:09:07 MB: So about those breadcrumbs… 18:09:36 https://github.com/w3c/aria-practices/issues/69 18:11:43 MK: Recommended change, drop the tab roles for an accordion pattern. 18:12:37 MK: We got feedback about the orientation of the tabs. 18:12:42 Link to design pattern: http://w3c.github.io/aria-practices/#accordion 18:13:13 We are replacing the accordian design pattern with one that does not use the tab or tabpanel roles. So, there will not be a nee 18:15:31 zakim, next item 18:15:31 agendum 5. "Issue#29: 2.13 Grid (Simple Data Tables) - changes https://github.com/w3c/aria-practices/issues/29" taken up [from mck] 18:16:17 MK: I was wroking on issues that An raised. 18:17:46 http://w3c.github.io/aria-practices/#grid 18:21:00 Birkir: Asking about difference btween arrow keys wrapping in data grids vs. layout grids. 18:21:43 MK: Useful when dealing with data it is useful to know that we ahve reached the end of a row or column. 18:22:29 Birkir: Was thinking specifically about datepickers. 18:23:49 MK: datepickers are a little different, we need to document that in the datepicekr pattern. 18:25:29 Bryan Garaventa's examples: https://www.linkedin.com/pulse/accessible-date-pickers-flexible-disabled-ranges-bryan-garaventa 18:27:32 MK: The introductary text indicates that the keyboard recommendations are flexible. 18:27:44 AA: Do we want to include Bryan's examples. 18:29:13 AA: Don't we want to link date pickers and grids. 18:29:32 MK: We can when we get the datepicker pattern done. 18:30:41 MK: Bryan's datepicker example is not APG ready, because it uses an external library. 18:30:59 rrsagent, make minutes 18:30:59 I have made the request to generate http://www.w3.org/2016/08/08-aria-apg-minutes.html Birkir 18:48:16 mck_ has joined #aria-apg 18:56:14 mck_ has joined #aria-apg 20:40:37 mck_ has joined #aria-apg