Wow, it’s been at least five years since I last set foot on a plane. (I can’t remember what brought me to #btconf Dusseldorf in 2019, plane or train.)
Goodbye Vienna, in the upcoming two days I’ll be enjoying the crème de la crème of the CSS world. Looking forward to #CSSDay. 🤩
Live at #CSSDay 2024. 🙌
Hello fellow #CSSDay attendees.
Got my badge, I confused the organizers by getting married and changing my last name. It’s actually my third time here. 😅
In reply to: @CSSence@mas.to .
Sorry about that! 🙂
In reply to: @KrijnHoetmer@mastodon.social .
All good.
#CSSDay {
counter-reset: marriage;
}
Here’s hoping I’ll use that #CSSDay hashtag wisely. (But feel free to mute me until the end of the week.)
I’ll start with a question for @adactio@mastodon.social and @mia@front-end.social: How does MCing feel compared to giving a talk?
In reply to: @CSSence@mas.to .
No slides, no prep, but you’re on all day? Terrifying. I plan to just do whatever @adactio@mastodon.social does (but worse).
In reply to: @mia@front-end.social .
That’s the spirit. 🙃
Re: Fluid web typography
@matthiasott@mastodon.social Are there rounding issues in browsers, or in other words, how’s the legibility of the text (especially on non-retina displays) when calculating the font size?
The original sin(). 😶
I remember @tink@front-end.social talking about a Firefox flexbox “bug” that changed tab order at my first #CSSDay eight years ago. It’s really important that we get ways to manage tabbing and reading order.cssence.com/2016/cssday/#comment-25
Continued from previous comment.
Big yes to reading-order-items, #A11y FTW!
That said, I don’t wanna be a browser maker having to implement this. 😰
Ah yes, .visually-hidden, curious to see where we are heading on that front.cssence.com/2024/native-visually-hidden
I limit inline styles to #CSS custom properties.cssence.com/2020/css-variables-in-style-attributes
(Also makes things easier on #CSSNakedDay.)
@julia_miocene@mastodon.social Do you have to put a “No Divs Were Harmed in the Making of This Character” disclaimer next to your creations? 🤯
@pixelambacht@typo.social mentioned his goal for #CSSDay is to turn one or two people on to nice web typography.
🤞cssence.com/2018/no-webfont-no-cry
Continued from previous comment.
@pixelambacht@typo.social Mission (already) accomplished, many times over. 👏
@pixelambacht@typo.social Can you feature-detect (as in: does font support it) font-variant-position to avoid superscript being not superscript, i.e. only the “browser default override” succeeds? Taking into account that a fallback font from the font-family chain may kick in.
In reply to: @CSSence@mas.to .
I wish we had some @supports-like rules for that! @famulimas@front-end.social agrees, I think!
In reply to: @CSSence@mas.to .
Cool thing is, you can also enable these features in local/system fonts!
Thanks @fantasai@w3c.social and everyone in the Web Standards world for doing what you are doing. The people in this #CSSDay church and online would probably not have the career they’re having without you.
In reply to: @CSSence@mas.to .
yessss. Thank you @fantasai@w3c.social! This is my church. These are my people.
In reply to: @sarajw@front-end-social .
Amen. 😉sarajoy.dev/blog/my-church
In reply to: @CSSence@mas.to .
yeeep!!
Science confirms it: Websites really do all look the same.
Sometimes you need to decide against going the well-trodden path.cssence.com/2021/beyond-100vw
Continued from previous comment.
Here’s the link to the article @stephenhay@front-end.social showed in his talk:www.fastcompany.com/[…]-web-sites-really-do-all-look-the-same
Excellent conference so far, I learned a lot on day 1 of #CSSDay. Obviously, we are now associating CSS Grid with balloons; thanks @rachelandrew@front-end.social.
Maybe today it’ll be Flexbox and blimps. We’ll see.
In reply to: @CSSence@mas.to .
…or text-wrap: balance; and parachutes…?
#CSSDay people, if you are still on [insert current Musk platform name], we need you on the Fediverse.cssence.com/2024/fediverse-live
In reply to: @CSSence .
I concur, but it would appear that @CSSDayConf isn’t there yet…?
In reply to: @schweinepriestr .
Well, the people behind it are (Krijn, PPK, …), works for me.
Yay, @kevinpowell@front-end.social doing a smolcss.dev shoutout! I have to find @5t3ph@front-end.social today and see if she still has stickers.
In reply to: @CSSence@mas.to .
I sure do! I’m in turquoise today.
In reply to: @5t3ph@front-end.social .
👀 I wore Sushi yesterday, today I’m covered in cats. #WhatDidIJustType
If you are having #CSSDay #FOMO, don’t fret, @kevinpowell@front-end.social brought a lot of --frostiness to #CSS 🤐
I already saw tiny birds on @SaraSoueidan@front-end.social’s slides. 💜
I stumbled upon the possibility to add a <label> to a <button> by accident many years ago. Given what @SaraSoueidan@front-end.social just said about violating WCAG I need to revisit this:cssence.com/2019/inclusive-toggle-buttons
In reply to: @CSSence@mas.to .
I’m not there so I don’t know what @SaraSoueidan@front-end.social said but I can’t see how using <label> with <button> would be different than Heydon’s method of using aria-labelledby on the <button>. Both replace the button’s contents as its name with different, adjacent text (Chrome DevTools’s Accessibility pane shows the computed name property).
Is it a failure of currently available voice control software?
In reply to: @cwilcox808@c.im .
As said, I need to look into it, but she was talking about potential double labelling.
My guess would also have been that both methods are interchangeable.
In reply to: @CSSence@mas.to , @cwilcox808@c.im .
Yep definitely check the accName. I don’t know of a use case where it might be used but just noted that it may cause double announcements using virtual cursor but as long as accName is fine and doesn’t violate Label in Name then it may have practical uses. I’d love to see practical uses for it.
In reply to: @SaraSoueidan@front-end.social .
I think the toggle button example in this post is a pretty good use case. The button contents should be replaced by the label for the button’s name calculation.
If the layout of the <label> and <button> doesn’t make their relationship clear, that could create a WCAG 2.5.3 Label in Name problem.
For the toggle button, if the adjacent label isn’t recognized, a user will likely think “on” and “off” are separate controls.
In all cases I would’ve needed to change alt text for CSS generated content so far is to suppress it, i.e. / "". I hope this is cool once Firefox is on board.
OK, I can’t type that fast, @SaraSoueidan@front-end.social just put that on a slide.
See also: mastodon.social/@joshtumath/112574653630520293
I’m seeing (and participating in) the most head-nodding in this church so far. 👏 @SaraSoueidan@front-end.social
In reply to: @CSSence@mas.to .
so happy to hear this 🥹
@tabatkins@mastodon.social Can we use the anchor() function to position a little arrow/triangle inside the anchored content so it points to the anchor element?
Or anchor-size()?
Achievement unlocked: A photo with my Accessibility Heroine @SaraSoueidan@front-end.social 😊
Who happens to be the best kind of party pooper.
In reply to: @CSSence@mas.to .
aw 🥹🫶
@kizu@front-end.social with an important reminder for the entire #WebDev community to not wait until specs are set in stone, but instead get involved. Give feedback!
Warning, shameless plug incoming for a blog post I wrote recently.
CSS is awesome.cssence.com/2024/hyphenation
Thanks @joshwcomeau@front-end.social, that was inspirational. Now I too wanna go the extra mile and try to truly understand things.
CSS has given us so many great new things in such a short time that I cannot make up my mind what else I would want (and that includes masonry).
In reply to: @CSSence@mas.to .
I made my point now I’ve been exposed to either the grid or display based implementation: none of them. I observe the masonry layout as a fashionable statement which doesn’t fit in the css specs.
In reply to: @bnbrv@indieweb.social/ .
Well, I’m more with how @Anneke@front-end.social sees this:front-end.social/@Anneke/112576060404933060
So, Masonry does make sense, I just have an empty wish list, because there’s so much I wanna do with stuff that has already been “sheeped”. 🐑
👏👏👏
Journal: CSS Day 2024
A genuinely inspiring event.
🔗 adactio.com/journal/21198
In reply to: @adactio@mastodon.social .
It would be great to see some of those students speaking about their work.
I think it would be genuinely fascinating to get their perspective on what we consider modern CSS, which to them is just CSS.
100% this. When I filled out the feedback form earlier today, I suggested to have students again next year, by which I meant the same format as we had. But this is an even better idea.
