This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
If the user wishes to increase the size of text in an iframe or other container element, the text may overflow the container. When text overflows the size of a box and the attribute value is set so that the overflow value is "hidden", the overflow text may not be passed to the Assistive Technology and the user may not be able to see the text that does not fit in the container. Proposal: Add after chart (Attribute value/'overflow' value) When the user has increased the text size of the document, the 'overflow' value should always be set to 'scroll'.
The HTML Accessibility Task Force intends to track these issues, per the proposal at http://lists.w3.org/Archives/Public/public-html-a11y/2010Jan/0245.html.
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: This doesn't seem to be in scope for HTML. This problem exists with any element in CSS, not just <iframe>s. If you have a <p> element with a given width and height in pixels, and the font-size is changed without the author's intent, then an 'overflow' value other than 'scroll' or 'auto' will similarly cause problems. Fixing this just for <iframe> isn't a thorough solution. In general, UAs that only allow changing the font size are generally not going to work. The recommended way of providing zooming is to zoom the pixel size, not the font size, and this handles this case fine. It also happens to be what all UAs do these days.
http://www.w3.org/2002/09/wbs/44061/20100520_bugs/results#x8622 Assign to Gez Lemon to create a change proposal.
Bug triage sub-team accepts disposition of this issue. There is a general user agent issue, but we believe this should be addressed in Implementing UAAG 2.0 and will refer this to the UAWG.