W3C

- DRAFT -

ARIA Practices TF

21 Nov 2014

See also: IRC log

Attendees

Present
Matt_King, LJWatson, James_Nurthen, Jemma, Bryan_Garaventa
Regrets
Chair
SV_MEETING_CHAIR
Scribe
mattking

Contents


<Jemma> hi!

<Jemma> I will be back in 2 min.

<scribe> scribe: mattking

<Jemma> I am back to meeting

List of APG 1.1 bugs:

https://www.w3.org/Bugs/Public/buglist.cgi?cmdtype=runnamed&list_id=47716&namedcmd=APG%201.1%20-%20open%20bugs

radio button pattern

http://www.w3.org/WAI/PF/aria-practices/#radiobutton

JN: pattern named radio button but it is all about radio group. Should we change the pattern name?
... there is one model where we do not have normal group behavior: radios at beginning of each row of a table used for selection.

MK: one special case where it works in a table; nothing in the table gets keyboard focus except for the radios.

JN: take the special case of the table and describe what is the normal case.

LW: agree

JN: we could add a not about the special case.

<Jemma> sure

RESOLUTION: change name to "Radio Group"

JN: need a description for radio group. current description uses words like single-select and list.

Current description is "An option in single-select list "

<Jemma> Bryan, can you share the github link here?

MK: is it really a best practice that you can move without selecting by using ctrl+arrow?

Others: never heard of that before.

JN: should it wrap?

GB: browser dependent

JN: Firefox puts all buttons in group in tab order if none are selected.

MK: I think that is a FF but.

JN: Chrome is nowt wrapping with native radios

MK: I think we should keep wrapping.
... should we strike the ctrl+arrow behavior?

<Jemma> agree

RESOLUTION: strike the ctrl+arrow behavior

BG: the logic of shift+tab and tab giving focus to diff buttons is complicated
... recommend that tabindex=0 go on the selected button, and if none is selected, it goes on the first one.

JN: this is different from most browsers with native radios
... we should have a note to that effect.

BG and MK: agree that it is more intuitive for screen reader users for forward and back tab to be consistent.

JN: ease of implementation can also be a justification for this approach.

RESOLUTION: first button in group will get focus regardless of tabbing direction when none are selected. the selected button will get focus otherwise. A note regarding difference from typical UA behvior will be added.

MK: what about this point: • If an image is used to render the state of a radio button, the image element does not appear in the accessibility API mapping. This is accomplished using CSS to render the image as a background image, or by setting role="presentation" on the image.

http://www.w3.org/WAI/PF/aria-practices/#radiobutton

JN: Do we need to specify that aria-checked = false is needed; the spec makes it implicit.
... OK to leave the checked = false as written.

BG: Do not recommend using role presentation to hide images

Mk: do not recommend bg images due to effect on high contrast mode
... do we want to strike or fix this?

JN: do we need a section that talks about how to remove elements from the a11y tree?
... we do not have a note like this in the checkbox pattern.

MK: I think we should strike the note and use examples that use images

JN: there is a note like this in checkbox.

BG: that note is not clear either.

RESOLUTION: create example implementations of the checkbox and radio group patterns that demonstrate how to implement with images and CSS rendering, and strike the bullets on that topic from the design pattern text.

ACTION create example implementations of radio group and checkbox that use CSS content images to render states

<trackbot> Error finding 'create'. You can review and register nicknames at <https://www.w3.org/WAI/PF/Group/track/users>.

<Jemma> sounds good

Next meeting

agenda will include spin button and menu

2 weeks from today

no meeting on Nov 28.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2014/11/21 18:53:11 $

Scribe.perl diagnostic output

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

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/note/not/
Found Scribe: mattking
Inferring ScribeNick: mattking
Default Present: Matt_King, LJWatson, James_Nurthen, Jemma, Bryan_Garaventa
Present: Matt_King LJWatson James_Nurthen Jemma Bryan_Garaventa

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

Got date from IRC log name: 21 Nov 2014
Guessing minutes URL: http://www.w3.org/2014/11/21-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]