Syntax highlighting on the client-side has unforeseen consequences shipping & executing a bunch of code for what should be cachable, idempotent functions at build-time or server-side instead runtime affecting performance & wasting resources.
I wish I knew. There are CSS queries for monochrome displays, but it seems mine reports to the OS as full color so you can’t really work with the device specifically (screenshots come back in color too). This blows because there are obvious scenarios I would remove a light gray background behind say code because it just looks awful. Just as much, you basically only want to be using #fff & #000 unless you have a good reason.
Semi-related: Does anybody know a good approach to debugging websites on a Kindle Paperwhite Beta Browser (the old one, with grayscale e-ink screen)?
I wish I knew. There are CSS queries for monochrome displays, but it seems mine reports to the OS as full color so you can’t really work with the device specifically (screenshots come back in color too). This blows because there are obvious scenarios I would remove a light gray background behind say code because it just looks awful. Just as much, you basically only want to be using #fff & #000 unless you have a good reason.
Thanks. Sounds like a target that is hard and/or barely worth supporting. Do you have experience with other screen readers?