We should do more to increase the accessibility of both software developers and users of software.
[Wayback/Archive] Serge Lachapelle 🇺🇦🇸🇪 on Twitter: “Quote of the day from @Vintharas. Don’t think of it as accessibility in your product design. Think of it as inclusivity.
#a11y#i9y“which refers to both
a11y– (computer) accessibility andi9y– inclusive design.
An important aspect there is to support case insensitive environments for both software developers and software users.
This sounds strange, as it makes systems less strict, but with the diversity of people not doing so makes it less accessible and decreases inclusivity.
It all started with reading [Wayback/Archive] /Fay-lee-nuh/ on Twitter: “Totally agree with this, case sensitivity does not add a lot apart from errors. Also note that some languages (Arabic, for example) do not have uppercase letters! So the whole idea of “case sensitive” to some people is new (and thus can make learning to program a lot harder)”.
Parts of the responses there and in the tweet Felienne quoted, were from people still insisting on case sensitivity or even limiting identifiers and filenames to US 7-bit ASCII.
I totally disagree, so I wrote a long thread in response, starting with [Wayback/Archive] “@Felienne @guido_leenders Sentence 2 in your first tweet should be an eye opener to everyone….” archived at the ThreadReaderApp as [Wayback/Archive] Thread by @jpluimers on Thread Reader App:
The Wiert Corner - irregular stream of stuff 