W3C

– DRAFT –
ARIA Authoring Practices Task Force

13 December 2022

Attendees

Present
isaacdurazo, Jem, jongund, Matt_King
Regrets
-
Chair
-
Scribe
jongund, MarkMcCarthy_

Meeting minutes

<Jem> https://github.com/w3c/aria-practices/wiki/December-13%2C-2022-Agenda

Next meeting

JK: Next year is our next meeting

MK: I have a risk qwith 10 January meeting

MK: Bocup contract should be in place for next year

PR 2417

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

MK: All the reviews are done, and it is in the publication branch, Alex can you explain

Alex: I am not sure what the error was in publishing

Alex: Steve said he will let me know, he said now it works in testing

Alex: Since SH did not share the exact error, it might be an environment issue

Alex: Not a simple situation

MK: We might be able to delpoy later this week

Alex: I did put Thursday as the date, hopefully Steve can help

<Jem> https://github.com/w3c/wai-aria-practices/pull/174

MK: here are 70 some redirects, so we need to work with this other person

MK: A bunch of pages are going to change URL, but it all needs to happen at the same time

MK: It may go live this week

Alex: I really want it to go live

MK: Me too

MK: We need to make sure there are no new merges in to the APG

Alex: Any new merges would be not the significant, so I think it would be ok

Design Update and Implementation Schedule

<Jem> https://github.com/w3c/aria-practices/issues/2535

<isaacdurazo> https://github.com/w3c/aria-practices/issues/2535

<Jem> isaac has updated version on the issue 2535

<Jem> Group talked about having new wai template which can accomodate left section, not hacking the existing wai template.

<Jem> Alex will look into how to suggest new APG template to update patterns page.

JK Wrap up the design an what can be done

JK: WAI template does not accomodate the left section

MK: I added an issue, let's avoid hacks

New about page

MK: I have a draft PR for the about page

PR#2558

MK: We might need to talk about this next years, we need to apply the new list view to the about page

MK: We do not have a preview link for this page yet

<Jem> https://github.com/w3c/aria-practices/issues/2423

AF: We need to get the preview links updated first

MK: If I merge this and then rebase, will it appear

AF: I should work

AF: It should work

MK: I would love it if we could get the design implemented so we could preview if soon

MK: It will have a standalone intro, separate acknowledgements, and more separate pages

MK: There is going to be some content for people to review

AF: Changes to the URL strucutr will require some changes to the APG repo

MK: Becasue we are adding in new pages?

AF: The new pages and the cards

MK: Let's coordinate on those things, but let's work on a preview before the end of the year

MK: There will need to be reviewers for the changes

MK: There is thumbs up between the cards and list view

MK: Will it be another template thing?

AF: That all within main so we have total control

<isaacdurazo> https://github.com/w3c/aria-practices/issues/2534

MK: So we have the read this first and then we are going to have ... what we want wrapped around that for accessibility

MK: We have the heading for the very first practice, so we are going to sandwich something between there

Issac: It belongs to the list of patterns

MK: A screen reader user can't

MK: MK: We could have an off screen H2

ID: There is something to tthe list of patterns

I need to leave again for a few minutes

I am back

MK: The placeholder would be redundant

ID: Can that label be off screen

MK: WHat would people do

MM: Consisten visible label, no off screen

ID: What is the reason for the persistent label?

MM: It enhances for everyone

JG: I think placeholder is bad, use visible label

MK: I think this can move up in the list

MK: Will span with role=header be detected by skipto

JG: The current script will not, but 5.1 it should

MK: The visible label for the filter field will be styled a little different

MK: Is it a problem to put a different class on the h2

AF: we can do that

AT Support tables

MK: JAWS 2023 will not be released until next week

MK: We will only have Jaws 2022 results for button and ...

MK: This a high priority

AF: The first priority is the support levels

MK: Exactly

AF: My vision is limted right now

MK: Is there an ETS for the support tables

AF: There is a meeting today to talk about the implementation

AF: About a week

MK: Can people sign up for a review for the preview

JK: I can

JG: I can

MK: So that is all we need for this topic

Rating slider

<Jem> https://github.com/w3c/aria-practices/issues/2501

<Jem> discussion of deprecating the rating slider

<Jem> jon: the goal of example is showing how to use ARIA.

<Jem> mck: how about 10 rating example?

<Jem> jon: radio pattern just use arrow key,

<Jem> rating slider can use home and end button

<Jem> ...rating scale is the scale, not radio selecton

<Jem> mck: how about modifying the rating scale as 10 point ones.

<Jem> jon: I can modify the example as more of rating survey

<Jem> mck: I don't enjoy the radio rating in the table

<Jem> mck: in 10 radio scale, you can easily jump into the middle point but rating example can do that.

<Jem> jon: making rating slide be more rating scale would be the compelling example.

<Jem> ... then we can differentiate two examples between raido and slide with X factor and show new features can be used for other use case.

rrsagent draft minutes

<Jem> rragnet, make minutes

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

Diagnostics

Maybe present: AF, Alex, ID, Issac, JG, JK, MK, MM

All speakers: AF, Alex, ID, Issac, JG, JK, MK, MM

Active on IRC: isaacdurazo, Jem, jongund, MarkMcCarthy_, Matt_King