- From: Jeanne Spellman <jeanne@w3.org>
- Date: Fri, 21 Aug 2009 13:27:31 -0400
- To: User Agent Working Group <w3c-wai-ua@w3.org>
jeanne note: This is not as bad as I first understood it. Closer
examination shows that this nesting only applies to nesting in the
article, aside, nav, and section elements. However, I still think it is
significant and should be pointed out to HTML.
http://dev.w3.org/html5/spec/the-xhtml-syntax.html#fonts-and-colors
11.2.5 Fonts and colors
states: <quote>
The article, aside, nav, and section elements are expected to affect the
font size of h1 elements, based on the nesting depth. If x is a selector
that matches elements that are either article, aside, nav, or section
elements, then the following rules capture what is expected:
@namespace url(http://www.w3.org/1999/xhtml);
x h1 { font-size: 1.50em; }
x x h1 { font-size: 1.17em; }
x x x h1 { font-size: 1.00em; }
x x x x h1 { font-size: 0.83em; }
x x x x x h1 { font-size: 0.67em; }
</quote>
Issue: Users with low vision adjust font sizes to the minimum size
needed for comfortable reading. Many users with low vision do not use
assistive technology, but rather adjust to the largest font size
supported by the user agent. Reducing the size of the font -
particularly a text-dense element like "article" - increases the
imbalance between font sizes in other parts of the page (e.g. the user
would be forced to increase font size for the article text to the point
where the font size in the non-nested parts of the page are enlarged so
much as to overflow their containers. Automatic reduction of the size is
unnecessary and will decrease access for users with low vision.
Proposal: Remove the section. Nested elements should not have the
containing text size reduced automatically. The author can choose to
reduce the size of nested text through CSS, but it should not happen to
font sizes automatically.
UAAG Issue: I don't think there is a UAAG version of this. This is an
HTML and CSS issue.
Received on Friday, 21 August 2009 17:27:51 UTC