– DRAFT –
Accessibility Guidelines Task Force Facilitators Coordination Call

Understanding Updates

<jallan> kw: reviewing techniques, apply or not, update as needed.

<jallan> ... some understandings nearing completion. should have wrapped up tomorrow.

<jallan> kw: are you looking for techniques to be done before understanding

<jallan> awk: don't need either to be done to review the other (technique vs understanding)

<jallan> awk: need examples. they may point to techniques

<jallan> ... they are not linked.

<jallan> kw: feedback on Understanding may inform techniques

<jallan> awk: if you have some docs that are ready send them to the group

<jallan> awk: need the AG to review

<jallan> kw: have 5 to review.

<jallan> kp: made changes to single key.

<jallan> awk: send address where AG can review

<jallan> ... then add to survey

<jallan> awk: will make surveys ready.

<jallan> awk: techniques on mobile.

<jallan> kw: secondary. focus on Understanding

<jallan> awk: let me know which Understanding Docs (UD) to release

<jallan> kp: after Thursday call?

<jallan> awk: for each UD, in its branch. the TF may have their own branches.

<jallan> kp: most in main branch.

<jallan> kw: have a local copy. need to merge. Detlev has pointer ones in a separate branch

<Kathy> https://‌rawgit.com/‌w3c/‌wcag21/‌pointer-cancellation/‌understanding/‌21/‌pointer-cancellation.html

<jallan> awk: hope that I can create surveys for UD branches rawgit.../UDTitle.html

<Kathy> https://‌rawgit.com/‌w3c/‌wcag21/‌pointer-cancellation/‌understanding/‌21/‌pointer-cancellation.html

<Kathy> https://‌rawgit.com/‌w3c/‌wcag21/‌motion-actuation/‌understanding/‌21/‌motion-actuation.html

<Kathy> https://‌rawgit.com/‌w3c/‌wcag21/‌concurrent-input-mechanisms/‌understanding/‌21/‌concurrent-input-mechanisms.html

<jallan> kp: edit from AG chart.

<jallan> awk: only an issue if forked, then the TF needs to merge into understanding branch

<jallan> ... then TF will say its ready and then awk will merge into master

<jallan> awk: work from chart, edit in that branch.

<jallan> ac: My Github approach working from a fork - save the file(s) with your changes somewhere outside the clone, nuke it, re-clone it from the W3C's, and put your changes back in. Then merges are fine.

<Kathy> https://‌github.com/‌w3c/‌wcag21/‌edit/‌target-size/‌understanding/‌21/‌target-size.html

<jallan> kw: if I edit. then I commit, get two radio buttons, 1 commit directly, 2 commit to a branch

<jallan> awk: most of the time choose 1

<alastairc> I think: Changes to understanding need to go into the SC's branch. Techniques or variants should be on new branches from the SC branch.... then get merged back in to the SC branch when approved.

<jallan> awk: if different radical idea, then choose 2 with additional hyphens in the name, so others can review, then merge, then merge with master

<Zakim> MichaelC, you wanted to ask why forks needed?

<jallan> mc: do we have to make forks. they are complicated

<jallan> awk: haven't been able to stop folks using branches.

<jallan> mc: would like to move people away from forks

<jallan> awk: edit in online editor. tho mentally taxing

<jallan> kp: an add on wold be useful.

<jallan> kw: leaves. the three urls above are ready for review

<jallan> kp: single character also ready

<jallan> https://‌rawgit.com/‌w3c/‌wcag21/‌text-spacing/‌understanding/‌21/‌text-spacing.html

<AWK> (Pointer Cancellation, Concurrent input mechanisms, motion actuation, and single character - are ready from MATF)

<jallan> https://‌rawgit.com/‌w3c/‌wcag21/‌reflow/‌understanding/‌21/‌non-text-contrast.html

<AWK> (Text spacing, and non-text contrast are ready - add caveat for NTC one that it is still needing more active review and changes)

<jallan> ac: early review would be useful

<jallan> rrsagent: make minutes

<jallan> awk: need WG engaged including TF members not normally engaged in WG meetings

<jallan> ac: perhaps making shorter surveys

<jallan> awk: have time to move at reasonable pace... for now

<jallan> mc: have an approval survey open for weeks...

<jallan> ... one big survey, folks can fill in as they get to it. also weekly review one or two.

<jallan> ac: could be difficult to track in survey if folks change their minds

<jallan> rrsagent: make minutes

<jallan> mc: survey with yes/no and force comments to github

<jallan> ... at sometime need WG approval for each UD. and have EO waiting to suggest edits

<jallan> rrsagent: make minutes