(Continuation)
Jason, sooner than I expected, you have finally convinced me to use REM!
I see PX everywhere, blogs, books, online courses and while inspecting webpages with the Chrome inspecting tool (including the MDN website). So I was a bit skeptical about REM and afraid of messing up the layout of the webpages. Then I checked the CSS files of an MDN webpage and realized that they use REM, just the Chrome tool tells the (computed?) value in PX. I needed to see REM in use before changing my mind for good.
I have read about *your* different devices in the past, but this time I really got it. Maybe, because I have been thinking on how the webpage should look on a very large screen: should I limit the content to centered 1366px? Then, if I use REM and your large screen device has 32px as default font size, everything auto adjusts, like seeing a movie on the television or going to the movie theater.
Now I have (maybe unnecessary, but works as a guide/reminder for my work):
body { font-size: 1rem; }
--
You { ..AND using the media attribute so you aren't sending "style" to UA's that don't care, or where certain style (like overriding tables with display:block or flex) doesn't screw over accessibility UA's. }
This part I didn't get.
I don't know the meaning of "UA". I don't get how display "block" or "flex" can be bad for screw readers.
I understand that you are talking about the "media" attribute of a link to an external style sheet.
According to MDN are 3 values for media types: all, screen and print.
Is media type relevant? Is printing an ordinary webpage (not a PDF) necessary?
--
I really think that you should write a book about web development, with easy step-by-step visual examples (screenshots showing PX x REM, for example).
In case, you don't want a book. How about an article series? I know you have some. But for this, you should consider:
1. Not all of your readers are fluent in English. I have to read your texts 3 times at least, and many times I have to guess what you mean.
2. Not all (almost none) of your readers have your deep knowledge.
3. Not all of your readers have your fast thinking.
About 2 and 3: maybe you should imagine yourself teaching babies, just small focused bits one by one. Be sure everybody understands the acronyms. You focus a lot about what not to do, but you should focus more on what to do and how to do, because that's what we, the newbies, need. Also, the why to do and the why not to do should be more practical than theoretical. Newbies don't care about
"what HTML is meant to be", they care about their webpages, being fast, looking pretty and easy to do.
I don't know all your work. Thus, maybe my remarks are unfair and not helpful.
---
Cheers!
