- From: Philip Jägenstedt <philipj@opera.com>
- Date: Tue, 27 Mar 2012 10:49:45 +0200
- To: public-html@w3.org
On Tue, 27 Mar 2012 04:47:07 +0200, Charles Pritchard <chuck@jumis.com> wrote: > 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 > vendors. > 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. I encourage anyone who finds bugs or limitations in Opera's implementation of <video controls> to file bugs at https://bugs.opera.com/wizarddesktop/ and to mail me the bug number. I assume that other vendors also welcome such feedback. -- Philip Jägenstedt Core Developer Opera Software
Received on Tuesday, 27 March 2012 08:50:16 UTC