17:56:41 RRSAgent has joined #aria-apg 17:56:41 logging to https://www.w3.org/2021/07/13-aria-apg-irc 17:57:01 MEETING: ARIA Authoring Practices Task Force 17:57:11 rrsagent, make log public 17:57:16 present+ 17:57:21 rrsagent, make minutes 17:57:21 I have made the request to generate https://www.w3.org/2021/07/13-aria-apg-minutes.html Matt_King 17:57:38 CHAIR: Jemma 17:58:39 jongund has joined #aria-apg 18:01:20 Jemma has joined #aria-apg 18:02:48 present+ 18:03:01 MarkMcCarthy has joined #aria-apg 18:03:03 rrsagent, make minutes 18:03:03 I have made the request to generate https://www.w3.org/2021/07/13-aria-apg-minutes.html Jemma 18:03:07 agenda? 18:03:42 https://github.com/w3c/aria-practices/wiki/July-13%2C-2021-Agenda 18:05:01 scribe: jongund 18:05:10 sarah_higley has joined #aria-apg 18:05:13 present+ 18:05:26 https://github.com/w3c/aria-practices/pull/1830 18:05:51 TOPIC: Meeting Survey 18:06:01 MK: Is there any sruvey results 18:06:11 JK: We can look at it at the end of the call 18:06:23 TOPIC: Update Accordion example code and behavior 18:06:28 https://github.com/w3c/aria-practices/pull/1830 18:06:46 https://github.com/w3c/aria-practices/pull/1834 18:07:02 TOPIC: Draft: Two accordion examples, one basic and one of a group with only one open accordion 18:07:09 https://github.com/w3c/aria-practices/pull/1834 18:07:31 SH: The issue raised with macOS is a known issue 18:07:36 MK: What happens 18:07:59 SH: It exposes the heading weirdly, some times the button and sometimes the heasing 18:08:19 SH: I have run into this problem before, and Apple knows about it 18:08:28 CurtBellew has joined #aria-apg 18:08:41 MK: We will see what happens when this get in the ARIA-AT project 18:08:45 present+ 18:08:53 present+ jongund 18:09:04 MK: It is not something we can change 18:09:33 SH: I have talked to people who think this is a problem, but Apple has not addressed the issue 18:09:45 MK: Does Chrome behave differently? 18:10:12 MK: Usually this type of issue is not browser dependent 18:10:25 JK: We need for people to complete their reviewes 18:10:28 siri has joined #aria-apg 18:10:42 MK: We will address the issue with ARIA-AT 18:11:05 SH: This bug has not seemed to gain any traction at Apple 18:11:51 MK: We need to updated the pending reviewers in GitHub 18:13:32 "At the APG meeting today is was suggested to remove the aria-required and aria-hidden from the standard form controls, since they are not needed for the accordion pattern and increase the amount of documentation and testing for the example." 18:13:55 SH: There were some comments and I will do an update 18:14:08 MK: We should wait for the changes 18:14:14 SH: I will make them today 18:14:33 https://github.com/w3c/aria-practices/pull/1834 18:15:35 TOPIC: Listbox Deprecation Warning 18:15:43 https://github.com/w3c/aria-practices/pull/1852 18:15:53 MK: I left comments, where they addressed? 18:17:07 JG: The checklist needs to be removed, we are only reviewing the label 18:17:15 https://github.com/w3c/aria-practices/pull/1852#issuecomment-833903987 18:17:38 "1. Prepend (Deprecated) to title tag and H1 18:17:38 2. Remove link from main doc and other example pages" 18:17:48 MK: When we deprecate the example, we should remove links o the document, we do not need to document in the APG that it is deprecated 18:17:57 MK: Does this PR remove the links? 18:18:36 JN: I am super confused about the new link, the example it points to is not deprecated 18:18:45 MK: I want to completely remove that links 18:18:57 JN: We need to link to the new combobox 18:19:24 MK: We have that link in the combobox section, I don;t think we should have a link from listbox 18:19:45 present+ Jamesn 18:19:49 JN: We could have a addtional links, people are use to looking for it in listbox 18:20:01 present+ curtbellew 18:20:04 MK: For this PR to keep it simple, we should just remove it 18:20:09 JN: That's fine 18:20:09 present+ Siri 18:20:26 MK: Is it removed from the other listbox example pages? 18:20:52 MK: In this PR can you removed the links in related examples? 18:20:55 SH: Yes 18:20:59 present+ 18:21:28 TOPIC: Coverage Report Update 18:22:34 jon: my request is about github.io so that this can have the most updated info about apg example coverage 18:23:05 mck: it would be beneficial to have updated automatically 18:23:24 s/have updated/have the coverage report updated/ 18:25:12 MK: First step is to get it automatically updated in GitHub actions 18:25:17 action items: 1)run the report automatically, 2) add report info to wiki and readme. 18:25:17 Error finding 'items'. You can review and register nicknames at . 18:27:00 Action: Jemma will create the issue for Simon to run the coverage report script automatically 18:27:01 Created ACTION-2156 - Will create the issue for simon to run the coverage report script automatically [on JaEun Jemma Ku - due 2021-07-20]. 18:27:02 coverage-report.js 18:27:47 Action: Jemma will add coverage report url to readme and wiki. 18:27:47 Created ACTION-2157 - Will add coverage report url to readme and wiki. [on JaEun Jemma Ku - due 2021-07-20]. 18:28:29 Topic: Expedited Review Update 18:29:53 jon: looking for new process to experdiated review. One idea may be setting some designated time for the review. 18:30:13 s/experdiated /expidited 18:32:25 mck: we have been priortizing the works and trying to go with sequence depending on the PRs 18:32:52 jon: what is your current rate of PR review/merge process? 18:33:44 mck: according to the second half of 202*, we processed 47(?), non npm issues. 18:36:43 jamesn/mck: we don't have enough reviewers to meet with expectation 18:37:00 ... but quality of doc is very important. 18:37:12 jon: how about community group's help? 18:37:58 jamesn: As aria re-chartering is near, may we add community group idea to new charter? 18:39:26 mck; I think the bigger charter question may be a joint task force with community group or only community group. but I have concern for adding w3c contact staff support to community group. 18:39:53 mck: we can name it as APG feedback community group? 18:41:39 jamesn: if we were to set something up, we can consider how we are going to recruit the right quality of people. 18:42:34 mck: I am really interested in recruiting the accessibility engineers, consultant to ensure the quality of the work 18:43:05 ...recruitng, onboarding and training should be added. 18:43:36 we need support on functionality and reviews. 18:45:21 sarah: only reviewing changes may be helpful(narrow down the scope of the review) 18:46:00 ... solicit reviews from wide range of audience 18:47:35 summary of topics: quality of work, more reviewers, commitment 18:48:41 curt: lack of resources which conflicting with full time job is the issue. 18:49:23 mark: I tried to recruit other people but they have the same challenges of conflicting resources. 18:49:42 jon: instead of weekly meeting, we can assign one week only for reviews. 18:50:06 james: would you like to use aria deep dive session for that? 18:50:52 mck: having some meeting time to excercise different accessibility will be good. 18:51:42 such as functionality, visual, and other review except code review. 18:52:05 siri: I like Jon's idea to utilize one aria meeting time. 18:52:21 and we provide the input/feedback about the example 18:52:48 ... document known issues so that we can avoid duplicate work. 18:53:46 Topic:Tooltip design subgroup 18:55:54 Jon: we can pull someone out of APG to get help 18:56:16 mck: we can reach out to WAI 18:58:13 sarah: one month to indicate the interest and then start the work? 18:58:35 mck: yes, that is reasonable. 18:59:00 jamesn: sarah can reach out to specific a11y slack channel 19:00:31 rrsagent, make minutes 19:00:31 I have made the request to generate https://www.w3.org/2021/07/13-aria-apg-minutes.html Matt_King 20:26:01 Zakim has left #aria-apg