664: Figma Sites, CSS Carousels, and Internship Prep
Episode
65 min
Read time
2 min
Topics
Leadership, Design & UX, Software Development
AI-Generated Summary
Key Takeaways
- ✓Figma Sites Accessibility: Figma launched Sites feature with significant accessibility problems including div-only markup and no semantic HTML. Despite Figma being a web company that should understand web standards, the product shipped with fundamental issues that make generated websites unusable for assistive technology users.
- ✓CSS Carousel Specification Flaws: The new CSS carousel specification shipped with accessibility problems including improperly implemented tab patterns where tabs don't reference their associated panels, and navigation dots labeled only as "content item" repeatedly. The specification appears accessible at surface level but fails deeper testing.
- ✓Logical Properties for Internationalization: Using CSS logical properties like margin-inline-start instead of margin-left enables automatic layout flipping for right-to-left languages including Hebrew, Arabic, and Urdu. This approach provides free internationalization support for millions of users without additional development work or translation services.
- ✓Internship Preparation Strategy: Before starting a front-end internship, install and hello-world the company's entire tech stack including Node, TypeScript, Git, and frameworks. Familiarize yourself with their product, run accessibility audits using Axe DevTools, and inventory your CSS and JavaScript strengths to communicate capabilities clearly.
- ✓Browser Feature Shipping Process: Major web platform features like CSS carousels and Figma Sites launch without adequate accessibility review despite being developed publicly for 18 months. The process lacks clear checkpoints where accessibility experts can provide paid audits before shipping, leading to features requiring potential un-shipping or major revisions.
What It Covers
Shop Talk Show episode 664 examines Figma Sites launch accessibility failures, CSS carousel specification problems, logical properties for RTL language support, and practical advice for front-end development internship preparation.
Key Questions Answered
- •Figma Sites Accessibility: Figma launched Sites feature with significant accessibility problems including div-only markup and no semantic HTML. Despite Figma being a web company that should understand web standards, the product shipped with fundamental issues that make generated websites unusable for assistive technology users.
- •CSS Carousel Specification Flaws: The new CSS carousel specification shipped with accessibility problems including improperly implemented tab patterns where tabs don't reference their associated panels, and navigation dots labeled only as "content item" repeatedly. The specification appears accessible at surface level but fails deeper testing.
- •Logical Properties for Internationalization: Using CSS logical properties like margin-inline-start instead of margin-left enables automatic layout flipping for right-to-left languages including Hebrew, Arabic, and Urdu. This approach provides free internationalization support for millions of users without additional development work or translation services.
- •Internship Preparation Strategy: Before starting a front-end internship, install and hello-world the company's entire tech stack including Node, TypeScript, Git, and frameworks. Familiarize yourself with their product, run accessibility audits using Axe DevTools, and inventory your CSS and JavaScript strengths to communicate capabilities clearly.
- •Browser Feature Shipping Process: Major web platform features like CSS carousels and Figma Sites launch without adequate accessibility review despite being developed publicly for 18 months. The process lacks clear checkpoints where accessibility experts can provide paid audits before shipping, leading to features requiring potential un-shipping or major revisions.
Notable Moment
The hosts question how Figma Sites shipped with only divs and spans despite Figma being a web company that builds websites professionally. They express disbelief that a billion-dollar company would launch a website generation tool without basic semantic HTML or accessibility considerations in 2025.
Episode Transcript
Hey there, Shopmaniacs. You're listening to another episode of the Shop Talk Show podcast all about front end web design development and probably a bunch of freaking AI. I'm Dave Rupert with me, Chris. Hey, Chris. How are you doing? Fantastic. How are you, Dave? It's hard to ignore the old AI. You know? It's in every Yeah. It is. Course. It's in every everything. You know? So Mhmm. It's just a constant. I don't have too much in my brain about it. I I noticed the, the Windsurf one. It wasn't it wasn't too long ago where I I tried out a bunch of them, including Windsurf. Windsurf is one of these Versus code forks from the company called Codeium that renamed themselves to WinServ as part of kinda creating that browser. And you know what? I thought it was pretty good. In some sense, it was one of my favorites because I thought the, you know, it's interesting to see, like, what an interesting design space to take Versus code, which obviously a lot of people like, and just have this little opportunity to just polish it up a little bit. Make a few little decisions. Not make it too too different because people don't want too different. It's already very popular. But, like, you know, round the corners a little bit, which is quite literally what they did in some cases and clean up a little of the UI. I liked it from that perspective. They make the AI more their AI solution more forward. Right? Like, it it's kind of buried or a plug in inside Versus code, like as code. Right? I was never quite clear which things they were unable to do as a plug in because there are some AI companies that are choosing to strongly remain a plug in. Like, we'll just be in Versus Code as a business choice. And I know this to be true that occasionally you know, like, Microsoft can you know, whatever. I know you don't speak for this. It has nothing to do with that. This is just saying they have the right to do whatever they want with Versus Code. You know? And if they, you know No. I mean, I think and, you know, this goes broadly. Any company can do whatever they want with any product. You know, I I heard this fireship goof where they're just like, if AI is so good, why can't AI code an AI editor? But anyway, that was funny. Instead of paying $3,000,000,000 or whatever it was, that was pretty funny dig. I think it's probably usually more about talent and stuff like that and who's going to maintain it. But anyway, there's that whole Chrome threatened to sell DOJ or whatever, you got to sell this. OpenAI is the big name in the acquisition space. I'm sure all Elon would make a play too. But what's interesting about that is you know, I think it's like …
Get the full transcript (11,544 words) + summary by email — free
One-time email with the complete transcript and AI summary of this episode. No account needed.
One email, no spam. We’ll also show you what SignalCast does.
You just read a 3-minute summary of a 62-minute episode.
Get Shop Talk Show summarized like this every Monday — plus up to 2 more podcasts, free.
Pick Your Podcasts — FreeKeep Reading
More from Shop Talk Show
731: Terminal UX, Running Multiple Services, Don’t Settle for an App
Sep 7 · 58 min
Pod Save America
1129: Why Democrats Must Oppose Trump's Iran War
Mar 3
More from Shop Talk Show
730: A/B Testing with Charts, Music Recommendations, & Web Permissions
Aug 31 · 60 min
WorkLife with Adam Grant
ReThinking: Ed Helms on growing through failure
Aug 5
Books, tools, and gear mentioned in this episode
SignalCast may earn commission on purchases via these links.
Tools
by Figma
“Figma launched Sites feature with significant accessibility problems including div-only markup and no semantic HTML.”
- Axe DevToolsRecommended
“run accessibility audits using Axe DevTools”
More from Shop Talk Show
We summarize every new episode. Want them in your inbox?
731: Terminal UX, Running Multiple Services, Don’t Settle for an App
730: A/B Testing with Charts, Music Recommendations, & Web Permissions
729: After Dark Edition! Microlighter, Tri-state Drama, and Editing Video Quickly
728: BIMI, Good Favicon Practice, and CSS @Layer Exploration
727: Front-End Complexity, AI Co-Authorship, and New CSS Navigation Patterns
Similar Episodes
Related episodes from other podcasts
Pod Save America
Mar 3
1129: Why Democrats Must Oppose Trump's Iran War
WorkLife with Adam Grant
Aug 5
ReThinking: Ed Helms on growing through failure
This Week in Startups
Sep 11
The Pentagon Wants Equity in AI Startups | E2336
Cognitive Revolution
Sep 5
AI:AM Highlights: Welcome to the AGI Era
Cognitive Revolution
Aug 22
AI in the AM — Weekly Highlights: Relaunch Week (Aug 17–20, 2026)
Explore Related Topics
This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.
Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.
You're clearly into Shop Talk Show.
Every Monday, we deliver AI summaries of the latest episodes from Shop Talk Show and 192+ other podcasts. Free for one show.
Start My Monday DigestNo credit card · Unsubscribe anytime