Open Bug 1616916 Opened 5 years ago Updated 1 years ago

SVGs rendered in high contrast mode should match CSSWG defined behaviour

Categories

(Core :: SVG, defect, P3)

defect

Tracking

()

Accessibility Severity s3

People

(Reporter: morgan, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(2 files)

Attached file forced-colors-mode-18.html (deleted) —

See https://github.com/w3c/csswg-drafts/issues/3855

I've attached a test case from WPT which should (eventually) be merged, but hasn't been for right now.

Attached file forced-colors-mode-18-ref.html (deleted) —
Summary: SVGs rendered in HCM should match CSSWG defined behaviour → SVGs rendered in high contrast mode should match CSSWG defined behaviour
Keywords: access
Priority: -- → P3
Blocks: hcm
Whiteboard: [access-p2]

Updating the Accessibility Team's impact assessment to conform with the new triage guidelines. See https://wiki.mozilla.org/Accessibility/Triage for descriptions of these whiteboard flags.

Whiteboard: [access-p2] → [access-s3]

nytimes.com is a great example of incorrect SVG usage in the wild.

Flags: needinfo?(mreschenberg)

Thanks addie! 😀

Flags: needinfo?(mreschenberg)
Severity: normal → S3
Accessibility Severity: --- → s3
Whiteboard: [access-s3]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: