[Webkit-unassigned] [Bug 22261] Clicking on a non-text input element does not give it focus

Mon May 24 16:24:21 PDT 2021

https://bugs.webkit.org/show_bug.cgi?id=22261

--- Comment #67 from John A. Bilicki III <jab_creations at yahoo.com> ---
> When people in leadership positions fail to comprehend that most
> fundamental aspect of usability those products and services fail.

>Could you be more specific?

Safari is not accessible; most designers and developers who don't own one to simply test Safari (I do, though I still don't have text labels on the GUI buttons or even a Reload button that I could at least have to go out of my way to enable for crying out loud so why would I willingly use it). They're wildly expensive considering not only the markup on the hardware though also the inability to customize the GUI or to be more precise without spending even more money. This removes incentives for many designers and developers to buy Apple products. So when those websites break those designers and developers do not care because if they do care about something it's about creating consistent behavior with the hardware and software that they do have access to. And that is for those trying to build websites don't just give up, abandon their customers and go in to something unrelated like selling insurance. That isn't how you create brand loyalty, that is how you create a cult, one that will one day be very easily convertible.

> How does that makes Safari an operating system?

No, Safari is a browser - the attitude of the gatekeepers here is to treat Safari like the operating system with it's limiting attitudes. In this situation the only proper thing to do is make the browser consistent in behavior, that is the point of cross-browser consistency. The attitudes could be constructively channeled in to creating an opt-in option to make Safari non-consistent with other browsers though consistent with the operating system.

Besides, most importantly - what is the benefit of not focusing a button? That is literal anti-accessibility.

The point of my bug report was to make my web platform extremely accessible to my users. The example was having 50 out of 100 email messages test messages that I just want to delete and obviously the check-all checkbox isn't a viable option in such a scenario. I wrote a script that when you press the up or down array key after clicking a checkbox would navigate to the next checkbox above or below and change it's checked state to that of the previous checkbox - absolutely genius as it's much faster, accurate and most importantly saves time! Most people don't want to have to battle their computer to do something simple in their minds, they have lives or are at least battling to get their lives on track. There are literally groups of people dedicated towards accessibility and usability literally telling whoever the gatekeepers are here for the past 13+ years at this point that the end user who actually uses products or services is more important than some snob's attitude who presumes that because they wouldn't use it that no one would. If you drive then you know that most other people are idiots. So yes, other people DO things that you wouldn't, though you might be the fool with five lanes though still blocking incoming traffic from on-ramps doing 15 slower than everyone else creating dangerous scenarios all in the name of driving "slow is safe". I've only had my success not by being wrong though by becoming aware of when I'm wrong. When someone wants to do something that I don't understand on my platform I resolve to know if it ultimately serves a use to someone that allows them to accomplish something even if I would never personally find any use for such a scenario. My goal is to make other people's lives better and the idea that I know all or that my personal preferences are somehow the end-all-be-all is not an attitude I tolerate, most especially in myself.

So the choice is simple: either do what people need and want or continue to enforce the ivory tower attitude.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20210524/65d351aa/attachment.htm>