RubenSandwich
Joined 12 years ago
Joined 12 years ago
I wanted to clear up a few misconceptions on this point:
"""There is no easy way to jump long distances in the interface: TAB key navigation obligates you to go through all elements between your starting point and the target point;"""
1. TAB key navigation obligates you to go through all elements
Tab actually should behave as the key to enter and exit widgets. Yes some widgets are a single item, like buttons and links, but for more complex widgets you should be using the Arrow keys to navigate.
For example: Example: Tabs - https://www.w3.org/TR/wai-aria-practices/examples/tabs/tabs-... Example: Dropdown Menu - https://www.w3.org/TR/2019/NOTE-wai-aria-practices-1.1-20190...
(Tip: Shift + Tab to move focus backwards on a page.)
Also pay attention to what happened when you move focus to the second tab and then move away from the Widget and then come back to it. You refocus to the previously active element, not the first on. This is called a "Roving Tabindex" a very common pattern.
This solves the problem of:
A. Having to press TAB a lot to move through a page
B. Making it clear when you enter and exit a widget
These specs/keyboard design patterns have existed for a long time, but most folks only focus on the WCAG which only talks about keyboard focus so folks think everything needs to be "tabable".
2. Tab is the only way to navigate with the keyboard
Nope. Most folks who use screen readers actually navigate by headings and page landmarks. Unfortunately that navigation isn't on by default but there does exist some extensions that can turn those on for everyone:
Extension: https://chrome.google.com/webstore/detail/landmark-navigatio... Code: https://github.com/matatk/landmarks
Webflow engineer here. (On the accessibility team.) We are on a mission to dramatically make it easier to build for the web and are hiring across a bunch of roles: https://boards.greenhouse.io/webflow.
Feel free to reach out with questions about the roles. Contact me at (my first name) at webflow.com.
“I’ve always been a very science-focused person (I studied Mechanical Engineering & Materials Science), and used to be more opposed Eastern philosophies and traditions (which is a whole thing to unpack as an Asian kid growing up in a white community), but I started seeing the benefits to having a more readily available language to express empathy/emotions in the form of astrology.”
It very briefly describes why you shouldn’t be so dismissive of astrology. Even if it’s not a hard science, that doesn’t mean that it’s useless in other people’s lives. It helps them communicate real emotional needs and wants.
I love Swift, it's a great language, but we shouldn't rewrite our stacks every time a better language comes out. This is where the engineering trade-offs come in. Maybe over time, but over a long period of time.
I checked Google Cache and it's still paywalled.
Impossible to have an informed opinion without reading the article. As "saving from capitalism" can mean so many different things.
[0] https://www.thelancet.com/journals/lanpsy/article/PIIS2215-0...
[1] https://www.thelancet.com/journals/lanpsy/article/PIIS2215-0...
Sulfur Lamp: 100 lumens per watt. [0]
Random LED Light bulb: 88.888 lumens per watt. [1]
~20% improvement.
[0] https://web.archive.org/web/20030818061414/http://195.178.16...
[1] https://www.amazon.com/TCP-Equivalent-Light-Bulbs-Non-Dimmab...
There is a very active discord community around the sensor watch. Come join us; https://discord.gg/Rdd9ewREaJ. I'm currently working on adding step counting support to the sensor watch pro. (Also I'd appreciate the help in getting a low power and low computation cost step counter working, which is a bit hard when your battery budget is a CR2016.)