Skip to content

[css-color-hdr] How to account for HDR in the cascade when UAs "limit the maximum luminance at a user option." #11790

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cookiecrook opened this issue Feb 26, 2025 · 4 comments
Assignees
Labels
css-color-hdr CSS HDR extension

Comments

@cookiecrook
Copy link
Contributor

cookiecrook commented Feb 26, 2025

Accessibility section of the CSS COLOR HDR spec says:

Some individuals may have a sensitivity to very bright colors, so user agents should provide a mechanism to limit the maximum luminance at user option.

Cite: https://www.w3.org/TR/css-color-hdr-1/#a11y

Apple's Reduce White Point is an accessibility feature for users experiencing light-sensitivity; often a comorbidity of low vision.

My question is how should this (or other UA switch as recommended) be implemented to work within the cascade context of HDR images and video? I heard some proposals about adding an user agent style sheet property (or using dynamic-range-limit?) to enable HDR by default, but allow authors (or an UA/AT feature like Reduce White Point) to override the default value.

@cookiecrook
Copy link
Contributor Author

@weinig @smfr @svgeesus FYI

@cookiecrook cookiecrook changed the title [css-color-hdr] How to account for HDR in the cascade when UAs "limit the maximum luminance at a user option. [css-color-hdr] How to account for HDR in the cascade when UAs "limit the maximum luminance at a user option." Feb 26, 2025
@svgeesus svgeesus added the css-color-hdr CSS HDR extension label Feb 26, 2025
@smfr
Copy link
Contributor

smfr commented Feb 27, 2025

I assume Reduce White Point acts on the entire screen? Isn't the OS-level reduction sufficient?

@cookiecrook
Copy link
Contributor Author

Yes, and reading between the lines, you’re correct that there probably isn’t a need for a media feature. However, the spec also includes this line:

The dynamic-range-limit property could also be set to standard or constrained-high in a user stylesheet.

I presume that’s in reaction to the user setting, and it’s not clear how the two recommendations fit together.

@svgeesus svgeesus self-assigned this Mar 3, 2025
@svgeesus
Copy link
Contributor

svgeesus commented Mar 3, 2025

I agree that setting it in a user stylesheet would set a useful default, but without !important would lose against a higher specificity rule in an author stylesheet.

What is needed is more of an override, like "always treat no-limit as constrained-high"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
css-color-hdr CSS HDR extension
Projects
None yet
Development

No branches or pull requests

3 participants