Re: A presentational img?

hi james

i think it would be a good idea to document the heuristics, I would suggest
the html API guide would be the place to do it.


regards
steve

On 10 May 2011 22:08, James Craig <jcraig@apple.com> wrote:

>
> On May 10, 2011, at 1:56 PM, Steve Faulkner wrote:
>
> > hi james,
> >
> >> what about an explicit alt="" inside a link?
> >> <a href="/path/about_us.html"><img src="contact.png" alt=""></a>
> >
> > not sure in what sense you mean 'what about'
> >
> > its certainly an author error, in this case, since the accessible name
> for the link is derived from its content and its content is absent, then a
> heusristic is to announce the href
> > NVDA goes one better and just announces the linked file name "about_us"
>
>
> As does VoiceOver: "about us". I'm just curious if it'd be worthwhile to
> have the HTML spec standardize the fallback heuristics there. Something like
> use "last filename component minus extension" on unlinked images, or use
> "last link path component minus extension" on linked images. It could also
> spec which special chars to replace with spaces, like underscore, hyphen,
> etc.
>
>
>


-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html