SAPC-APCA VS darkreader

Why the New Contrast Method APCA

For a more future oriented version (as setting a font to black wont work with dark pages), check out the CSS Color Module Level 5 spec for color-contrast(), which will automatically choose a color that has a proper contrast ratio: https://www.w3.org/TR/css-color-5/#funcdef-color-contrast

One caveat is it's currently only supported in Safari technical preview.

Another thing worth mentioning is the relative brightness algo used in the repo for the linked plugin is using the WCAG 2 formula for relative luminance. This works pretty well in light mode for non-colored backgrounds, but doesn't incorporate perceived luminosity differences of different hues very well. A better algorithm to use here is the Advanced Perceptual Contrast Algorithm (APCA), which is the one used in the WCAG 3 working spec. It more accurately accounts for hue: https://github.com/Myndex/SAPC-APCA

Note the licensing note in the repository[1] of the APCA™ index the author’s company[2] promotes:

> The files currently in this repository are presently considered pre-release, and as such do not have a permanent license attached. In this repositiory, all files present are under a time-barred beta license, and intended for use with web-based content only, and not for any other use without written permission.

The non-pre-release stuff[3] offered to W3C is better but still seems to be intended to end up non-FOSS:

> Files in this repository are licensed to the W3/AGWG under their cooperative agreement for use with WCAG accessibility guidelines for web-based content only, and not for any other use.

(The question being, of course, how much of this is copyrightable at all.)

[1] https://github.com/Myndex/SAPC-APCA/

[2] https://www.myndex.com/CVD/

[3] https://github.com/Myndex/apca-w3/

Second: There are a number of contrast checkers that use APCA technology. The canonical "official" one is https://www.myndex.com/APCA/ but I want to mention it is an open public beta, and is not backwards compatible with WCAG_2 (this is in part because WCAG_2 is not perceptually accurate and thus the areas where WCAG_2 incorrectly fails pairs that APCA will pass is at issue).

Andrew Somers W3 AGWG Invited Expert Color Science Researcher Myndex Perception Research Inventor APCA/co-author WCAG3

change to light mode, and try out https://darkreader.org/

I was able to reproduce and reported this to Dark Reader https://github.com/darkreader/darkreader/issues/11952

I highly recommend utilizing a dark reader.

I totally forgot about the atrocious default HN theme. Yeah that's unreasonable, unreadable. A low-contrast light theme is literally equivalent to shining a flashlight in your eyes. Only unreasonable people do that to others (e.g. the police).

If you use Firefox, I recommend the Dark Reader[1] extension for taking care of all the websites that insist on destroying your eyes.

[1]: https://darkreader.org

i use https://darkreader.org/ for chrome and don't see flies 99% of the time

- very efficient to navigate(shortcuts, quick tab navigation, etc.) - Shortcuts - Terminal for easy to type commands - Tab Management - Quick Tab Navigation - Search Bar Integration - Bookmark Management - History Management - Smart Address Bar - Speed Dial - Back and forward Navigation - WM like behaviour for tabs - Floating search bar for quick searches - Powerful autocomplete in address bar(stored in-browser to avoid privacy issues) - privacy focus - Use of Duck Duck Go when privacy-focus is on - Built in Powerful Adblocker - Avoids the use of trackers - Possibility to block Trackers - Possibility to search with TOR - Option to enable or disable JS fully - Option to Disable Cookies - Encrypted DNS - Auto HTTPS upgrade - DNT(Do Not Track) by default - Adoption of G-Hacks - Built in Temp-mail for not frequently visited addresses - A slider for the amount of privacy-conviniency - Whilst doing so it selects and unselects some packages - History as a Module - Don't log certain websites to History - Creation of fake entries on History - Delete History tabs easily - By name - By category - open source - decentralized - compatible all OS - consumes low resources - minimalist - highly customizable - Dark Mode by Default - Characteristics of [Dark Reader](https://darkreader.org/) - Predefined Themes - Community Themes - Support for Wallpapers - Also the ability to configure it via .config files that can be edite - Ability to make the tabs semitransparent and either show the background or a custom wallpaper - fast - Modules - Written in almighty RUST - light - easy to use - Unbloated - Modern UI - advanced users characteristics -The option to cache websites so you can access them when you don't have internet connection, they would be stored locally (might not work on all websites) -Reader Mode: Selects only the text and offers the ability to speed read(maybe through the integration of Swift read) - Vertical Tabs Option - Using commands for faster navigation - Ability to open multiple tabs at once using a shortcut - Workspace Switching - Heavy Local Focus - Modular - Rename Downloads to something meaningful - Download folder differentiation