W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2017

Re: Are All Capital Letters accessible?

From: Kevin White <kevin@dewoollery.co.uk>
Date: Wed, 10 May 2017 18:02:36 +0100
Message-Id: <73B74C54-E9EC-44CF-8392-420D645D9563@dewoollery.co.uk>
To: W3C WAI ig <w3c-wai-ig@w3.org>
I may have missed it, but the conversation seems to be missing the impact of all-caps on individuals with some form of reading impairment, such as dyslexia.

This is something that is commented on in a number of places:

• Dyslexia Action: http://www.dyslexiaaction.org.uk/page/text-formatting-best-practice
• British Dyslexia Association: http://www.bdadyslexia.org.uk/common/ckeditor/filemanager/userfiles/About_Us/policies/Dyslexia_Style_Guide.pdf
• BBC: http://www.bbc.co.uk/skillswise/tutors/inclusive-learning/tutors-article-dyslexia

Not sure on the evidence base for these - anyone?

Thanks

Kevin

> On 10 May 2017, at 14:04, Elizabeth Pyatt <ejp10@psu.edu> wrote:
> 
> FWIW - I don’t think anyone thinks all caps is a legibility barrier for headlines, but I haven’t seen any compelling evidence for using them in long text passages as long as the font rendering is smooth enough. For one thing, it saves space!
> 
> ALL CAPS VERSION - I DON’T THINK ANYONE THINKS ALL CAPS IS A LEGIBILITY BARRIER FOR HEADLINES, BUT I HAVEN’T SEEN ANY COMPELLING EVIDENCE FOR USING THEM IN LONG TEXT PASSAGES. FOR ONE THING, IT SAVES SPACE!
> 
> Elizabeth
> 
>> On May 10, 2017, at 8:39 AM, Harry Loots <harry.loots@ieee.org> wrote:
>> 
>> Gregg 
>> The blog article mentioned by Mohsen seem to throw in doubt what both of us (and others) have accepted as the truth. 
>> 
>> Perhaps it's time for a re-evaluation of our beliefs in this regard.
>> 
>> Personally I prefer and will continue to use mixed case for copy,  but have never felt uncomfortable to use upper case in headings or buttons,  and in all the user research I've engaged in over the years, testing designs with actual users,  I cannot recall a single occasion where a user objected to a heading or button being in uppercase. 
>> 
>> Kindest regards 
>> Harry 
>> 
>> 
>> On 8 May 2017 16:59, "Gregg C Vanderheiden" <greggvan@umd.edu> wrote:
>> I would look for quality research in a peer-reviewed journal for answers to this.   
>> 
>> But I do know that the outlines of words is one thing we use to decode them — and all caps do not have outlines.    But whether the larger letters of all caps offsets this — I would not guess.  I would look to research — and not just one paper.   You can find a paper proving just about anything - including the earth is flat.   
>> 
>> 
>> g 
>> 
>> Gregg C Vanderheiden
>> greggvan@umd.edu
>> 
>> 
>> 
>> 
>>> On May 8, 2017, at 9:46 AM, Mohsen Mahjoobnia <mm14kl@student.ocadu.ca> wrote:
>>> 
>>> Hello and good day,
>>> 
>>> I would appreciate a clarification on the topic of all capital (titles, headings, and text).
>>> 
>>> My understanding is that we should not use all caps!
>>> But a colleague of mine has suggested the article below from a blog (I don't know the author or the blog's credibility)  It’s a Myth That All Capital Letters Are Inherently Harder to Read 
>>> 
>>> < http://www.blog.theteamw.com/2009/12/23/100-things-you-should-know-about-people-19-its-a-myth-that-all-capital-letters-are-inherently-harder-to-read/ >  
>>> 
>>> PS. Personally as a x-graphic designer, i used to love using all caps, until I was introduced to digital accessibility few years back. And now (having glasses) I can see the difference and I can also relate.
>>> 
>>> Thank you,
>>> Cheers
>>> 
>>> M 
>>> ----- Digital Signature ----- 
>>> 
>>> Mohsen Mahjoobnia, Accessible Home Consultant
>>> MDes, Inclusive Design, OCAD University
>>> 
>>> RE/MAX Ultimate Realty Inc. Brokerage,
>>> 1739 Bayview Ave.| Toronto, ON M6J
>>> Cell: +1-647-460-7009
>>> ca.linkedin.com/in/moisenm/ 
>>> 
>>> Please consider the environment before printing this e-mail
>>> 
>>> The information contained in and transmitted with this e-mail is privileged and confidential; intended only for the recipient(s)  specified.  
>> 
Received on Wednesday, 10 May 2017 17:03:09 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 10 May 2017 17:03:11 UTC