W3C

– DRAFT –
ARIAAuthoring Practices Task Force

08 November 2022

Attendees

Present
CurtBellew, jongund, Matt_King
Regrets
-
Chair
Matt King
Scribe
CurtBellew

Meeting minutes

QA for Restructure

Matt_King: before QA we need a preview link. That's on Alex's plate. An update from Alex

Alex: Preview link is not far off. Patterns pages, practices pages, homes pages etc look great. Lacking is the 'About' pages. Possibly tomorrow for a link

Alex: we may need a different PR for ARIA practices to remove transformations when they aren't needed.

Alex: That PR might be where the link will be contained

Alex -> Alexander Flenniken

Matt_King: Do we actually want to cahnge the pattern or what's on the patterns page?

Alex: The pattern. Just a few cases of altering first sentences

Matt_King: If we change the pattern page first sentence has to be done with care

Matt_King: Expecting a preview link this week

Alex: Yes

Matt_King: PR 2417. Is the PR with the preview link. We will need reviewers

Matt_King: Ideally we would have 6 people. It's a very visual review. Mostly this review is due to changes in HTML and we want to be sure the styling is preserved.

Matt_King: Comparing the existing pages to the new version. Divided up in to 3 buckets overall. Listed in the PR

<Matt_King> Link to PR 2417: https://github.com/w3c/aria-practices/pull/2417

Matt_King: Assigning reviewers. Testing to be sure all the content is visible and that functionality is not interrupted. Goal of having reviews done by November 29th 2022.

Matt_King: 60 to 90 minutes available for testing.

Matt_King: around 35 pages in each bucket. Hoping to have at least 2 people testing per bucket.

Matt_King: Alex, should testers be testing links etc

Alex: Yes. Best practice would be to test links.

Matt_King: Could the testers do a sampling of links on the page to be effective or would it be necessary to test each link.

Alex: Yes. Spot checking is adequate. We fully expect all the links to work but a sanity check is best.

jongund: I can take a couple buckets

Matt_King: Assigned reviewers - Siri, CurtBellew, jongund, Helen , Jemma

Matt_King: Adding a separate comment that will assign people to buckets. Once the preview link is ready I'll create a comment with names and buckets

Matt_King:

<siri> can you please keep issue number once again

<jongund> https://github.com/w3c/aria-practices/pull/2417

Matt_King: Let's understand the buckets . Bucket 1 - patterns page and any of the examples linked to from that pattern. Landmark regions. Practices. Home page.

Matt_King: Landmarks includes doing the landmark example pages. Linked to from the practices page

Matt_King: Bucket 2 - patterns and examples linked to. Names and descriptions and developing a keyboard interface and the index page

Matt_King: Bucket 3 - Slider through window splitter. Patterns and the About page

Siri: Will assign the buckets to us specifically?

Matt_King: yes. You'll get an update from the github system when I make the update

Siri: A comment would be great plus a comment as to when the preview available and when it's needed.

Alex: will merge the About page PR in to merge examples

Alex: the note PR - I have left a not there. I may take back some of my feedback and then work on some styling issues. Leaning towards just merging it.

Matt_King: Conflicts in PR 2417. Landmark CSS - there are 3 files that are different between branches. Two HTML files that are in conflict having to do with Landmarks

Alex: conflict between main branch and move-examples branch

Alex: ?

Alex: I'll look at each case individually

Matt_King: Yes , best idea is just to take the lines in conflict and make those inline modification directly

Matt_King: After the preview is in place an review is happening I will bookmark a bunch of pages where the URLs will be changing so I can sample the bookmarks to make sure the redirects are working.

Checkbox key repeat fix

Matt_King: We talked about checkbox fix last week. We do have some approvals to merge. Waiting for a review from Alex related to test.

Matt_King: Should we hold this until after 2417 is merged and then ask the person to rebase? or Should we merge this domain to save the new contributor this trouble?

Alex: I would be willing to 'cherry pick' the commit for the changes and merge

PR # 2518

Alex: Why on keyup instead of keydown

Matt_King: to avoid toggle repeat when key is held down

Matt_King: Ratings slider - jongund had to leave so we skip it this week

Matt_King: Navigation treeview issue. Specific to talkback. Is there anybody on this call who can test with Talkback?

All answered that nobody has access to a Talkback device.

“Radio Group Example Using aria-activedescendant” does not work in iOS/VoiceOver

<Matt_King> github: https://github.com/w3c/aria-practices/issues/2475

Matt_King: Guessing this is with quicknav turned off while using the arrow keys and space bar ?

Matt_King: It's possible that IOS is not supporting this. Bryan Garaventa , can you please test this?

Bryan: Yes. I don't use a keyboard on IOS. When you use the arrow keys it just navigates through the options rather than selecting the radio buttons

Bryan: Previous is in reference to cases where you use a bluetooth keyboard with iOS.

Bryan: In my testing it doesn't seem like the active descendant will function in this scenario

Matt_King: So there is some question as to whether or not javascript can ever receive an arrow key in this scenario

Bryan: they work in some cases. There were some cases added to the slider role for instance

Next Meeting

<Matt_King> Next meeting is November 29.

Minutes manually created (not a transcript), formatted by scribe.perl version 196 (Thu Oct 27 17:06:44 2022 UTC).

Diagnostics

No scribenick or scribe found. Guessed: CurtBellew

Maybe present: Alex, Bryan, Siri

All speakers: Alex, Bryan, jongund, Matt_King, Siri

Active on IRC: CurtBellew, jongund, Matt_King, siri