This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10851 - Javascript access to rendered (calculated) styling information of a DOM node
Summary: Javascript access to rendered (calculated) styling information of a DOM node
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords: a11y
Depends on:
Blocks:
 
Reported: 2010-09-30 13:42 UTC by jgunder
Modified: 2010-10-19 15:48 UTC (History)
9 users (show)

See Also:

Attachments

Description jgunder 2010-09-30 13:42:31 UTC 
Accessibility evaluation tools built into debugging tools like Firebug need to have run time (calculated) information about the foreground and background colors of rendered text content and the information about other rendering information related to CSS display and visibility properties.  This information is critical for the evaluation of color contrast requirements of WCAG 2.0 and for determining if structural information like headers is visible to assistive technologies like screen readers.
Comment 1 Boris Zbarsky 2010-09-30 14:06:42 UTC 
What makes this an HTML spec issue?
Comment 2 Tab Atkins Jr. 2010-09-30 14:49:46 UTC 
This is a CSS issue, not an HTML issue.  Specifically, it's an issue for the CSS Object Model, which defines the javascript interface with CSS.

Asking an element for its foreground and background colors is trivial by using the getComputedStyle() function and asking it for 'color' and 'background-color'.
Comment 3 Ian 'Hixie' Hickson 2010-09-30 18:46:34 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Closing based on comment 1 and comment 2. Please reopen if this is indeed an HTML spec issue, but if so please indicate more clearly what you would like changed exactly.
Comment 4 Martin Kliehm 2010-10-19 15:48:56 UTC 
The bug-triage sub team agrees with comment 2, not making this a11yTF priority