- From: Al Gilman <Alfred.S.Gilman@IEEE.org>
- Date: Thu, 21 Jul 2005 17:38:21 -0400
- To: www-style@w3.org
- Cc: wai-liaison@w3.org
<note class="lastCall comment transmittal"> This comment has met with consensus support within the Protocols and Formats Working Group. Please accept this as a comment from the Group. We would, as ever, welcome the chance to discuss this with you if it is unclear or for any reason it does not strike the CSS Working Group as a "just do it." Al /chair, Protocols and Formats WG </note> DOM Final format in CSS: We were under the impression that the CSS working group took over the CSS DOM API from the DOM working group, so this question is directed at the CSS working group. What provision is being made in the CSS DOM API to acquire the final format css properties. This information is used by assistive technologies and in fact is a fulfillment requirement of accessibility APIs. It is valuable for platform accessibility API implementations to use a standard DOM API to accomplish this task. Is the working group providing a standard API mechanism for resolving the final format font and color information of content without requiring resolving the final format by processing the cascaded style from the applied style sheets? Rich Rich Schwerdtfeger Distinguished Engineer, SWG Accessibility Architect/Strategist Emerging Technologies Chair, IBM Accessibility Architecture Review Board blog: <http://www-106.ibm.com/developerworks/blogs/dw_blog.jspa?blog=441>http://www-106.ibm.com/developerworks/blogs/dw_blog.jspa?blog=441 schwer@us.ibm.com, Phone: 512-838-4593,T/L: 678-4593, mobile: 512-876-9689 "Two roads diverged in a wood, and I - I took the one less traveled by, and that has made all the difference.", Frost
Received on Thursday, 21 July 2005 21:39:23 UTC