W3C

- DRAFT -

ARIA APG TF

11 Jun 2018

Agenda

Attendees

Present
AnnAbbott, CurtBellew, ShirishaGubba, jamesn, jongund, matt_king, BryanGaraventa
Regrets
Jemma
Chair
MattKing
Scribe
AnnAbbott

Contents


<scribe> scribe: AnnAbbott

Structural roles section for APG 1.2

Milestone for 1.2 APG Working Draft 1 (https://github.com/w3c/aria-practices/milestone/7)

https://github.com/w3c/aria-practices/milestone/7

jn: provide guidance on first three
... when cost prohibited to totally rewrite code, add ARIA - better than doing nothing

<jamesn> Steve's first rule of aria

<jamesn> https://www.w3.org/TR/aria-in-html/#firstrule

jn: would like ASAP - can modify later as needed

mck: target pull request before Thurs ARIA call
... currently has widget focus, except Section 4 (landmarks) plus more
... segment into Patterns, Guidance and How To plus Appendix
... divide guide into Structure and Patterns
... propose making last section (#9)

jn: will do pr for that

mck: no APG 1.2 branch created yet
... ok to not have Structure until 1.2?

jn: target Q42019 completion for ARIA 1.2

mck: will work with Michael on 1.2 branch set-up

jn: already done #701 but has nowhere to put it

mck: setting up 1.2 branch will take care of that

<jamesn> https://github.com/w3c/aria-practices/issues/564

#564 aria-errormessage gets ID pointing to another place on page

mck: author MUST either remove aria-errormessage attribute OR make sure message isn't rendered
... seems unnecessary author overhead if user agent is validating

jg: working with student on inline error mssg
... aria-errormessage and aria-describedby can co-exist?

mck: confusing when they get concantonated
... doesn't think spec is super practical
... do error message and describedby need to be mutually exclusive
... error message + describedby only if significantly different

jg: screen readers can filter, correct?

mck: screen readers do not want to be in deciding position

jn: verbosity settings determine whether describedby is announced

siri: don't confuse user: describedby = instructions, error message = errors

jg: what happens if both point to same ID?

mck: don't know - spec doesn't say. Need example
... one example with native HTML (no other aria)

jg: ok

mck: : First Public Working Draft 1.2 - doesn't have guidance section

jg: can take on guidance section
... can work on guidance for treegrid also

mck: including impact today doesn't have any downside
... probably already out there in Chrome & FF

Navigation menubar updates

mck: jg created pr for #592 & #159

jg: can't put links inside other links
... sometimes link has menu item, sometimes not

Future meetings and other business

no meeting July 2, July 23, July 30

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.152 (CVS log)
$Date: 2018/06/11 18:01:25 $

Scribe.perl diagnostic output

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

Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00)

Present: AnnAbbott CurtBellew ShirishaGubba jamesn jongund matt_king BryanGaraventa
Regrets: Jemma
Found Scribe: AnnAbbott
Inferring ScribeNick: AnnAbbott
Agenda: https://github.com/w3c/aria-practices/wiki/June-11%2C-2018-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.)


[End of scribe.perl diagnostic output]