MINUTES: 14 MARCH 2016 ARIA Authoring Practices Guide Taskforce

Link:
https://www.w3.org/2016/03/14-aria-apg-minutes.html


[W3C]<http://www.w3.org/>

- DRAFT -
WAI-PF ARIA Authoring Practices Guide Taskforce
14 Mar 2016

See also: IRC log<http://www.w3.org/2016/03/14-aria-apg-irc>

Attendees
Present
JamesNurthen, MichielBijl, IanPouncey, JaeunJemmaKu, Bryan
Regrets
LéonieWatson, JonGunderson
Chair
SV_MEETING_CHAIR
Scribe
jamesn, jemma
Contents

  *   Topics<https://www.w3.org/2016/03/14-aria-apg-minutes.html#agenda>
1.   Example reviews and update pattern work assignments https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status<https://www.w3.org/2016/03/14-aria-apg-minutes.html#item01>

  *   Summary of Action Items<https://www.w3.org/2016/03/14-aria-apg-minutes.html#ActionSummary>
  *   Summary of Resolutions<https://www.w3.org/2016/03/14-aria-apg-minutes.html#ResolutionSummary>

________________________________

<MichielBijl> 11 is?

<jamesn> 1) For example, source code link name in button example page should be button.css and button.js NOT link.css and link.js

<jamesn> The same for the example, checkbox-2

<jamesn> https://rawgit.com/w3c/aria/Mar_2016_Heartbeats/practices/examples/checkbox/checkbox-2.html

<jamesn> They should be checkbox-3.css and checkbox-3.js

<jamesn> 3) Menu example was not updated in the publication yet.

<jamesn> 4) Radio example was not updated yet

<jamesn> mck: the example page, the code refers to the correct thing but the file name on the page is incorrect

<jamesn> mck: for (3) and (4) you are saying that the entire sub directory are not merged

<jamesn> mck: would also mean editing practices to create a link to them

<jamesn> mb: can a mail be sent for how to use github to do this kind of thing

<jamesn> mk: we can discuss later.

<jamesn> mb: branched would solve this

<jamesn> scribe: jamesn

mck: Jemma to create a PR ASAP for this

https://github.com/w3c/aria/tree/Mar_2016_Heartbeats

Example reviews and update pattern work assignments https://github.com/w3c/aria/wiki/Aria-Authoring-Practices-Patterns-Status

mk: want to make sure that not missing anything. got more patterns ready for examples

setting aside until get aria 1.1 combo box text final

I think we will want an ARIA 1.0 combo box and a 1.1 combo box

other than that are there any other examples that youy know of which are done but have not been reviewed

JK: Jon is working on toolbar and tabpanel

MB: tabpanel was assigned to me
... want to look at issues - going to be looking at this at CSUN

MK: were we going to look at what was going to be shown at cSUN here

IP: indedpendent work

MK: what is being done at CSUN

IP: MB and IP have created 2 versions of tabpanel and accordion. we have patterns.

at csun will also do some f2f tests

MK: 2 different tab panels

IP: for accordion 2 versions - discolsure vs what is currently documented

MK: do either have tab versions
... what are the differences for the tab panel?

MB: 2 examples. 1 a simple tab panel example, the 2nd is a simplified version of the APG version where you can only tab to the active tab

JN: concerned as to how the results get interpreted based on the context

MK: curious to understand the context of the example where all of the tabs are in the tab order

MB: want to see if people associate a tab with disclousre buttons etc.

IP: questions are straightforward

<MichielBijl> scribe: jemma

take up item 2

<mck> is an element that displays a brief, important message in a way that attracts the user's attention without interrupting the user's task. Dynamically rendered alerts are automatically announced by most screen readers, and in some operating systems, they may trigger an alert sound. It is important to note that, at this time, screen readers do not inform users of alerts that are present on the...

<mck> ...page before page load completes.

mk: does the address this intent of this bug?

mb: I think so

mk: what do you think about "at this time"
... which screen reader do not inform?

<MichielBijl> mkc: It is important to note that not all screen readers inform users of alerts that are present on the...

bb: there is confusion about when alert added.

take up item 3

mk: we have dialog and non dialog which is clear
... if it is focusable tooltip should not it be a dialog?

bb: aria-own is rearranged a11y tree in new release in chrome and firefox

mb: now we can manupulate the dom order

mk: I am still thinking what dialog tooltip should be. if tooltip has a link it is focusable. there is no standardized key to operate the tool tip

BB: tooltip is usually overlay icon
... to get help something

mk: point of aria is on interaction

BB: it is not desirable or necessary to trap the focus in the tooltip

mk: what do you mean by "trapping"?
... it sounds that it act like a dialog, you open and close it

BB: tooltip is more of giving the contextual infor
... not trapping user actions in the tooltip
... quick thought, would it be similar to footnote?

mk: dialog requires mechanism to open and close.
... we are talking about Hover help
... there is not standardized keyboard for tooltip

BB: this involves lots of things, marking up correctly and more...

mk: there should be a realistic example since people will learn from the example.
... main thing is alerting screen user about presence of tooltip and enable keyboard users to get into it.

BB: focus management and mousein/out problem in tooltip

mk: short key for element can be used but short cut key is adjacent to overlay. how would you say to screen readers that this short key is related to tooltip?
... some ui do not use separate icon and it is not in the tab order

if tooltip has separate focusable icon, then it is easy

mk: in that case, we may just refer back to dialog pattern.

take up item 4

mk: we wanted to tap panel as tab
... will create a bug for this

<mck> the label/title area of the tab panel. This is where you click to activate a tab panel

<mck> The element in a tablist that serves as the title for one of the tabpanels

<mck> The element in a tablist that serves as the title for one of the tabpanels. Activating a tab displays a tabpanel.

mk: the way we address orientation in ARIA - like in tool bar should be used here too?
... see the example, https://rawgit.com/w3c/aria/master/practices/aria-practices.html#toolbar

for vertical orientation

mk: we should be consistent in the pattern
... will create a bug about tab panel including orientation.