The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,953 other followers

Archive for the ‘accessibility (a11y)’ Category

The Oxymoron of “Data-Driven Innovation” – Chelsea Troy

Posted by jpluimers on 2022/10/11

Must read: [Wayback/] The Oxymoron of “Data-Driven Innovation” – Chelsea Troy

My summary retweet:

[] Jeroen Wiert Pluimers on Twitter: “Building for marginalised groups not only broadens your user base, but actually makes your product better for majority groups as well and increases the value of your product and your profits.… “

Do go read it, as there are so many insights in it. Basically data-driven innovation will get you on the wrong side of the 80/20 rule. Better optimise for the 20% of the Pareto Principle.

This goes for any product development, be it software, hardware, services or otherwise.

Via: [] Kristian Köhntopp on Twitter: “The Oxymoron of Data Driven Innovation”


Posted in accessibility (a11y), Development, Software Development | Leave a Comment »

Inclusie/toegankelijkheid voor het @LUMC_Leiden: een tabel in HTML in plaats van plaatje zonder alt-text – #a11y

Posted by jpluimers on 2022/06/20

Voor inclusie en toegankelijkheid heb ik het plaatje van de tabel met voedingsmiddelen op [Wayback/Archive] Coloscopie | LUMC onderstaand in een HTML versie gegoten dankzij Google Lens die voor mij de tekst via OCR eruit gehaald heeft.

Dit vanwege een ingreep die binnenkort plaatsvindt waarbij een laxeerprotocol met Picoprep bij hoort.

De tabel als plaatje

De tabel is niet leesbaar voor mensen met een visuele beperking, en is afgedrukt bovendien zo klein dat zelfs voor mensen met een normaal zicht dit bijna niet leesbaar is.

Vanuit oogpunt van (verplichte, zie onder) toegankelijkheid en inclusie van mensen met een beperking is dit onwenselijk.

Read the rest of this entry »

Posted in accessibility (a11y), Awareness, Development, Health, Hospital, Inclusion / inclusive society, LifeHacker, LUMC, Power User, Web Development | Leave a Comment »

To make Twitter a better place for visually impaired: please do without those fancy Unicode letters in your account and messages – Global Accessibility Awareness Day 2022 – #a11y

Posted by jpluimers on 2022/05/19

Today is Global Accessibility Awareness Day, so it is a good day to write about a Twitter bot that tries to coerce people in having more accessible Twitter names and messages.

I knew I made a bookmark of [Wayback/Archive] Jacques Favreau on Twitter: “@Conundrum9999 @asciiArtHelpBot will make a little video of reading these things if anybody wants to try it out on a tweet.”

But when searching for it earlier this month, I could not find it (see below how in the end I did find it back).

The tweet was part of a thread that started with this tweet which very well describes why you should refrain from using fancy characters in Tweets or Twitter names:

[Wayback/Archive] Katie Mixtochtli – read my pinned – use alt text on Twitter: “Why you should avoid symbols and nonstandard letters in your twitter name if you want to be screen reader friendly: #DisabilityTwitter #disabilityinclusion Read on to see how “𝕁𝕒𝕞𝕖𝕤 – ʷʰᵉʳᵉ ⁱˢ ᵗʰᵉ ᵖʳᵒᵗᵉˢᵗ – ℂ𝕣𝕠𝕩𝕥𝕠𝕟 liked your reply” sounds to me 👇🏼”

The thread contains the long text you get when a screen reader reads that tweet. A video of that is below, and I saved the thread at [Wayback/Archive] Thread by @Conundrum9999 on Thread Reader App:

Read the rest of this entry »

Posted in accessibility (a11y), Awareness, Development, Inclusion / inclusive society, SocialMedia, Twitter, TwitterBot | Leave a Comment »

Increase sales: ensure your web-shop is accessible

Posted by jpluimers on 2021/09/01


  • Inaccessible web-shops cut themselves off from at least 5% customers.
  • Customers with accessibility issues are very loyal, so if your accommodate them, they will stay
  • Accessible web sites cut back on customer support questions (as high as a 15-30% decrease) saving on average EUR 10 per customer support request

Source: Maak webwinkels ook toegankelijk voor mensen met een beperking (behind a sign-in wall, sometimes this link or visiting via the below Twitter posts works)




Read the rest of this entry »

Posted in accessibility (a11y), Development, LifeHacker, Power User, Web Development | Leave a Comment »

Yet again, GitHub violates the Web Content Accessibility Guidelines by stealing a key: not it is the dot (.)

Posted by jpluimers on 2021/08/17

More sites seem to have a tendency of stealing keyboard shortcuts and violating the WCGA (Web Content Accessibility Guidelines), especially the (lowest!) conformance level A in [Wayback] WCAG version 2.1, section Success Criterion 2.1.4 Character Key Shortcuts

If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:

1. Turn off
mechanism is available to turn the shortcut off;
2. Remap
A mechanism is available to remap the shortcut to use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
3. Active only on focus
The keyboard shortcut for a user interface component is only active when that component has focus.

Mind you, I’m a keyboard person, there is even a: Keyboards and Keyboard Shortcuts category, but they always need to be configurable, anything else is a sin.

And GitHub did it again: [] GitHub on Twitter: “🤫 New shortcut: Press . on any GitHub repo.… “.

So I’m totally with these:

Now they have started to steal the dot (.) keyboard to (in-place, with a fully new URL and no indication how to easily go back) start Visual Studio Code in the current repository.

Going back, though not documented, actually takes between one and three “back” movements in your web-browser history: utterly ridiculous for a key one can accidentally hit.

This behaviour violates all three above sub-criterions:

  1. it cannot be turned off
  2. there is no way to remap it
  3. it is almost always activated (unless there a text input – like “search” or “goto file” – has focus)

This is a very bad way to cope with accessibility, especially as conformance level A is yet again violated.

[Wayback] WCAG 2.1: section 5.2.1 Conformance Level:

One of the following levels of conformance is met in full.

  • For Level A conformance (the minimum level of conformance), the Web page satisfies all the Level A Success Criteria, or a conforming alternate version is provided.
  • For Level AA conformance, the Web page satisfies all the Level A and Level AA Success Criteria, or a Level AA conforming alternate version is provided.
  • For Level AAA conformance, the Web page satisfies all the Level A, Level AA and Level AAA Success Criteria, or a Level AAA conforming alternate version is provided.

To me another cardinal sin is that they stole Ctrl-F / Command-F (depending if you use non-MacOS or MacOS) from the web browser. So now it does not find it in the full page, but only in the currently selected file. (You guessed it, I’m with [] KewlCat on Twitter: “I hate it when they intercept “/” and even [Ctrl]-F… “ too)

More of those conformance violation sins are at [Wayback] Keyboard shortcuts – GitHub Docs.

It isn’t hard to prevent this kind of thinking: it’s a mind set as described by [] Patrick Joannisse on Twitter: “I don’t know if you are expecting a real answer but here goes: it starts with the mindset. In my training they had us wear goggles to block our vision and made us use a screen reader for a while. We met people with disabilities and they would show us how they work.… “

If you still like it and want to know how it works


Read the rest of this entry »

Posted in accessibility (a11y), Development, GitHub, Keyboards and Keyboard Shortcuts, Power User, Software Development, Source Code Management | Leave a Comment »

%d bloggers like this: