W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2012

Re: [webcomponents] Custom Elements Spec

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 8 May 2012 14:49:26 +0200
Message-ID: <CADnb78jGtYfb3f1r8o5y4W6T2ty53a76QfhAX=FXZL3YpQuEkg@mail.gmail.com>
To: Scott González <scott.gonzalez@gmail.com>
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Dimitri Glazkov <dglazkov@chromium.org>, Ian Hickson <ian@hixie.ch>, Rafael Weinstein <rafaelw@google.com>, public-webapps <public-webapps@w3.org>
On Tue, May 8, 2012 at 2:33 PM, Scott González <scott.gonzalez@gmail.com> wrote:
> Accessibility is hard.

What makes it hard here is that you have to implement everything from
scratch. You have to implement keyboard support, mapping to the
accessibility API (WAI-ARIA), etc. Given that those code paths will
not be frequently used on most sites (including by the sites'
developers) it's not really surprising they either won't work at all
or are buggy.

I really think we should aim higher than "WAI-ARIA can be used,
mission accomplished" because that will result in a web where few
pages are accessible. (Given the complexity most likely only those
where this is a requirement by law or contract.)

Anne — Opera Software
Received on Tuesday, 8 May 2012 12:50:00 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:34 UTC