scribe, AnnAbbott

ARIA and AT Project Update

<jamesn> scribe: AnnAbbott

mck: had kickoff meeting Jan 22
... had about 5 join planning meeting

<MarkMcCarthy> mck: any questions?

House keeping update

<MarkMcCarthy> mck: working on getting editor config built in with PR 856

PR 856: https://github.com/w3c/aria-practices/pull/856

<MarkMcCarthy> mck: i did a test, and it's weird that you have to specify what things to ignore

<MarkMcCarthy> evan: yeah, a blacklist might be hard to maintain

<MarkMcCarthy> ... the opinions of the editor config might be useful to look at too

<MarkMcCarthy> mck: that's consitent with our style guide though, right?

<MarkMcCarthy> mck: evan, do you know how to change the blacklist to a whitelist?

<MarkMcCarthy> MichielBijl: if we have to use labels for this stuff can we use something other than “white list” and “black list”?

<MarkMcCarthy> jamesn: +1

<MarkMcCarthy> evan: yeah, it's not exactly a whitelist or blacklist... yeah I know how to do that. Maybe we ask Nick about that

Jemma: ask Nick to take up 856

PR 841: https://github.com/w3c/aria-practices/pull/841

mck: don't know how to control what gets spell checked
... concerned about maintenance levels
... volunteer to dig in and help out with spell check

Evan: can look into this
... will respond in issue

Date Picker Combo Box Example

<jemma> Questions we have: 1)Where should focus go after a date is chosen from the grid in the dialog? If it goes to the text field, that pops open mobile keyboards. If it goes to the down arrow icon, it is confusing for screen reader and keyboard users who moved focus into the dialog from the text field with down arrow.

<jemma> 2)When should the dialog be visually displayed? It is very common for calendars to display when the text field is focused or clicked. Does that mean the user has to move focus out of the input to get the calendar to disappear?

mck: will create separate issues for other examples, like BryanGaraventa's

bg: ok to set focus back to input
... is expected behavior

mck: if tapping input displays grid and keyboard?

bg: need different pattern for mobile/touch and desktop
... separate icons for each

mck: if on small screen, what happens when dialog and kbd are both displayed

jn: need extra tap on small screen
... this pattern is problematic based on small screen vs desktop
... can make it so kbd doesn't display on small screen
... have to work around design issues

mck: expectation is focus goes to edit field
... and will display dialog but not move focus ther

jn: problem if it does both
... on small screen, most users will utilize picker and not data enter
... will have to look closely at each for details

bg: may have to hack around UI design patterns

mck: touch clicks are equal to mouse clicks

mb: libraries can distinguish between touch click and mouse click

mck: in VO, does double click imitate click event?
... could have behavior based on focus and touch
... displaying dialog if touch input
... and if gets focus
... requires second tap to give focus
... logic: if touch detected and dialog is not displayed, display dialog
... if touch detected and dialog is already displayed, focus goes to input
... if click detected on input, give input focus and display dialog
... if tabbed to, display dialog
... to close, Escape closes no matter where focus is
... clicking down arrow, closes dialog
... clicking Cancel closes dialog

Skipping Issue Triage this week

Editorial guidelines -- Comma and Quote Placement

mck: will add decision to Editorial Guidelines

<MarkMcCarthy> An exception note: "This system or a variation may be appropriate in works of textual criticism or in computer coding and other technical or scientific settings."

aa: if usage is for actual sentences, follow Style guide. If usage is for code tag, use actual code value

<jamesn> Yes

<jamesn> :)

<MichielBijl> “set <code>aria-disabled</code> to <code>true</code>.”

<jamesn> punctuation should never be added into a code tag

<jamesn> me/s/should/must/

mck: : if part of code tag, use code style

<jamesn> :)

Future meetings and other business

No meeting February 18 due to US President's day holiday.

No meeting March 11 do to CSUN

PR Review Tutorial

Training PR 985: https://github.com/w3c/aria-practices/pull/985

This is scribe.perl Revision: 1.154  of Date: 2018/09/25 16:35:56  
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/TOPIC ARIA and AT Project Update/TOPIC: ARIA and AT Project Update/
Succeeded: s/TOPIC House keeping update/TOPIC: House keeping update/
Succeeded: s/logic: if touch detected, display dialog/logic: if touch detected and dialog is not displayed, display dialog/
Present: AnnAbbott MarkMcCarthy evan jamesn CurtBellew MichielBijl Bryan_Garaventa matt-king jongund
Found Scribe: AnnAbbott
Inferring ScribeNick: AnnAbbott
Agenda: https://github.com/w3c/aria-practices/wiki/February-11%2C-2019-Meeting

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.)