Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I mean no offense, but you're effectively writing a post about how people are neglecting 5-10% of the population who are dyslexics in a font that is utterly unreadable to the other 90-95%. I'm not exactly sure whether that will have the wanted effect.


It's not clear to me what you are trying to say. Accessibility issues have to logically start somewhere.

Do you understand what the wanted effect is? Because I'm pretty sure the gist of this entire discussion is: Don't use inline styles, which any front-end developer worth their salt would already agree to[1], outside of the accessibility debate. But what is more, accessibility might be one of many reasons why a front-end developer would raise the point about inline style at all.

[1] http://www.youtube.com/watch?v=R-BX4N8egEc


What I'm trying to say is that you can't make a point about accessibility by making the point (not fully but quite) inaccessible to most people. I agree that this is an issue, but you're not pointing it out in the best way possible. In fact, you're doing exactly what you're trying to get rid of.

What is needed is something like Dyslite[1] but free (and probably better). A browser plugin that overrides font-settings to use dyslexia-optimized fonts. Ranting about inline-styles doesn't help anyone. Clearly, one should be able to override even inline-styles for accessibility rather than forbidding web designers their use, even though I agree it's not exactly a good practice anyway.

Then again, I like to say that there's always a time and place for everything. Damnit even goto's have some valid use cases.

[1] http://dyslite.com


Dyslite is a software product. This is an impromptu conversation on a message board.

If that's what you mean by your concluding comments. Yes, I should be working on software for these issues, and I am; -- but in my morning reading time, my crutch was kicked out from under me. If you want to say that you disagree with my style, that's fine. I disagree with yours. Most people, most of the time, disagree when it comes to details, and certainly, even further, on opinions of style. I'm not going to lose sleep over people disagreeing with my diction. If I did that, then I'd never get any sleep. (That is, I have not, and I will not change my style. I'm being myself, and using my own voice.)

And it still isn't even clear why this is the case, that my Stylish "!important" overrides are not overriding the inline styles of that Web page. I've provided a link to my post which contains my Stylish snippet. You can see it for yourself, that this should not be happening, given the rules of CSS Specificity.


It sounds like you should complain to the developers of Stylish or your browser.

You could also try writing a user script that deletes all font-related styles from all elements.

Does running that post through the Readable or Readability bookmarklets leave the inline styles intact?




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: