Re: [Bug 5758] insufficient accessibility fallback for <audio> or <video>

Joe >> This follows the model set by <object> and could result in use 
of the following construction:

.<video autoplay controls>
 <source src="tgif.vid">
 <source src="lgif.zvid">
  <p><a href="tgif.vid">Download the video file.from this
link.</a></p>
</video>

>> In this example if the UA recognizes <video ...> but does not 
>> recognize  vid content then the the potential fallback video 
>> content .zvid will be  tried. If still no go, then the html 
>> "fallback" content enclosed in <p>  element would be shown 
>> according to the <video>, <p>, and <<a> styles.

Simon > No, it wouldn't.

OK, I must be really off in my thinking of how it could work. SInce I 
haven't found an example in the spec that is giving me understanding 
(or changing my preconceptions), please tell me if the above is even a 
legitimate contruction, and how you are expecting <video> to work.

The following description of the example did not get a comment so I am 
supposing that thie following is a reasonable description of what 
should happen if <video> is not recognized by the (legacy) UA at all. 
:

>> In this example if the UA did not recognize the <video> element 
>> then the html "fallback" content enclosed in <p> and <a> element 
>> would be shown. This operation is more than just a specification 
>> for <video>, <audio>, or <object> but just intrinsically how the 
>> web UA should work: Skip elements that are not in the vocabulary. 
>> So, here, an old UA would just naturally skip <video ... >, <source 
>> ... >, and <source ... > and end up showing the html link according 
>> to the <p> and <a> style, although the UA will probalbly also apply 
>> CSS specified for <video>..

This seemed reasonable to me for this example because I suppose in 
this case the UA follows the same sort of rules as <object>.

Now, again for this case where the <video> is recognized but none of 
the <source> resources work:

>> In this example if the UA recognizes <video ...> but does not 
>> recognize .vid content then the the potential fallback video 
>> content .zvid will be tried. If still no go, then the html 
>> "fallback" content
enclosed in <p> element would be shown according to the <video>, <p>, 
and <a> styles.

Please tell me what actually should happen in the case where none of 
the listed <videdo> resources are playable.

Thank You and Best Regards,
Joe
.

Received on Monday, 15 March 2010 12:38:04 UTC