W3C home > Mailing lists > Public > public-html-a11y@w3.org > April 2012

Re: 48-Hour Consensus Call: ARIA-DescribedAT & Longdesc

From: Janina Sajka <janina@rednote.net>
Date: Tue, 3 Apr 2012 10:47:50 -0400
To: Laura Carlson <laura.lee.carlson@gmail.com>
Cc: Leif Halvard Silli <xn--mlform-iua@xn--mlform-iua.no>, HTML Accessibility Task Force <public-html-a11y@w3.org>
Message-ID: <20120403144750.GE4579@sonata.rednote.net>
Hi, All:

Please note the 6 definitions of the word "confirm" at:
http://dictionary.reference.com/browse/confirm

I believe this discussion has focussed on meaning #3 to the exclusion of
the first two, which are most appropriate in this instance. The question
of "validating" PF's decision was not the question here. However, poing
it out, agreeing to its implications, and supporting it--all of those
other meanings of "confirm" do apply here.

The point of this resolution is do confirm that ARIA-DescribedAT will
not be available to HTML 5 in HTML 5's current timeline toward
recommendation status at the W3C.



Janina


Laura Carlson writes:
> Hi Leif and all,
> 
> > Laura, would it help if the statement was turned into two sentences,
> > where the second sentence began "The ARIA TF" instead of "and
> > therefore"?
> 
> Yes two resolutions would work, if indeed we are authorized to speak
> for PF. Janina are we?
> 
> > Please note:
> >
> > * First half - until the comma - answers a question from
> >  the chairs. It would be unacceptable to not answer them.
> 
> Leif, it is difficult for me to believe that you or I or this task
> force has any right or authority to set PF's ARIA timeline or workload
> or speak to the HTML Chairs on PF's behalf.
> 
> However if we are in fact endowed with that authority, two separate
> and independent task force resolutions would be appropriate:
> 
> 1. RESOLUTION: The HTML-A11Y Task Force confirms that PF will not have
> ARIA-DescribedAT ready in the HTML 5 timeframe.
> 
> 2. RESOLUTION: The HTML-A11Y Task Force reaffirms its support of
> Laura's authored CP to reinstate longdesc (Issue-30).
> 
> Best Regards,
> Laura
> --
> Laura L. Carlson
> 
> On Mon, Apr 2, 2012 at 7:16 AM, Leif Halvard Silli
> <xn--mlform-iua@xn--mlform-iua.no> wrote:
> > Laura, would it help if the statement was turned into two sentences,
> > where the second sentence began "The ARIA TF" instead of "and
> > therefore"?
> >
> > Please note:
> >
> > * First half - until the comma - answers a question from
> >  the chairs. It would be unacceptable to not answer them.
> > * Even if we amended the statement (like I suggest or like
> >  you suggest), the sentiment of many in the TF is
> >  nevertheless best expressed in the current version, and
> >  this is for sure also understood by the chairs.
> >
> > Leif H Silli
> >
> > Laura Carlson, Mon, 2 Apr 2012 06:21:02 -0500:
> >> Hi Janina,
> >>
> >> I object to the first half of this resolution for several reasons.
> >>
> >> 1. Longdesc is a useful native HTML attribute in and of itself [1].
> >>
> >> 2. The resolution is predicated upon ARIA. Linking aria-describedat to
> >> longdesc in this manner is uncalled for and counter-productive to
> >> reinstating longdesc.
> >>
> >> 3. The PF working group is chartered to specify ARIA. The HTML
> >> Accessibility Task Force is not. The Accessibility TF is not
> >> authorized to confirm or deny ARIA timelines. If the HTML chairs
> >> desire a statement regarding PF's timeline that communication should
> >> come separately and directly from PF.
> >>
> >> The task force longdesc resolution requires no reservations or
> >> dependencies. Please revise it to simply state:
> >>
> >> RESOLUTION: The Accessibility Task Force reaffirms its support of
> >> Laura's authored CP to reinstate longdesc (Issue-30).
> >>
> >> Thank you.
> >>
> >> Best Regards,
> >> Laura
> >>
> >> [1] aria-describedat may be useful too. I wish Rich and Steve all the
> >> best on it.
> >>
> >>
> >> On Thu, Mar 29, 2012 at 11:45 AM, Janina Sajka <janina@rednote.net> wrote:
> >>> Colleagues:
> >>>
> >>> On 29 March last the HTML-A11Y Task Force teleconference meeting
> >>> reached consensus as follows:
> >>>
> >>> RESOLUTION: The HTML-A11Y Task Force confirms that ARIA-DescribedAT will
> >>> not be ready for HTML 5 in HTML 5's currently published timeframe, and
> >>> therefore reaffirms its support of Laura's authored CP to reinstate
> >>> longdesc (Issue-30).
> >>>
> >>> The TF resolution, together with minutes of the discussion leading up to
> >>> it, is logged at:
> >>> http://www.w3.org/2012/03/29-html-a11y-minutes.html#item03
> >>>
> >>> As usual, if there is objection to this consensus position, please
> >>> respond by replying to this message no later than close of business,
> >>> Boston Time, on Monday 2 April.
> >>>
> >>> --
> >>>
> >>> Janina Sajka,   Phone:  +1.443.300.2200
> >>>                sip:janina@asterisk.rednote.net
> >>>
> >>> Chair, Open Accessibility       janina@a11y.org
> >>> Linux Foundation                http://a11y.org
> >>>
> >>> Chair, Protocols & Formats
> >>> Web Accessibility Initiative    http://www.w3.org/wai/pf
> >>> World Wide Web Consortium (W3C)
> >> --
> >> Laura L. Carlson
> >>
> 
> 
> 
> -- 
> Laura L. Carlson

-- 

Janina Sajka,	Phone:	+1.443.300.2200
		sip:janina@asterisk.rednote.net

Chair, Open Accessibility	janina@a11y.org	
Linux Foundation		http://a11y.org

Chair, Protocols & Formats
Web Accessibility Initiative	http://www.w3.org/wai/pf
World Wide Web Consortium (W3C)
Received on Tuesday, 3 April 2012 14:48:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 04:42:57 GMT