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

Hi Steve

 

>From what I can tell, JAWS, NVDA, VO have made some sort of implementation,
<http://davidmacd.com/test/figure.html>
http://davidmacd.com/test/figure.html

none of them just ignore it. JAWS & NVDA both read the figcaption text
twice, once when encountering the figure and once when encountering the
text. VO announces a group. If you go past it and come back to it seems to
not say it’s a group. In other words they have all put it on their agenda
and from what I can tell made poor decisions about implement it. I would
certainly like to get other people's opinions on this.

 

Neither of them announce whether there is an image or not inside the figure
element or that it is a figure element. The HTML 5 spec says that any type
of 

‘flow content” can be inside the figure element. So I would think it would
be important to screen reader user to know that it is a graphic and when
they encounter this graphic they would hear the figcaption. 

 

Now I have to admit I'm a little unclear of what to expect if it is
implemented properly. There are three things that can get focus.

- The figure element, 

-the flow content, usually an image

-figcaption.

 

If the figure element gets focus I would expect the accessibility API to
report the figcaption as the accName. What if the flow content gets focus?
If it's an image I would think any alt text or the figcaption would get the
accName if there is no alt text. If the flow content is not an image, one
would expect the user to be able to access it with a screen reader ... So
it's not a simple algorithm.

 

I'm just digging into this element now and so I expect learn more next
couple of days... And will refer to the API mapping guide in the ARIA test
harness to better understand the expect behavior. Right now it seems like a
big mess.

 

Cheers,

David MacDonald

 

CanAdapt Solutions Inc.

Tel:  613.235.4902

 <http://ca.linkedin.com/in/davidmacdonald100>
http://ca.linkedin.com/in/davidmacdonald100

 <http://www.can-adapt.com/> www.Can-Adapt.com

   

  Adapting the web to all users

            Including those with disabilities

 

This e-mail originates from CanAdapt Solutions Inc. Any distribution, use or
copying of this e-mail or the information it contains by other than the
intended recipient(s) is unauthorized. If you are not the intended
recipient, please notify me at the telephone number shown above or by return
e-mail and delete this communication and any copy immediately. Thank you.

 

Le présent courriel a été expédié par CanAdapt Solutions Inc. Toute
distribution, utilisation ou reproduction du courriel ou des renseignements
qui s'y trouvent par une personne autre que son destinataire prévu est
interdite. Si vous avez reçu le message par erreur, veuillez m'en aviser par
téléphone (au numéro précité) ou par courriel, puis supprimer sans délai la
version originale de la communication ainsi que toutes ses copies. Je vous
remercie de votre collaboration.

 

From: Steve Faulkner [mailto:faulkner.steve@gmail.com] 
Sent: January 14, 2014 6:01 AM
To: David MacDonald
Cc: Detlev Fischer; rcorominas@technosite.es; Joshue O Connor;
w3c-wai-gl@w3.org; kirsten@can-adapt.com
Subject: Re: [html-techs-tf] caption vs alt

 

 

On 14 January 2014 10:55, David MacDonald <david100@sympatico.ca> wrote:

My experience is
that once assistive technologies look at an element or attribute and make a
bad decision about how to execute it the possibility of future accessibility
support is weakened considerably.

 

Hi dave I am unclear how you came to the conclusion about figure/figcaption,
what I think has happened so far is nothing as far as AT is concerned. i.e.
the support is as yet unimplemented and browser acc layer support is still
in its infancy.




--

Regards

SteveF

HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/>