![]() ![]() In general, I wish PMs at SlackHQ were forced to use Slack app once a week without a mouse - where only keyboard is allowed. Can you imagine how hard it is for people who are? It is still quite difficult to use the app and you are still forced to use the mouse. I have played with F6-mode and tried navigating with it. Also would be nice to be able to start (jump to) a thread in F6-mode by pressing a key, maybe, or react with emoticon by pressing maybe? Having to press multiple times is not only annoying, it's inconsistent - when you are in a thread there are different actions compared to when you are not. When in F6-mode, would be nice if it was possible to navigate using h/j/k/l (Vim users would appreciate) Would it be possible to duplicate so it can be initiated without having to move one's hand? Also latest Macbooks don't even have F-keys. Now, we just need to figure out which company will have to show the world how to do it. But the vast majority of companies avoided the obvious win until Apple’s stock price shocked them into caring.Ī significant fraction of everyone’s user base (including the core users) would benefit from accessible and thoughtful design, because like the article says, we’re all disabled sometimes. We forget this, but back before the resurgence of Apple, design was an afterthought, not a forethought even though there were obvious gains to be had and a better future to lead towards. And that’s often the status quo until an Apple comes along. Not because of a lack of want, but because Discord has been coasting on accessible design for years.Įverything takes more resources than we expect, but surely a theme for their client (we do have some proof that it is theme-able) that is friendlier for screen readers shouldn’t take more time than an entire games store?įor me, the big takeaway from hearing about Slack’s issues and contrasting it with Discord is that people just don’t seem to care. My company uses Discord for comms and I’m active in several Discord communities, but my vision impaired co-worker isn’t. I would even go as far as to say that Discord’s design is aggressively thoughtless for the visually impaired. Not saying it can't happen, but so far it seems like Jamf has built a very solid updater tool.I would like to flog a (still live) horse and point out that Discord is even worse. In my limited playing around with Jamf App Catalog, the updates they provide have always worked and have never borked a program. I'm not using Jamf App Catalog just yet, because we're still in the process of migrating from on-prem to cloud, but we plan on using it full on once our transition has happened. If you know of some examples where it could create a problem or conflict, I'd love to hear about it. I can't think of any right now, but that doesn't mean there aren't any. ![]() That said, I'm certain there are some edge cases where the vendor provided update mechanism may be needed or desired over the Jamf one. In the end, the apps will get updated, just using a different Jamf controlled process over the vendor one. But with the introduction of Jamf App Catalog, for my purposes, I may be ok with just allowing Jamf App Installers to take over the updating of those apps. I mean, why not, if your org allows that sort of thing. In the past, I would have said, when possible, use an apps built in auto updating mechanism. That could create some issues, but I guess it really depends on how you want your apps to be updated on the endpoints. I have noted that in nearly all cases, the app installers Jamf builds do not include the vendor auto update mechanisms, or explicitly disables them in any case.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |