web-accessibility Approach: browser extension vs website feature

Hey! Really interesting to stumble upon this project :)

What's the rationale for championing a site-centric rather than browser-centric solution in this space? Would it not be better to create a set of browser extensions for these features, and encourage #a11y-conscious web developers to test their sites with this tool?

Anyhow, I'm genuinely ignorant of this problem space, so hopefully my comments do come across as discouraging!

Sep 07 '13 04:09 patcon

For many browsers, the extension solution would involve creating css/js similar to what is in this repository. :)

Sep 09 '13 03:09 antijingoist

Sorry, not sure I follow. Yes, it would involve recreating that css/js in the extension, but that would be in one place rather than on every site, right? I suppose I'm not sure whether you're agreeing that an extension is the more maintainable route or not :)

Sep 09 '13 04:09 patcon

Basically, this is code that can be used in an extension, or someone's website. The intention is to provide a base. For instance, some of the same CSS is in OpenDyslexic extensions, and all of this may make it's way into browser extensions at some point. However, most of my time is currently dedicated to other projects.

Sep 10 '13 01:09 antijingoist

gotcha :+1: :)

Sep 10 '13 03:09 patcon

Meanwhile, someone made this into a browser extension, see https://github.com/javoire/dyslexia-friendly

Feb 01 '19 15:02 selfthinker