RE: Updates to Issue-201 Change Proposal per our conversation

Steve's proposed text below looks reasonable; I believe this addition sufficiently explains the correct usage for authors.

Thanks
Frank


-----Original Message-----
From: Philippe Le Hegaret [mailto:plh@w3.org] 
Sent: Saturday, July 28, 2012 6:55 AM
To: Steve Faulkner; eoconnor@apple.com; Frank Olivier
Cc: Richard Schwerdtfeger; public-html-a11y@w3.org; public-html@w3.org
Subject: Re: Updates to Issue-201 Change Proposal per our conversation

On Sat, 2012-07-28 at 10:56 +0100, Steve Faulkner wrote:
> Hi Philippe,
> current status is that
> 1.Rich and I have provided text for which we are waiting for review 
> [2] 2. there is a new point of possible contention for which Rich (and 
> I concur with his request) has requested a removal [1]
> 
> The amount of time it will take to reach an agreeement is wholly 
> dependent on the rate at which the parties involved communicate in 
> regards to these outsanding issues.

Steve, thank you for the update

Ted, Frank, your input would be welcome,

Philippe

> [1] http://lists.w3.org/Archives/Public/public-html/2012Jul/0216.html

> [2] http://lists.w3.org/Archives/Public/public-html/2012Jul/0162.html

> 
> On 27 July 2012 17:50, Philippe Le Hegaret <plh@w3.org> wrote:
>         Steve, Ted, Frank, Richard,
>         
>         on 201, the Chairs are currently assuming that you will all
>         come to a
>         conclusion by end of next week, ie agree on the change
>         proposal. If
>         that's a false assumption, please let them know and ask for
>         more time.
>         
>         Philippe
>         
>         On Thu, 2012-07-26 at 15:43 +0100, Steve Faulkner wrote:
>         > Hi all,
>         >
>         > so in regards to the clarification i am seeking I found that
>         the spec
>         > text is in one of the diffs: (thanks for adding the links to
>         the diffs
>         > in the proposal)
>         > http://html5.org/tools/web-apps-tracker?from=7028&to=7029

>         >
>         >         If any of the following conditions are met, throw a
>         +
>         >         <code>NotSupportedError</code> exception and abort
>         these +
>         >         steps.
>         >         ...
>         >
>         >          The arguments object's control member is not  null
>         but is
>         >         neither an a element that  represents a hyperlink,
>         a  button
>         >         element, an input element whose  type attribute is
>         in one of
>         >         the Checkbox or  Radio Button states,  nor an input
>         element
>         >         that is a button.
>         >
>         > This strongly suggests to me that no ARIA custom control can
>         be
>         > referenced by the control() method unless it is built on top
>         of of one
>         > of the listed elements. And the vast majority of HTML
>         elements cannot
>         > by referenced by control, including interactive elements
>         such as
>         > <input type=text> or <input type=range> etc.
>         >
>         >
>         > regards
>         > SteveF
>         
>         
>         
> 
> 
> 
> --
> with regards
> 
> Steve Faulkner
> Technical Director - TPG
> 
> www.paciellogroup.com | www.HTML5accessibility.com | 
> www.twitter.com/stevefaulkner
> HTML5: Techniques for providing useful text alternatives - 
> dev.w3.org/html5/alt-techniques/ Web Accessibility Toolbar - 
> www.paciellogroup.com/resources/wat-ie-about.html
>

Received on Thursday, 2 August 2012 15:37:04 UTC