- From: Peter Korn <peter.korn@oracle.com>
- Date: Thu, 28 Jun 2012 07:13:44 -0700
- To: Gregg Vanderheiden <gv@trace.wisc.edu>
- CC: "Hoffman, Allen" <Allen.Hoffman@HQ.DHS.GOV>, "Crowell, Pierce" <Pierce.Crowell@ssa.gov>, "'public-wcag2ict-tf@w3.org'" <public-wcag2ict-tf@w3.org>
- Message-ID: <4FEC6698.1080705@oracle.com>
Gregg, Thanks for catching that, I'm fine with "to be". Peter On 6/28/2012 6:47 AM, Gregg Vanderheiden wrote: > this looks good except for the word SHOULD which I didn’t notice > before -- but shouldn’t be here. We are avoiding formal standard > terms MUST/SHALL SHOULD MAY > > perhaps change it to "to be" > > > Most platform accessibility services go beyond programmatic exposure > of name and role, and programmatic setting of states, properties and > values (and notification of same), and specify additional information > *to be *exposed and/or set */(for example, obtaining a list of the > available actions for a given user interface component, and > programmatically executing one of the listed actions)./* > > RE the example at the end. -- this seems to be good info but the > wrong form. The sentence is about "information to be exposed" but > the example is not information but a n example of a use of the > information (I think). maybe it should be " e.g a list > > */(for example a list of the available actions for a given user > interface component, and a means to programmatically execute one of > the listed actions)./* > > that would give us > > * > * > *Most platform accessibility services go beyond programmatic exposure > of name and role, and programmatic setting of states, properties and > values (and notification of same), and specify additional > informationto be exposed and/or set (for example a list of the > available actions for a given user interface component, and a means to > programmatically execute one of the listed actions).* > > > /Gregg/ > -------------------------------------------------------- > Gregg Vanderheiden Ph.D. > Director Trace R&D Center > Professor Industrial & Systems Engineering > and Biomedical Engineering > University of Wisconsin-Madison > > Co-Director, Raising the Floor - International > and the Global Public Inclusive Infrastructure Project > http://Raisingthefloor.org --- http://GPII.net > > > > > > > > > On Jun 28, 2012, at 6:44 AM, Hoffman, Allen wrote: > > I’m fine with Peter’s last writing here. > *From:*Peter Korn [mailto:peter.korn@oracle.com] > *Sent:*Wednesday, June 27, 2012 7:27 PM > *To:*Crowell, Pierce > *Cc:*'public-wcag2ict-tf@w3.org <mailto:public-wcag2ict-tf@w3.org>' > *Subject:*Re: Action Item #19 Work with Al to come up with a couple of > examples for 4.1.2 > Pierce, > > For me the parenthetical remark "(and notification of same)" are > "event notifications", so I think mentioning such notification a > second time is redundant. But there are two aspects of actions that > might be called out separately, so as to have two examples: > enumerating them and programmatically executing them. > > Here's a proposed edit, with the new example text in the parenthetical > example at the end, in*/boldface italics/*:\ > Most platform accessibility services go beyond programmatic exposure > of name and role, and programmatic setting of states, properties and > values (and notification of same), and specify additional information > that could or should be exposed and/or set*/(for example, obtaining a > list of the available actions for a given user interface component, > and programmatically executing one of the listed actions)/*. > > Regards, > > Peter > > On 6/27/2012 2:05 PM, Crowell, Pierce wrote: > Action Item #19 Work with Al to come up with a couple of examples for > 4.1.2 > We propose the last sentence read: > Most platform accessibility services go beyond programmatic exposure > of name and role, and programmatic setting of states, properties and > values (and notification of same), and specify additional information > that could or should be exposed and/or set (for example, event > notifications and lists of available actions). > Pierce > -- > <image001.gif> <http://www.oracle.com> > Peter Korn | Accessibility Principal > Phone:+1 650 506 9522 <tel:+1%20650%20506%209522> > OracleCorporate Architecture Group > 500 Oracle Parkway | Redwood City, CA 94065 > ------------------------------------------------------------------------ > Note: @sun.com e-mail addresses will shortly no longer function; be > sure to use:peter.korn@oracle.com <mailto:peter.korn@oracle.com>to > reach me > ------------------------------------------------------------------------ > <image002.gif> <http://www.oracle.com/commitment>Oracle is committed > to developing practices and products that help protect the environment > -- Oracle <http://www.oracle.com> Peter Korn | Accessibility Principal Phone: +1 650 5069522 <tel:+1%20650%205069522> 500 Oracle Parkway | Redwood City, CA 94065 Green Oracle <http://www.oracle.com/commitment> Oracle is committed to developing practices and products that help protect the environment
Received on Thursday, 28 June 2012 14:14:45 UTC