Made it to the juicy part of @prestonso’s #AEASF talk about languages. 🏃♀️☕️ More CSS properties to help meet our users where they are, no matter what language they’re using:
- dir
- writing-mode
- lang (even mixed with another languages)
- text-orientation
- text-combine-upright
Remember to use HTML first to set the default reading direction, don’t just use CSS to do whatever you want. Set the structure first. @prestonso#AEASF
Markup that I never knew about, to help give readers of logographic languages more context about a character they might not know about: <ruby> and <rb>
Also, the CSS prop “text-emphasis” can customize text styles you want to bold, but bold wouldn’t look great. @prestonso#AEASF
.@prestonso encourages us to think more logically in our web layouts, not physical. That gives us more flexibility when it comes to languages. Be agnostic to writing mode, not specific. Try stuff like “margin-block-start” instead of “margin-top”. #AEASF
There’s even markup to indicate how spoken language should be read on platforms like Siri. Not much for signed languages yet, but @prestonso is excited to see what comes up next. #AEASF
Takeaways from @prestonso’s #AEASF talk:
- Understand your users’ languages deeply and treat them all as first-class citizens
- Use lang attributes
- Pay attention to lines of text (breaks, wrap, hyphenations)
- Respect directions the text can go
And think bigger beyond the web!
It certainly takes a polyglot the level of @prestonso to create such a great rundown of design considerations around so many languages! (He can read 20-22, speak about 13.) Thanks for sharing that knowledge with #AEASF.
Heh, @prestonso didn’t get into translations, since the data level “gets very hairy very fast.” Whew, don’t we know at SF Digital Services! 😅 (We have a translation manager starting VERY SOON and we are SO EXCITED!!!)
Audience Q&A about making a site literally for everyone. @prestonso mentions NYC subway as an example: the website uses Google Translate to cover everyone. Only use it as a last resort, but human translations for everything is impossible (and NYC is not made of money!). #AEASF
(Can attest to the difficulty of human translations. Doing the COVID work, I saw print work being passed back and forth >5x with changes in English, that needed to be retranslated and relaid out in InDesign. 😩)
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Last at #AEASF (sadface) is @movie_pundit with his talk “What If People Weren’t the Product? Building a web that loves humanity.” (Yes, we gave each other high-fives about how we had talks about becoming person-oriented! 🙌)
Back in the truly olden days, we didn’t have mirrors. To see ourselves, we needed to find a still body of water. Instead, we looked at each other. @movie_pundit#AEASF
With the advent of mirrors, we suddenly became aware of how we looked to other people. The results ranged from 1st person novels to standing armies. Now the web, where “we cannot get away from ourselves” with ad personalization. We see ourselves as a product. @movie_pundit#AEASF
Next (and before #AEASF lunch LOL) is @kryshiggins about designing better onboarding. How do you balance understanding with “engagement” and features and prompts?
If we act on our fear (that our users will miss something!) then it can lead to unhelpful solutions! If you front-load instructions, they’re hard to remember, out of context, and have questionable value. @kryshiggins#AEASF
And framing is important. If you give people ALL the instructions up front, it can give the impression that a task must be super hard! Plus they’re costly to maintain. @kryshiggins#AEASF
Here for @Folletto’s #AEASF talk about hybrid meetings. Remote collaboration should not actually default to calls or meetings. Think about if they’re sync/async or in-person/virtual, but they can be combined too.
.@Folletto wants to leverage the benefits of each approach - it’s not about not meeting anyone ever. Async can make it possible for the less boisterous people to contribute too. Ask what the outcome of this call should be. #AEASF
Also ask if the call is in the right format. @Folletto made a chart for it! #AEASF
Very apropo for me right now - @youngfonz is going to talk about navigating changes in your [fill in the blank] career! #AEASF
Tip #1 for navigating career changes - have patience and resilience. @youngfonz had to go outside his comfort zone seeking resources to bolster his computer science education. But it was a journey! #AEASF
Tip #2 for navigating career changes: Have a strategy. Don’t just react, have a plan. And remember to learn EQ aka “soft skills” not just hitting the books (IQ). It depends on where you’re at! @youngfonz#AEASF
Learning all about ARIA attributes with @tolu_xyz at #AEASF! Some really interesting examples about how you’d indicate to assistive technologies about what’s visually happening on a component.
Hah I like how #AEASF attendees are all 👎 about carousels! #SameTeam
.@tolu_xyz recommends doubling up in code when using native HTML landmarks, since assistive tech reads them out inconsistently. So even if you’re using <nav> it’s a good idea to also use <div role=“navigation”> to make sure all your bases are covered! #AEASF
First up at #AEASF is @adactio about declarative design! (Yes, I'm back to my live-tweeting thing!)
He's starting off with music - there's Mozart writing every note down, then there's Miles Davis doing improv. All sorts of ways to compose music, and both are considered genius!
@adactio Same thing in programming too - imperative programming gives the computer step by steps. Then there's declarative programming (like SQL), where you tell the computer the result you want. @adactio#AEASF
.@timberners_lee created the World Wide Web with the "principle of least power" - use the most efficient way to parse information. Both HTML and CSS are declarative, fault-tolerant languages. They ignore what they don't understand. @adactio#AEASF