W3C home > Mailing lists > Public > public-html-admin@w3.org > October 2014

Re: request a heartbeat publication of HTML5: Techniques for providing useful text alternatives

From: Janina Sajka <janina@rednote.net>
Date: Fri, 10 Oct 2014 16:45:24 -0400
To: Grant Simpson <glsimpso@gmail.com>
Cc: Steve Faulkner <faulkner.steve@gmail.com>, "public-html-admin@w3.org" <public-html-admin@w3.org>
Message-ID: <20141010204524.GD2681@opera.rednote.net>
What you say makes sense to me.

But, then that's precisely the problem here. The consensus required
isn't there just now, and asking one of the three groups to publish, but
neglecting to ask the other two at the same time just doesn't seem an
effective approach to building that consensus.


Grant Simpson writes:
> I assume that’s directed at me. It’s not a matter of one version having different content but that one version represents a different maturity level of the document. With a heartbeat draft I can feel comfortable saying that the document represents WG consensus (even if it’s subject to change), whereas editor’s drafts "have no official standing whatsoever, and do not necessarily imply consensus of a Working Group or Interest Group, nor are their contents endorsed in any way by W3C” [1]. It’s a matter of presenting a document that is readily accessible from the index of technical reports and that has been given the WG’s go ahead to publish. 
> 
> Best,
> Grant 
> 
> [1] http://www.w3.org/2014/Process-20140801/#Reports
> 
> On Oct 10, 2014, at 4:11 PM, Janina Sajka <janina@rednote.net> wrote:
> 
> > Steven Faulkner writes:
> >>> 
> >>> It would be extremely helpful to have a heartbeat draft. In my class, I
> >>> integrate accessible techniques throughout the curriculum and when it comes
> >>> to discussing text alternatives in HTML, I have been at a bit of a loss as
> >>> to how to explain the current state of the art.
> >> 
> > 
> > Steve:
> > 
> > This makes no sense.
> > 
> > What is it you can't explain from the editor's draft that you would be
> > able to explain to your class from a heartbeat?
> > 
> > Janina
> > 
> >> 
> >> Note the latest version of the document is available here:
> >> http://w3c.github.io/alt-techniques/
> >> 
> >> Also if you want a stable draft link, the bulk of the material is also
> >> available in the HTML5 PR spec
> >> http://www.w3.org/TR/html/embedded-content-0.html#alt
> >> 
> >> --
> >> 
> >> Regards
> >> 
> >> SteveF
> >> HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>
> >> 
> >> On 10 October 2014 16:38, Grant Simpson <glsimpso@gmail.com> wrote:
> >> 
> >>> It would be extremely helpful to have a heartbeat draft. In my class, I
> >>> integrate accessible techniques throughout the curriculum and when it comes
> >>> to discussing text alternatives in HTML, I have been at a bit of a loss as
> >>> to how to explain the current state of the art.
> >>> 
> >>> TL;DR: +1.
> >>> 
> >>> On Oct 10, 2014, at 11:31, Gez Lemon <glemon@paciellogroup.com> wrote:
> >>> 
> >>>> +1
> >>>> 
> >>>> Regards,
> >>>> 
> >>>> Gez
> >>>> 
> >>>> On 10 October 2014 13:01, Steve Faulkner <faulkner.steve@gmail.com>
> >>> wrote:
> >>>>> Dear Chairs.
> >>>>> 
> >>>>> In regards to:
> >>>>> HTML5: Techniques for providing useful text alternatives
> >>>>> http://w3c.github.io/alt-techniques/
> >>>>> 
> >>>>> As It is unclear when  the document will be published as a note and what
> >>>>> direction the planned changes will take I consider it a reasonable
> >>> request
> >>>>> that  a heartbeat draft be published by the HTML WG  before the new
> >>>>> editor(s) start work on the document. In its current form the document
> >>>>> accurately reflects the related advice on provision of text alternatives
> >>>>> contained in the HTML5 PR specification [1]. The current HTML5:
> >>> Techniques
> >>>>> for providing useful text alternatives WD
> >>>>> http://www.w3.org/TR/html-alt-techniques/ is 2 years old and is largely
> >>>>> obsolete. I consider it an important of the review process to be able to
> >>>>> have a stable up to date snapshot of the document in its current form
> >>>>> available for myself and others who intend to contribute feedback as the
> >>>>> document changes.
> >>>>> 
> >>>>> 
> >>>>> 
> >>>>> [1] http://www.w3.org/TR/html/embedded-content-0.html#alt
> >>>>> 
> >>>>> --
> >>>>> 
> >>>>> Regards
> >>>>> 
> >>>>> SteveF
> >>>>> HTML 5.1
> >>>> 
> >>>> 
> >>>> 
> >>>> --
> >>>> _____________________________
> >>>> Senior Accessibility Consultant - TPG
> >>>> http://www.paciellogroup.com
> >>>> 
> >>> 
> >>> 
> > 
> > -- 
> > 
> > Janina Sajka,	Phone:	+1.443.300.2200
> > 			sip:janina@asterisk.rednote.net
> > 		Email:	janina@rednote.net
> > 
> > Linux Foundation Fellow
> > Executive Chair, Accessibility Workgroup:	http://a11y.org
> > 
> > The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
> > Chair,	Protocols & Formats	http://www.w3.org/wai/pf
> > 	Indie UI			http://www.w3.org/WAI/IndieUI/
> > 
> 

-- 

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

Linux Foundation Fellow
Executive Chair, Accessibility Workgroup:	http://a11y.org

The World Wide Web Consortium (W3C), Web Accessibility Initiative (WAI)
Chair,	Protocols & Formats	http://www.w3.org/wai/pf
	Indie UI			http://www.w3.org/WAI/IndieUI/
Received on Friday, 10 October 2014 20:45:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:37:36 UTC