Open Bug 1542151 Opened 5 years ago Updated 2 years ago

The Color Contrast Accessibility tool Will not display the updated Contrast info in Dev Tools for the same text

Categories

(DevTools :: Accessibility Tools, defect, P3)

Desktop
All
defect

Tracking

(firefox66 disabled, firefox67 affected, firefox68 affected)

Tracking Status
firefox66 --- disabled
firefox67 --- affected
firefox68 --- affected

People

(Reporter: rdoghi, Unassigned)

Details

Attachments

(2 files)

Attached video TextColor.mp4

[Affected versions]:
Nightly 68.0a1

[Affected platforms]:
Platforms: All

Steps :

  1. Launch the Firefox browser and reach the https://contrast-ratio.com/
  2. Turn On accessibility tools.
  3. Use the Inspector to hover over any text in order to see the Contrast Ratio.
  4. Click that text in order to see the Contrast information in DevTools.
  5. Change the Color of the text to any other color or contrast.
  6. Use the inspector to hover over the same text in order to see the new Contrast information.
  7. Click the same text as before.

Expected Results :
The New contrast information should be updated in dev tools as well.

Actual Results :

The old Contrast information is not updated in dev tools.

We don't re-calculate contrast values, unless the node gets re-selected. We need to explore ways of how to determine if the contrast needs to be re-calculated.

Priority: -- → P3

I've run into this as well. Another thing that would help here is that if you select a node in one tree, it would also be selected in the other tree so you don't have to find the same thing twice. I realize this is complicated somewhat by these trees being separate to some extent, but it would make debugging a whole lot better.

(In reply to Anne (:annevk) from comment #2)

I've run into this as well. Another thing that would help here is that if you select a node in one tree, it would also be selected in the other tree so you don't have to find the same thing twice. I realize this is complicated somewhat by these trees being separate to some extent, but it would make debugging a whole lot better.

Just a comment regarding the navigating to the right node between trees, in inspector if you open a context menu for a node, you can choose inspect accessibility properties item to jump to the corresponding accessible object.

The problem is the other way around, right? You've found an accessibility issue and then want to make some changes in the node tree.

(In reply to Anne (:annevk) from comment #4)

The problem is the other way around, right? You've found an accessibility issue and then want to make some changes in the node tree.

Ah in that case, in the sidebar in properties, you can click on the target icon in the DOMNode row.

Thanks Yura, that's great! (I also ran into the issue reported by OP though, in that I tried to change some colors around and the accessibility panel still showed the old results.)

Flags: needinfo?(annevk)

Yep, this is tracked and will be fixed in the next couple of releases.

Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.