Testing needed

1

We want to find usability evidence to answer 4 style points we did not identify sufficient usability evidence for in Beta. If no evidence exists, we'll carry out new usability studies.

2

3

If you know of any evidence for any of these please add a comment on this page, if possible link to the usability study.

4

5

6

== Positive contractions ==

7

8

We know negative contractions cause issues for some users. Do positive contractions also reduce readability for people with dyslexia, low vision and learning difficulties?

== Numbers ==

Does type font sufficiently reduce any confusion people experience between 1 (one), l (lowercase letter l) and I (uppercase letter i) and 0 (zero) and O (capital letter o)? Is it enough to recommend writing sentences another way to avoid this or do we need special style rules for 0 and 1 in long form copy? Should we recommend removing these from automatically generated passwords and customer codes?

14

15

16

== Punctuation and screen readers ==

We know users can:

* configure their screen reading software

21

* adapt to idiosyncrasies of software

22

* use software that learns user preferences

23

* comprehend spoken text at very high speeds

24

* slow down, pause and replay spoken text for clarity

25

26

27

But we would still like to know if having punctuation, for example "en dash", read out is problem, even a low level one, for any users. As we can alleviate that type of thing with sensible content readability guidelines. That is what they are for.

28

29

Can we gather a comprehensive list of how screen readers read out dashes? And find out what they do with hyphens? Can we comprehensively research screen readers with other punctuation that conveys meaning or adds nuance, like brackets?

== Our approach ==

First we're searching through existing usability evidence available from:

35

36

* [[Abilitynet – resources>>https://abilitynet.org.uk/free-resources]]

37

* [[WEBaim – articles>>http://www.webaim.org/articles]]