Skip to content
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

Add some actionable advice to "Large scale (text) > Note 1" in the glossary #228

Closed
patrickhlauke opened this issue Aug 16, 2016 · 7 comments
Labels
ErratumRaised Potential erratum for a Recommendation Survey - Has pull request Don't put this in the survey, include the PR

Comments

@patrickhlauke
Copy link
Member

In https://www.w3.org/TR/WCAG20/#larger-scaledef Note 1 currently reads

Note 1: Fonts with extraordinarily thin strokes or unusual features and characteristics that reduce the familiarity of their letter forms are harder to read, especially at lower contrast levels.

This does not provide any actual advice to authors (or auditors). I'd recommend a (slightly expanded) cherry-pick of https://github.com/patrickhlauke/wcag/commit/c15ab1771b8bc61e5cef5bfea1e1e26ad6cf43bd (which does not substantially change the meaning of the definition, nor the note, but closes the loop in terms of why it's actually mentioned)

@joshueoconnor
Copy link
Contributor

Thanks Patrick. That's one for the LVTF to review. @lauracarlson could you make sure this gets on the LVTF radar?

@lauracarlson
Copy link
Contributor

lauracarlson commented Aug 22, 2016

@joshueoconnor will do.

The email message to the LVTF is WCAG WG Github Issue #228.

@joshueoconnor
Copy link
Contributor

Thanks! @lauracarlson

@mraccess77
Copy link

My initial thoughts: We could start by adding "advisory" and then go on to explain that just because large scale text is used doesn't mean the text will be readable or have the needed contrast for users with low vision etc. That is one thing that Gregg V. has brought up before -- just because we allow large text to have lesser contrast doesn't mean the text will be readable by people with low vision. Also the larger the text does not mean less contrast is always acceptable. You could have text a foot high and if it has low contrast it may be unperceivable by some people with low vision.

@alastc
Copy link
Contributor

alastc commented Jun 10, 2019

I've created a PR in this repo, #774.

It seems like a small update, but reasoanble advice for people.

Anything further would overlap with #665

@alastc alastc added ErratumRaised Potential erratum for a Recommendation Survey - Ready for labels Jun 10, 2019
@alastc alastc added Survey - Has pull request Don't put this in the survey, include the PR and removed Survey - Ready for labels Jun 20, 2019
@alastc
Copy link
Contributor

alastc commented Jul 30, 2019

From the group's discussion: We won't accept the pull request, but we'll make a similar change to the understanding document.

@patrickhlauke
Copy link
Member Author

Probably superseded by this #2083

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ErratumRaised Potential erratum for a Recommendation Survey - Has pull request Don't put this in the survey, include the PR
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants