I have /classicPress 2.7.0, Classic Commerce 1.0.4, and am checking score in Pagespeed Insights. I get this error for low-contrast text. I can’t find where to add the style snippet for this class.
Can anyone help with this?
We know of the issues of Classic Commerce, and the insight you see pertains to the product page templates.
So basically that template is the product page template of Classic Commerce and you find it inside the CC plugin. This means you will need to check the template to be able to see the classes it uses in order to style them.
PSI in your first screenshot did the job, it’s telling you exactly which class:
.woocommerce-Price-amount
That being said, I never trust PSI’s suggestions. I have the same issue, but I really like muted colours, so I just ignore the low-contrast suggestion.
Thanks. I see both sides of that, but I dislike errors.
I have noticed that some color pallets differ in their opinion of readability. For example w3schools thinks white on red buttons work well and PSI doesn’t.
I thought in this case a strike-through is a good start and maybe a font-weight of 100 might satisfy both design and errors. I will have to go looking through the CSS.
Thanks again.
It’s not an error. It’s a warning. Warnings, like deprecations, make you aware of things you might want to change. Errors cause things to fail.
Correct. The terminology is less important than the effect.
I see it this way. In order to make the web user-friendly, errors are suppressed. But each error makes the website slower and they can add up quickly. I want to know what they are and fix them.
I appreciate your replies.
Terminology is important because it creates impressions. That’s why different things have different names. Errors cause things not to work. Warnings and deprecations don’t. If you call something an error when it isn’t, you create the impression that it will cause something not to work, when that’s not true. There’s plenty of unnecessary fear spread on the Internet already without adding to it.
