41–50 of 81 posts
Earlier quoted context omitted.
Custom CSS risks being scope creep, IMO. A dark mode with options of a standard dark and a pure black dark would likely account for 99% of use anyways.
Custom CSS also means users can fix the designed-for-480p font sizes and paragraph widths, which the HN crew seem to have no interest in doing.
[1] https://www.accessibilitychecker.org/audit/?website=https%3A...
Earlier quoted context omitted.
I'd suggest a two phase approach. 1) come into conformance with the least possible change to current experience, and 2) make the structural change which might change current user experience but provides for assisted access improvement. I'm not a fan of big-change, and I am of a belief most of the current HN mob are pretty OK that it remains much as it is (not that they are unwilling to countenance change but there's…
This isn't the first time these issues have been brought up though. Or even the tenth time. I've seen many small open source projects make accessibility a top priority, actively seeking feedback from visually impaired users, going through multiple prototypes etc. With HN, this just continues to not happen. I could produce a 10-line CSS patch that would solve lots of issues, but at this point I have no reason to belie…
Earlier quoted context omitted.
Custom CSS also means users can fix the designed-for-480p font sizes and paragraph widths, which the HN crew seem to have no interest in doing.
It won't fix the multiple "critical" accessibility issues[1] though, some of which require HTML changes for screen reader users. [1] https://www.accessibilitychecker.org/audit/?website=https%3A...
Dark mode can come after that (some may want dark mode all the time, some may want it to obey system settings, some may want a simple toggle on every screen).
Trivial to do in Brave (for MacOS or iOS).
Earlier quoted context omitted.
Dark Reader is free and open source software, always has been. That price on the main page is just for a voluntary donation if you so desire. The free download buttons are in the middle of the page. There are also multiple links to the source code at the bottom.
Not true. You must install from the AppStore and it charges you.
Just use the links in the middle of the page and it will install it for free like every other normal browser extension people use all the time.
https://addons.mozilla.org/en-US/firefox/addon/darkreader/
The firefox extension alone has 1 million installs just from this page, we all installed it for free and have been using it for years. I think asserting that there are only paid options is disingenuous to say the least.
What I'd* like to do is let people upload their own CSS and have HN serve it back to them. Then you can make your own darkmode (or anymode), and people can share them so you can reuse someone else's. One question this is contingent on: does there exist a well-defined secure subset of CSS such that we don't have to worry about weird vulnerabilities? * actually I think this was originally kogir's idea