See also: IRC log
<scribe> Scribe: Birkir
MK: We have no Jon on the call, nor a Bryan for that matter.
Bryan shows up in the nick of time.
MK: Any updates on example work, something to share, progress report or questions.
Bryan, work is on track.
<jamesn> advance regrets from me for 7/25, 8/1 and 8/8
MK: James, delete header and otehr goodies from row 13 and put Matt's name on the grid.
MK Need to meet my gridual commitments to Fred and others.
JN: For complex content the example could be implemented using the feed role.
MK: I need a date (for the assignment).
JN: I'll at least put in a year.
MK: Looks like some of the next couple of meetings should be canceled.
July 25th meeting to be canceled, August 1st tentative, should resume on the 8th.
Purpose, make it easier for people to contribute.
<mck_> https://github.com/w3c/aria-practices/wiki/APG-Editorial-Style-Guidelines
1. Editorial. 2. contributing examples (we hope to be able to farm some of taht work out).
For editorial, see wiki page (link in chat log).
MK: See page for examples,
techniques and other editorial related tasks.
... Page should not be too contravertial, but questions are
welcome.
JN: There are some problems,
including style and wording (should be consistent across the
different sections).
... We need to put a link in here explaining how to link to
ARIA states and properties.
JN to take on that task!
Next step: Create an overview of repository and where things are located (Jon is working on that).
<IanPouncey> https://ianpouncey.github.io/code-guide/
Ian has been working on documentation on how to contribute and review code examples. Enter Ian.
IP: Posted link into the IRC
chat.
... Go for readability and familiarity, expandability and ease
of maintenance (performance is bottom of that list).
MK: What about compatibility?
IP: Perhaps use a table or grid for this. Or just a compatibility statement in text.
MK: What about relying on CSS/ECMA compatibility rather than browser compatibility.
IP: I think browser support is a better approach. We need to find out the best way to note this.
MK: Brwoser versioning gets old quickly.
IP: What about phrasing it more
along the lines of "works in latest versions of browser x", at
the time of contribution.
... That means we are assuming that if an example works in
browser version x it will work in more recent versions of said
browser.
MK: Get uncomfortable if we start
trakinc too many browsers. Chrome/Firefox work on both Windows
and Mac.
... From 11y perspective. There is little advantage to asking
people to test examples in IE.
... That can change over time.
... REcommend taht people take time to review Ian's
contribution pge and provide feedback.
IP: Consistency in formating is important. Consistency is key.
HN: Confused about the IE compatibility mode section.
IP: If we are not too worried about IE we could take out this section.
Discussion about IE and meta tags ensues, including swear words such as "IE7",.
JN: Recommends removal of section.
MK/Birkir agree dropping the section.
IP: Need feedback on the Javascript generated markup section.
We need to ensure Javascript code is consistent and re-usable.
We hightly recommend checking out James's YouTube link (see chat).
MK: Keyboard section added from
May 23rd discussion (section 5).
... Have done minimal editing since then.
... Have not been able to follow up on JG's idea about turning
the guide into a "how-to" with steps.
... Need work on the "junk basket" section, 5.9.
JN: That is super long.
... Suggest taking the focus event section out, then talks
himself into leaving it.
... Suggests removeig the first and last sentence of that
section.
... We don't want to tell people what to do or not to do, but
rather tell them what to be aware of.
AA: I think the last bullet should go to the top. (bullet that says "use key handlers...").
JN: Don't use keypress .. because it does not work consistently across browsers.
IP: With a real button, event is fired onkeydown for enter, onkeyup for spacebar.
JN: We can't put too much Javascript stuff into the APG.
General consensus is that our examples can show people how to code Javsacript keyboard events, but the guide shouldn't go into too many details about coding.
JN: ON a Mac (native) space bar activates the currently focused button. Ener activates the default button.
MK: Sounds like we want to keep the first bullet, but delete bullets 2 through 5 (5th bullet deals with IE pseudo classes).
AA: All these bullets are related
to implementing custom controls.
... We could integrate some of that content into the building
custom widget section.
We need to move the propegation warning into the first bullet, or as a 9th bullet in the summary section.
MK: Supporting tooltips with keyboard section .. content might belong in the tooltip pattern.
JN/MK: The section is confusing.
JN: IE has pretty tooltips, accessible with keyboard, but they don't repond to zoom.
MK: This partis at the heart of
what we need to be focusing on right now.
... This is the whackage page.
JN: We ahve our quarterly working drafts that do not get overridden.
MK/JN: We need to whack the appendix (or large parts of it), prevents ARIA from appendicitis.
Note from scribe, in the south we call this section shrimp and gritds.
MK: Split this section into a
layout grid and data grid.
... My impression is that in a layout grid you should be able
to have arrow key navigation wrap (e.g. pressing arrow down at
end of column one wraps focus to first item in column 2). For
data grids this is not expected.
JN: Should we merge tables into this section perhaps rename it to (tabular structure)
Birkir: Consider the case of "hybrid" tables/grids, such as tables taht can be sorted by column headers.
JN: Also cosnider case of tables with a bunch of links, providing a keyboard shortcut to the row they want rahter than having to tab through the whole table.
This is scribe.perl Revision: 1.144 of Date: 2015/11/17 08:39:34 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: Birkir Inferring ScribeNick: Birkir Present: IanPouncey JamesNurthen matt_king AnnAbbott WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Got date from IRC log name: 11 Jul 2016 Guessing minutes URL: http://www.w3.org/2016/07/11-aria-apg-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]