W3C home > Mailing lists > Public > public-html@w3.org > March 2012

Re: Text description for @poster (was RE: CP, ISSUE-30: Link longdesc to role of img [Was: hypothetical question on longdesc])

From: Charles Pritchard <chuck@jumis.com>
Date: Mon, 26 Mar 2012 19:47:07 -0700
Message-ID: <4F712A2B.7020107@jumis.com>
To: Leif H Silli <xn--mlform-iua@xn--mlform-iua.no>
CC: laura.lee.carlson@gmail.com, silviapfeiffer1@gmail.com, html-a11y@w3.org, public-html@w3.org
On 3/26/12 5:50 PM, Leif H Silli wrote:
> Laura Carlson 26/3/'12,  19:13
>> I hope that everyone in the HTML Working Group comprehends the big
>> picture here. Increasingly HTML5 is relying on ARIA to provide for
>> HTML5's accessibility failings.
> It is not a problem that Aria is a good technology.

HTML5 is increasingly trying to restrict ARIA usage in the DOM as part 
of an effort for better HTML practices. That is a growing problem.

The <video controls> UI element is only partially implemented by many 
It is a very basic, immature component in most code bases.

Yes, it can be "fixed" by using JavaScript and ARIA. Use an image tag 
and JavaScript to swap in the video as a sibling, and implement JS+ARIA 
based video controls. It fixes all sorts of issues. But as a long term 
solution, it's quite verbose and heavily relies on ARIA flow vocabulary. 
It doesn't work well for static pages.

It would benefit many an author if the stock <video controls> UI were 
higher quality. If authors are going to use native controls, those 
controls need to be easy, fast and have quality. Otherwise authors are 
stuck using media players through the <object> tag or developing large 
component libraries with JS.

Received on Tuesday, 27 March 2012 02:47:32 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:45:50 UTC