Uppercase; what's on screen should also be what's presented to the API

Hi,


I am trying to resolve best, modern practice, for general treatment of uppercase content, particularly phrases (not focussing on abbreviations); for example: "This is the BEST GOAT IN THE PADDOCK, and I can prove it with this video of her jumping."


When presented with uppercase content by clients, rather than coding said content in lowercase and using CSS to present it as uppercase, I should like to propose to my team that we leave the content untouched. Am I right to want to do this?


Leaving aside the issues around readability (which are important but not what I am trying to understand here), I am wondering if there is a W3C recommendation or other authoritative source I can quote when it comes to treatment of uppercase text.


Links such as these, perhaps particularly Léonie Watson's, make me think that my instinct to, generally, leave uppercase as uppercase, is correct.


https://accessibility.blog.gov.uk/2017/02/08/advice-for-creating-content-that-works-well-with-screen-readers/



https://www.drupal.org/project/drupal/issues/2958239#comment-12571641:~:text=The%20screen%20reader%20has%20no%20idea%20that%20it%20was%20lowercase%20in%20the%20HTML%20source



https://openlab.citytech.cuny.edu/blog/help/reading-ease-and-accessibility/#:~:text=Screen%20readers%20generally%20do%20not%20read%20text%20differently%20if%20it%20is%20in%20all%20upper%20case%20letters​


Any feedback appreciated.


Regards,

Alan
. . . . -   . . - - -
Alan Bristow ( he / him / il )
Web Developer / Développeur Web
Elections Canada / Élections Canada
alan.bristow@elections.ca<mailto:alan.bristow@elections.ca>

Received on Thursday, 29 June 2023 19:12:34 UTC