18:54:51 <RRSAgent> RRSAgent has joined #aria-apg
18:54:56 <RRSAgent> logging to https://www.w3.org/2023/01/31-aria-apg-irc
18:55:05 <Matt_King> rrsagent, make log public
18:55:25 <Matt_King> MEETING: ARIA Authoring Practices Task Force
18:55:33 <Matt_King> CHAIR: Jemma
18:55:37 <Matt_King> present+
18:55:44 <Matt_King> rrsagent, make minutes
18:55:45 <RRSAgent> I have made the request to generate https://www.w3.org/2023/01/31-aria-apg-minutes.html Matt_King
19:02:35 <Jem> https://github.com/w3c/aria-practices/wiki/January-31%2C-2023-Agenda
19:02:51 <CurtBellew> CurtBellew has joined #aria-apg
19:03:17 <Jem> scribe+ Helen
19:03:19 <howard-e> howard-e has joined #aria-apg
19:03:38 <Jem> present+
19:03:40 <howard-e> present+
19:03:47 <CurtBellew> present+
19:04:00 <Jem> Topic: Status of in-progress site updates
19:04:08 <Jem> TOPIC: Status of in-progress site updates
19:04:10 <jamesn> jamesn has joined #aria-apg
19:04:22 <helen> helen has joined #aria-apg
19:05:29 <Jem> https://github.com/w3c/aria-practices/pull/2417
19:06:09 <helen> matt: making change to pre-build script
19:06:45 <Jem> CHAIR: Matt
19:06:47 <howard-e> https://github.com/w3c/wai-aria-practices/pull/184
19:07:17 <helen> howard: restructure of the page getting reviewed
19:07:40 <helen> matt: put the redirect in place before making the change live
19:08:17 <helen> howard: next attempt to publish on Thursday and hope get things ready today
19:08:31 <jamesn> present+
19:08:58 <Jem> Work in progress on first AT support table - pull request #2569
19:08:59 <Github> https://github.com/w3c/aria-practices/pull/2569 : Button Example: Add AT support tables from ARIA-AT
19:09:15 <helen> matt: request from this task force and the AT group
19:09:57 <helen> alex: switching to Aria AP site and going through the issues
19:10:49 <Jem> In the support table cells that contain the word "None", change copy to one of the two options described below.
19:11:11 <helen> alex: looking into one issue mentioned in the table: changing "none" to "not applicable" to see if it's reasonable to quickly add it
19:11:19 <Jem> one for we don't have the data due to combination of mac and jaws and nvda
19:11:37 <Jem> the other one is where the testing results are not available yet.
19:11:47 <helen> matt: maybe make a separate issue to track it for the sake of time
19:12:10 <helen> alex: trying to get it by this week while working on the app
19:12:46 <helen> matt: that puts us on the right track for the final review
19:13:29 <helen> matt: next issues to consider: "link alert" and "radio group"
19:13:48 <Jem> In cells that contain the word "None", change copy to one of the two options described below.
19:13:57 <Jem> s/In cells that contain the word "None", change copy to one of the two options described below./ /
19:14:12 <Jem> Same level navigation on Single Pattern and Single Practice pages
19:14:47 <helen> jemma: need a template for "same level of navigation on single pattern and single practice page"
19:15:04 <helen> matt: need Shaun's input
19:15:40 <helen> matt: last week the group disucssed about bringing new talents to the project
19:16:32 <helen> matt: finding ways to broadly marketing the projects and attrack contributors
19:17:11 <helen> TOPIC: APG TF Vision Discussion
19:17:30 <helen> matt: what the template would look like for starter projects?
19:18:44 <helen> matt: what would be a good platform to use? e.g. wiki page?
19:20:35 <helen> curtis: need guidance for the format or process being used
19:21:15 <helen> matt: one potential audience is people who are already on GitHub and contributing, marketing on Github makes it easier for them
19:21:47 <helen> matt: for people who are not familiar with Github it can be a barrier
19:22:49 <helen> curtis: even people who use github may need more guidance for the review process
19:23:41 <helen> mark: when processes involve a lot of jargons, it's helpful to provide basic instructions
19:24:13 <helen> james: a list of commands for beginners to help understand the technology
19:26:32 <helen> matt: we can make a github issue for providing guidance and also something to make it easier to help people know where to start
19:29:32 <helen> matt: for the current members, query the current issues and come up with a list of potential starter projects, and then identify additional information to add
19:30:26 <helen> matt: what are potential places where we can find interested audiences?
19:35:31 <helen> matt: we can try to reach beyond the accessiblity community to those IT professionals who haven't thought about contributing to accessibility
19:36:21 <helen> curtis: come cross some broken links in the wiki
19:37:16 <helen> matt: will look into broken links
19:37:48 <helen> TOPIC: New Issue Action Planning
19:38:44 <Matt_King> new issues list: https://github.com/w3c/aria-practices/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2021-08-15+no%3Alabel++sort%3Aupdated-desc
19:39:49 <Matt_King> TOPIC: Issue 2576 Seeking advice about conditional non-radio fields appearing inside radiogroup
19:40:04 <Matt_King> github: https://github.com/w3c/aria-practices/issues?q=is%3Aissue+is%3Aopen+created%3A%3E2021-08-15+no%3Alabel++sort%3Aupdated-desc
19:40:51 <Matt_King> github: https://github.com/w3c/aria-practices/issues/2576
19:48:46 <helen> matt: the input is outside of radio group unless "other" is checked, in which case use the aria-labled by
19:49:45 <Matt_King> Advice: Place input outside radio group. Disable unless last radio is checked. Use aria-labelledby to label the input.
19:49:51 <jamesn> https://design-system.service.gov.uk/components/radios/conditional-reveal-error/index.html
19:52:30 <Matt_King> HTML is somewhat more flexible b/c canput elements between radios.
19:53:13 <Matt_King> In aria could use group instead of radiogroup, but placing intermediate elements between radios could break the aria-setsize calculation by the browser.
19:53:42 <Matt_King> Could use aria-setsize and aria-posinset to override broser calculations.
19:54:47 <Matt_King> Would be good to mock up this test case in ARIA using aria group, aria-setsize, and aria-posinset.
19:56:15 <Matt_King> TOPIC: ISSUE 2583 The aria-current docs aren't clear about how to handle a "current" nav-item that isn't a link-to-current-page.
19:56:56 <Matt_King> github: https://github.com/w3c/aria-practices/issues/2583
20:03:23 <MarkMcCarthy> MarkMcCarthy has joined #aria-apg
20:03:24 <MarkMcCarthy> present+
20:04:10 <helen> Advice: use 'aria-current="true" but the AT may have the same result as aria-current="page"
20:04:28 <helen> TOPIC: Next Time
20:04:45 <helen> Next meeting is on Feb. 7th
20:04:58 <helen> rrsagent, make minutes
20:04:59 <RRSAgent> I have made the request to generate https://www.w3.org/2023/01/31-aria-apg-minutes.html helen
20:05:57 <helen> *matt: yes, will do
21:56:15 <howard-e> howard-e has joined #aria-apg
21:57:06 <howard-e_> howard-e_ has joined #aria-apg
21:57:37 <howard-e_> @shawn the deploy PR is available at https://github.com/w3c/wai-aria-practices/pull/185
22:02:45 <howard-e_> howard-e_ has joined #aria-apg
22:03:56 <howard-e> howard-e has joined #aria-apg
23:27:46 <Zakim> Zakim has left #aria-apg