View source for Text adaptation user to content requirements

[[Category: WCAG 2.1]]
[[Category: Issue 78]]
A page to work out the content requirements from the user requirements and issues.

== User requirements ==

User requirements (for text-adaptation) are the ability to:

* Change the font-family to your preference.
* Change the foreground/background colors for text.
* Increase the spacing for text by letter/word/paragraph.
* Perceive non-text images that are used instead of text (e.g. icons used for buttons)

== Issues found (what actually breaks for users) ==

Let’s assume the user has the ability to select text-adaptations via a browser extension, the issues found when that is done are:

# 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.
# Un-clickable links, when a large font-family is selected and/or increased spacing is applied to text for some layouts.
# Icons can become unreadable when colors are changed when they are background-images.
# Font-icons disappear when font-family is overridden.
# Users have difficulty overriding author inline CSS rules that use !important.
# The Stylish addon does not override author inline !important CSS rules.
# Text that is hidden with color becomes visible.
# Transparent images used for text in controls that depend on a page's background color for visibility become unreadable when background color is overridden.
# Background image sprites used for text become unreadable when high contrast mode is enabled.
# Text becomes unreadable when author changes foreground color and doesn't change background color.
# User adding text in Canvas using a string is not able to be overridden.

'''@@ Any more??'''

== Content requirements (what authors need to do) ==

The content requirements could then be (straw man example):

# Allow for a 10% buffer on text size within a layout. (#1)
# Same as #1.
# Use foreground (HTML) image methods such as img / svg,  (#3) or
#* Provide fallback. Identify background images that are content in a semantic way so they can be ignored by the user-agent changes.  Use [https://www.w3.org/WAI/GL/wiki/Issue_78_Options#James.27_Icon_Font_Technique James' Icon Font Technique] (#3)
# Same as #3
# Nothing/not applicable:  No content requirement as users can override inline &#33;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 [http://www.d.umn.edu/%7Elcarlson/wcagwg/tests/user_styles/important_spacing.html CSS &#33;important Spacing Test] (#5) 
# 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 [http://www.d.umn.edu/%7Elcarlson/wcagwg/tests/user_styles/important_spacing.html CSS &#33;important Spacing Test](#6) 
# Same as #10
# Same as #3 & #10? Or does this fall under [https://github.com/w3c/wcag21/issues/10 User Interface Component Contrast (Minimum) SC]?
# Heed [https://www.w3.org/TR/WCAG20-TECHS/F3.html F3] (Failure of Success Criterion 1.1.1 due to using CSS to include images that convey important information). (#9) 
# Heed [https://www.w3.org/TR/WCAG20-TECHS/F24.html 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. (#10) 
# Nothing/not applicable. In the understanding document state that we consider Canvas's implementation of text to be images of text. (#11)

== Tracker Issues ==

* [https://www.w3.org/WAI/GL/low-vision-a11y-tf/track/issues/2 ISSUE-2: Need to think about things which are programmatically available but not visible (popups, icon fonts, background images, sprites). may need an sc.]

== LVTF resolutions ==

* [https://www.w3.org/2017/04/27-lvtf-minutes.html#resolution01 RESOLUTION: removing font family from Adapting Text SC text, because font width is very similar to letter spacing. we will address spacing and font family in the understanding document.] -27 April 2017