-
Notifications
You must be signed in to change notification settings - Fork 251
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
Provide exception/limitation text for visual/presentation text #3337
Comments
I didn't file issues related to line and paragraph spacing, as they seemed to be addressed by the comment above. For posterity, though, we had some discussion of line/paragraph spacing:
Some writing systems expect larger inter-line gaps than others. @kidayasuo mentioned that case for Japanese in #2680 (comment) and @yyyug mentioned the case for Chinese in #2680 (comment) . Moreover, for Traditional Chinese, if the Bopomofo annotation mark is taller than the base character, the line spacing may need to be increased further. Moreover, the complexity of characters in some Brahmic scripts may affect line height settings too. See Tamil and Thai for examples.
Some writing systems prefer to indent the first line of a paragraph, rather than leave vertical gaps between paragraphs, like Chinese and Japanese. We should change the guideline to something like this:
@aphillips made a comment:
|
As part of discsussions between i18n and the AG chairs we're proposing to add a note (or notes) under visual presentation. I've drafted an initial note in #3351 Another aspect for Visual Presentation is that the group does not recommend requiring all level AAA criteria, that might ease the concern of some objectors. As something to point to, in WCAG under conformance there is a section on conformance levels which includes this note:
|
https://www.w3.org/TR/WCAG22/#visual-presentation
Section 1.4.12 (https://www.w3.org/TR/WCAG22/#text-spacing) provides an exception that says:
Section 1.4.8 provides no exception or note about the applicability of this SC to various languages. We think this is a "root cause" for much of the discussion in #2680, since we note that WCAG maintains that pages are compliant if they allow users to override the various presentational values up to certain limits without rendering failure, but users of various writing systems do not understand the relationship of the SC to their own needs.
One question on I18N's mind is whether WCAG intends these criteria to apply primarily to the Latin-script writing system, with others adapting as needed, or whether these criteria have been successfully used in other writing systems (and which ones?)
We would suggest that 1.4.8 include a similar "exception", although given the description of this SC in #2680, perhaps just a note of explanation. Perhaps something like:
The text was updated successfully, but these errors were encountered: