- From: Andrew Arch <andrew.arch@digital.gov.au>
- Date: Thu, 18 Feb 2016 12:00:50 +1100
- To: Shawn Henry <shawn@w3.org>
- Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
- Message-ID: <CALrq49am7OvouAHjFMc0n8xi3JcaEHhGoHWysCdtYkUW-iry_g@mail.gmail.com>
Hi Shawn and all, Re "check the next option" - yes - see previous reply Re "Rivers are primarily caused by full justification" - yes, full justification is the cause, but the effect of full justification (especially poor algorithms for it) is poor word spacing and that is what cause the rivers of white. I was suggesting the split as the spacing is what causes the rivers of white (even though the poor spacing is caused by full justification) - rivers of white is a traking issue, hence suggesting it fits under 3.2. Maybe I'm being too pedantic ;-) Re "difficulty reading because of rivers, what could they do about it" - not sure about the 'proportional font' suggestion, proportional-spaced fonts still cause rivers of white. One other ideal suggestion - "change the degree of hyphenation". [maybe talk to Bert Bos about some current CSS considerations / maybe also the Digital Publishing Interest Group / Digital Publishing A11y TF ] Andrew ------------------- *Andrew Arch* *Lead *– Accessibility / Inclusivity / Assisted Digital Digital Transformation Office <http://www.dto.gov.au/> 0438 156 883 (general office) e. andrew.arch@digital.gov.au | t. @AusDTO <https://twitter.com/AusDTO> @amja <https://twitter.com/amja> On 18 February 2016 at 01:30, Shawn Henry <shawn@w3.org> wrote: > Andrew Arch via WBS Mailer wrote: > ... > >> --------------------------------- >>> Accessibility Requirements for People with Low Vision - Before Draft >>> Publication >>> ---- >>> Is there anything that is important to address before FPWD publication? >>> >>> If you put comments in GitHub, please label them "before FPWD". >>> >>> * ( ) I reviewed or skimmed it and do not see any issues that need to >> be >> addressed before it is published as a draft. >> * (x) I reviewed it and put comments in GitHub that need to be addressed >> before it is published as a draft. >> > > Did you mean to check the next option? :-) > > * ( ) I reviewed it and put Comments below that need to be addressed >> before it is published as a draft. >> * ( ) I have not yet gotten to it, and will by the date below. >> * ( ) I will pass on commenting this time. >> >> Editors' discretion, but should be considered: >> 3.4.3 'rivers of 'white' issue should be split off and placed under 3.2 >> consider cross referencing 3.4.6 with 3.6.2 >> > > Thanks for reviewing the doc, Andrew! > > Rivers are primarily caused by full justification, afaik. It could be made > worse by increased space between words. Are there other causes? > > If a person has difficulty reading because of rivers, what could they do > about it - in an ideal situation? > * undo full justification > * change the word wrapping / line length -- e.g., resize the text area > width, or change the text size in a fixed width > * ? change from monospaced font to proportional font > * @@ anything else? > > The issue of rivers is primarily within paragraphs, afaik. 3.4.6 and 3.6.2 > are more about spacing around paragraphs (and other things) rather than > spacing within paragraphs. > > If you have any more info or references -- formal or informal -- to share > to help the LVTF further understand the issue, we welcome them! > > Best, > ~Shawn >
Received on Thursday, 18 February 2016 01:01:30 UTC