W3C home > Mailing lists > Public > public-html@w3.org > January 2010

Re: Discussion on Change Proposal for ISSUE-66

From: Lachlan Hunt <lachlan.hunt@lachy.id.au>
Date: Fri, 22 Jan 2010 11:52:07 +0100
Message-ID: <4B598357.3050206@lachy.id.au>
To: Maciej Stachowiak <mjs@apple.com>
Cc: 'Matt May' <mattmay@adobe.com>, 'HTML WG' <public-html@w3.org>, public-html-a11y@w3.org
I've had a go at writing a proposal for some alternative spec text to 
resolve this issue.

When the user is unable to make direct use of the image, e.g. due to a 
visual disability or because they are using a text terminal with no 
graphics capabilities, user agents may also provide the user with the 
ability to obtain any other information about the image that may assist 
the user in understanding its content or purpose, utilising any 
available repair technique.

Such techniques may be based on information from any relevant source 
including, but not limited to, the following suggestions:
* Obtaining the file name from the URL reference or HTTP headers
   supplied with the resource, such as the Content-Location or
   Content-Disposition header fields.
* Extracting human readable metadata embedded within the resource.
   e.g. EXIF, RDF or XMP.
* Referring to alternative text associated with another instance of the
   same resource on the page.
* Applying OCR techniques to recognise and extract textual content that
   is graphically represented on the image.

For more information, refer to the User Agent Accessibility Guidelines 
techniques for repairing missing content ([UAAG10-TECHS], section 2.7).

(Note that the first 3 techniques listed above are based on the 
techniques listed in UAAG)

Lachlan Hunt - Opera Software
Received on Friday, 22 January 2010 10:52:42 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:57 UTC