Understanding Text Spacing

[awkawk]

The 1.4.12 Text Spacing (AA) SC has draft Understanding content that can be viewed at Understanding Text Spacing.

Please review the Understanding document and submit a comment on this issue for any changes that are needed to the content.

[becka11y]

This understanding document is very good - I appreciate the addition of visual examples.

If I follow the Allow for Spacing Override link under the sufficient techniques in the Understanding document (https://www.w3.org/WAI/GL/wiki/Allowing_for_Spacing_Override). There is a very good explanation of how to test this SC. The test explicitly requires the screen size set to 1280x768 for testing but I can't find out why that resolution is necessary. I don't see anything in the SC text that implies a specific screen size?

FWIW most responsive web sites pass at 1280x768 using the testing technique described. More fail at lower resolutions (1024x768). Thus, since the size used for testing does make a difference in the outcome it should be explained.

I realize I am getting ahead of myself in reading and commenting on the sufficient technique but if screen size is important it should be part of the SC.

thanks

[lauracarlson]

Thanks for the comment @becka11y

Becky wrote:

The test explicitly requires the screen size set to 1280x768 for testing but I can't find out why that resolution is necessary. I don't see anything in the SC text that implies a specific screen size?

FWIW most responsive web sites pass at 1280x768 using the testing technique described. More fail at lower resolutions (1024x768). Thus, since the size used for testing does make a difference in the outcome it should be explained.

I realize I am getting ahead of myself in reading and commenting on the sufficient technique but if screen size is important it should be part of the SC.

@alastc @allanj-uaag Do you recall the rationale for 1024x768? Think that may also be applicable to the Reflow Understanding doc #781 and the Draft Allowing for Reflow Technique.

[alastc]

It looks like part of the reflow method has been copied over?

The 1280 width comes from there, because 1280px wide at 400% = 320px wide, and Reflow explicitely references that size.

For text-spacing, the width and zoom level are not important. Or rather, not dependant: theoretically text-spacing should work at any size/zoom level.

In practice we have found very few differences at different sizes, if you don't set fixed heights it's generally ok.

For testing spacing, perhaps we could say somehting like: Where a page has mutiple layouts (e.g. in a repsonsive design) text-spacing should be tested in each layout.

[lauracarlson]

Hi @alastc,

Alastair wrote,

It looks like part of the reflow method has been copied over?

Ah yes. Now I recall. Last summer we were testing both spacing and reflow SCs so the method was combined.

The 1280 width comes from there, because 1280px wide at 400% = 320px wide, and Reflow explicitely references that size.

For text-spacing, the width and zoom level are not important. Or rather, not dependant: theoretically text-spacing should work at any size/zoom level.

In practice we have found very few differences at different sizes, if you don't set fixed heights it's generally ok.

For testing spacing, perhaps we could say somehting like: Where a page has mutiple layouts (e.g. in a repsonsive design) text-spacing should be tested in each layout.

I've updated the Allowing for Spacing Override Technique with that verbiage.

Do we need to repeat "Where a page has multiple layouts (e.g. in a responsive design) text spacing should be tested in each layout" in both the Understanding Doc and the Technique? Or is it better not to go into such detail in Understanding?

Thank you!

[iamjolly]

For testing spacing, perhaps we could say somehting like: Where a page has mutiple layouts (e.g. in a repsonsive design) text-spacing should be tested in each layout.

👍 That seems very logical @alastc. And thanks @lauracarlson!

[awkawk]

@iamjolly We do have a note under "full pages" in the conformance section that says: A full page includes each variation of the page that is automatically generated by the page for various screen sizes. Each of these variations needs to conform (or needs to have a conforming alternate version) in order for the entire page to conform.

[iamjolly]

Thanks, @awkawk. I didn't originally notice that note, but it's good to know it is in there and the other info has been updated, too. You all are doing fine work on this.

[lseeman]

Can we add Ideally, there should be sufficient white space between blocks of text such as sections and call out boxes to make them easy to differentiate for people with cognitive disabilities.

@eadraffan can you improve this wording?

[alastc]

Given the inclusion of the paragraph spacing bullet in the SC, I think the intent and benefits should include that aspect as well. E.g.

increase space between lines, words, letters and paragraphs to increase reading speed.

Extending to sections & call out boxes (Lisa's line above) needs to be clearly 'additional' to the SC, I think that could be done at the end of the Intent section.

[eadraffan]

Reading the document on https://rawgit.com/w3c/wcag21/text-spacing/understanding/21/text-spacing.html - I have highlighted these suggestions in bold

The intent of this Success Criterion (SC) is to help ensure that people with disabilities who override spacing can continue to read the text. For example, people with low vision or dyslexia may override an author's set spacing to enable readability or increased reading speed. delete as this is explained in the next sentence and could confuse 'It allows for a buffer' Increased spacing between lines, words, and letters has benefits for people who want buffers between text by override author settings via user stylesheet, bookmarklet, extension, or application. They may also need to change font family (e.g. to a wider one) than the author has set to effectively read text. They may increase spacing between lines, words, and letters to effectively read text. Line spacing also helps with tracking. Tracking is following along lines of text, including getting from the end of one line to the beginning of the next line.

Also I think there are 2 errors in the exception section. Correction indicated by bold Character Spacing Individual characters in words remained intact though they were spaced a bit further apart

Word Spacing Words were spaced farther apart. In languages that do not have words (e.g. Japanese) applying word spacing had no effect. This is expected.

[lauracarlson]

Hi @eadraffan,

Thank you very much for reviewing the document. I fixed the 2 typos.

I am wondering why we would want to change the first sentence from:

The intent of this Success Criterion (SC) is to help ensure that people with disabilities who override spacing can read text.

to

The intent of this Success Criterion (SC) is to help ensure that people with disabilities who override spacing can continue to read the text.

For some people with low vision, spacing provides the ability to read text not just to continue to read it. Please consult the Accessibility Requirements for People with Low Vision (3.4 Spacing for Reading):

Some people need more space between lines to be able to read text.

Some people need more space between letters to read text.

Some people need more space between words to read text.

Thank again, Laura

[lauracarlson]

Hi @eadraffan ,

I wonder if we can simplify your proposed sentence:

Increased spacing between lines, words, and letters has benefits for people who want buffers between text by override author settings via user stylesheet, bookmarklet, extension, or application.

It has an an average grade level of about 18. It should be understood by 23 to 24 year olds. (Flesch Kincaid Reading Ease: 19.6, Flesch Kincaid Grade Level: 17.2, Gunning Fog Score 19.7., Coleman Liau Index: 19.5, and Automated Readability Index: 20.3).

How about breaking it into 2 sentences? Maybe something such as:

Increased spacing between lines, words, and letters has benefits for people who need a spacing buffer. They may override author spacing settings via user stylesheet, bookmarklet, extension, or application.

That has an average grade level of about 14. It should be easily understood by 19 to 20 year olds.

Note I changed "want" to "need" as spacing is a low vision need.

Thank you!

[lauracarlson]

@alastc wrote:

Given the inclusion of the paragraph spacing bullet in the SC, I think the intent and benefits should include that aspect as well. E.g.

Thanks, Alastair. I added "and paragraphs".

[lauracarlson]

Hi @alastc, @lseeman and all,

Lisa wrote:

Can we add Ideally, there should be sufficient white space between blocks of text such as sections and call out boxes to make them easy to differentiate for people with cognitive disabilities.

Alastair wrote:

Extending to sections & call out boxes (Lisa's line above) needs to be clearly 'additional' to the SC, I think that could be done at the end of the Intent section.

Would any one oppose adding the following to the end of the intent section?

<h3>Additional</h3>

<p>Although not required by this SC, white space between blocks of text can help people with cognitive disabilities discern sections and call out boxes.</p> 

[eadraffan]

Actually I do not think that was my sentence, but I am very happy to miss out even 'buffer' as that could be construed as being padding or an image etc. But please simplify it in the way you suggest if everyone else is happy.

Best wishes

E.A.

From: Laura Carlson [mailto:notifications@github.com] Sent: 23 April 2018 15:26 To: w3c/wcag21 wcag21@noreply.github.com Cc: eadraffan ea@emptech.info; Mention mention@noreply.github.com Subject: Re: [w3c/wcag21] Understanding Text Spacing (#783)

Hi @eadraffan https://github.com/eadraffan c

I wonder if we can simplify your proposed sentence:

Increased spacing between lines, words, and letters has benefits for people who want buffers between text by override author settings via user stylesheet, bookmarklet, extension, or application.

It has an an average grade level of about 18 https://www.webpagefx.com/tools/read-able/check.php . It should be understood by 23 to 24 year olds. (Flesch Kincaid Reading Ease: 19.6, Flesch Kincaid Grade Level: 17.2, Gunning Fog Score 19.7., Coleman Liau Index: 19.5, and Automated Readability Index: 20.3).

How about breaking it into 2 sentences? Maybe something such as:

Increased spacing between lines, words, and letters has benefits for people who need a spacing buffer. They may override author spacing settings via user stylesheet, bookmarklet, extension, or application.

That has an average grade level of about 14. It should be easily understood by 19 to 20 year olds.

Note I changed "want" to "need" as spacing is a low vision need.

Thank you!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/w3c/wcag21/issues/783#issuecomment-383594298 , or mute the thread https://github.com/notifications/unsubscribe-auth/AAtX3PUM9LNBa9JX_Yf7_15WYbsjhFZSks5treRugaJpZM4SaCxi . https://github.com/notifications/beacon/AAtX3Pjy1lzr50E-YiOpeey_8t8nqdN4ks5treRugaJpZM4SaCxi.gif

[lauracarlson]

Hi @eadraffan and all,

You wrote:

Actually I do not think that was my sentence, but I am very happy to miss out even 'buffer' as that could be construed as being padding or an image etc. But please simplify it in the way you suggest if everyone else is happy.

If 'buffer' was the original the problem that you were trying address, what if we just eliminate the sentence:

It allows for a buffer.

Then we could leave the rest as is.

Thoughts?

[lauracarlson]

Hi @lseeman

You wrote:

Ideally, there should be sufficient white space between blocks of text such as sections and call out boxes to make them easy to differentiate for people with cognitive disabilities.

Instead of adding a separate section for this as previously proposed, I added a bullet to the benefits section, as Michael said the doc has has too many sub-sections now.

[lauracarlson]

Hi @eadraffan ,

You wrote:

I am very happy to miss out even 'buffer' as that could be construed as being padding or an image etc. But please simplify it in the way you suggest if everyone else is happy.

I removed the "It allows for a buffer" sentence.

[michael-n-cooper]

Moved to https://github.com/w3c/wcag/issues/347