See also: IRC log
<MichaelC> Last week's minutes
<MichaelC> ARIA mapping issues and actions
<cshelly> url for actions?
<MichaelC> action-39: duplicate of action-38
<MichaelC> close action-39
<MichaelC> action-2: superseded by the creation of the ARIA mapping sub-group
<MichaelC> close action-2
<MichaelC> scribe: janina
<scribe> scribe: janina
general discussion trying to achieve clarity on our actions
sf: the current (modified)
mapping doc is roughly this
... understand we need a rationale
cs: let's look at the role categories -- where's the table?
cs: looking at this link is descendent of widget, should it be overwritable by any widget?
sf: somewhat confused ... command is also subclass of widget
<davidb> regrets, I am IRC only for now
cs: pieces of a slider often made
of links, but not the slider itself ...
... is it inputs that are not also composites?
sf: spinbutton is subclass of range ... trying to follow the text because can't follow the chart
cs: buttons, list items, and menu
items, and tree items most link users
... does turning a link into a checkbox make sense?
sf: seen it being done
... looking for an example
... aren't we just going to define by mapping
cs: so it's buttons and options?
rs: anything activatable -- so not grid
mc: i updated taxonomy last week, some where hard to graph
cs: link is a command--so we can say all commands can replace each other
cs: so, links can be turned into commands and ranges
sf: thumb displaying the range
isn't marked with a role, is it?
... usually slider is a container element
cs: it's clearer that commands
are the same
... range does seem very different
... can't say i've seen a lot of this
rs: not difficult
cs: can menu items?
cs: doesn't seem to make sense
rs: perhaps a spinbutton
cs: but ht5 already has
rs: but as a range item
... could have a menu item with a slider in it
<cshelly> Commands can all replace each other
<cshelly> buttons and links are special cased. they can be replaced by ranges which are not composites
<cshelly> commands=link, button, menuitem, menuitemcheckbox, treeitem, menuitemradio
above from cs appears to be group consensus
further checking via the diagram
mc: explaining uml convention where arrow points to parent
<cshelly> ranges that are not composites = progressbar, slider, scrollbar
mc: another internal convention
is that all roles are in rows
... anything below is descendent
cs: option is a command in ht5,
mc: but not here ...
cs: suggest: any role can be overwritten by a descendent
mc: should one of our best design patterns
cs: a bp or this doc
cs: suggest: div and span can be overwritten by anything
sf: take that for granted
janina: never take rocks for granite
cs; inputs are trickier ...
cs: options often overwritten by
... expect ht5 to do that automagically
sf: inputs in ref to command?
cs: looking at taxonomy
... not reasonable to say all inputs can overwrite each other
sf: what about tree item
cs: not a command
... it's a list item
... so three decisions -- and if we see this doesn't work, probably a taxonomy error
sf: sounds good
cs: so next week i'm due for a draft
sf: yes, all of us
... rich, cyns, and steve
rs: i'm out next week
cs: should discuss input or my
... which is best?
... maybe inputs, ranges and some coposite for next week
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: janina Inferring ScribeNick: janina Found Scribe: janina Inferring ScribeNick: janina WARNING: No "Topic:" lines found. Default Present: Janina, Rich, Steve_Faulkner, Michael_Cooper, Cynthia_Shelly Present: Janina Rich Steve_Faulkner Michael_Cooper Cynthia_Shelly Agenda: http://lists.w3.org/Archives/Public/public-html-a11y/2010May/0103.html Got date from IRC log name: 11 May 2010 Guessing minutes URL: http://www.w3.org/2010/05/11-aria-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option. WARNING: No "Topic: ..." lines found! Resulting HTML may have an empty (invalid) <ol>...</ol>. Explanation: "Topic: ..." lines are used to indicate the start of new discussion topics or agenda items, such as: <dbooth> Topic: Review of Amy's report[End of scribe.perl diagnostic output]