RE: HTML5 alt text advice update

> Does Steve's work make all the above moot?

At the A11Y TF meeting today the TF did state that it was their intent to obsolete the Alt techniques document by the work that Steve is doing on 5.1.

I then asked if it was possible to track the set of alt-related 5.1 changes that Steve has made or is proposing to make?  Since the TF suggested they would want to "back port" Steve's changes to HTML 5.0 would it be possible to identify the alt-related 5.1 bugs with a tag so a Bugzilla search can be used to easily identify those changes?

Steve:  Could you tag those bugs if you have not already done so and provide a Bugzilla query that identifies the current bugs?

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329


-----Original Message-----
From: Paul Cotton [mailto:Paul.Cotton@microsoft.com] 
Sent: Tuesday, July 09, 2013 8:48 PM
To: Janina Sajka; 'Steve Faulkner'
Cc: kirsten@can-adapt.com; David MacDonald; 'HTML Accessibility Task Force'
Subject: RE: HTML5 alt text advice update

> Unless there's significant disagreement in the TF, we will probably move toward closure on this issue.

Not sure what you mean by "this issue".  So I went looking for bugs.

The following bug is open on the LC1 Alt techniques document:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=12726 

The following search finds the five open bugs on the CR Alt techniques document:
http://tinyurl.com/lwn4ehy 

Does Steve's work make all the above moot?

/paulc

Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (425) 705-9596 Fax: (425) 936-7329

-----Original Message-----
From: Janina Sajka [mailto:janina@rednote.net]
Sent: Tuesday, July 09, 2013 5:27 PM
To: Paul Cotton
Cc: 'Steve Faulkner'; kirsten@can-adapt.com; David MacDonald; 'HTML Accessibility Task Force'
Subject: Re: HTML5 alt text advice update

Hi, Paul:

Steve has previously posted to the TF, the WG re edits he has made.
These have also been discussed on TF calls.

The HTML Facilitators telecon this past Monday looked at remaining language edits for Sec. 4.9.1.X, the portions of the HTML spec relating to the alt attribute on the image element. We agreed on the changes we want to present to the TF and expect we will spend a good deal of the TF call this Thursday looking at this language.

Unless there's significant disagreement in the TF, we will probably move toward closure on this issue.

Janina

Paul Cotton writes:
> What is the status of the "alt text advice" work?  
> 
> Paul Cotton, Microsoft Canada
> 17 Eleanor Drive, Ottawa, Ontario K2E 6A3
> Tel: (425) 705-9596 Fax: (425) 936-7329
> 
> 
> -----Original Message-----
> From: David MacDonald [mailto:david100@sympatico.ca]
> Sent: Saturday, June 15, 2013 3:36 AM
> To: 'Steve Faulkner'; 'HTML Accessibility Task Force'
> Cc: kirsten@can-adapt.com
> Subject: RE: HTML5 alt text advice update
> 
> I went through all the sections listed below, and filed a few bugs as suggestions... great work Steve...
> 
> Cheers
> David MacDonald
> 
> CanAdapt Solutions Inc.
>   Adapting the web to all users
>             Including those with disabilities www.Can-Adapt.com
> 
> 
> 
> -----Original Message-----
> From: Steve Faulkner [mailto:faulkner.steve@gmail.com]
> Sent: June-06-13 9:14 AM
> To: HTML Accessibility Task Force
> Subject: HTML5 alt text advice update
> 
> Hi all,
> I have updated/added the following subsections in the HTML 5.1 spec.
> So they are ready for review. Any sections from
> 
> 'Requirements for providing text to act as an alternative for images'
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#a
> lt
> 
> not listed below are still in progress.
> 
> A link or button containing nothing but an image 
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#a
> -link- or-button-containing-nothing-but-an-image
> Images of Text
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#i
> mages-
> of-text
> 
> Images that include text
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#i
> mages-
> that-include-text
> 
> A purely decorative image that doesn't add any information 
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#a
> -purel y-decorative-image-that-doesn%27t-add-any-information
> 
> A group of images that form a single larger picture with no links 
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#a
> -group -of-images-that-form-a-single-larger-picture-with-no-links
> 
> A group of images that form a single larger picture with links 
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#a
> -group -of-images-that-form-a-single-larger-picture-with-links
> 
> An image not intended for the user
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#a
> n-imag
> e-not-intended-for-the-user
> 
> Icons
> http://www.w3.org/html/wg/drafts/html/master/embedded-content-0.html#i
> cons
> 
> 
> --
> 
> Regards
> 
> SteveF
> HTML 5.1
> 
> 
> 
> 

-- 

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 Thursday, 18 July 2013 15:53:30 UTC