See also: IRC log
<trackbot> Date: 08 January 2015
<scribe> scribe: allanj
<scribe> New Disposition update http://jspellman.github.io/UAAG-LC-Comment/
<Jan> brb
<Jan> back
open item 3
<Greg> In Firefox, right-click anywhere on the page, choose Inspect Element to bring up the Page Inspector, click the Style Editor button, type the following into the source pane: "* {line-height:200%}".
proposal withdrawn.
text customization http://lists.w3.org/Archives/Public/w3c-wai-ua/2014OctDec/0071.html
proposal withdrawn http://lists.w3.org/Archives/Public/w3c-wai-ua/2015JanMar/0004.html
close item 3
Open Item 1
discussion of comments
jr: need to arrive at spirit, not specific numbers.
js: need to be technology agnostic and not so specific (have comments regarding being too specific)
<Jan> 1.8.5 Allow Zoom:
<Jan> The user can rescale content within top-level graphical viewports as follows: (Level A)
<Jan> Zoom in: to 500% or more of the default size
<Jan> Zoom out: to 10% or less of the default size, so the content fits within the height or width of the viewport
gl: worry about when we say 3
values, they may choose the smallest increments that meet the
rule but are not helpful to users.
... agree with Jan, that we change wording and give at least 1
and a range 3 values between 1.25 and 2
<Jan> maybe...Line spacing, choosing from a range with at least three values up to at least 2 times the default.
from the LC 9/14 Line spacing, choosing from a range with at least three values
gl: note: better to provide a large range of increments. go into reference doc
RESOLUTION: change bullet 4 of 1.4.1 to be "Line spacing, choosing from a range with at least three values up to at least 2 times the default."
<Greg> Note: When it comes to magnification, size, or spacing, the optimum value for a given user would vary based on their visual impairment and the size of the content they’re reading. Therefore it’s recommended that user agents provide a wider range of values, and a greater number of increments, to allow the user to adjust the view for their current task.
<jeanne> ... At a minimum, we recommend 1, 1.25, 1.5 and 2.0
<Greg> That Note applies not just to 1.4.1 bullet 4, but also to a number of other SCs and their bullets.
<Greg> Maybe it should join the other 3 Notes in the intro to 1.4.
<jeanne> ... At a minimum, we recommend a line spacing options of 1, 1.25, 1.5 and 2.0
<Greg> Although I wouldn't mind linking to that Note from the related resources for each affected SC, or reiterate it.
<Greg> 1.4 Note 3 is incorrect. It says "For platforms without user stylesheets, text configuration needs to be provide to users through the user agent's main user interface." but it can also be satisfied using extensions.
<Greg> At a minimum, we recommend a line spacing options of 1, 1.25, 1.5 and 2.0, and a text scale of 1, ...
http://www.w3.org/WAI/UA/2014/ED-UAAG20-20140410/#gl-text-config
<jeanne> Last CAll version of 1.4 is http://www.w3.org/TR/2013/WD-UAAG20-20131107/#gl-text-config
js: the reason we too out the
numbers was to be more consistent
... numbers should not be in main document, and better in
reference doc
jr: like the line height number. good to quantify where we can - provide a range, but not strip all numbers.
<Jan> URI?
<jeanne> http://w3c.github.io/UAAG/UAAG20-Reference/#sc_141
<jeanne> At a minimum, it is recommended to give line spacing options of 1, 1.25, 1.5 and 2.0.
<jeanne> At a minimum, it is recommended to offer line spacing options of 1, 1.25, 1.5 and 2.0.
RESOLUTION: Added Note 4 to GL1.4 and changed the intent of 1.4.1
<Greg> 1.4 Note 3 is incorrect. It says "For platforms without user stylesheets, text configuration needs to be provide to users through the user agent's main user interface." but it can also be satisfied using extensions.
current wording Note 3: The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provide to users through the user agent's main user interface.
<Greg> As I said, it can also be met using extensions, not just the main UI.
proposed: Note 3: The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provided to users through the user agent's main user interface or via an extension..
RESOLUTION: changed wording on Note 3 to be Note 3: The success criteria in guideline 1.4 can be met through user stylesheets. For platforms without user stylesheets, text configuration needs to be provided to users through the user agent's main user interface or via an extension.
<jeanne> From Shawn: Current text: "1.8.5 Allow Zoom: The user can rescale content within
<jeanne> top-level graphical viewports as follows: (Level A) Zoom in: to 500% or
<jeanne> more of the default size..."
<jeanne> As it is written, a user agent that provided just two options for zoom:
<jeanne> 100% and 500%, would meet this criteria; however, that's not
<jeanne> sufficiently accessible because the vast majority of users who need zoom
<jeanne> will need it at a percent in between 100 & 500%.
comment: Current text: "1.8.5 Allow Zoom: The user can rescale content within
top-level graphical viewports as follows: (Level A) Zoom in: to 500% or
more of the default size..."
As it is written, a user agent that provided just two options for zoom:
100% and 500%, would meet this criteria; however, that's not
sufficiently accessible because the vast majority of users who need zoom
will need it at a percent in between 100 & 500%.
<jeanne> Above is Shawn's comment, pasted in twice
ja: don't see only 500% I see a range
gl: the wording means a UA could do only 500% and comply
js: this is already well implemented, the UA already have nearly infinite zoom up to 500%, this is fighting over wording for something that is already done. UAAG wording is agnostic and allows UAs to use what ever method to provide the scaling to 500%
kp: agrees with js
gl: raises mobile device flag...different devices provide different limitations
RESOLUTION: Comment is not accepted because this is already well implemented, the UA already have nearly infinite zoom up to 500%, this is fighting over wording for something that is already done. UAAG wording is agnostic and allows UAs to use what ever method to provide the scaling to 500%
perhaps add the range of values to the reference document
Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the font height
Character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width
<jeanne> Shawn's comment: * Current text: "Character spacing, choosing from a range with at least
<jeanne> 5 values" This may have the same issue as above, although maybe not because the
<jeanne> range of character spacing needed is far less, afaik.
Word spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width
gl: not currently implemented in UAs, user must use CSS and can choose whatever size they need.
RESOLUTION: add the following to the Reference document for 1.4.3
Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the font height
Character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width
Word spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width
<jeanne> Line spacing is already in 1.4.1, and Word spacing has been dropped
RESOLUTION: add Character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width to reference doc under 1.4.3
<jeanne> Fonts are installed, colors are platform
<Greg> We should change 1.4.2 to say "installed fonts" rather than "platform fonts", to match 1.4.1.
RESOLUTIONS: UA will use "installed fonts" and "platform colors" - additional fonts can be installed, colors only exist on the platform
gl: want to be able to turn off Globally bold, italics, and underline.
<Greg> I argue that there is a need to be able to turn off bolding, underlining, and italicizing; turning them off is less important, although there may be cases where a person finds a certain font, bolded, to be the easiest to read, and wants to have the entire page done that way.
js: bolding decreases character spacing and increases character width.
<jeanne> I disagree, people would be better served with a different font or size than bolding.
<Greg> ED-UAAG20-20131030-table.htm: <td class"whole-line"><strong class="title">1.4.3 Text Spacing and Style (Globally):</strong> The user can globally s
<Greg> et all of the following characteristics of visually rendered blocks of text:(Level AA) * Line spacing of at least 1.0, 1.3, 1.5, and 2.0 times the fon
<Greg> t height * Character spacing of at least 0.01, 0.03, 0.06, 0.09 times the base character width * Word spacing of at least 0.01, 0.03, 0.06, 0.09 ti
<Greg> mes the base character width * Text style (underline, italic, bold) * Justification (left, right, or full)</td>
<Greg> As you can see, we used to have text style as a required global configuration.
was in http://www.w3.org/WAI/UA/2014/ED-UAAG20-20140213/#gl-text-config
<Greg> Discussing whether word-spacing should be restored, after we deleted it a while back. It can be adjusted using CSS using Page Inspector, Stylish, etc., just as other things we do require (e.g. line spacing).
<Greg> Jeanne is concerned that it might discourage things like PDF rendering plug-ins from trying to comply with UAAG20, if they can't comply with something as small as word spacing.
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found Scribe: allanj Inferring ScribeNick: allanj Default Present: Jim_Allan, Jeanne, Greg_Lowney, Jan, Kim_Patch Present: Jim_Allan Jeanne Greg_Lowney Jan Kim_Patch Regrets: Eric Found Date: 08 Jan 2015 Guessing minutes URL: http://www.w3.org/2015/01/08-ua-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]