-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Text spacing update #860
Text spacing update #860
Conversation
<p>The intent of this Success Criterion (SC) is to ensure that people can override text spacing to improve their reading experience. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.</p> | ||
<p>This SC focuses on the ability to increase spacing between lines, words, letters, and paragraphs. Any combination of these may assist a user with effectively reading text. As well, ensuring users can override author settings for spacing also signficantly increases the likelihood other style preferences can be set by the user. For example, a user may need to change to a wider font family than the author has set in order to effectively read text. </p> | ||
<p>The intent of this Success Criterion (SC) is to ensure that people can override author specified text spacing to improve their reading experience. Each of the requirements stipulated in the SC's four bullets helps ensure text styling can be adapted by the user to suit their needs.</p> | ||
<p>The specified metrics set a minimum baseline. The values in between the author's metrics and the metrics specified in this SC should not have loss of content or functionality.</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At first reading, it sounds like the second sentence (about in-between values) follows on directly from the fist (mentioning the minimum baseline). But that's not really the case. Maybe the second sentence needs an "also" somewhere to make it clear this is an additional intention/requirement.
Also, later on under author responsibility the same first sentence is repeated, but there's a different follow-on. That looks odd/confusing. I'd say maybe remove this paragraph here, and add the second sentence from here to the one in author responsibility, to keep it all in one place - as it's the author's responsibility to also ensure that the in-between metrics work.
Please ignore this if someone else mentioned it. I cannot read all
these emails.
The sentence: "For example, a user may need to change to a wider font
family than the author has set in order to effectively read text." is wrong.
The SC does not enable font family change. However if the default
letter spacing
for a font family is to narrow, the user can increase it.
Best, Wayne
…On Tue, Aug 13, 2019 at 3:20 PM Alastair Campbell ***@***.***> wrote:
Updates from Jim's doc, preview on rawgit
<https://raw.githack.com/w3c/wcag/text-spacing-understanding-update/understanding/21/text-spacing.html>,
but viewing the files tab is probably easiest to see the changes.
------------------------------
You can view, comment on, or merge this pull request online at:
#860
Commit Summary
- Updates from Jim's doc.
File Changes
- *M* understanding/21/text-spacing.html
<https://github.com/w3c/wcag/pull/860/files#diff-0> (9)
Patch Links:
- https://github.com/w3c/wcag/pull/860.patch
- https://github.com/w3c/wcag/pull/860.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#860?email_source=notifications&email_token=AB6Q4F4H55QRRUIRYANVQATQEMXRFA5CNFSM4ILPI37KYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HFCII3Q>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB6Q4F47TJUIIZJD2VOW75DQEMXRFANCNFSM4ILPI37A>
.
|
Updates from Jim's doc, preview on rawgit, but viewing the files tab is probably easiest to see the changes.
The previous discussion led to asking LVTF to consider this, which is where this update came from. Agreeing to this would be closing the previous issue, and not agreeing to changing the SC text.
Closes #637, #635