I built Update My Address Book (https://updatemyaddressbook.com) more than a decade ago to make it easier to collect addresses from family and friends so that we could send out Christmas cards. It's been the app that I've rewritten every few years when I want to test out a new tech stack.
After getting laid off a few weeks ago, I decided to give it a complete rewrite with some new features (offline support, lists, passkeys) and a new UI.
It's still very much a work in progress, but I'd really appreciate any feedback that could help make it useful for others as well.
If it's really accessible from *.google.com, wouldn't this be simple to verify/exploit by using Google Sites (they publish your site to sites.google.com/view/<sitename>)?
We made drag-and-drop interfaces accessible by allowing users to TAB through the original list, press ENTER on the item they want to move, then use the arrow keys to move the item and press ENTER again when done (or ESC to cancel). After each move, the item's current position, and any necessary local context, was announced via `aria-live` region.
There are other ways that this can be accomplished with even fewer keystrokes, so I can't imagine a scenario where drag-and-drop interfaces would have to be avoided because they couldn't be made meaningfully accessible.
It helps to reframe your thoughts on accessibility as a subset of user experience (UX). Putting aside any potential moral argument, how important is UX to your business/project?
When accessibility is thought about and incorporated ahead of time, your overall user experience tends to be better. This is sometimes referred to as Universal Design.
I managed a project where we implemented a UI redesign for our existing enterprise SaaS software and we "went the extra mile" to not just make the experience accessible but to make that experience pleasant for our users with disabilities. In the end, some of the features -- especially around keyboard navigation -- that came out of that accessibility work were considered the best part of the redesign to our users.
I've taken the approach of only reading the 3-star reviews.
In most cases, a 3-star review will provide a pretty thorough assessment of the pros and cons, and it's generally easier to determine the authenticity of the review.
It's worth noting that this is comparing the Apple Developer Transition Kit (with the A12Z SoC from the March 2020 iPad Pro) to the Surface Pro X (with the MS/Qualcomm SQ1 from October 2019).
It'll be interesting to see what Apple actually ships in production hardware.
I get your point that a highly-motivated attacker has other, less sophisticated, ways of getting to your data.
However, if we're playing poker and I learn your tell, it's in my best interest that you are naive to that fact. While not the best analogy, I would think that the same concept would apply to state actors.
An "unknown caller" is typically one that has no caller ID information provided (e.g., unlisted number). However, getting a random telemarketing call from a VoIP-provided
(or spoofed) local number would still come through since the caller ID information is provided, even though the number is not in your contacts list.
As silly as it may sound, three-finger drag is the primary reason why I will likely be purchasing a MacBook Pro instead of a Surface Book as my next laptop.
I get your point, and somewhat agree, but I think it's important to remember that the two (feature updates to Terminal and Notes vs. stability/performance/etc.) aren't typically mutually exclusive; the developer that would implement Markdown support in Notes isn't likely the same developer that would be implementing performance/stability enhancements to the core of the OS.
Took me a while to find it too, even though it's linked in the article. The product is called HR Basics and includes onboarding, employee directory/resource lists, and PTO management: https://gusto.com/free-hr
Basically, you lose auto-placement, named grid areas, and simple grid gaps, so you have to manually place items in the specific row/column for IE. But, I've found that it's still easier than the alternative in many cases.
The Android app also supports standard SMS with non-Signal users. Those messages are not encrypted, so they show the lock to indicate whether the message was sent via Signal or SMS.
After getting laid off a few weeks ago, I decided to give it a complete rewrite with some new features (offline support, lists, passkeys) and a new UI.
It's still very much a work in progress, but I'd really appreciate any feedback that could help make it useful for others as well.