Important note: This Wiki page is edited by participants of the AGWG. It does not necessarily represent consensus and it may have incorrect information or information that is not supported by other Working Group participants, WAI, or W3C. It may also have some very useful information.
Adapting text user to content requirements table
A table to help correlate issues found (what actually breaks for users), content requirements (what authors need to do), as well as to help determine LVTF Actions for SC 78 going forward.
|Issue #||Issues found (what actually breaks for users)||Content requirements (what authors need to do)||LVTF Action for SC 78|
|1||Unreadable text (either wrapping out of the containing box, or causing boxes to overlap) when a large font-family is selected and/or increased spacing is applied to text for some layouts.||Allow for spacing buffer||Verify with Wayne that the spacing metrics in the SC are adequate for when a large font-family is selected and/or increased spacing is applied to text for some layouts. Then remove the font bullet. So far Wayne has said that the numbers are fine as currently specified.|
|2||Un-clickable links, when a large font-family is selected and/or increased spacing is applied to text for some layouts.||Same as #1||Same as #1|
|3||Icons fonts disappear when font-family is overridden.||Use foreground (HTML) image methods such as img / svg, or provide fallback. Identify background images that are content in a semantic way so they can be ignored by the user-agent changes. Use James' Icon Font Technique||
Nothing/not applicable for SC 78 as it is a failure of 1.3.1 and 4.1.2. We have identified a technique. The LVTF has filed bug #297 on 2.1, has drafted a technique (maybe do a failure too?), and may consider publicizing in LVTF announcements.
F87: Failure of Success Criterion 1.3.1 due to inserting non-decorative content by using :before and :after pseudo-elements and the 'content' property in CSS.
|4||Icons can become unreadable when colors are changed when they are background-images.||Same as #3||Same as #3|
|5||Background image sprites used for text become unreadable when high contrast mode is enabled.||
Heed F3 (Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information).
|Same as #3|
|6||Text becomes unreadable when author changes foreground color and doesn't change background color.||Heed F24: Success Criterion 1.4.3, 1.4.6 and 1.4.8 due to specifying foreground colors without specifying background colors or vice versa.||Remove color as a bullet point as it is already covered per F24.|
|7||Text that is hidden with color becomes visible.||Don't hide text with color. Heed 1.4.3 Contrast (Minimum): The visual presentation of text and images of text has a contrast ratio of at least 4.5:1.||Nothing/not applicable for SC 78.|
|8||Transparent images used for text in controls that depend on a page's background color for visibility become unreadable when background color is overridden.||Same as #3?||Nothing/not applicable for SC 78.|
|9||User adding text in Canvas using a string is not able to be overridden.||Nothing/not applicable.||In the understanding document state that we consider the Canvas implementation of text to be images of text. Ref @mraccess77.|
|10||Users have difficulty overriding author inline CSS rules that use !important.||Nothing/not applicable: No content requirement as users can override inline !important author CSS rules. Users need to carefully craft their user rules to be at the same or higher specificity level as an author's rules. This necessitates users investigating an author's markup. Check CSS !important Spacing Test||Nothing/not applicable for SC 78.|
|11||The Stylish addon does not override author inline !important CSS rules.||Nothing/not applicable: No requirement as this is a Stylish bug. The addon applies CSS at document level and not as a true user stylesheet. Check CSS !important Spacing Test||Nothing/not applicable for SC 78.|
Related page: Text adaptation user to content requirements