W3C

- DRAFT -

ARIA Authoring Practices Task Force

29 Sep 2020

Attendees

Present
mck, ZoeBijl, Jemmaku, jongund, JamesN, Carmacleod, MarkMccarthy, bryan
Regrets
Chair
SV_MEETING_CHAIR
Scribe
Jemma

Contents


<mck> CAIR: Matt King

Meeting Agenda: https://github.com/w3c/aria-practices/wiki/September-29%2C-2020-Agenda

ok.

Next meeting is scheduled for 10/13

Future meeting agendas

TPAC meeting on APG Redesign

Thursday Oct 15, 8:00 AM Pacific for 1 hour 45 minutes.

Meeting agenda WAI/ARIA APG Redesign/ - W3C Wiki

https://www.w3.org/wiki/WAI/ARIA_APG_Redesign/#ARIA_APG_Redesign

mck: please bring the your idea to the meeting.

<jamesn> /me it is free though

<carmacleod> Registration: https://www.w3.org/2002/09/wbs/35125/TPAC2020/

jamesN: who will be chairing the meeting?

mck: I will raise the question about the chair via ongoing email thread.

Status of 1.2 release 1

https://github.com/w3c/aria-practices/wiki/APG-1.2-Release-1-Plan

Target date is November

<scribe> Completed Priorities:

Combobox pattern and examples project: Revise to support 1.2 specification and significatnly improve quality.

Carousel project: Add tabbed carousel example and incorporate feedback about the pattern.

Guidance for range related properties

Work in Progress:

Revise Navigation Tree Example to match Disclosure Navigation Example · Issue #1526 · w3c/aria-practices

Guidance for aria-level

Codepen Button Implementation Project

other editorial issues

other bugs

mck: I am working on change log and updating milestones
... what do you think about "Revise Navigation Tree Example to match Disclosure Navigation Example · Issue #1526 · w3c/aria-practices", Jon?

jon: 80% is completed.

Mck: Guidance for aria-level is almost done by me, just some language tone.

jemma will look into bug list for this milestone.

Update on APG examples code review documentation

we will discuss this next time when Sarah attends the meeting

Update on infrastructure changes

<scribe> Completed so far:

Support for Codepen button

Using GitHub Action for regression test, ESLint, Stylelint, and deploy

Regression coverage report now showing in a PR comment

Fixed Dependabot

mck: one is the spelling check

<jamesn> /me https://idsgn.dropmark.com/107

<carmacleod> Spell-check PR: https://github.com/w3c/aria-practices/pull/1520

<ZoeBijl> jongund: if you send me the PR I can add some content :)

mck: I am proposing to use spelling check in the testing procedure. It will fail the testin if there is misspelling.
... is there any veto for above suggestions?
... Spell check will be easy to fix because misspelled word will be shown in file.

jon: can we complie all the high contrast support example in one place so that people can find those easily?

can we add data tag of high contrast verified to Jon's index of APG example page?

mck: index can be the tracking of those examples.

jon: Chrome is coming with HCM(high contrast mode) and I am not sure whether our examples can be still valid

james and car: we can use Edge and firefoxfor high contrast with white and black and HCM testing will be done.

mck: regarding Jon's feedback on adding general css to codepen

jamesn: we can use external css so that it can be consumed by codepen.

mck: can James and Zoe add your feedback on css to the issue?

https://github.com/w3c/aria-practices/pull/1532

WIP:

Make spelling a failing check? Infrastructure: Convert spellcheck to GitHub Action by nschonni · Pull Request #1520 · w3c/aria-practices

Need review - Codepen button should show only when resources loaded by spectranaut · Pull Request #1533 · w3c/aria-practices

CSS feedback from Jon - Add codepen button to examples - part 1! by spectranaut · Pull Request #1532 · w3c/aria-practices

CI for examples/index.html syncing, swwitch HTML linting to GitHub Actions FYI:

How to add the Open In Codepen button to an example page · w3c/aria-practices Wiki

May want to include codepen changes in in-flight PRs to existing examples. If so, move appropriate card in the Codepen Button Implementation Project

Keyboard nav among sections

https://github.com/w3c/aria-practices/issues/130#issuecomment-700278041

mck: redundant use of F6 key in various platform causes problem
... I am leaning toward of flexibility of using key for sections - not necessarily focus on landmark region. F6 is also used for dialog.
... I am wondering whether option key is a good modifier for F6 key.

james: MacOS would not need a modifier.

<jamesn> s/iOs/MacOS

mck: This was one of blocker for creating non-modal pattern.
... it is something should be done by author(developer)

Develop example of window splitter design pattern #130

Review open pull requests

1. Update menubutton examples: High Contrast Support and APG Coding Practices by jongund · Pull Request #1401

2. Color Picker Slider Example: Improve high contrast support, Conformance with APG coding practices, and mobile support by jongund · Pull Request #1472

mck and Jemma: we will work on closing above two PR

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/09/29 19:02:39 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision of Date 
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Succeeded: s/firsfox /firefox/
Succeeded: s/learning/leaning/
Succeeded: s/iOs/iOS/
FAILED: s/iOs/MacOS/
Succeeded: s/iOS/MacOS/
Succeeded: s/brian/bryan/
Present: mck ZoeBijl Jemmaku jongund JamesN Carmacleod MarkMccarthy bryan
No ScribeNick specified.  Guessing ScribeNick: Jemma
Inferring Scribes: Jemma

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth


WARNING: No date found!  Assuming today.  (Hint: Specify
the W3C IRC log URL, and the date will be determined from that.)
Or specify the date like this:
<dbooth> Date: 12 Sep 2002

People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.


WARNING: IRC log location not specified!  (You can ignore this 
warning if you do not want the generated minutes to contain 
a link to the original IRC log.)


[End of scribe.perl diagnostic output]