Changes for page Testing needed

Last modified by Lizzie Bruce on 2020/01/12 00:13
From version Icon 6.1 Icon
edited by Lizzie Bruce
on 2019/05/30 17:23
Change comment: Updated to reflect last chats
To version Icon 7.1
edited by Lizzie Bruce
on 2020/01/12 00:13
Change comment: on page redirect

Summary

Details

Icon Page properties
Content
... ... @@ -1,43 +1,1 @@
1 -We want to find usability evidence to answer 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?
9 -
10 -
11 -== Punctuation and screen readers ==
12 -
13 -We know users can:
14 -
15 -* configure their screen reading software
16 -* adapt to idiosyncrasies of software
17 -* use software that learns user preferences
18 -* comprehend spoken text at very high speeds
19 -* slow down, pause and replay spoken text for clarity
20 -
21 -
22 -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.
23 -
24 -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?
25 -
26 -
27 -== Numbers ==
28 -
29 -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 clear a typeface, or rewriting sentences to avoid letter and number confusion, 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?
30 -
31 -
32 -== Our approach ==
33 -
34 -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]]
38 -* [[Digital Accessibility Centre – resources>>http://www.digitalaccessibilitycentre.org/index.php/resources]]
39 -* [[RNIB linked site – accessible websites>>https://www.sightadvicefaq.org.uk/independent-living/technology/accessible-website]]
40 -* [[Scope – designing content for everyday equality>>https://www.scope.org.uk/news-and-stories/designing-content-to-achieve-everyday-equality]]
41 -
42 -
43 -Then, if applicable, we'll investigate carrying out new usability testing.
1 +Please go to [[readabilityguidelines.co.uk/testing-needed>>url:https://readabilityguidelines.co.uk/testing-needed/]].