– DRAFT –
ARIA Authoring Practices Task Force

<Jemma> Meeting Topic: https://github.com/w3c/aria-practices/wiki/April-20%2C-2021-Agenda

setup and reviewing agenda

<Matt_King> Next meeting is next tuesday

ARIA APG redesign project

<Jemma> https://wai-aria-practices.netlify.app/aria-practices/

<Matt_King> jemma: that is url for mock up of phase 1

<Matt_King> mk: this all very tenatitive, that is the mock up is

<Jemma> https://github.com/bocoup/wai-aria-practices

<Matt_King> just a starting point for discussion.

<Matt_King> This repo has all the docs

<Matt_King> We have meeting tomorrow afternoon

<Matt_King> It is a planning/admin meeting with bocoup and w3c staff.

APG index page

<Jemma> https://github.com/w3c/aria-practices/pull/1859

<Matt_King> jg: the aria-lable indexing now works

<Jemma> https://raw.githack.com/w3c/aria-practices/update-example-index/coverage/index.html#example_coding

<Jemma> https://raw.githack.com/w3c/aria-practices/update-example-index/coverage/index.html

<Matt_King> Added a new table in coverage report to document which components use prototype or class and whether they use svg, and whether force color adjust is used, and where before and after pseudo classes are used.

<Jemma> https://www.irccloud.com/pastebin/LPlU1MuQ/

<Jemma> CSV Files of Role, Properties and States Coverage

<Jemma> Roles with no Guidance or Examples (27)

<Jemma> Roles with at Least One Guidance or Example (9)

<Jemma> Roles with More than One Guidance or Example (33)

<Jemma> Properties and States with no Examples (24)

<Jemma> Properties and States with One Examples (15)

<Jemma> Properties and States with More than One Example (9)

<Jemma> Example Coding Practices

<Matt_King> Example: 22 examples use svg

<Matt_King> Also documents which use keycode

<Matt_King> Carolyn: should we also document mouse vs pointer events

<sarah_higley> so pessimistic. I bet we can merge by 2049!

<Matt_King> sarah: just about to submit a review

<Matt_King> A few minor syntax issues

<Matt_King> Jemma: when report gets run?

<Matt_King> jg: it is manual, not part of a process now.

<Jemma> matt: we may be able to merge this by next week.

Slider

<Jemma> after the review by Sarah and work by jon

<Jemma> https://github.com/w3c/aria-practices/pull/1857

<Matt_King> jemma: James Choels left some commnts

<Matt_King> jg: added seek slider

<Matt_King> do we want 2 sliders in separate examples?

<Jemma> https://github.com/w3c/aria-practices/issues/1847

<Matt_King> and, the seek slider represents 5 minutes, and valuetext reps minutes and seconds

<Jemma> "In aria-valuetext, the number of seconds is zero-padded so you get announcements like, "1 minute 0 0 seconds" and "2 minutes 0 5 seconds"."

<Jemma> https://github.com/w3c/aria-practices/pull/1857#issuecomment-820771593

<Matt_King> Temperature slider is fixed point decimal with the word degress appended.

<Jemma> example is https://raw.githack.com/w3c/aria-practices/slider-valuetext/examples/slider/slider-valuetext.html

<Matt_King> James asked if the value should include range info, like 1 minute of 5 minutes?

<Matt_King> mk: talk about should we have sperate pages for each slider

<Matt_King> jg: makes it easier to manage code and maybe easier to read

<Matt_King> jemma and marc: agree

<Matt_King> easier to read

<Matt_King> jg: info spread across more pages, e.g., have to look at multiple pages for all info about valuetext

<Matt_King> mk: I think one example per page for simplicity

<Jemma> https://github.com/w3c/aria-practices/pull/1857#issuecomment-820771593

<Jemma> "Do we want the seek bar to indicate the maximum value (i.e. the total duration) in its value text? For example, "1 minute 30 seconds of 5 minutes"."

<Matt_King> mk: now what about the question of range info in the valuetext value?

<Matt_King> jg: example: should valuetext be like 1 min of 5 min

<Jemma> car: it would be pretty verbose

<Jemma> adding info of max value

<Jemma> ...users would need to hear just once of max value

<Matt_King> mk: could there be downsides to putting range info in a valutext if people do this this consistently across patterns

<Matt_King> carolyn: Maybe do this on initial focus, but then not repeat it as you change the value so it is not repeated over and over

<Matt_King> mk: I think that is a really good idea

<Matt_King> mk: How about we provide it on focus but then when the value changes, either automatically or by icrement, the range info is not repeated

<Matt_King> jg: A focus event would add the info and then the move to function would not.

<Matt_King> Might be hard to explain to other people

<sarah_higley> +100 to "we need to realize that not everything we write, people are going to read"

<Matt_King> Need to have clear documentation.

<Matt_King> mk: would be part of accessibility features section

<Matt_King> Siri: Should valuemin and max be in minutes or seconds?

<Matt_King> Right now in seconds

<Matt_King> jg: that is part of reason for using valuetext, because seconds is hard to understand

<Matt_King> jemma: do we have consensus on including max in valuetext on focus?

<Matt_King> Downside is needs documentation, that is a bit complex\

<Matt_King> upside: Gives more info to users

<siri> hearing the 1 min 20 sec out of 300 might be confusing

<Matt_King> curt: reminds me of how grouping works, reports it on initial focus

<MarkMccarthy> +1 Curt

<Jemma> +1

<Jemma> to Curt

<Jemma> This is the case of Media Seek slider - avoid verbosity and still add max value of the slider in meek slider example

<Matt_King> Jemma: let's give it a try

<siri> acting like legend in fieldset :)

<Jemma> https://github.com/w3c/aria-practices/pull/1857#issuecomment-820771593

<Matt_King> jg: OK, will do that and then separate into two example pages

<Matt_King> Jemma: what about James' ther feedback; already addressed.

Jumpto

Jemma: where are we for this feature?

Jon: I updated the PR, it's added using the app.js script, which adds it to all the examples now

<Jemma> https://github.com/w3c/aria-practices/pull/1860

MK: what else is in app.js?

Jon: app.js has support notices and stuff

Jon: so, it has an IIFE to...

(general looking up code words)

<Jemma> https://github.com/w3c/aria-practices/blob/main/examples/js/app.js

MK: it's not that important , since this stuff is almost certainly going to get redone as part of the redesign project. We should have somebody do a code review here

Matt: I think from functionality from what I looked at, it was already good

MK: we should get a code review on that one

Accordion example

Jemma: accordion example, this is Sarah's example

<Jemma> https://github.com/w3c/aria-practices/pull/1830

<Matt_King> There are 2 sub PRs as well

<Matt_King> They are linked in referenced examples

<Matt_King> Removed arrow keys to move between heading

<Jemma> General cleanup:

<Jemma> Updates JS file to a class syntax

<Jemma> Update classnames to be lowercase

<Jemma> Fix some border-radius issues in focus styling

<Jemma> Updated example page wrapper id attributes to match other example pages

<Jemma> Behavior changes:

<Jemma> Removed arrow key and force-one-open functionality

<Jemma> Updated tests to reflect behavior change

<Jemma> Removed section that talked about focus styling for "enhanced keyboard interaction"

<Jemma> Removed arrow key/home/end rows in example page keyboard table

<Jemma> Removed aria-disabled row in example page attributes table

<Matt_King> sarah: Might have also removed the requirement that one open at a time

<Jemma> 1830 resolve https://github.com/w3c/aria-practices/issues/1819

<Matt_King> sarah: now have version where all canbe collapsed.

<sarah_higley> SH: So this is from the discussion we had earlier, where I removed the arrow key to navigate between headings

<Matt_King> two different ways: one is by having a switch and one is by having 2 sperate examples

<Matt_King> mk: you gave the group a menu of choices--what way do we like better?

<Matt_King> sarah: yes

<Jemma> https://github.com/w3c/aria-practices/pull/1834

<Matt_King> the 2 different draft examples are 1833 and 1834

<sarah_higley> the two different options for supporting only-one-at-a-time accordions are https://github.com/w3c/aria-practices/pull/1833 and https://github.com/w3c/aria-practices/pull/1834

<Jemma> https://raw.githack.com/w3c/aria-practices/accordion-step-example/examples/accordion/accordion.html

<Matt_King> we need to choose one oor the other of those

<Matt_King> which one does the group like better

<Jemma> https://raw.githack.com/w3c/aria-practices/accordion-step-example/examples/accordion/accordion-group.html

<Matt_King> mk: the arrow key change is independent?

<Jemma> remove arrow key and update documentation for #1830

<sarah_higley> MK: so the one that removes arrow keys, we can just merge that one, and then talk about the two drafts later?

<Matt_King> sarah: yes, changes key behavior and updates the code and documentation. code not uses a class

<Matt_King> james: We shouldn't merge arrow key behavior without making all sections collapsable

<Matt_King> sarah: I can make that change

<sarah_higley> JN: let's first make it so you can collapse the first section, then we can merge

<sarah_higley> MK: we should merge 1830 first, then choose between 1833 and 1834 as the next

<Matt_King> mk: we should merge 1830 first and then choose between 1833 and 1834 as next step

<Matt_King> sarah: the version that forces one open at a time is a step by step process, kind of like a wizzard.

<Jemma> https://raw.githack.com/w3c/aria-practices/accordion-step-example/examples/accordion/accordion.html

<Matt_King> the other one is just presentation of content

<Matt_King> jemma: let's have people look this week and then make a decision next week

<sarah_higley> Jemma: Next meeting, we'll choose one of the two options

<Matt_King> or make decision now?

<Matt_King> carolyn: I think it makes sense to have it on next week's agenda

<Matt_King> Carolyn: one other topic, seems like the editor's draft seems out of date

<Jemma> https://w3c.github.io/aria-practices/

<Matt_King> seems like it broke wen we changed from master to main

<carmacleod> https://github.com/w3c/aria-practices/issues/1853

<Matt_King> mk: whenever we merge to main, the editor's draft should be updated