Adjust the background/text color when a field is made read-only by UI policy

[#1]

Does anyone know how to adjust the background/text color when a field is made read-only by UI policy?

Typically, when needing to make fields read-only on a form, I am enforcing this by UI Policy rather than Clint script because any scripting I don't have to do is preferable in case I'm not here and something is wrong (and I am lazy).

The problem that was brought to my attention was that fields made read only via a UI policy are "hard for old men with bad eyes to read" and fields disabled by Dictionary or Client script are more legible.

I attached a screenshot. The UI policy disabled fields appear like a screen was put over the field and there is way less contrast between the background and text colors. As if the text was actually lightened because it does not look black anymore. The dictionary/script disabled fields are an inset darker gray color, and the text remains the same color.

I'm guessing there is a property somewhere that controls the way it appears, or if it doesn't exist, it uses the out-of-box coloring. I have looked all through Styles, Properties and everywhere I can think of to locate something that controls the background/text color but the closest I can get are the css entries for field labels.

I don't want to have to convert these UI Policies to scripts, but will if I have to.

[cybermom302003]

Did you find a solution to this yet? I am having the same problem.

[#3]

cybermom302003

Negative.
Unfortunately I didn't spend much more time on it. I had more action items to handle, and one was tweaking the Approval Summarizer for Change Req's. Just basically added or changed entries into the XML. All the fields that were hard for old men to read ended up on the summarizer and they thought it was great. I didn't need to spend anymore time on it. I would still like to revisit it because I personally don't like the mismatched grays. I feel like writing client scripts would take less time though.

[cybermom302003]

Oddly enough, I found that a UI Policy works to resolve this if you are using FireFox. The text in a disabled field is black rather than gray.