dmazzoni@, lpalmaro@: WDYT? Do you think there would be a demand for this API? Or do you have any use cases in your mind?

Currently chrome.accessibilityFeatures seems to be focused on enabling/disabling accessibility features rather than changing preferences of those features.

My proposal is to add chrome.accessibilityFeatures.screenMagnifierScale if we are going to expose it.

It may be worth doing even if there isn't much demand. But if there is a demand, it should be better if we can implement this API as it covers expected use cases.