W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > July to September 2009

RE: HTML5 Rendering Margins and Padding

From: Jim Allan <jimallan@tsbvi.edu>
Date: Wed, 19 Aug 2009 13:14:19 -0500
To: "'Jeanne Spellman'" <jeanne@w3.org>, "'User Agent Working Group'" <w3c-wai-ua@w3.org>
Cc: "'Kelly Ford'" <Kelly.Ford@microsoft.com>, "'Markku Hakkinen'" <markku.hakkinen@gmail.com>
Message-ID: <08f301ca20f8$df0dc400$9d294c00$@edu>
Great Jeanne!
I like your proposal. The 'b' part about changing overflow to be scroll is
an issue for UAWG. Current UA with caret browsing cannot 'get into' the
overflow area to scroll the content. Unless you have a mouse or screenreader
that content is non-existent. 
On 2 April Kelly, Mark and I took an action, but it was not written
properly, so never got assigned. 

JA, MH, KF to draft a proposal by 16 April
overflow http://lists.w3.org/Archives/Public/w3c-wai-ua/2009JanMar/0087.html


navigating into scrollable overflow regions is not explicitly mentioned in
UAAG. It falls under 4.1.1 Keyboard Operation and Guideline 3.10 Help user
to use and orient within viewports, since the overflow region functions much
like a separate viewport.

Jim
> -----Original Message-----
> From: w3c-wai-ua-request@w3.org [mailto:w3c-wai-ua-request@w3.org] On
Behalf
> Of Jeanne Spellman
> Sent: Wednesday, August 19, 2009 12:44 PM
> To: User Agent Working Group
> Subject: HTML5 Rendering Margins and Padding
> 
> HTML section: 11.2.3 Margins and padding
> http://dev.w3.org/html5/spec/the-xhtml-syntax.html#margins-and-padding
> issue: 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 for change: 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'.
> 
> UAWG related issue/concern: We have addressed this for graphics:
> 3.10.5 Scrollbars: Graphical viewports include scrollbars if the
> rendered content (including after user preferences have been applied)
> extends beyond the viewport dimensions, overriding any values specified
> by the author. (Level A)
> I propose adding a new SC in 3.6 Provide text configuration.
> proposal: 3.5.x  Container overflow options. When text resized by the
> user overflows the containing element the user has the option to either:
> (a) expand the size of the containing element to display the text or
> (b) to override any author setting preventing scrollbars in order to
> display all of the text
> 
> 
> 
Received on Wednesday, 19 August 2009 18:18:34 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 06:52:15 GMT