- From: Paul Cotton <Paul.Cotton@microsoft.com>
- Date: Mon, 12 May 2014 19:39:57 +0000
- To: Steve Faulkner <faulkner.steve@gmail.com>
- CC: HTML Accessibility Task Force <public-html-a11y@w3.org>, "public-html-admin@w3.org" <public-html-admin@w3.org>, Sam Ruby <rubys@intertwingly.net>, Mark Sadecki <mark@w3.org>, Janina Sajka <janina@a11y.org>
- Message-ID: <2fe540d5827f480989ea40b151d29e77@BL2PR03MB418.namprd03.prod.outlook.com>
Where do we stand with closing out the open bugs [1] on this specification so that we get a finalized version to publish as a WG Note? /paulc [1] http://tinyurl.com/kf7qdqn Paul Cotton, Microsoft Canada 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 Tel: (425) 705-9596 Fax: (425) 936-7329 From: Steve Faulkner [mailto:faulkner.steve@gmail.com] Sent: Monday, April 21, 2014 1:13 PM To: David MacDonald Cc: HTML Accessibility Task Force; public-html-admin@w3.org; Paul Cotton; Sam Ruby; Mark Sadecki; Janina Sajka Subject: Re: text alternatives standalone draft HI Dave, thanks sorry I should have said before, could people file bugs - thanks! file a bug - https://www.w3.org/Bugs/Public/enter_bug.cgi?comment=&product=HTML%20WG&component=CR%20alt%20techniques%20%28editor%3A%20Steven%20Faulkner%29 -- Regards SteveF HTML 5.1<http://www.w3.org/html/wg/drafts/html/master/> On 21 April 2014 15:49, David MacDonald <david100@sympatico.ca<mailto:david100@sympatico.ca>> wrote: Hi Steve A couple a thoughts... 1) I think screen reader users should be explicitly informed that information below is the alternative... rather than deducing it from the heading above the alternative. alt="Flowchart: Dealing with a broken lamp."> I would add "full description below" alt="Flowchart: Dealing with a broken lamp. Full description below"> ======== alt="Bar chart: Average rainfall in millimetres by Country and Season." Same here alt="Bar chart: Average rainfall in millimetres by Country and Season. Table of data below" 2) I'm not sure of "more than a couple of sentences" being the guidance for providing a long text alternative. I've always understood it to be if it requires more than about 100 words, OR if there is a necessity to structure it, then a long and structured description should be provided. A couple of sentences means about 20 words. Do we really want people to start requiring a long description if the alt is more than 20 words? Remember, the general public will take this document as the final word... I would like other's thoughts on this. 3) Also I think we need an example of the long description immediately following the image, where it is hidden in an expandable tag such as the Details/Summary (or a JavaScript fallback) .... every developer I know resists long text following an image because they don't want to give up the page real estate. Cheers, David MacDonald CanAdapt Solutions Inc. Tel: 613.235.4902<tel:613.235.4902> LinkedIn<http://www.linkedin.com/in/davidmacdonald100> www.Can-Adapt.com<http://www.Can-Adapt.com> Adapting the web to all users Including those with disabilities If you are not the intended recipient, please review our privacy policy<http://www.davidmacd.com/disclaimer.html> On Sun, Apr 20, 2014 at 2:06 PM, Steve Faulkner <faulkner.steve@gmail.com<mailto:faulkner.steve@gmail.com>> wrote: here is an updated draft of the alt text standalone doc I have been threatening to prepare but not actually delivered on until now. Its still needs a little work, but is almost ready. This is intended to be published as a note. HTML5: Techniques for providing useful text alternatives W3C Editor's Draft 20 April 2014 http://rawgit.com/w3c/alt-techniques/master/index.html -- Regards SteveF HTML 5.1<http://www.w3.org/html/wg/drafts/html/master/>
Received on Monday, 12 May 2014 19:40:33 UTC