Re: [html-techs-tf] caption vs alt

The problem with sufficient techniques that have no accessibility 
support is that developers rely on them anyway, because they follow the 
argument that "if W3C says this, it is good practice". Maybe it WILL be 
good practice in the future, but for the moment it is creating barriers 
for real people.

Regards,
Ramón.

Loretta said:

> Yes, this should be a sufficient technique (under the right 
> circumstances) but it sounds like there is no accessibility support at 
> this point.


>         I've done some testing with a simple image.____
> 
>         http://davidmacd.com/test/figure.html____
> 
>         __ __
> 
>         It is a simple image inside the figure tag with placeholder text
>         in the figcaption. ____
> 
>         __ __
> 
>            -Jaws with Internet Explorer and Firefox: : it read the text
>         of the figcaption but did not announce a figure and did not
>         recognize that there was a graphic on the page. The Jaws key "G"
>         to read the next graphic does not work because Jaws does not
>         appear to recognize as a graphic. ____
> 
>         __ __
> 
>            -NVDA with Internet Explorer and Firefox: it read the text of
>         the figcaption but did not announce a figure and did not
>         recognize that there was a graphic on the page. The key "G" to
>         read the next graphic does not work because NVDA does not appear
>         to recognize it as a graphic.____
> 
>         __ __
> 
>            -Safari in Maverick: does not recognize the figure element
>         and just says “group”, then an empty image and the text
>         afterwards as if it was a paragraph as if there was no
>         relationship between the legend and the graphic. ____
> 
>         __ __
> 
>         -Aviewer and IE: screenshot below...   I guess it shows up as a
>         group the image has not reported Accname. So API seems to only
>         report the content of the figcaption when the figcaption as
>         focus.____
> 
>         __ __
> 
>         Discussion: I'm really struggling to figure out where I stand on
>         all of this because the ways things are being reported right now
>         in a Windows environment does not really allow the screener user
>         to even know that there is a figure there. It just reads a text
>         of the figcaption without announcing that it's a figure. In
>         Safari it does announce as a group. It's hard to tell when the
>         group ends. It just simply has a graphic without an alternative
>         and then the next time the person arrows down they get the
>         figcaption which doesn't appear to be a programmatic association
>         except for the word “group” before the item. VoiceOver screen
>         reader users will have to get themselves acclimatized to this
>         new type of group. But all in all I'm quite disappointed with
>         the way it works. It almost seems like this belongs in that
>         larger discussion about accessible names and alternative text.
>         Right now it seems there's more success with some of the other
>         nonstandard alternatives than with figcaption. Which makes it
>         difficult to say this is okay and the others are not. I'm really
>         committed to unity between HTML5 and WCAG, but reticent to
>         create a technique that is sufficient using figcaption right
>         now. And I'm wondering what others think.____

Received on Monday, 13 January 2014 20:34:26 UTC