- From: Chaals McCathie Nevile <chaals@yandex-team.ru>
- Date: Fri, 29 Jan 2016 18:51:45 +0100
- To: public-webpayments-ig@w3.org
- Cc: intlcore <public-i18n-core@w3.org>
cc+ the internationalisation folks who also need to review things and have thought about this problem. I don't know of a formal guide, but here are some personal opinions: On Thu, 28 Jan 2016 19:16:36 +0100, Ian Jacobs <ij@w3.org> wrote: > * If APA has guidelines for spec design to facilitate accessibility > review, please let us know. Obviously, make the spec conform to WCAG, and try to solve problems that are not clearly addressed by WCAG. For example: - Zooming the spec significantly (say 5 times, not just the double formally required) should still result in something readily legible. - All images need a description that explains them, which may be part of the text itself or linked through e.g. longdesc - Make sure images are clear, and can be viewed under high contrast - no super-fine lines, black on grey, tiny text, and the like. Have a look at the tricks I used in http://svg-access-w3cg.github.io/use-case-examples/rectrack2-notes.html for some clues, but note that, like all SVG accessibility, is a work in progress. (If you do work from it as a basis I'd love to get your input on doing so). - Avoid walls of text. Break explanations into manageable chunks, minimise jargon, link to definitions of technical terms, and add illustrative diagrams. - Check the stylesheet for adequate contrast. Examples using green text on a green background or light text on a light background aren't helpful. - Don't assume people can deconstruct a written algorithm. Explain the effect, and ideally provide a diagram as well. cheers Chaals -- Charles McCathie Nevile - web standards - CTO Office, Yandex chaals@yandex-team.ru - - - Find more at http://yandex.com
Received on Friday, 29 January 2016 17:52:36 UTC