Meeting minutes
APG redesign project update
<Jemma> rich: isaac started is working on implementing changes with engineering team.
<Jemma> ... this coming week, we can commit the implementing those changes.
<Jemma> ... working with template change with bocoup engineering team.
<Jemma> mck: we can also talk to w3c Education and Outreach working group such as landmark issues
<Jemma> ... we would need issues to be complied to be addressed to w3c EOW.
<Jemma> rich: we will prepare separate issues for EOW
<Jemma> rich: I created the question list regarding repo inquiry by matt king
<Jemma> ... to get the direction for migration project
<Jemma> jongund: what is the update for jump to function for redesign project?
<Jemma> rich: "jump to" is noted item to the redesign project.
<Jemma> jongund: contact me if you have any question about "jump to"
<Jemma> rich: I will get back to you with timeline
<Jemma> ... due to AT project, apg redesign project will not in this sprint
<Jemma> next sprint, 10/18 will include the apg redesign project.
<Jemma> ...engineering team will look into the issues
<Jemma> mck: at app has the priority over apg redesign project.
PR discussion/working session
<Jemma> https://
jongund: I made some changes to the button description. if the button takes up the whole cell the button name and header become the same. was using ariadescribeby
<Jemma> "I changed the labels, let me know what you think.
<Jemma> The trick is not changing the accessible name of the button, otherwise the button accessible name gets used as the column name when using table navigation commands. But I am open to other ideas, But this is something that is very common and we should have some guidance in the practices." Jon's comment
<Jemma> https://
Matt_King: now when I tab to a button it is less distracting and easier to understand.
jamesn: why does last name have aria button label none of the others do?
jongund: i see, let me fix that.
jamesn: we should be consitent on all the buttons
Jemma: Bryan do need the link to the example?
Jemma: will place in chat
<Jemma> <th aria-sort="ascending">
<Jemma> <button aria-describedby="id-change-sort" data-column-index="0">
<Jemma> First Name
<Jemma> <span aria-hidden="true"></span>
<Jemma> </button>
<Jemma> </th>
Bryan: this is a standard data table. Sounds like it is valid
Matt_King: I was wondering if you thought aria-describedby is best practice.
Bryan: typically I don't have anything on the button but typically the header uses aria-sort. That provides all the necessary data for the person hearing it.
Matt_King: some people feel it is necessary to provide all the information a button does.
jamesn: do we have an aria equivalent for abbr?
Matt_King: I think aria-description might work there.
Bryan: why can't use the title attribute?
Matt_King: good question
Matt_King: do we need text labels for those things that appear on hover? If symbols have meaning do we need to provide help to people on what they mean? Especially for people with cognitive disabilities.
jongund: would you like a tooltip put in?
jamesn: I prefer simplification.
<Jemma> https://
jongund: I would caution against having too many examples.
Matt_King: then possible in the documentation talk about trade offs and then they can choose. I think two versions is enough.
<Jemma> https://
Matt_King: we will remove diamonds and show the arrow once the button is pressed/sorted. After it is sorted we want them to appear on arrow/hover.
rrsagent draft minutes