W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

Re: Front-end frameworks and accessibility

From: Patrick H. Lauke <redux@splintered.co.uk>
Date: Thu, 26 Jan 2017 10:06:54 +0000
To: w3c-wai-ig@w3.org
Message-ID: <7a32653d-64c4-8dcd-5099-084fabebab06@splintered.co.uk>
On 26/01/2017 09:46, Jens Oliver Meiert wrote:
> Very good questions around an important issue. From my experience both
> on the accessibility side and as a frameworks developer, there is
> really only so much frameworks can cater for accessibility-wise apart
> from following general best practices; too much depends on the
> content, and how the framework is actually *used*.

As one of the Bootstrap team members, I wholeheartedly agree. I've had 
to hold back from implementing very specific patterns, because authors 
often "pervert" some of our widgets/structures for completely different 
purposes, so having a lot of fixed things like very specific ARIA roles 
etc would actually lead to pages that are even less accessible than 
without them, as there would be structures that are identified as 
something they're not (if that makes sense).

> (This as well as the general impossibility for an external framework
> to know one’s needs leads me to generally advise *against* external
> frameworks [1].)
>
> Very brief take, maybe there’s discussion to differentiate a bit more.
>
>
> [1] http://www.oreilly.com/web-platform/free/book-of-html-css-frameworks.csp
>


-- 
Patrick H. Lauke

www.splintered.co.uk | https://github.com/patrickhlauke
http://flickr.com/photos/redux/ | http://redux.deviantart.com
twitter: @patrick_h_lauke | skype: patrick_h_lauke
Received on Thursday, 26 January 2017 10:07:23 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 26 January 2017 10:07:24 UTC