Meeting minutes
<Jem> https://
Status of in-progress site updates
Status of in-progress site updates
<Jem> w3c/
matt: making change to pre-build script
<howard-e> w3c/
howard: restructure of the page getting reviewed
matt: put the redirect in place before making the change live
howard: next attempt to publish on Thursday and hope get things ready today
<Jem> Work in progress on first AT support table - pull request #2569
<Github> w3c/
matt: request from this task force and the AT group
alex: switching to Aria AP site and going through the issues
<Jem> In the support table cells that contain the word "None", change copy to one of the two options described below.
alex: looking into one issue mentioned in the table: changing "none" to "not applicable" to see if it's reasonable to quickly add it
<Jem> one for we don't have the data due to combination of mac and jaws and nvda
<Jem> the other one is where the testing results are not available yet.
matt: maybe make a separate issue to track it for the sake of time
alex: trying to get it by this week while working on the app
matt: that puts us on the right track for the final review
matt: next issues to consider: "link alert" and "radio group"
<Jem> Same level navigation on Single Pattern and Single Practice pages
jemma: need a template for "same level of navigation on single pattern and single practice page"
matt: need Shaun's input
matt: last week the group disucssed about bringing new talents to the project
matt: finding ways to broadly marketing the projects and attrack contributors
APG TF Vision Discussion
matt: what the template would look like for starter projects?
matt: what would be a good platform to use? e.g. wiki page?
curtis: need guidance for the format or process being used
matt: one potential audience is people who are already on GitHub and contributing, marketing on Github makes it easier for them
matt: for people who are not familiar with Github it can be a barrier
curtis: even people who use github may need more guidance for the review process
mark: when processes involve a lot of jargons, it's helpful to provide basic instructions
james: a list of commands for beginners to help understand the technology
matt: we can make a github issue for providing guidance and also something to make it easier to help people know where to start
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
matt: what are potential places where we can find interested audiences?
matt: we can try to reach beyond the accessiblity community to those IT professionals who haven't thought about contributing to accessibility
curtis: come cross some broken links in the wiki
matt: will look into broken links
New Issue Action Planning
<Matt_King> new issues list: https://
Issue 2576 Seeking advice about conditional non-radio fields appearing inside radiogroup
<Matt_King> github: https://
<Matt_King> github: w3c/
matt: the input is outside of radio group unless "other" is checked, in which case use the aria-labled by
<Matt_King> Advice: Place input outside radio group. Disable unless last radio is checked. Use aria-labelledby to label the input.
<jamesn> https://
<Matt_King> HTML is somewhat more flexible b/c canput elements between radios.
<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.
<Matt_King> Could use aria-setsize and aria-posinset to override broser calculations.
<Matt_King> Would be good to mock up this test case in ARIA using aria group, aria-setsize, and aria-posinset.
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.
<Matt_King> github: w3c/
Advice: use 'aria-current="true" but the AT may have the same result as aria-current="page"
Next Time
Next meeting is on Feb. 7th