- From: Alastair Campbell <acampbell@nomensa.com>
- Date: Sun, 19 Apr 2020 18:20:12 +0000
- To: "Schnabel, Stefan" <stefan.schnabel@sap.com>
- CC: "w3c-wai-gl@w3.org" <w3c-wai-gl@w3.org>
Hi Stefan, > why are the whole prerequisites for the text spacing requirement also not part of https://www.w3.org/TR/WCAG21/#reflow? Mainly because it is a different requirement, you could pass reflow with fixed size boxes. Of course, when you approach from a good-practice point of view you can combine text-size, text-spacing and reflow together. For example, as part of a project I contributed this to the NHS service manual: https://service-manual.nhs.uk/accessibility/development#test-that-text-sizes-and-zooms-correctly That works when you are in the context of a particular pattern library and development approach. However, sites in general can and do fail one or the other, and the issues they cause for users could be based on one or the other. It would also make the SC text itself much more complex, and the already long understanding documents would be huge when combined. When we were working on 2.1 I wrote down my thoughts on levels of accessibility customisation: https://alastairc.ac/2017/02/four-levels-of-accessibility-customisation/ That might provide some help in thinking about the cut-off between "don't break it" and more active customisation. The TL;DR is that things which try to over-ride layout tend not to work, that's where you run into really big issues. Cheers, -Alastair
Received on Sunday, 19 April 2020 18:20:28 UTC