Podcasts about Web standards

In this repeat episode, Chris Coyier, co-founder of CodePen, talks about the evolving landscape of HTML heading into 2025. He delves into topics like the slow evolution of HTML compared to CSS and JavaScript, the importance of backwards compatibility, new HTML elements and pseudo-elements, and the potential of declarative shadow DOM for server-side rendering in web components. Links Website: https://chriscoyier.net Codepen: https://codepen.io/chriscoyier Frontend Social: https://front-end.social/@chriscoyier Github: https://github.com/chriscoyier Threads: https://www.threads.net/@chriscoyier Bluesky: https://bsky.app/profile/chriscoyier.net We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understanding where your users are struggling by trying it for free at LogRocket.com. Try LogRocket for free today. (https://logrocket.com/signup/?pdr) Special Guest: Chris Coyier.

AGNTCY - Unlock agents at scale with an open Internet of Agents. Visit https://agntcy.org/ and add your support.     What if AI agents needed digital passports to act on your behalf?   In this episode, Ankur Banerjee, Co-Founder and CTO of cheqd.io, reveals how decentralized identity is becoming the foundation of the AI agent economy.    From booking Taylor Swift tickets with an agent to proving you're a real person online, we explore why identity and trust are the hidden infrastructure shaping the future of AI.   Ankur explains how cheqd is building privacy-first tools that let AI agents verify who they are, what they can do, and who they're working for, all without handing over your data to big tech. We dig into the rise of digital credentials, the limits of biometrics, and how protocols like MCP are making the internet safe for autonomous agents.   If you've ever wondered how AI will operate on your behalf in the real world, this conversation offers a glimpse into what's coming next.   Stay Updated: Craig Smith on X: https://x.com/craigss Eye on A.I. on X: https://x.com/EyeOn_AI     (00:00) Why AI Needs Identity (02:16) Ankur's Path to cheqd (05:39) Delegating Tasks to AI Agents (11:26) Identity Lessons from Governments (17:25) Trusting AI with Digital Credentials (23:42) The Problem with Biometrics (30:49) Web Standards for Agent Identity (36:46) MCP and Agent Interoperability (48:47) Bridging Web2 and Web3 Identity (55:18) Why Companies Should Care About Decentralized ID

Peter Pistorius, co-creator of RedwoodJS, talks about the evolution from RedwoodJS GraphQL to the new Redwood SDK, a React framework built for Cloudflare. They dive deep into serverless architecture, React Server Components, durable objects, AI-assisted development, and the challenges of modern deployment and hosting. Learn how Redwood SDK is empowering developers to focus on building and shipping, instead of managing infrastructure. Links https://rw-sdk.com http://peterp.org https://github.com/peterp https://bsky.app/profile/p4p8.bsky.social https://x.com/appfactory https://cursor.sh https://neon.tech Resources https://rwsdk.com We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Em, at emily.kochanek@logrocket.com (mailto:emily.kochanek@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket's Galileo AI watches user sessions for you and surfaces the technical and usability issues holding back your web and mobile apps. Understand where your users are struggling by trying it for free at LogRocket.com (https://logrocket.com/signup/?pdr).

Carson Gross, creator of HTMX, talks about its evolution from intercooler.js, its viral rise on social media, and its philosophy of simplicity and stability. They dive into how HTMX fits into the modern web dev ecosystem, the idea of building 100-year web services, and why older technologies like jQuery and server-side rendering still have staying power. Carson also shares insights on open-source marketing, progressive enhancement, and the future of web development. Links https://bigsky.software https://www.linkedin.com/in/1cg https://github.com/bigskysoftware https://x.com/htmx_org https://htmx.org https://htmx.org/discord https://hypermedia.systems https://github.com/surrealdb/surrealdb.js https://unpoly.com https://ui.shadcn.com We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Carson Gross.

Ever wondered how web standards are made? Martin and Gary from Google Search take you behind the scenes of the internet's governing bodies. From the IETF to the W3C, learn about the consensus-driven processes that shape the web. Find out why these standards are crucial for ensuring a consistent and reliable online experience. Resources: Episode transcript →  https://goo.gle/sotr089-transcript    Listen to more Search Off the Record → https://goo.gle/sotr-yt Subscribe to Google Search Channel → https://goo.gle/SearchCentral   Search Off the Record is a podcast series that takes you behind the scenes of Google Search with the Search Relations team.   #SOTRpodcast #SEO   Speakers: Lizzi Sassman, John Mueller, Martin Splitt, Gary Illyes Products Mentioned: Search Console - General  

Hong Minhee, an open source developer and creator of the Fedify ActivityPub library, discusses the ActivityPub protocol and the fediverse with SE Radio's Jeremy Jung. They explore ActivityPub use cases, including microblogging applications such as Mastodon and Misskey, as well as activities built into the specification such as Like, Follow, and Accept. They also discuss extending the specification to include properties like Discoverable and Suspended, how different implementations communicate when they don't implement the same extensions, ND the use of JSON-LD and why it is challenging to implement. Finally, they consider the HTTP-based inbox communication model, difficulties with scaling when using a push rather than a pull model, account migration, and resources for implementing the ActivityPub specification. Brought to you by IEEE Computer Society and IEEE Software magazine.

Chris Coyier, co-founder of CodePen, talks about the evolving landscape of HTML heading into 2025. He delves into topics like the slow evolution of HTML compared to CSS and JavaScript, the importance of backwards compatibility, new HTML elements and pseudo-elements, and the potential of declarative shadow DOM for server-side rendering in web components. Links https://chriscoyier.net https://codepen.io/chriscoyier https://front-end.social/@chriscoyier https://github.com/chriscoyier https://www.threads.net/@chriscoyier https://bsky.app/profile/chriscoyier.net We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Chris Coyier.

Brooks Lybrand discusses the transformation of React Router from a simple routing library to a powerful framework option for React applications. Learn about React Router 7's new framework mode, upcoming middleware support, and the team's innovative approach to React Server Components. Brooks explains how the Remix team is working to bring proven patterns and web standards to the broader React community while building a foundation for future web development that leverages native web APIs.Chapter Marks0:00 - Intro0:37 - Guest Introduction & SNL Jacket Discussion1:12 - The Remix "Nap" Announcement3:25 - Understanding React Router's Evolution7:51 - React Router Framework Mode10:21 - Middleware Support Plans15:42 - React Server Components Integration19:14 - Server-Side Capabilities & RSC Benefits24:17 - Team Size and Structure25:13 - Remix Brand & Future Direction30:19 - Future of Web APIs32:03 - Austin Remix Meetup Discussion34:54 - Community Engagement and Open Source36:19 - Picks and Plugs LinksPeople & Profiles:Brooks Lybrand's social profilesTwitterBlueSkyMichael ChanJames PerkinsRyan FlorenceEvan Bacon (mentioned for RSC mobile demo)Tools & Projects:React Router 7Remix RunRemix DiscordVite 6Cursor AI (mentioned in Amy's pick)The dev.to article about Cursor settings that Amy referencedElgato XLR Deck (Brad's pick)OXO Silicon Measuring Cup (Amy's pick)Events & Communities:Epic Web Conf (March 2024, where Brooks will be speaking)React Miami (April 2024, where Brooks will be speaking)Remix Austin MeetupTechnical Resources:React Server Components documentationRemix Project RoadmapVite's Environment API documentationBooks:The Three-Body Problem book series (Brooks' pick)Additional Resources:Netflix's Three-Body Problem show (mentioned in relation to Brooks' pick)

In this episode of Environment Variables, host Chris Adams dives into the evolving landscape of sustainable web development with Alexander Dawson and Tzviya Siegman from the World Wide Web Consortium (W3C). Dawson and Siegman discuss the W3C's efforts to develop Web Sustainability Guidelines (WSG), a comprehensive set of evidence-based practices aimed at reducing the environmental impact of web technologies. They explore the creation and potential impact of these guidelines, especially as global interest grows in embedding sustainable practices within web standards. The episode also covers the challenges of driving adoption across public and private sectors, the role of testability in sustainability guidelines, and future directions for standards that minimize digital carbon footprints. This engaging conversation provides listeners with insights into how W3C's sustainability initiatives could shape the future of the web.

In a special guest episode, Rob Eisenberg joins the podcast to talk about the role web components play in today's web development ecosystem. Rob is uniquely qualified to discuss web components, as the former architect for Microsoft's web component tech stack, FAST, used by about 1,500 internal MSFT teams, and creator of the Web Component Engineering course. Special Guest(s):Rob Eisenberg, Founder and Chief Software Architect at Blue Spire, former architect for Microsoft's FAST Web Components technology, creator of the Web Component Engineering course, and Web Standards advocate. Rob on Twitter @EisenbergEffectRob's Web Component Engineering courseRob on LinkedInRob on GitHubRob on MediumWhat Makes Us Happy this Week:Paige - Da Vinci Eye appTJ - GitHub Copilot updatesRob - Buttermilk PancakesThanks as always to our sponsor, the Blue Collar Coder channel on YouTube. You can join us in our Discord channel, explore our website and reach us via email, or Tweet us on X @front_end_fire and BlueSky.Front-end Fire websiteBlue Collar Coder on YouTubeBlue Collar Coder on DiscordReach out via emailTweet at us on X @front_end_fireFollow us on Bluesky @front-end-fire.com

Anthony Alaribe, co-founder of API Toolkit, discusses the power of the browser for building data-heavy applications. He talks about myths around single-page apps versus multi-page apps, leveraging tools like HTMX and Workbox, and the significance of browser-native features for interactive web development. Links https://htmx.org https://tonyalaribe.medium.com https://x.com/tonialaribe https://github.com/tonyalaribe https://www.linkedin.com/in/anthony-alaribe-293a41bb We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Anthony Alaribe.

In this episode, Dan Applequist of Samsung explores the intersection of open source security and web development. Drawing from his extensive experience with the World Wide Web Consortium (W3C) and initiatives like Open Source Security Foundation (OpenSSF) and C2PA, Dan discusses the challenges and opportunities of uniting the open source security community with web developers. Emphasis is placed on the critical importance of mobile security, considering the sensitive information on mobile devices and industry best practices such as OWASP guidelines. The conversation also highlights the importance of security education, referencing resources like OpenSSF Security 101 and OWASP's global meetups. Additionally, media authenticity through protocols like C2PA and the role of organizations such as the BBC in this domain are discussed. The episode concludes with recommendations for developers to enhance their security practices through continuous learning and community engagement.   00:00 Introduction 00:25 Dan's Role at Samsung and Open Source Contributions 00:45 Web Standards and Privacy Initiatives 04:20 Bridging Web Development and Open Source Security 08:08 Challenges in Web and Mobile Security 09:26 The Importance of Mobile Security 11:40 Threat Models and Security Concerns 12:05 Protecting Yourself and Your Data 12:38 Web Security Best Practices 13:46 Challenges for Web Developers 15:28 Open SSF and W3C Collaboration 17:36 Expanding Security Education 19:44 The Importance of Media Authenticity 22:25 Final Thoughts and Future Discussions   Resources: W3C SWAG Group: https://www.w3.org/community/swag/ - and GitHub repo https://github.com/w3c-cg/swag with meeting minutes Last year's W3C / OpenSSF/ OWASP / OpenJS "Secure the Web Forward" workshop: https://www.w3.org/2023/03/secure-the-web-forward/ (includes videos of all talks and workshop report) W3C Ethical Web Principles https://www.w3.org/TR/ethical-web-principles/ W3C Privacy Principles https://www.w3.org/TR/privacy-principles/ W3C Security & Privacy self-check https://www.w3.org/TR/security-privacy-questionnaire/ Guest: Dan Appelquist is Open Source Strategist at Samsung Open Source Group. He is a web & mobile industry veteran and long-time participant and leader in open source and open standards. He has been co-chair of the W3C Technical Architecture Group for the last ten years. He was an early web pioneer and "dot-com CTO." He's led efforts at Vodafone, Telefónica, Samsung and the UK Government relating to open standards and the open web. You may find him on the Fediverse at @torgo@mastodon.social.  

Auferstanden nach Wochen der Stille präsentiert sich #WWSIV wieder mit Gast! Mit Stefan Judis sprechen wir über Web Standards, Inspiration und wo er die immer heißen News für seinen Newsletter her bekommt. Dazu gibts einen Font mit eingebautem Syntax-Highlighting und Heimautomatisierung. Tinkerbell hätte keine zauberhaftere Folge herbeiklamüsern können

Where web accessibility, digital sustainability, content management, open-source software, and web standards intersect, you'll find Mike Gifford. Mike is the open standards and practices lead at Civic Actions, a company that helps governments deliver better digital services.  Through his practice, Mike ensures that the content systems they deliver are built as sustainably as possible, deliver accessible experiences to citizens, and work well for authors and others who use the system. https://ellessmedia.com/csi/mike-gifford/

Lange war es still um PWAs, doch jetzt ist das Thema Progressive Web Apps gerade aktueller denn je: Zum einen hat der Bereich viel Aufmerksamkeit erfahren, als Apple im Frühjahr 2024 kurz davor war, das Feature unter iOS in Europa dauerhaft abzuschalten. Zum anderen erleben PWAs dank der neuen WebGPU-APIs und dem Hype um AI eine Art Renaissance.Aber was sind eigentlich Progressive Web Apps und was unterscheidet sie von „normalen“ Webseiten oder Bookmarks auf dem Homescreen? Und macht die Art der Anwendung für Endnutzer:innen wirklich einen Unterschied?All diesen Fragen und vielen weiteren gehen Dennis und Jan nach und sprechen dafür mit Nico Martin, Google Developer Expert fürs Web. Dabei geht's nicht nur um APIs, Browser-Implementierungen und Webstandards, sondern auch darum, was User:innen von Webseiten erwarten und welche UX für sie relevant ist.Schreibt uns!Schickt uns eure Themenwünsche und euer Feedback: podcast@programmier.barFolgt uns!Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. TwitterInstagramFacebookMeetupYouTube

In this episode, Amy, Brad, and Bekah welcome back Kent C. Dodds, who shares exciting updates about his latest project, Epic Web.dev. Kent discusses the philosophy behind his comprehensive web development course, the importance of understanding foundational technologies, and the motivation behind creating Epic Web Conf. He also dives into the benefits of building your own authentication systems and the decision-making process behind the Epic Stack. The conversation is filled with insights on balancing different technologies, creating cohesive learning experiences, and the future of web development education. SponsorsConvexConvex is the backend for founders. Convex is the backend application platform for product-obsessed founders Show Notes0:00 - Intro1:09 - Sponsor: Convex2:09 - Overview of EpicWeb.dev3:09 - Journey from PayPal to Epic Web8:14 - Teaching Approach and Workshop App10:47 - Building your own Authentication System16:59 - Decision-Making and Epic Stack21:35 - Launching Epic Web Conf27:26 - Consistency in Teaching and Conferences35:03 - Future Plans for EpicWeb.dev43:16 - Picks and PlugsKentPick: Brandon Sanderson's books - Particularly the Mistborn series and his involvement in the Wheel of Time series.Plug: Epic Web Conf - An exciting web development conference happening in Park City, Utah.BekahPick: Primal Buffalo Chicken StickPlug: @opensauced on Twitter/XBradPick: Ray-Ban Wayfarer SunglassesPlug: @bradgarropy on Twitter/XAmyPick: The Artists Way by Julia CameronPlug: Two Week Build 

Delve into a thought-provoking discussion with Owen Buckley, a seasoned web developer with 20 years of experience. Owen introduces Greenwood, a project focused on leveraging web standards and simplifying web development. Throughout the episode, They explore Greenwood's evolution, capabilities, and unique approach to application scaffolding and local development. From the emphasis on HTML and web components to Greenwood's seamless integration with HTMX, they uncover the project's vision to provide an onramp close to web standards. Join them as they navigate through the world of web development and gain valuable insights from Owen's expertise and passion for web standards and components.SponsorsChuck's Resume TemplateDeveloper Book ClubBecome a Top 1% Dev with a Top End Devs MembershipSocialsLinkedIn: Owen BuckleyPicksCharles - The White CastleOwen - Hypermedia SystemsBecome a supporter of this podcast: https://www.spreaker.com/podcast/javascript-jabber--6102064/support.

Es gibt einiges zu besprechen in dieser News-Ausgabe! Um über Apples alternative App-Marketplaces und deren Bedeutung für das Ökosystem zu sprechen, haben sich Sebi und Jan einmal Jens Abke, Mitgründer von Lotum, ins Podcast-Studio geholt.Zusammen diskutieren wir, für wen das neue App-Store-Preismodell sinnvoll sein kann, welche Chancen sich ergeben und auf welche Risiken man bei aller Euphorie achten sollte.Darüber hinaus wird es technisch, denn Sebi hat die aktuellsten News zur Browser-Interop-Initiative im Gepäck und erklärt uns, warum Web-Standards alleine oftmals nicht ausreichend sind, um gleichartiges Browserverhalten sicherzustellen.Und – man glaubt es kaum – es geht auch um jQuery. Das ist nämlich in Version 4 erschienen und hält sich wohl an das Motto „weniger ist mehr“.Zu guter Letzt hat Jan die Meldung über ein neues Leadership bei JetBrains dabei und macht deutlich, warum das eigentlich keine News sein sollte.Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback: podcast@programmier.barFolgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. TwitterInstagramFacebookMeetupYouTube

In this supper club episode of Syntax, Wes and Scott talk with Eric Meyer about his start on the web, the early days of CSS, where CSS is headed, are we going to lose a browser, and more! Show Notes 00:32 Welcome 01:26 Who is Eric Meyer? 05:44 In the earliest days, what browsers supported CSS? 10:23 The current web platform test suite web-platform-tests 17:59 Are CSS features shipping faster these days? 20:45 CSS learning from preprocessors 26:24 What do you think about Tailwind and inline CSS? 33:26 Alternative spaces where CSS may be used CSS Speech Module Level 1 The World Wide Web Consortium Issues CSS2 as a W3C Recommendation 37:17 Do companies push CSS forward for a business use case? 44:06 Trying to keep up with all the things is difficult 48:19 What's on Eric Meyer's CSS wishlist? 54:35 Supper Club Questions Bruce Lawson Firefox Nightly desktop, Android and iOS. SerenityOS The Ladybird browser project Thunderbird — Free Your Inbox. — Thunderbird Arc from The Browser Company Mozilla Foundation - Homepage 01:58 Sick Picks Sick Picks Polypane Shameless Plugs Igalia - Open Source Consultancy and Development meyerweb.com Hit us up on Socials! Syntax: X Instagram Tiktok LinkedIn Threads Wes: X Instagram Tiktok LinkedIn Threads Scott:X Instagram Tiktok LinkedIn Threads

As a well-known agency founder and design leader, Andy helps companies like Virgin Holidays, John Lewis and Penguin Random House with issues of customer experience, product strategy, and digital transformation. Andy's role at Clearleft was to set strategy and vision, promote the value of design, and help their clients realise their digital potential. Andy was very active in the company's day-to-day running, managing the leadership team, setting company culture, and looking after the happiness and well-being of 30+ staff. Andy is a designer at heart, having spent over 20 years in the field. He loves using his design, technology, and human behaviour knowledge to influence product strategy. As such, Andy is in his element when working alongside board members and their management teams. In his early career, Andy helped pioneer the field of Web Standards through his work, his blog (one of the highest trafficked in the UK at the time), and the publication of his best-selling book, CSS Mastery. Later, Andy helped popularise the field of UX design, setting up the UK's first dedicated UX agency, along with its first and arguably best UX conference. When he's not running the company or managing our creative output, Andy can be found sharing his wealth of knowledge at conferences around the world like SXSW, An Event Apart and The Next Web. He also curates the UX London and Leading Design conferences. In 2011, Andy co-founded the Brighton Digital Festival, a citywide celebration of digital culture attracting 40,000 visitors and over 190 events. He currently runs an online community of over 1,500 Heads, Directors and VPs of Design, and is a founding member of Adobe's Design Circle. These are just some of the reasons his company has won Netmag Agency of the Year several times, and he's appeared on both the Wired 100 and BIMA 100 lists. Never happier than when he's diving some remote tropical atoll, Andy is a qualified PADI dive instructor and retired shark wrangler. With a degree in Aeronautical engineering, Andy is currently learning to fly. In this episode, Andy discusses the essential qualities and skills a successful design leader should possess. He also shares his insights on building and managing a design team, fostering collaboration and creativity, advocating for an organisation's design, and the importance of empathy in design leadership. Andy also provides tips on how to navigate through various challenges while growing on the ladder as a designer leader and how to approach feedback and critique to help your team grow and improve their design skills. Finally, Andy shared his vision for the future of design leadership and the most important skills or qualities for design leaders in the coming years. Thank you for listening to this episode of Nodes of Design. We hope you enjoy the Nodes of Design Podcast on your favourite podcast platforms- Apple Podcast, Spotify, Google Podcasts, Amazon Music, and many more. If this episode helped you understand and learn something new, please share and join the knowledge-sharing community Spreadknowledge. This podcast aims to make design education accessible to all. Nodes of Design is a non-profit and self-sponsored initiative by Tejj.

TWiGS host Chris Adams is joined by special guests, Anne Faubry and Alexander Dawson of the W3C Community Group. This week, they discuss the Web Sustainability Guidelines as well as the Content Accessibility Guidelines. Web standards as specified by the World Wide Web consortium, play a huge role in shaping expectations about how the web is supposed to work, and for whom. This week's guests talk about their respective roles in the W3C and in publishing the guidelines, as well as how they came to be part of the group. Listen in to learn more about the differences between standards and guidelines, and what the Web Sustainability Guidelines aim to achieve.

In this episode of the Building the Open Metaverse podcast, Ken Russell and Corentin Wallez from the Google Chrome graphics team discuss using web browsers and technologies like WebGPU, WebGL, and WebAssembly to build an open and accessible metaverse.   They explain how new browser capabilities like WebGPU's compute shaders and multi-threading support can enable complex 3D experiences on par with console and mobile games. Russell and Wallez examine performance considerations like streaming assets and reducing security overhead. An open question is supporting multi-user experiences across origins while maintaining security.   The guests are optimistic that an open metaverse can be built using web principles like transparency and permissionless innovation. They see opportunities for blending languages like Rust, C++, JavaScript, and TypeScript. A key benefit of web tech is portability across devices. Russell and Wallez encourage industry collaboration on ethical guidelines and standards. ==== Have any comments or questions? Email the show Feedback@Buildingtheopenmetaverse.org   Want more information? Visit our website www.buildingtheopenmetaverse.org   And make sure you follow us on Linkedin for all of our show updates   https://www.linkedin.com/company/buildingtheopenmetaverse/ Building the Open Metaverse is a podcast hosted by Patrick Cozzi (Cesium) and Marc Petit (Epic Games) that invites a broad range of technical experts to share their insights on how the community is building the metaverse together. #BuildingTheOpenMetaversePodcast #MetaversePodcast #Metaverse

We're joined by Joyce Peralta to explore McGill's "Web Standards", the key to managing 1,500 sites & transforming their digital landscape. Learn how your organization can benefit too!

In dieser Folge unterhalten wir uns mit Andre Landgraf über das Full Stack Framework Remix. Andre ist Entwickler bei LinkedIn und hat auf der diesjährigen Remix Conf den Talk "Convince your boss to use Remix" gehalten.Diesem Titel ist er auch in dieser Folge gerecht geworden und hat Fabi und Sebi dazu animiert, das Framework auszuprobieren! Andre erklärt uns, was es heißt, dass Remix von vielen in der Community spaßig das "Boomer Framework" genannt wird. Remix setzt konsequent auf Web Standards, Formulare etc. und will auch ohne JavaScript im Client möglichst viel Funktionalität bieten.Wir tauchen mit Andre in die Details des Frameworks ein und klären, was die Philosophie hinter dem Framework ist, was catch & error boundaries sind, wie Remix einem so viel Arbeit abnimmt und wie Remix es schafft, dem "Spinnageddon" adieu zu sagen.Picks of the Day: Darknet Diaries – Darknet Diaries sind Geschichten aus dem Darknet als Podcast. Unbedingt reinhören! Mimestream – Ein Macos only mail Client der optimiert ist für Gmail Accounts. Sebi schwört drauf! Red Bull Mobile Data App – Günstige Internet Tarife im Ausland. Ganz einfach als eSim. Der perfekte Begleiter im Urlaub. Schreibt uns! Schickt uns eure Themenwünsche und euer Feedback: podcast@programmier.barFolgt uns! Bleibt auf dem Laufenden über zukünftige Folgen und virtuelle Meetups und beteiligt euch an Community-Diskussionen. TwitterInstagramFacebookMeetupYouTubeMusik: Hanimo

In this episode, we speak with Desigan Chinniah, previously at Mozilla, advisor to many web startups and now on the board of Tor. We discuss the evolution of web tech from websites to complex decentralized applications running on browser APIs, the competitiveness of the browser rendering engine versus the UX layer and how developers think about privacy. Does it live in browser settings, extensions or on the protocol core level?About Dees ChinniahDesigan Chinniah is a creative technologist. After two decades of dot-com checks in, Dees now has a portfolio of advisory roles (Ably, Coil, Replay, SEDNA, Zama) and board positions (Ushahidi, The Tor Project). He invests early into diverse and under-represented minority founders and is a mentor at Design Club, Mozilla and Seedcamp.Other things mentioned:MozillaFigmaVS CodeHTML5GeckoWebKitBraveFirefoxOperaEdgeHomomorphic encryptionReplayGlitchSourcegraphDesiganchinniah.comLet us know what you think on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmyttonhttps://twitter.com/cyberdeesOr by email: hello@console.devAbout ConsoleConsole is the place developers go to find the best tools. Our weekly newsletter picks out the most interesting tools and new releases. We keep track of everything - dev tools, devops, cloud, and APIs - so you don't have to. Sign up for free at: https://console.dev.

Sam and Ryan chat about how Suspense lets you remove defensive and confusing useEffect code from your React components. They also share some initial thoughts about how Remix is positioning itself in the frontend dev space.Topics include:0:00 - Intro4:53 - How compatible are non-Suspense APIs with Suspense, and how can we bridge these two worlds?33:35 - Impressions about Remix's positioning around web standardsLinks:Sam's video for this weekRemixThe Cursed Computer Iceberg MemeCoding MachinesFlappy Bird in Super Mario World

Starting with Cloudflare CTO, John Graham-Cumming on 6 Jan 2022, in season 2 of the Console DevTools Podcast we'll be speaking to 11 interesting people currently working in devtools about a specific technical topic. Upcoming guests:Dev infrastructure, with John Graham-Cumming (Cloudflare)Security, with Thomas Ptacek (Fly.io)Observability, with Charity Majors (Honeycomb)Decentralization, with Brooklyn Zelenka (Fission)Devtools investing, with Ed Sim (Boldstart)Homomorphic Encryption, with Rand Hindi (Zama)Dev communities, with Rosie Sherry (Orbit)Web standards & privacy, with Desigan (Dees) Chinniah (Tor / Ex-Mozilla)Designing dev products, with Ellen Chisa (Boldstart)Terminal tools, with Michelle Lim & Zach Lloyd (Warp)Developer experience, with Jean Yang (Akita)Join David for our first episode, on 6th January 2022. In the meantime, subscribe to the Console newsletter for weekly reviews of the best 2-3 devtools.Follow us on Twitter:https://twitter.com/consoledotdevhttps://twitter.com/davidmytton

In part two of the nGen story, Gene and Carl talk about the shift from Flash to Web Standards, the collaborative nature of a young industry, finding your people, and the birth of Happy Webbies. Get the weekly newsletter to read more. https://us4.campaign-archive.com/home/?id=790197d7f2&u=3c7b14630509cce52d23ffec0

Strings bereinigen mit Web-Standards! Was klingt wie ein Arbeitsauftrag der Wäscherei vom Puff nebenan, könnte bald Einzug in die Browserwelt halten: die HTML Sanitizer API! Sie tritt an um HTML Strings, die mit JavaScript gebaut werden, endlich sicher, und Libraries wie DOMPurify überflüssig zu machen. String rein, sicheres HTML raus. Wie, was, wo und warum erklärt uns Frederik Braun, Staff Security Engineer bei Mozilla und Mitverfasser des W3C Standard-Drafts. Dazu berichten wir noch vom Twitch Leak, und Constantin erklärt und die CSS-Eigenschaft "offset". Eine Runde Sache (die ins Eck musste, oder so).

01:09 - Todd's Superpower: Advocacy For Accessibility * Getting Started * Designing With Web Standards by Jeffrey Zeldman (https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0321616952) * The A11Y Project (https://www.a11yproject.com/) * W3C (https://www.w3.org/) 06:18 - Joining The W3C * The W3C Community Page (https://www.w3.org/community/) 07:44 - Getting People/Companies/Stakeholders to Care/Prioritize About Accessibility * Making A Strong Case For Accessibility by Todd Libby (https://www.smashingmagazine.com/2021/07/strong-case-for-accessibility/) * Diplomatic Advocacy * You Don't Want To Get Sued! / $$$ * “We are all temporarily abled.” 15:20 - The Domino's Pizza Story * Supreme Court hands victory to blind man who sued Domino's over site accessibility (https://www.cnbc.com/2019/10/07/dominos-supreme-court.html) 18:21 - Things That Typically Aren't Accessible And Should Be * The WebAIM Million Report (https://webaim.org/projects/million/) * WCAG (https://www.w3.org/WAI/standards-guidelines/wcag/) * Color Contrast * Missing Alt Text on Images * Form Input Labels * What's New in WCAG 2.1: Label in Name by Todd Libby (https://css-tricks.com/whats-new-in-wcag-2-1-label-in-name/) * Empty Links * Not Using Document Language * Triggering GIFS / Flashing Content * Empty Buttons – Use a Button Element!! * Tab Order * Semantic HTML, Heading Structure 26:27 - Accessibility for Mobile Devices * Target Size * Looking at WCAG 2.5.5 for Better Target Sizes (https://css-tricks.com/looking-at-wcag-2-5-5-for-better-target-sizes/) * Dragging Movements 28:08 - Color Contrast * Contrast Ratio (https://contrast-ratio.com/) 33:02 - Designing w/ Accessibility in Mind From the Very Beginning * Accessibility Advocates on Every Team * Accessibility Training 36:22 - Contrast (Cont'd) 38:11 - Automating Accessibility! * axe-core-gems (https://github.com/dequelabs/axe-core-gems) Reflections: Mae: Eyeballing for contrast. John: We are all only temporarily abled and getting the ball rolling on building accessibility in from the beginning of projects going forward and fixing older codebases. Mandy: Using alt-tags going forward on all social media posts. Todd: Accessibility work will never end. Accessibility is a right not a privilege. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Transcript: JOHN: Welcome to Greater Than Code, Episode 251. I'm John Sawers and I'm here with Mae Beale. MAE: Hi, there! And also, Mandy Moore. MANDY: Hi, everyone! I'm Mandy Moore and I'm here today with our guest, Todd Libby. Todd Libby is a professional web developer, designer, and accessibility advocate for 22 years under many different technologies starting with HTML/CSS, Perl, and PHP. Todd has been an avid learner of web technologies for over 40 years starting with many flavors of BASIC all the way to React/Vue. Currently an Accessibility Analyst at Knowbility, Todd is also a member of the W3C. When not coding, you'll usually find Todd tweeting about lobster rolls and accessibility. So before I ask you what your superpower is, I'm going to make a bet and my bet is that I'm 80% positive that your superpower has something to do with lobster rolls. Am I right? [laughter] Am I right? TODD: Well, 80% of the time, you'd be right. I just recently moved to Phoenix, Arizona. So I was actually going to say advocacy for accessibility, but yes, lobster rolls and the consumption of lobster rolls are a big part. MAE: I love it. That's fantastic. MANDY: Okay. Well, tell me about the advocacy. [chuckles] TODD: So it started with seeing family members who are disabled, friends who are disabled, or have family members themselves who are disabled, and the struggles they have with trying to access websites, or web apps on the web and the frustration, the look of like they're about ready to give up. That's when I knew that I would try to not only make my stuff that I made accessible, but to advocate for people in accessibility. MAE: Thank you so much for your work. It is critical. I have personally worked with a number of different populations and started at a camp for children with critical illnesses and currently work at an organization that offers financial services for people with disabilities – well, complex financial needs, which the three target populations that we work with are people with disabilities, people with dementia, and people in recovery. So really excited to talk with you today. Thanks. TODD: You're welcome. JOHN: When you started that journey, did you already have familiarity with accessibility, or was it all just like, “Oh, I get to learn all this stuff so I can start making it better”? TODD: So I fell into it because if you're like me and you started with making table-based layouts way back in the day, because what we had—Mosaic browser, Netscape Navigator, and Internet Explorer—we were making table-based layouts, which were completely inaccessible, but I didn't know that. As the web progressed, I progressed and then I bought a little orange book by Jeffrey Zeldman, Designing with Web Standards, and that pretty much started me on my journey—semantic HTML, progressive enhancement in web standards, and accessibility as well. I tend to stumble into a lot of stuff [laughs] so, and that's a habit of mine. [laughs] MAE: It sounds like it's a good habit and you're using it to help all the other people. So I hate to encourage you to keep stumbling, but by all means. [laughter] Love it. If you were to advise someone wanting to know more about accessibility, would you suggest they start with that same book too, or what would you suggest to someone stumbling around in the dark and not hitting anything yet? TODD: The book is a little outdated. I think the last edition of his book was, I want to say 2018, maybe even further back than that. I would suggest people go on websites like The A11Y project, the a11yproject.com. They have a comprehensive list of resources, links to learning there. Twitter is a good place to learn, to follow people in the accessibility space. The other thing that, if people really want to dive in, is to join The W3C. That's a great place and there's a lot of different groups. You have the CSS Working Group, you have the accessibility side of things, which I'm a part of, the Silver Community Group, which is we're working on the Web Content Accessibility Guidelines 3.0, which is still a little ways down the road, but a lot of great people and a lot of different companies. Some of those companies we've heard of—Google, Apple, companies like that all the way down to individuals. Individuals can join as individuals if your company isn't a member of the W3C. So those are the three things that I mainly point to people. If you don't really want to dive into the W3C side of things, there's a lot of resources on the a11yproject.com website that you can look up. MANDY: So what does being a member entail? What do you have to do? Do you have to pay dues? Do you have to do certain projects, maybe start as an individual level, because I'm sure we have mostly individuals listening to the show. Me as a newbie coder, what would I do to get started as a member of this initiative? TODD: Well, I started out as an individual myself, so I joined and I can get you the link to The W3C Community Page. Go to sign up as an individual and someone will approve the form process that you go through—it's nothing too big, it's nothing complicated—and then that will start you on your way. You can join a sub group, you can join a group, a working group, and it doesn't cost an individual. Companies do pay dues to the W3C and if your company is in the W3C, you get ahold of your company's liaison and there's a process they go through to add you to a certain group. Because with me, it was adding me to The Silver Community Group. But as an individual, you can join in, you can hop right into a meeting from there, and then that's basically it. That's how you start. JOHN: What are the challenges you see in getting not only the goals of a W3C, but I'm assuming specifically around accessibility? TODD: Some of the things that I've seen is buy-in from stakeholders is probably the number one hurdle, or barrier. Companies, stakeholders, and board members, they don't think of, or in some cases, they don't care about accessibility until a company is getting sued and that's a shame. That's one of the things that I wrote about; I have an article on Smashing Magazine. Making A Strong Case for Accessibility, it's called and that is one of few things that I've come across. Getting buy-in from stakeholders and getting buy-in from colleagues as well because you have people that they don't think about accessibility, they think about a number of different things. Mostly what I've come across is they don't think about accessibility because there's no budget, or they don't have the time, or the company doesn't have the time. It's not approved by the company. The other thing that is right up there is it's a process—accessibility—making things accessible and most people think that it's a big this huge mountain to climb. If you incorporate accessibility from the beginning of your project, it's so much easier. You don't have to go back and you don't have to climb that mountain because you've waited until the very end. “Oh, we have time now so we'll do the accessibility stuff,” that makes it more hard. MAE: John, your question actually was similar to something I was thinking about with how you developed this superpower and I was going to ask and still will now. [chuckles] How did you afford all the time in the different places where you were overtime to be able to get this focus? And so, how did you make the case along the way and what things did you learn in that persuasion class of life [chuckles] that was able to allow you to have that be where you could focus and spend more time on and have the places where you work prioritize successful? TODD: It was a lot of, I call it diplomatic advocacy. So for instance, the best example I have is I had been hired to make a website, a public facing website, and a SAAS application accessible. The stakeholder I was directly reporting to, we were sitting down in a meeting one day and I said, “Well, I want to make sure that accessibility is the number one priority on these projects,” and he shot back with, “Well, we don't have the disabled users,” and that nearly knocked me back to my chair. [laughs] So that was a surprise. MAE: There's some groaning inside and I had to [chuckles] do it out loud for a moment. Ooh. TODD: Yeah, I did my internal groaning at the meeting so that just was – [chuckles] Yeah, and I remember that day very vividly and I probably will for the rest of my life that I looked at him and I had to stop and think, and I said, “Well, you never know, there's always a chance that you're able, now you could be disabled at any time.” I also pointed out that his eyeglasses that he wore are an assistive technology. So there was some light shed on that and that propelled me even further into advocacy and the accessibility side of things. That meeting really opened my eyes to not everyone is going to get it, not everyone is going to be on board, not everyone is going to think about disabled users; they really aren't. So from there I used that example. I also use what I call the Domino's Pizza card lately because “Oh, you don't want to get sued.' That's my last resort as far as advocacy goes. Other than that, it's showing a videotape of people using their product that are disabled and they can't use it. That's a huge difference maker, when a stakeholder sees that somebody can't use their product. There's numbers out there now that disabled users in this country alone, the United States, make up 25% of the population, I believe. They have a disposable income of $8 trillion. The visually disabled population alone is, I believe it was $1.6 billion, I think. I would have to check that number again, but it's a big number. So the money side of things really gets through to a stakeholder faster than “Well, your eyeglasses are a assistive technology.” So once they hear the financial side of things, their ears perk up real quick and then they maybe get on board. I've never had other than one stakeholder just saying, “No, we're just going to skip that,” and then that company ended up getting sued. So that says a lot, to me anyways. But that's how I really get into it. And then there was a time where I was working for another company. I was doing consulting for them and I was doing frontend mostly. So it was accessibility, but also at the same time, it was more the code side of things. That was in 2018. 2019, I went to a conference in Burlington, Vermont. I saw a friend of mine speaking and he was very passionate about it and that talk, and there was a couple others there as well, it lit that fire under me again, and I jumped right back in and ever since then, it's just then accessibility. MAE: You reminded me one of the arguments, or what did you say? Diplomatic advocacy statements that I have used is that we are all temporarily abled. [chuckles] Like, that's just how it is and seeing things that way we can really shift how you orient to the idea of as other and reduce the othering. But I was also wondering how long it would be before Pizza Hut came up in our combo. [laughter] MANDY: Yeah, I haven't heard of that. Can you tell us what that is? TODD: [chuckles] So it was Domino's and they had a blind user that tried to use their app. He couldn't use their app; their app wasn't accessible. He tried to use the website; the website wasn't accessible. I have a link that I can send over to the whole story because I'm probably getting bits and pieces wrong. But from what I can recall, basically, this user sued Domino's and instead of Domino's spending, I believe it was $36,000 to fix their website and their app, they decided to drag it out for a number of years through court and of course, spent more money than just $36,000. In the end, they lost. I think they tried to appeal to the Supreme Court because they've gone up as high as federal court, but regardless, they lost. They had to – and I don't know if they still have an inaccessible site, or not, or the app for that matter because I don't go to Domino's. But that's basically the story that they had; a user who tried to access the app and the website, couldn't use it, and they got taken to court. Now Domino's claimed, in the court case, that he could have used the telephone, but he had tried to use the telephone twice and was on hold for 45 minutes. So [laughs] that says a lot. JOHN: Looks like it actually did go to the Supreme Court. TODD: Yeah. Correct me if I'm wrong, I think they did not want to hear it. They just said, “No, we're not going to hear the case.” Yeah, and just think about all these apps we use and all the people that can't access those apps, or the websites. I went to some company websites because I was doing some research, big companies, and a lot of them are inaccessible. A little number that I can throw out there: every year, there's been a little over 2,500 lawsuits in the US. This year, if the rate keeps on going that it has, we're on course for over 4,000 lawsuits in the US alone for inaccessible websites. You've had companies like Target, Bank of America, Winn-Dixie, those kinds of companies have been sued by people because of inaccessible sites. MAE: Okay, but may I say this one thing, which is, I just want to extend my apologies to Pizza Hut. [laughter] MANDY: What kinds of things do you see as not being accessible that should be or easily could be that companies just simply aren't doing? TODD: The big one, still and if you go to webaim.org/projects/million, it's The WebAIM Million report. It's an annual accessibility analysis of the top 1 million home pages on the internet. The number one thing again, this year is color contracts. There are guidelines in place. WCAG, which is the Web Content Accessibility Guidelines, that text should be a 4.5:1 ratio that reaches the minimum contrast for texts. It's a lot of texts out there that doesn't even reach that. So it's color contrast. You'll find a lot of, if you look at—I'm looking at the chart right now—missing alt texts on images. If you have an image that is informative, or you have an image that is conveying something to a user, it has to have alternative text describing what's in the picture. You don't have to go into a long story about what's in the picture and describe it thoroughly; you can just give a quick overview as to what the picture is trying to convey, what is in the picture. And then another one being another failure type a is form input labels; labels that are not labeled correctly. I wrote a article about that [chuckles] on CSS-Tricks and that is, there's programmatic and there's accessible names for form labels that not only help the accessibility side of it, as far as making the site accessible, but also it helps screen reader users read forms and navigate through forms, keyboard users also. Then you have empty links and then a big one that I've seen lately is if you look up in the source code, you see the HTML tag, and the language attribute, a lot of sites now, because they use trademarks, they don't have a document language. I ran across a lot of sites that don't use a document language. They're using a framework. I won't name names because I'm not out to shame, but having that attribute helps screen reader users and I think that's a big thing. A lot of accessibility, people don't understand. People use screen readers, or other assistive technologies, for instance, Dragon NaturallySpeaking voice input. But at the same time, I've got to also add accessibility is more than just deaf, or blind. I suffer from migraines, migraine headaches so animation, or motion from say, parallax scrolling can trigger a migraine. Animations that are too fast, that also trigger migraine headache. You have flashing content that can potentially cause seizures and that's actually happened before where an animated GIF was intentionally sent to someone and it caused a seizure and almost killed the person. So there's those and then the last thing on this list that I'm looking at right now, and these are common failures, empty buttons. You have buttons that don't have labels. Buttons that have Click here. Buttons need to be descriptive. So you want to have – on my site to send me something on the contact form, it's Send this info to Todd, Click here, or something similar like that. MAE: Can you think of any, John that you know of, too? I've got a couple of mind. How about you, Mandy? MANDY: For me, because I'm just starting out, I don't know a whole lot about accessibility. That's why I'm here; I'm trying to learn. But I am really conscious and careful of some of the GIFs that I use, because I do know that some of the motion ones, especially really fast-moving ones, can cause problems, migraines, seizures for people. So when posting those, I'm really, really mindful about it. JOHN: Yeah, the Click here one is always bothers me too, because not only is it bad accessibility, it's bad UX. Like HTML loves you to turn anything into a link so you can make all the words inside the button and it's just fine. [laughs] There's so many other ways to do it that are just – even discounting the accessibility impact, which I don't want it. TODD: Yeah, and touching upon that, I'm glad you brought up the button because I was just going to let that go [chuckles] past me. I have to say and I think it was in the email where it said, “What's bothering you?” What bothers me is people that don't use the button. If you are using a div, or an anchor tag, or a span, stop it. [laughs] Just stop it. There's a button element for that. I read somewhere that anchor tag takes you somewhere, a div is a container, but button is for a button. MAE: I love that. The only other ones I could think of is related to something you said, making sure to have tab order set up properly to allow people to navigate. Again, I liked your point about you don't have to be fully blind to benefit from these things and having keyboard accessibility can benefit a lot of people for all kinds of reasons. The other one is, and I would love to hear everybody's thoughts on this one, I have heard that we're supposed to be using h1, h2, h3 and having proper setup of our HTML and most of us fail just in that basic part. That's another way of supporting people to be able to navigate around and figure out what's about to be on this page and how much should I dig into it? So more on non-visual navigation stuff. TODD: Yeah, heading structure is hugely important for keyboard users and screen reader users as well as tab order and that's where semantic HTML comes into play. If you're running semantic HTML, HTML by default, save for a few caveats, is accessible right out of the box. If your site and somebody can navigate through using let's say, the keyboard turns and they can navigate in a way that is structurally logical, for instance and it has a flow to it that makes sense, then they're going to be able to not only navigate that site, but if you're selling something on that site, you're going to have somebody buying something probably. So that's again, where tab order and heading structure comes into play and it's very important. JOHN: I would assume, and correct me if I'm wrong, or if you know this, that the same sort of accessibility enhancements are available in native mobile applications that aren't using each HTML, is that correct? TODD: Having not delved into the mobile side of things with apps myself, that I really can't answer. I can say, though, that the WCAG guidelines, that does pertain to mobile as well as desktop. There's no certain set of rules. 2.2 is where there are some new features that from mobile, for instance, target size and again, I wrote another article on CSS-Tricks about target size as well. So it's if you ever noticed those little ads that you just want to click off and get off your phone and they have those little tiny Xs and you're sitting there tapping all day? Those are the things target size and dragging movements as well. I did an audit for an app and there was a lot of buttons that were not named. A lot of the accessibility issues I ran into were the same as I would run into doing an audit on a website. I don't know anything about Swift, or Flutter, or anything like that, they pretty much fall into the same category with [inaudible] as far as accessible. JOHN: I also wanted to circle back on the first item that you listed as far as the WebAIM million thing was color contrast, which is one of those ones where a designer comes up with something that looks super cool and sleek, but it's dark gray on a light gray background. It looks great when you've got perfect eyesight, but anybody else, they're just like, “Oh my God, what's that?” That's also one of the things that's probably easiest to change site-wide; it's like you go in and you tweak the CSS and you're done in a half hour and you've got the whole site updated. So it's a great bit of low-hanging fruit that you can attach if you want to start on this process. TODD: Yeah. Color contrast is of course, as the report says, this is the number one thing and let me look back here. It's slowly, the numbers are dropping, but 85.3%, that's still a very high number of failures and there's larger text. If you're using anything over 18 pixels, or the equivalent of 18—it's either 18 points, or 18 pixels—is a 3:1 ratio. With that color contrast is how our brains perceive color. It's not the actual contrast of that color and there are people far more qualified than me going to that, or that can go into that. So what I'll say is I've seen a lot of teams and companies, “Yeah, we'll do a little over 4.5:1 and we'll call it a day.” But I always say, if you can do 7:1, or even 10:1 on your ratios and you can find a way to make your brand, or whatever the same, then go for it. A lot of the time you hear, “Well, we don't want to change the colors of our brand.” Well, your colors of your brand aren't accessible to somebody who that has, for instance, Tritanopia, which is, I think it's blues and greens are very hard to see, or they don't see it at all. Color deficiencies are a thing that design teams aren't going to check for. They're just not. Like you said, all these colors look awesome so let's just, we're going to go with that on our UI. That's one thing that I actually ran into on that SAAS product that I spoke about earlier was there was these colors and these colors were a dark blue, very muted dark blue with orange text. You would think the contrast would be oh yeah, they would be all right, but it was horrible. JOHN: You can get browser plugins, that'll show you what the page looks like. So you can check these things yourself. Like you can go in and say, “Oh, you're right. That's completely illegible.” TODD: Yeah. Firefox, like I have right here on my work machine. I have right here Firefox and it does this. There's a simulator for a visual color deficiencies. It also checks for contrast as well. Chrome has one, which it actually has a very cool eyedropper to check for color contrast. If you use the inspector also in Firefox, that brings up a little contrast thing. The WAVE extension has a contrast tool. There's also a lot of different apps. If you have a Mac, like I do, I have too many color contrast because I love checking out these color contrast apps. So I have about five different color contrast apps on my Mac, but there's also websites, too that you can use at the same time. Just do a search for polar contrast. Contrast Ratio, contrast-ratio.com, is from Lea Verou. I use that one a lot. A lot of people use that one. There's so many of them out there choose from, but they are very handy tool at designer's disposal and at developers' disposal as well. JOHN: So I'm trying to think of, like I was saying earlier, the color contrast one is one of those things that's probably very straightforward; you can upgrade your whole site in a short amount of time. Color contrast is a little trickier because it gets into branding and marketing's going to want to care about it and all that kind of stuff. So you might have a bit more battle around that, but it could probably be done and you might be able to fix, at least the worst parts of the page that have problems around that. So I'm just trying to think of the ways that you could get the ball rolling on this kind of a work. Like if you can get those early easy wins, it's going to get more people on board with the process and not saying like, “Oh, it's going to take us eight months and we have to go through every single page and change it every forum.” That sounds really daunting when you think about it and so, trying to imagine what those easy early wins are that can get people down that road. TODD: Yeah. Starting from the very outset of the project is probably the key one: incorporating accessibility from the start of the project. Like I said earlier, it's a lot easier when you do it from the start rather than waiting till the very end, or even after the product has been launched and you go back and go, “Oh, well, now we need to fix it.” You're not only putting stress on your teams, but it's eating up time and money because you're now paying everybody to go back and look at all these accessibility issues there. Having one person as a dedicated accessibility advocate on each team helps immensely. So you have one person on the development team, one person on the dev side, one person on the marketing team, starting from the top. If somebody goes there to a stakeholder and says, “Listen, we need to start incorporating accessibility from the very start, here's why,” Nine times out of ten, I can guarantee you, you're probably going to get that stakeholder onboard. That tenth time, you'll have to go as far as maybe I did and say, “Well, Domino's Pizza, or Bank of America, or Target.” Again, their ears are going to perk up and they're going to go, “Oh, well, I don't really, we don't want to get sued.” So that, and going back to having one person on each team: training. There are so many resources out there for accessibility training. There are companies out there that train, there are companies that you can bring in to the organization that will train, that'll help train. That's so easier than what are we going to do? A lot of people just sitting there in a room and go, “How are you going to do this?” Having that person in each department getting together with everybody else, that's that advocate for each department, meeting up and saying, “Okay, we're going to coordinate. You're going to put out a fantastic product that's going to be accessible and also, at the same time, the financial aspect is going to make the company money. But most of all, it's going to include a lot of people that are normally not included if you're putting out an accessible product.” Because if you go to a certain website, I can guarantee you it's going to be inaccessible—just about 99% of the web isn't accessible—and it's going to be exclusive as it's going to – somebody is going to get shut out of the site, or app. So this falls on the applications as well. Another thing too, I just wanted to throw in here for color contrast. There are different – you have color contrast text, but you also have non-text contrast, you have texts in images, that kind of contrast as well and it does get a little confusing. Let's face it, the guidelines right now, it's a very technically written – it's like a technical manual. A lot of people come up to me and said, “I can't read this. I can't make sense of this. Can you translate this?” So hopefully, and this is part of the work that I'm doing with a lot of other people in the W3C is where making the language of 3.0 in plain language, basically. It's going to be a lot easier to understand these guidelines instead of all that technical jargon. I look at something right now and I'm scratching my head when I'm doing an audit going, “Okay, what do they mean by this?” All these people come together and we agree on what to write. What is the language that's going to go into this? So when they got together 2.0, which was years and years ago, they said, “Okay, this is going to be how we're going to write this and we're going to publish this,” and then we had a lot of people just like me scratching their heads of not understanding it. So hopefully, and I'm pretty sure, 99.9% sure that it's going to be a lot easier for people to understand. MAE: That sounds awesome. And if you end up needing a bunch of play testers, I bet a lot of our listeners would be totally willing to put in some time. I know I would. Just want to put in one last plug for anybody out there who really loves automating things and is trying to avoid relying on any single developer, or designer, or QA person to remember to check for accessibility is to build it into your CI/CD pipeline. There are a lot of different options. Another approach to couple with that, or do independently is to use the axe core gems, and that link will be in the show notes, where it'll allow you to be able to sprinkle in your tests, accessibility checks on different pieces. So if we've decided we're going to handle color contrast, cool, then it'll check that. But if we're not ready to deal with another point of accessibility, then we can skip it. So it's very similar to Robocop. Anyway, just wanted to offer in some other tips and tricks of the trade to be able to get going on accessibility and then once you get that train rolling, it can do a little better, but it is hard to start from scratch. JOHN: That's a great tip, Mae. Thank you. TODD: Yeah, definitely. MANDY: Okay. Well, with that, I think it's about time we head into reflections; the point of the show, where we talk about something that we thought stood out, that we want to think about more, or a place that we can call for a call of action to our listeners, or even to ourselves. Who wants to go first? MAE: I can go first. I learned something awesome from you, Todd, which I have not thought of before, which is if I am eyeballing for “contrast,” especially color contrast, that's not necessarily what that means. I really appreciate learning that and we'll definitely be applying that in my daily life. [chuckles] So thanks for teaching me a whole bunch of things, including that. TODD: You're welcome. JOHN: I think for me, it's just the continuing reminder to – I do like the thinking that, I think Mae have brought up and also Todd was talking about earlier at the beginning about how we're all of us temporarily not disabled and that I think it helps bring some of that empathy a little closer to us. So it makes it a little more accessible to us to realize that it's going to happen to us at some point, at some level, and to help then bring that empathy to the other people who are currently in that state and really that's, I think is a useful way of thinking about it. Also, the idea that I've been thinking through as we've been talking about this is how do we get the ball rolling on this? We have an existing application that's 10 years old that's going to take a lot to get it there, but how do we get the process started so we feel like we're making progress there rather than just saying, “Oh, we did HTML form 27 out of 163. All right, back at it tomorrow.” It's hard to think about, so feeling like there's progress is a good thing. TODD: Yeah, definitely and as we get older, our eyes, they're one of the first things to go. So I'm going to need assistive technology at some point so, yeah. And then what you touched upon, John. It may be daunting having to go back and do the whole, “Okay, what are we going to do for accessibility now that this project, it's 10 years old, 15 years old?” The SAAS project that I was talking about, it was 15-year-old code, .net. I got people together; one from each department. We all got together and we ended up making that product accessible for them. So it can be done. [laughs] It can be done. JOHN: That's actually a good point. Just hearing about successes in the wild with particularly hard projects is a great thing. Because again, I'm thinking about it at the start of our project and hearing that somebody made it all through and maybe even repeatedly is hard. TODD: Yeah. It's not something that once it's done, it's done. Accessibility, just like the web, is an ever-evolving media. MANDY: For me. I think my reflection is going to be, as a new coder, I do want to say, I'm glad that we talked about a lot of the things that you see that aren't currently accessible that can be accessible. One of those things is using alt tags and right now, I know when I put the social media posts out on Twitter, I don't use the alt tags and I should. So just putting an alt tag saying, “This is a picture of our guest, Todd” and the title of the show would probably be helpful for some of our listeners. So I'm going to start doing that. So thank you. TODD: You're welcome. I'm just reminded of our talk and every talk that I have on a podcast, or with anybody just reminds me of the work that I have to do and the work that is being done by a lot of different people, other than myself as well, as far as advocacy goes in that I don't think it's ever going to be a job that will ever go away. There will always be a need for accessibility advocacy for the web and it's great just to be able to sit down and talk to people about accessibility and what we need to do to make the web better and more inclusive for everybody. Because I tweet out a lot, “Accessibility is a right, not a privilege,” and I really feel that to my core because the UN specifically says that the internet is a basic human and I went as far as to go say, “Well, so as an accessibility of that internet as well.” So that is my reflection. MAE: I'll add an alt tag for me right now is with a fist up and a big smile and a lot of enthusiasm in my heart. MANDY: Awesome. Well, thank you so much for coming on the show, Todd. It's been really great talking with you and I really appreciate you coming on the show to share with us your knowledge and your expertise on the subject of accessibility. So with that, I will close out the show and say we do have a Slack and Todd will be invited to it if he'd like to talk more to us and the rest of the Greater Than Code community. You can visit patreon.com/greaterthancode and pledge to support us monthly and again, if you cannot afford that, or do not want to pledge to help run the show, you can DM anyone of us and we will get you in there for free because we want to make the Slack channel accessible for all. Have a great week and we'll see you next time. Goodbye! Special Guest: Todd Libby.

02:51 - Jennifer's Superpower: Kindness & Empathy * Complex Post Traumatic Stress Disorder (https://www.verywellmind.com/what-is-complex-ptsd-2797491) (C-PTSD) 07:37 - Equitable Design and Inclusive Design * Section 508 (https://www.section508.gov/) Compliance * Web Content Accessibility Guidelines (https://www.w3.org/WAI/standards-guidelines/wcag/) (WCAG) * HmntyCentrd (https://hmntycntrd.com/) * Creative Reaction Lab (https://www.creativereactionlab.com/) 15:43 - Biases and Prejudices * Self-Awareness * Daniel Kahneman's System 1 & System 2 Thinking (https://www.marketingsociety.com/think-piece/system-1-and-system-2-thinking) * Jennifer Strickland: “You're Killing Your Users!” (https://vimeo.com/506548868) 22:57 - So...What do we do? How do we get people to care? * Caring About People Who Aren't You * Listening * Using Web Standards and Prioritizing Web Accessibility * Designing with Web Standards by Jeffrey Zeldman (https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0321616952) * Bulletproof Web Design by Dan Cederholm (https://www.amazon.com/Bulletproof-Web-Design-flexibility-protecting/dp/0321509021) * Progressive Enhancement * Casey's Cheat Sheet (https://moritzgiessmann.de/accessibility-cheatsheet/) * Jennifer Strickland: “Ohana for Digital Service Design” (https://www.youtube.com/watch?v=VfsZlkm59BE) * Self-Care 33:22 - How Ego Plays Into These Things * Actions Impact Others * For, With, and By * Indi Young (https://indiyoung.com/) 44:05 - Empathy and Accessibility * Testability/Writing Tests * Screen Readers * TalkBack (https://support.google.com/accessibility/android/answer/6283677?hl=en) * Microsoft Narrator (https://support.microsoft.com/en-us/windows/complete-guide-to-narrator-e4397a0d-ef4f-b386-d8ae-c172f109bdb1) * NVDA (https://www.nvaccess.org/about-nvda/) * Jaws (https://www.freedomscientific.com/products/software/jaws/) * Heydon Pickering (https://twitter.com/heydonworks/status/969520320754438144) Reflections: Casey: Animals can have cognitive disabilities too. Damien: Equitable design initiatives and destroying the tenants of white supremacy. Jennifer: Rest is key. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Transcript: MANDO: Hello, friends! Welcome to Greater Than Code, Episode number 243. My name is Mando Escamilla and I'm here with my wonderful friend, Damien Burke. DAMIEN: Thank you, Mando, and I am here with our wonderful friend, Casey Watts. CASEY: Hi, I'm Casey, and we're all here today with Jennifer Strickland. With more than 25 years of experience across the product lifecycle, Jennifer aims to ensure no one is excluded from products and services. She first heard of Ohana in Disney's Lilo & Stitch, “Ohana means family. Family means no one gets left behind, or forgotten.” People don't know what they don't know and are often unaware of the corners they cut that exclude people. Empathy, compassion, and humility are vital to communication about these issues. That's Jennifer focus in equitable design initiatives. Welcome, Jennifer! JENNIFER: Hi! DAMIEN: You're welcome. MANDO: Hi, Jennifer. So glad you're here. JENNIFER: I'm so intrigued. [laughs] And I'm like 243 and this is the first I'm hearing of it?! DAMIEN: Or you can go back and listen to them all. MANDO: Yeah. CASEY: That must be 5, almost 6 years? JENNIFER: Do you have transcripts of them all? CASEY: Yes. JENNIFER: Great! MANDO: Yeah. I think we do. I think they're all transcribed now. JENNIFER: I'm one of those people [chuckles] that prefers to read things than listen. DAMIEN: I can relate to that. CASEY: I really enjoy Coursera courses. They have this interface where you can listen, watch the video, and there's a transcript that moves and highlights sentence by sentence. I want that for everything. MANDO: Oh, yeah. That's fantastic. It's like closed captioning [laughs] for your audio as well. JENNIFER: You can also choose the speed, which I appreciate. I generally want to speed things up, which yes, now that I'm getting older, I have to realize life is worth slowing down for. But when you're in a life where survival is what you're focused on, because you have a bunch of things that are slowing your roll and survival is the first thing in your mind, you tend to take all the jobs, work all the jobs, do all of the things because it's how you get out of poverty, or whatever your thing is. So I've realized how much I've multitasked and worked and worked and worked and I'm realizing that there is a part of the equality is lost there, but we don't all have the privilege of slowing down. DAMIEN: I can relate to that, too. So I believe every one of our past 243 episodes, we asked our guests the same question. You should know this is coming. Jennifer, what is your superpower and how did you acquire it? JENNIFER: I don't know for sure. People have told me that I'm the kindest person they've ever met, people have said I'm the most empathetic person I've ever met, and I'm willing to bet that they're the same thing. To the people, they just see them differently. I acquired being empathetic and kind because of my dysfunction in my invisible disabilities. I have complex post-traumatic stress disorder from childhood trauma and then repeated life trauma, and the way it manifests itself is trying to anticipate other people's needs, emotions, moods, and all of that and not make people mad. So that's a negative with a golden edge. Life is full of shit; how you respond to it shows who you are and rather than molesting kids, or hurting people, I chose to do what I could to make sure that no one else goes through that and also, to try to minimize it coming at me anymore, too. [chuckles] But there's positive ways of doing it. You don't have to be like the people who were crappy to you and the same goes like, you're in D.C.? Man, they're terrible drivers and it's like, [laughter] everybody's taking their bad day and putting it out on the people they encounter, whether it's in the store, or on the roads. I was like, “Don't do that.” Like, how did it feel when your boss treated you like you were garbage, why would you treat anyone else like garbage? Be the change, so to speak. But we're all where we are and like I said in my bio, “You don't know what you don't know.” I realized earlier this week that it actually comes from Donald Rumsfeld who said, “Unknown unknowns.” I'm like, “Oh my God. Oh my God.” MANDO: You can find good in lots of places, right? [laughs] JENNIFER: If you choose to. MANDO: Absolutely. Yeah. JENNIFER: Look at, what's come out of the horror last year. We talk about shit that we didn't use to talk about. Yeah, it's more exhausting when lots of people, but I think in the long run, it will help move us in the right direction. I hope. MANDO: Yeah. That's absolutely the hope, isn't it? JENNIFER: We don't know what we don't know at this time. My sister was volunteering at the zoo and she worked in the Ape House, which I was super jealous of. There's an orangutan there named Lucy who I love and Lucy loves bags, pouches, and lipstick. So I brought a backpack with a pouch and some old lipstick in it and I asked a volunteer if I could draw on the glass. They gave me permission so I made big motions as I opened the backpack and I opened the pouch and you see Lucy and her eyes are like, she's starting to side-eye me like something's going on. And then she runs over and hops up full-time with her toes on the window cell and she's like right up there. So I'm drawing on the glass with the lipstick and she's loving it, reaches her hand behind, poops into her hand, takes the poop and repeats this little actions on the glass. MANDO: [laughs] Which is amazing. It's hilarious so that's amazing. JENNIFER: It's fantastic. I just think she's the bomb. My sister would always send pictures and tell me about what Lucy got into and stuff. Lucy lived with people who would dress her in people clothing and so, she's the only one of the orangutans that didn't grow up only around orangutans so the other orangutans exclude her and treat her like she's a weirdo and she's also the one who likes to wear clothes. Like my sister gave her an FBI t-shirt so she wears the FBI t-shirt and things like that. She's special in my heart. Like I love the Lucy with all of it. DAMIEN: Well, that's a pretty good display of your super empathetic superpower there. [laughter] And it sounds like it might be really also related to the equitable design initiatives? JENNIFER: Yeah. So I'm really grateful. I currently work at a place that although one would think that it would be a big, scary place because of some of the work that we do. I've found more people who know what equity is and care about what equity is. The place I worked before, I talked about inclusive design because that's everywhere else I've worked, it's common that that's what you're doing these days. But they told me, “Don't say that word, it's activism,” and I was stunned. And then I'm like, “It's all in GSA documents here,” and they were like, “Oh,” and they were the ones that were really bad about like prioritizing accessibility and meeting section 508 compliance and just moving it off to put those issues in the backlog. The client's happy, no one's complained, they think we're doing great work. It's like, you're brushing it all under the rug and you're telling them what you've done and you're dealing with people who don't know what section 508 is either because who does? Very few people really know what it means to be section 508 compliant because it's this mystery container. What is in this? What is this? What is this thing? DAMIEN: So for our listeners who don't know, can you tell us a bit what section 508 is? JENNIFER: Sure. So section 508 means that anything paid for with federal funds must be section 508 compliant, which means it must meet WCAG 2.0 success criteria and WCAG is Web Content Accessibility Guidelines. If you're ever looking for some really complicated, dense, hard to understand reading, I recommend opening up the Web Content Accessibility Guidelines. I think the people that are on the working groups with me would probably agree and that's what we're all working towards trying to improve them. But I think that they make the job harder. So rather than just pointing at them and complaining like a lot of people do on Twitter, or deciding “I'm going to create a business and make money off of making this clear for people,” I decided instead to join and try to make it better. So the Web Content Accessibility Guidelines are based on Perceivable, Operable, Understandable, and Robust, POUR. Pour like this, not poor like me. [laughs] So there's just a bunch of accessibility criteria that you have to meet to make your work section 508 compliant. It's so hard to read and so hard to understand that I feel for everybody like of course, you don't know what section 508 compliance is. It's really, really hard to read. But if somebody who is an accessibility specialist tells you and writes up an issue ticket, you don't argue with them. You don't say, “This isn't a thing,” you say, “Okay, how soon do I need to fix it?” and you listen to them, but that's not what I experienced previously. Where I am now, it's amazing. In the place I worked before here, like just the contracting, they welcomed everything I said to them regarding accessibility. So I just clearly worked at a contractor that was doing a lot of lip service and not talking the talk, not walking the talk, sorry. [laughs] Super frustrating. Because accessibility is only a piece of it. I am older probably than anybody on this call and I'm a woman working in tech and I identify as non-binary. The arguments I've had about they/them all my life have been stupid, but I'm just like, “Why do I have to be female?” It's just, why do I have to be one, or the other? Anyway, everyone has always argued with me so I'm so grateful for the young ones now for pushing all that. I'm Black, Native, Mexican, and white all smushed together and my grandma wouldn't let me in the house because apparently my father was too dark so therefore, I'm too dark. Hello? Look at this! [laughter] Currently, some people are big on the one drop rule and I always say to people, “If you hate me, or want to exclude me so much because somewhere in me you know there is this and how do you feel about so-and-so? I'm done with you and you are bad people and we've got to fight this stupidity.” I have also invisible disabilities. So I'm full of all these intersectional things of exclusion. I personally experience a lot of it and then I have the empathy so I'm always feeling fuzzy people who are excluded. So what am I supposed to do with the fact that I'm smart, relatively able-bodied, and have privilege of being lighter skin so I can be a really good Trojan horse? I have to be an advocate like, what else am I supposed to do with my life? Be a privileged piece of poop that just wants to get rich and famous, like a lot of people in tech? Nope. And I don't want to be virtue signaling and savior complex either and that's where equitable design has been a wonderful thing to learn more about. HmntyCntrd.com and Creative Reaction Lab out in Missouri, those are two places where people can do a lot of learning about equity and truly inclusion, and challenging the tenants of white supremacy in our working ways. I'm still trying to find better ways of saying the tenants of white supremacy because if you say that in the workplace, that sounds real bad, especially a few months back before when someone else was in office. When you say the tenants of white supremacy in the workplace, people are going to get a little rankled because that's not stuff we talk about in the workplace. DAMIEN: Well, it's not just the workplace. JENNIFER: Ah, yes. DAMIEN: They don't like that at sports bars either. Ask me how I know. MANDO: No, they sure don't. [laughter] JENNIFER: We should go to sports bars together. [laughs] Except I'm too scared to go to them right now unless they're outdoors. But when we talk to people about the actual individual tenants about power hoarding, perfectionism, worship of the written word, and things like that, people can really relate and then you watch their faces and they go, “Yeah, I do feel put my place by these things and prevented from succeeding, progressing, all of these things.” These are things that we've all been ingrained to believe are the way we evaluate what's good and what's bad. But we don't have to. We can talk about this stuff when we can reject those things and replace them with other things. But I'm going to be spending the rest of my life trying to dismantle my biases. I'm okay with my prejudices because even since I was a kid, I recognized that we were all prejudice and it's okay. It's our knee jerk first assumption, but you always have to keep an open mind, but that prejudice is there to protect you, but you always have to question it and go, “What is that prejudice? Is that bullshit? Is it right? Is it wrong?” And always looking at yourself, it's always doing that what you call self-awareness stuff, and always be expanding it, changing it, and moving it. But prejudice? Prejudice has a place to protect, speaking as someone who's had guns in her face, knives through her throat, and various other yucky things, I know that when I told myself, “Oh, you're being prejudiced, push yourself out into that vulnerable feeling,” things didn't go very well. So instead, recognize “Okay, what are you thinking in this moment about this situation? Okay, how can you proceed and keep an open mind while being self-protective?” DAMIEN: Yeah, it sounds like you're talking about Daniel Kahneman's System 1 and System 2 Thinking. We have these instinctive reactions to things and a lot of them are learned—I think they're all learned actually. But they're instinctive and they're not things we decide consciously. They're there to protect us because they're way faster, way more efficient than most of what we are as humans as thinking and enacting beings. But then we also have our rational mind where we can use to examine those things and so, it's important to utilize both. It's also important to know where your instinctive responses are harmful and how to modify them so that they're not harmful. And that is the word. JENNIFER: I've never heard of it. Thanks for putting that in there. Power accretion principles is that it? CASEY: Oh, that's something else. JENNIFER: Oh. CASEY: Type 1 and type 2 thinking. JENNIFER: But I know with a lot of my therapy work as a trauma survivor, I have to evaluate a lot of what I think and how I react to things to change them to respond things. But there are parts of having CPTSD that I am not going to be able to do that, too. Like they're things where for example, in that old workplace where there was just this constant invalidation and dismissal of the work, which was very triggering as a rape survivor/incest survivor, that I feel really bad and it made me feel really unsafe all the time. So I felt very emotional in the moment and so, I'd have to breathe through my nose, breathe out to my mouth, feel my tummy, made sure I can feel myself breathing deeply, and try to calmly explain the dire consequences of some of these decisions. People tend to think that the design and development decisions we make when we're building for the web, it's no big deal if you screw it up. It's not like an architect making a mistake in a building and the building falls down. But when you make a mistake, that means a medical locator application doesn't load for an entire minute on a slow 3G connection—when your audience is people who are financially challenged and therefore, unlikely to have always high-speed, or new devices—you are making a design decision that is literally killing people. When you make a design decision, or development decision not to QA your work on mobile, tablet, and desktop, and somebody else has to find out that your Contact Us options don't open on mobile so people in crisis can't reach your crisis line. People are dying. I'm not exaggerating. I have a talk I give called You're Killing Your Users and it got rejected from this conference and one of the reviewers wrote, “The title is sensationalism. No one dies from our decision,” and I was just like, “Oh my God, oh my God.” MANDO: [laughs] Like, that's the point. JENNIFER: What a privileged life you live. What a wonderfully privileged life! There's a difference between actions and thoughts and it's okay for me to think, “I really hope you fall a flight of stairs and wind up with a disability and leave the things that you're now trying to put kibosh on.” But that's not me saying, “I'm going to go push you down a flight of stairs,” or that I really do wish that on someone. It's emotional venting, like how could you possibly close yourself off to even listening to this stuff? That's the thing that like, how do we get to a point in tech where so many people in tech act like the bad stereotype of surgeons who have this God complex, that there are particular entities working in government tech right now that are told, “You're going to save government from itself. You've got the answers. You are the ones that are going to help government shift and make things better for the citizen, or the people that use it.” But the people that they hire don't know what they don't know and they keep doing really horrible things. Like, they don't follow the rules, they don't take the time to learn the rules and so, they put user personal identifying information, personal health information on the public server without realizing it that's a no-no and then it has to be wiped, but it can never really fully be wiped. And then they make decisions like, “Oh, well now we're only worried about the stuff that's public facing. We're not worried about the stuff that's internally facing.” Even though, the internally facing people are all some of the vulnerable people that we're serving. I'm neutralizing a lot of what I'm talking about. [chuckles] MANDO: Of course. [laughter] DAMIEN: Well, convinced me of the problems. It was an easy sell for me. Now, what do we do? JENNIFER: The first thing we do is we all give a fuck about other people. That's the big thing, right? Like, how do I convince you that you should care about people who aren't you? MANDO: Yeah. CASEY: I always think about the spectrum of caring. I don't have a good word for it, but there are active and passive supporters—and you can be vocal, or quiet—like loud, or quiet. I want more people to be going around the circle of it so if they're vocally opposed, just be quiet, quietly opposed, maybe be quietly in support, and if you're quietly in support, maybe speak up about it. I want to nudge people along around this, the four quadrants. A lot of people only focus on getting people who passively care to be more vocal about it. That's a big one. That's a big transition. But I also like to focus on the other two transitions; getting a lot of people to be quiet about a thing that as opposed. Anyway, everywhere along that process is useful. JENNIFER: I think it's important to hear the people who were opposed because otherwise, how are we ever going to help understand and how are we going to understand if maybe where we've got a big blind spot? Like, we have to talk about this stuff in a way that's thoughtful. I come from a place in tech where in the late 90s, I was like, “I want to move from doing print to onscreen and printing environmental to that because it looks like a lot of stuff has gone to this web thing.” I picked up Jeffrey Zeldman's Designing with Web Standards and Dan Cederholm's Bulletproof Web Design and all of them talk about using web standards and web standards means that you prioritize accessibility from the beginning. So the first thing you build is just HTML tagging your content and everyone can use it. It's not going to be fancy, but it's going to be completely usable. And then you layer things on through progressive enhancement to improve the experience for people with fancy phones, or whatever. I don't know why, but that's not how everybody's coming into doing digital work. They're coming in through React out of the box, thinking that React out of the box is – and it's like nope, you have to build in the framework because nobody put the framework in React. React is just a bunch of hinges and loops, but you have to put the quality wood in and the quality glass panes and the handles that everybody can use. I'm not sure if that analogy is even going to work. But one of the things I realized talking with colleagues today is I tend to jump to three steps in when I really need to go back, start at the beginning, and say, “Here are the terms. This is what section 508 is. This is what accessibility is. This is what A11Y is. This is WCAG, this is how it's pronounced, this is what it means, and this is the history of it.” I think understanding history of section 508 and what WCAG is also vital in the first version of WCAG section 508, it adopted part of what was WCAG 1.0, but it wasn't like a one to one for 1.0, it was just some of it and then it updated in 2017, or 2018, I forget. Without my cheat sheet, I can't remember this stuff. Like I got other things to keep in my brain. CASEY: I just pulled up my favorite cheat sheet and I put it in the chat sidebar here. JENNIFER: Oh, thank you. It's in my slides for Ohana for Digital Service Design that I gave at WX Summit and I think I also gave it recently in another thing. Oh, UXPA DC. But the thing is, the changes only recently happened where it went to WCAG 2.0 was 2018, I think it got updated. So all those people that were resisting me in 2018, 2019, 2020 likely never realized that there was a refresh that they need to pay attention to and I kept trying to like say, “No, you don't understand, section 508 means more now.” Technically, the access board that defines what section 508 is talking about moving it to 2.1, or 2.2 and those include these things. So we should get ahead of the ball, ahead of the curve, or whatever you want to call it and we should be doing 2.1 and 2.2 and even beyond thinking about compliance and that sort of stuff. The reason we want to do human beings is that 2.1 and 2.2 are for people who are cognitively fatigued and I don't think there's anyone who's been through the pandemic who is not cognitively fatigued. If you are, you are just a robot. I don't know. I don't know who could not be not cognitive fatigue. And then the other people that also helps are mobile users. So if you look at any site, look at their usage stats, everything moving up and up and up in mobile devices. There's some people who don't have computers that they only have phones. So it just seems silly not to be supporting those folks. But we need, I don't know. I need to think more about how to get there, how to be more effective in helping people care, how to be more effective in teaching people. One of the big pieces I've learned in the last six months is the first step is self-care—sleep, exercise, eat, or maybe those two need to be back and forth. I haven't decided yet because I'm still trying to get the sleep workout. Before I moved to D.C., I was a runner, hiker, I had a sit spot at the local pond where I would hang out with the fishes and the turtles and the frogs and the birds and here, I overlook the Pentagon and there's swarms of helicopters. I grow lots of green things to put between me and it, but it's hard. The running is stuck because I don't feel safe and things like that. I live in an antiseptic neighborhood intentionally because I knew every time I went into D.C. and I saw what I see, I lose hope because I can't not care. It kills me that I have to walk by people who clearly need – this is a messed up world. We talk about the developing world as the place where people are dying on the side of the road. Do you have blinders on like, it's happening here? I don't know what to do. I care too much. So what do we do? What do you think? DAMIEN: Well, I think you have a hint. You've worked at places that are really resistant to accessibility and accessibility to improvements, and you've worked at some that are very welcoming and eager to implement them. So what were the differences? What do you think was the source of that dichotomy? JENNIFER: I think at the place I worked after I left the hellhole; the product owner was an Asian woman and the other designer was from India. Whereas, before the other place was a white woman and a white man and another white man who was in charge. And then the place I work now, it's a lot of people who are very neurodiverse. I work at MITRE, which is an FFRDC, which is a Federally Funded Research and Development Center. It's full of lots of smart people who are very bookish. It's funny when I was a little kid, I was in the gifted and talented kids and so, they would put us into these class sessions where we were to brainstorm and I love brainstorming. I love imagining things. I remember thinking, “I want to work in a think tank and just all I do all the time is brainstorm and we'd figure out a way to use some of those things!” And I feel a little bit like I'm there now, which is cool and they treat one another really well at MITRE, which is nice. Not to say it's perfect there. Nowhere is perfect. But compared to a lot of places, it's better. I think it's the people are taking the time to listen, taking the time to ask questions. The people I work with don't have a lot of ego, generally. At least not the ones I'm working with. I hear that they do exist there, but I haven't run into many of them. Whereas, the other place, there was a lot of virtue signaling and a lot of savior complex. Actually, very little savior conflicts. They didn't really care about saving anyone, sorry. Snark! [laughs] DAMIEN: Can you tell us a little more about ego and how ego plays into these things? JENNIFER: How do you think ego plays into these things? DAMIEN: Well, I think it causes people to one up and turn questions around it on me, that's one way. Ego means a lot of things to a lot of different people, which is why I asked the question. I think it was introduced to English by Freud and I don't want to use a Freudian theory for anything ever. [laughter] And then when I talk to people about death of the ego and [inaudible] and all of these things, it seems really unpleasant. People like their self-identity, people like being themselves, and they don't want to stop being themselves. So I'm not sure how that's related to what you were saying. CASEY: The way I'm hearing you use ego here sounds like self-centered, thinking about your own perspective, not taking the time and effort and energy to think about other people's perspectives. And if you don't have a diverse set of experiences to lean on your own, you're missing out on a lot. JENNIFER: Yeah. I tend to think about, I guess, it's my dysfunction. Once again, it's like, how do my actions impact others? Why are other people thinking about how their actions impact others? When you're out in public and you've got to cut the cheese, are you going to do it when there are a lot of people around? Are you going to take a stinky deuce in a public bathroom that you know other people in there? If you think about the community around you, you would go find a private one if you cared at all. But most people don't care and they think, “I do what I got to do.” I just think we need to think a little bit more about the consequences of our actions and I tweeted yesterday, or this morning about how – oh, it was yesterday. I was watching TV and a new, one of those food delivery commercials came on. This one, they send you a stove, you get a little oven, and you cook all of their meals in this little throwaway dishes. So you have no dishes, nothing. How much are we going to just keep creating crap? When you think about all of this takeout and delivery, there's just so much trash we generate. We should be taxing the bleep out of companies that make these sorts of things like, Amazon should have the bleep taxed out of it because of all the cardboard and I'm just as guilty because I ordered the thing and the box of staples arrives in a box. It has a plastic bubble wrap all around it. Like it's just a box at $2.50 staples, but I couldn't be bothered to go – I don't know if they have them at Walgreens. Like for real, I don't know. We need to do better. We need to think about the consequences of these decisions and not just do it like, that's the thing that tech has been doing is let's make an MVP and see if it has wheels. Let's make a prototype, but do the thing. Okay, let's do the thing. Oh, it's got wheels. Oh, it's growing, it's growing, it's growing, it's growing. Who cares about the consequences of all of it? Who cares? Your kids, your grandkids someday maybe will when the world is gone. We talk about climate change. We talk about 120-degree temperatures in Seattle and Portland, the ocean on fire, the beaches are eroding, like the ice cap—most of the Arctic is having a 100 and some odd degree temperature day. Like we are screwing it up and our legislation isn't keeping pace with the advances in technology that are just drawing things. Where are the people who care in the cycle and how are they interrupting the VCs who just want to like be the next big tech? Everybody wants to be the next Zuckerberg, or Jack, or Bezos, or Gates, or whatever, and nobody has to deal with the consequences of their actions and their consequences of those design and development decisions. That's where I think it's ego, it's self-centeredness, it's wanting to be famous, it's wanting to be rich instead of really, truly wanting to make the world a better place. I know my definition of better. We've got four different visions of what better is going to be and that's hard work. Maybe it is easier to just focus on getting famous and getting rich than it is on doing the hard work of taking four different visions of what good is and trying to find the way forward. DAMIEN: Making the world a better place. The world will be a better place when I'm rich and famous. But that also means – and that's the truth. [laughter] But what else you said was being empathetic and having a diverse – well, marginalized people in charge where you can see that that's why the impact that things are having on other people. It's not just about me being rich and famous, but it's also about things being better for other people, too. JENNIFER: Yeah. I don't necessarily mean marginalized people have to be in charge. DAMIEN: Right. I took that jump based on your description of the places you worked for. I should have specified that. I wasn't clear enough. JENNIFER: I do have to say that in general, when I've worked for people who aren't the status quo, more often than not, they bring a compassionate, empathetic approach. Not always. There have been some that are just clearly driven and power hungry, and I can't fault them either because it's got to take a lot to come up from wherever and fight through the dog-eat-dog world. But in the project work, there's the for, with and by. The general ways that we redesign and build things for people, then the next piece is we design and build things with the people that we're serving, but the newer way of doing things is that we don't design and build the things, the people that we're serving design the things and tell us what they want to design, and then we figure out how to make sure that it's built the way they tell us to. That goes against the Steve Jobs approach where Steve Jobs said people don't know what they want sort of thing. Wasn't that was he said? DAMIEN: Yeah. Well, there was Henry Ford who said, “If you ask people what they wanted, they would've said faster horses.” JENNIFER: Right. D And Steve Jobs kind of did the same thing. JENNIFER: Right. And we, as designers, have to be able to work with that and pull that out and suss it out and make sure that we translate it into something useful and then iterate with to make sure that we get it. Like when I do research, listening sessions with folks, I have to use my experience doing this work to know what are the – like, Indi Young's inner thinking, reactions, and guiding principles. Those are the things that will help guide you on what people are really wanting and needing and what their purpose is. So you make sure that whatever your understanding is closer to what they're really saying, because they don't know what can be built. They don't know what goes on, but they do know what their purpose is and what they need. Maybe they don't even know what they need, but they do know what their purpose is, or you keep validating things. CASEY: I want to amplify, you said Indi Young. I read a lot of her work and she just says so many things that I wish someone would say, and she's been saying them for a while. I just didn't know about her. Indi Young. JENNIFER: It's I-N-D-I and Y-O-U-N-G. I am so grateful that I got to take her courses. I paid for them all myself, except for one class—I let that other place pay for one through my continuing ed, but I wanted to do it so badly that I paid for all myself. The same thing with all the Creative Reaction Lab and HmntyCntrd stuff; I paid for those out of my own money that probably could have gone to a vacation, [chuckles] or buying a car, or something. But contributing to our society in a responsible and productive way, figuring out how to get my language framework better. Like you said earlier, Damien, I'm really good at pointing out what the problems are. I worry about figuring out how we solve them, because I don't really have the ego to think that I know what the answer is, but I'm very interested in working with others to figure out how we solve them. I have some ideas, but how do you tell a React developer that you really have to learn HTML, you have to learn schematic HTML. That's like learning the alphabet. I don't understand. CASEY: Well, I have some ideas around that. Amber is my go-to framework and they have accessibility baked into the introduction tutorial series. They have like 13 condoned add-ons that do accessibility related things. At the conference, there's always a whole bunch of accessibility tracks. Amber is like happy path accessibility right front and center. React probably has things like that. We could have React's onboarding docs grow in that direction, that would be great, and have more React add-ons to do that that are condoned and supported by the community could have the same path. And it could probably even use a lot of the same core code even. The same principles apply. JENNIFER: If you want to work together and come up with some stuff to go to React conferences, or work with the React team, or whatever. 
CASEY: Sounds fun. DAMIEN: Well, one of the things you talked about the way you described it and made it sound like empathy was so much of the core of it. In order to care about accessibility, you have to empathize with people who need that functionality. You have to empathize with people who are on 3G flip phones. That's not a thing, is it? [laughs] But nonetheless, empathizing. JENNIFER: A flat screen phone, a smartphone looking thing and it's still – if anyone's on a slow 3G, it's still going to be a miserable experience. DAMIEN: Yeah, 3G with a 5-year-old Android OS. JENNIFER: But I don't think it's necessarily that people have to empathize. In an ideal world would, but maybe they could be motivated by other things like fast. Like, do you want to fast cumulative layout shift? Do you want like a great core vitals Google score? Do you want a great Google Lighthouse score? Do you want the clear Axe DevTools scan? Like when I get a 100% little person zooming in a wheelchair screen instead of issues found. Especially if I do it the first time and like, I hadn't been scanning all along and I just go to check it for the first time and it's clean, I'm like, “Yes!” [laughs] CASEY: Automation helps a lot. JENNIFER: Yeah. CASEY: When I worked at USCIS, I don't know what this meant, but they said we cannot automate these tests. I think we can and they didn't do it yet, but I've always been of baffled. I think half of it, you can automate tests around and we had none at the time. JENNIFER: Yeah, you catch 30 to 50% of the accessibility issues via the Axe rule set and JSX Alley and all that. You can catch 30 to 50. CASEY: Sounds great. JENNIFER: That's still better than catching none of them. Still not great, but it's still better than nothing. They're not here to tell us why they can't, but adding things into your end-to-end test shouldn't be that hard if you know how to write tests. I don't personally know how to write tests. I want to. I don't know. Like, I have to choose which thing am I going to work on? I'm working on an acquisition project, defining the requirements and the scope and the red tape of what a contract will be and it's such foreign territory for me. There's a lot of pieces there that I never ever thought I would be dealing with and my head hurts all the time. I feel stupid all the time, but that's okay. If you're not doing something you haven't done before, maybe you're not learning, it's growing. I'm growing. I'm definitely growing, but in different ways and I miss the code thing of I have a to-do list where I really want to get good at Docker, now I want to learn few, things like that and I want to get back to learning Python because Python, I think is super cool. CASEY: There's one thing I wanted to mention earlier that I just remembered. One thing that was eye-opening to me for accessibility concerns is when I heard that screen reader has existed, which was several years into my programming career. I didn't know they were a thing at all. I think it's more common now that people know about them today than 10, 15 years ago. But I still haven't seen someone use a screen reader and that would be really important for me as a developer. I'm not developing software lately either so I'm not really coding that. But if anyone hasn't, you should use a screen reader on your computer if you're developing software that might have to be used by one. JENNIFER: So everyone on a Mac has voiceover. Everyone on an iPhone has voiceover. It's really hard on the iPhone, I feel like I can't, oh, it's really hard. I've heard great things about Talkback on Android. And then on Windows, newer versions have Microsoft Narrator, which is a built-in screen reader. You can also download NVDA for free and install it. It depends on how much money you want to spend. There a bunch of different ways to get Jaws, do Jaws, too. Chrome has Chromebox so you can get another screen reader that way. CASEY: So many options. It's kind of overwhelming. If I had to recommend one for a Windows user and one for a Mac user, would you recommend the built-in ones just to start with, to play with something? JENNIFER: So everywhere I've tested, whether it was at the financial institution, or the insurance place, or the government place, we always had to test with Jaws, NVDA, and voiceover. I test with voiceover because it's what I have on my machine, because I'm usually working on a Mac. But the way I look at the screen reader is the number of people who are using screen readers is significantly fewer than the number of people with cognitive considerations. So I try to use good semantic markup, basic web standards so that things will work; things have always been pretty great in screen readers because of that. I try to keep my code from being too complicated, or my UI is from being complicated, which might do some visual designers seem somewhat boring to some of them. [chuckles] CASEY: Do you ever turn off CSS for the test? JENNIFER: Yes, and if it makes sense that way, then I know I'm doing it right and is it still usable without JavaScript. Better yet, Heydon Pickering's way of like, it's not usable unless you turn off the JavaScript, that was fabulous. I pissed off so many people. But to me, I try to focus on other things like how clear is, how clean is it? Can I tab through the whole UI? Can I operate it with just a keyboard? Your keyboard is your best assistive tech tester. You don't skip. If you can tap through anything without getting stuck, excellent. If you don't skip over nav items. CASEY: My biggest pet peeve is when websites don't work when you zoom in, because all of my devices I zoom in not because my vision is bad, but because for my posture. I want to be able to see my screen from a far distance and not lean in and craning my neck over laptop and my phone, both and a lot of websites break. JENNIFER: Yeah. CASEY: You zoom in the text at all, you can't read anything. JENNIFER: Yeah. At the one place I worked before, we required two steps of zoom in and two steps of zoom out, and it still had to be functional. I don't see that in most places; they don't bother to say things like that. CASEY: Yeah. JENNIFER: At the government, too – CASEY: I wonder how common it is if people do that. I do it so I think it's very common, but I don't know the right. [laughter] JENNIFER: But that's how the world is, right? I can tell you that once you hit this old age and your eyes start to turn against you and things are too small, or too light, you suddenly understand the importance of all of these things so much more. So for all of those designers doing your thin gray text on white backgrounds, or thin gray text on gray backgrounds, or your tiny little 12 and under pixels for your legaleas, karma is out to get you. [chuckles] We've all done it. Like there was a time I thought nobody cared about the legaleas. That's not true. Even your footer on your website should be big enough for people to read. Otherwise, they think I'm signing away my soul to zoom because I can't read it. If you can zoom it in, that's great. But some apps disable the zoom. DAMIEN: So we usually end on a series of reflections. How do you feel about moving to that? JENNIFER Sure! DAMIEN: We let our guests go last. Casey, do you have a reflection you want to share with us? CASEY: I'm thinking back to Mando's dog and I thought it was interesting, Jennifer, that you linked your experiences with the dog's experiences. Like, some of the symptoms you have might be similar if a dog has CPTSD, too and I think that's really insightful. I think a lot of animals have that kind of set up, but we don't treat them like we treat humans with those issues even if they're similar. DAMIEN: It was in your bio, equitable design initiatives, I really want it to dig into that because that fascinates me and I guess, if draws that bridge between things that I think are very important, or very important for me, both accessibility, that sort of work, especially in software design, because that's where I'm at. And then destroying the tenants of white supremacy and being able to connect those as things that work together and seeing how they work together. Yeah, that's what I'm going to be reflecting on. JENNIFER: Yeah. Whenever we're doing our work, looking for opportunities to surface and put it out for everyone to look at who has power, if this changes who has power, if this doesn't change who has power, what is motivating the players, are people motivated by making sure that no one's excluded, or are people motivated by making sure that their career moves forward, or they don't get in trouble rather than truly serving? I still am in the mindset of serving the people with a purpose that we're aiming to meet the needs of kind of thing. I still have that mindset. A lot of the prep work, we're still talking about the people we aim to serve and it's still about getting them into the cycle. That is a very big position of power that a designer has and acknowledging that that's power and that I wield that power in a way that I consider responsible, which is to make sure that we are including people who are historically underrepresented, especially in those discussions. I'm really proud of a remote design challenge where all of our research participants were either people of color, or people with disabilities. Man, the findings insights were so juicy. There was so much that we could do with what we got. It was really awesome. So by equitable design initiatives, it's really just thinking about acknowledging the power that we have and trying to make sure we do what we can to share it, transfer it, being really respectful of other perspectives. I've always thought of it as infinite curiosity about others and some people have accused me being nosy and they didn't realize it's not about getting up in their private business. It's just, I want to be gracious and respect others. What I will reflect on was how I really need to rest. I will continue to reflect on how I rest is key. I'm making a conscious decision for the next couple of months to not volunteer because I tend to do too much, as Casey may, or may not know. [chuckles] Yeah, I want to wake up in the morning and feel energized and ready to take full advantage of, which is not the right way to phrase it, but show up as my best self and well-prepared for the work. Especially since I now have found myself a new incredibly compassionate, smart place that genuinely aims to improve equity and social justice, and do things for the environment and how grateful I am. I totally thought this place was just about let's them all and it's so not. [laughs] So there's so many wonderful people. I highly recommend everybody come work with me if you care about things. DAMIEN: That's awesome. Well, thank you so much, Jennifer for being our guest today. It's been a pleasure. The author's affiliation with The MITRE Corporation is provided for identification purposes only, and is not intended to convey or imply MITRE's concurrence with, or support for, thepositions, opinions, or viewpoints expressed by the author. ©2021 The MITRE Corporation. ALL RIGHTS RESERVED. Approved for public release. Distribution unlimited 21-2206. Special Guest: Jennifer Strickland.

Greg Whitworth is the Director of LWC's application and backend services. He's also the Director of Standards and Web Platform here at Salesforce. Today, I am talking with him about his long history of working with web browsers. Specifically, we get into his experience with web standards committees, discuss how these standards come about and the benefits they can have for Salesforce and it's developers.   Greg has a very unique perspective and history with these topics. Tune in to hear it and lots of great background information on web standards.   Show Highlights:   What Greg's job looks like day to day. All about web browser committees and how to join one. How something becomes a web standard. How his input on standards benefits Salesforce, its developers, and its customers. Examples of standards that are helpful to Salesforce. How standards improve developers' skills and user experience. What the composite layer is. What polyfills are and how to work with them.   Links: Greg on LinkedIn: https://www.linkedin.com/in/gregwhitworth/ Greg on Twitter: https://twitter.com/gregwhitworth?lang=en Greg on Github: https://github.com/gregwhitworth Greg's blog: https://www.gwhitworth.com/posts/ Braces to Pixels: https://alistapart.com/article/braces-to-pixels/ Braces to Pixels video: https://vimeo.com/182528420 Customizable Control Presentation: https://noti.st/gregwhitworth The story of CSS Grid: https://alistapart.com/article/the-story-of-css-grid-from-its-creators/ Open UI: https://open-ui.org/

Wir begeben uns in die Welt der (Web-)Standards und Best-Practices die wenig genutzt werden, unterschiedlich implementiert sind oder sich nie etabliert haben. Das führt über Registrierungen und Authentifizierungsmethoden über Formularstyling zu Bildformaten und Videoplayer-Usability. Nebenbei zeigen wir euch, wie man per CSS den Cursor in Regenbogenfarben blinken lassen kann und zeigen, dass VSCode auch im Browser laufen kann. Ein bunter Strauß Themen (Allergikerfreundlich!).

In this episode, we get to speak with King of Web Standards, Jeffrey Zeldman. We discuss the current situation with...

We’re bringing Creativity Evangelist Denise Jacobs to our virtual workshop lineup this year! Here, she chats with Lou about how the current era of “doom-scrolling” means it’s more important than ever to unlock our creative minds and make meaningful connections. One challenge of working remotely is the loss of a sense of personal connection. Having tools that allow you to collaborate in a virtual environment and overcome isolation is a way to expand the collective creativity of the whole team. Her workshop (https://rosenfeldmedia.com/public-ux-workshops/master-creative-collaboration-and-communication/) is an opportunity to expand your knowledge base, skill set, and be inspired by creativity and collaboration using new and different tools to figure out how to add extra life to the work-from-home environment. Denise’s three day workshop this February (10 hours over 3 segments: February 2-4, 2021) will focus on leveraging collective brilliance, becoming confident in sharing your ideas, and learning to be an excellent listener. Next comes “the fun part” — how to use improvisation to make collaboration feel like a game, and not like work. Denise Recommends: ° Restore Yourself by Edy Greenblatt https://www.amazon.com/Restore-Yourself-Antidote-Professional-Exhaustion/dp/0981929915 ° Around the Writer’s Block by Rosanne Bane https://www.amazon.com/Around-Writers-Block-Science-Resistance-ebook/dp/B0085DP1LM About Denise Denise Jacobs is a Speaker + Author + Creativity Evangelist who speaks at conferences and consults with companies worldwide. As the Founder + CEO of The Creative Dose, keynote speaker, and trainer, she helps individuals in companies unleash their creativity through banishing their inner critic and hacking their creative brains. Denise’s keynotes and trainings give A Creative Dose™ – an injection of inspiration and immediately applicable tools to help people do their best work. Through working with Denise, people become engaged contributors, synergistic collaborators, and authentic leaders. Denise is the author of Banish Your Inner Critic, the premier handbook on silencing fears to unleash creativity. A web and tech industry veteran, Denise is also the author of The CSS Detective Guide and co-author of the Smashing Book #3 1/3 and Interact with Web Standards. She is also the founder of Rawk The Web and the Head Instigator of The Creativity (R)Evolution.

We're back to finish the inaugural episode of the Front End Nerdery Podcast with Jeffrey Zeldman. We talked about the web of yesterday, web standards, A Book Apart, what makes a good writer and conference speaker, and much more. Enjoy the second half of this very special two-part episode! Intro/Outro music graciously given permission to use called, "Settle In" by Homer Gaines. Transcripts can be found at https://toddl.dev/podcast/transcripts/zeldman2/ Shownotes https://zeldman.com - Jeffrey Zeldman Personal Site https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0321616952 - Designing with Web Standards 3rd Edition https://www.nytimes.com/2012/04/21/technology/hillman-curtis-a-pioneer-in-web-design-dies-at-51.html - Hillman Curtis https://www.zeldman.com/2019/12/01/bluebeanieday2019/ - Blue Beanie Day article https://aneventapart.com - An Event Apart conference https://abookapart.com - Books for designers and developers https://alistapart.com - A List Apart resources and articles https://en.wikipedia.org/wiki/A_List_Apart - A List Apart wiki --- Support this podcast: https://podcasters.spotify.com/pod/show/frontendnerdery/support

For the inaugural episode of the Front End Nerdery Podcast, I interviewed Jeffrey Zeldman. We talked about the web of yesterday, web standards, An Event Apart, A Book Apart, and much, much more that had to be done in two parts. Enjoy the first half of this very special two-part episode! Intro/Outro music graciously given permission to use called, "Settle In" by Homer Gaines. Transcripts can be found at https://toddl.dev/podcast/transcripts/zeldman1/ Shownotes https://zeldman.com - Jeffrey Zeldman Personal Site https://www.amazon.com/Designing-Web-Standards-Jeffrey-Zeldman/dp/0321616952 - Designing with Web Standards 3rd Edition https://www.nytimes.com/2012/04/21/technology/hillman-curtis-a-pioneer-in-web-design-dies-at-51.html - Hillman Curtis https://www.zeldman.com/2019/12/01/bluebeanieday2019/ - Blue Beanie Day article https://aneventapart.com - An Event Apart conference https://abookapart.com - Books for designers and developers https://alistapart.com - A List Apart resources and articles https://en.wikipedia.org/wiki/A_List_Apart - A List Apart wiki --- Support this podcast: https://podcasters.spotify.com/pod/show/frontendnerdery/support

(April 3, 2019)   Rick Viscomi and Jen Simmons (CSS Working Group, Mozilla) discuss the process of CSS standardization and the evolution of how developers style the web. For more info about everything discussed in this video, check out the original video→ https://goo.gle/3dZ4rps

(January 2, 2019) Rick and Nektarios (Chrome) talk about making the web more accessible for people with disabilities. Learn about the importance of accessibility and how you can make use of the latest web standards and tools to help make the web more accessible. WCAG → https://goo.gle/3evCLbX  WCAG 2.1 → https://goo.gle/36xFb75  Udacity webinar → https://goo.gle/2X9F7Ya  Accessibility guides → https://goo.gle/3eqkHQl  Accessibility in product design → https://goo.gle/2XBuBaR  Designing for accessibility → https://goo.gle/3d6rbUk

Александра Шинкевич, руководитель отдела фронтенд-разработки в LOVATA, и Никита Дубко, frontend-разработчик в минском офисе Яндекса, вновь в гостях у Андрея Смирнова из Frontend Weekend. Хочешь поддержать Frontend Weekend, переходи на http://frontendweekend.ml ;)Видеоверсия будет опубликована позже. 01:23 Впечатления от прошедших Web Standards Days в Москве и React Amsterdam 06:11 Зачем ребята помогали готовиться Андрею к его докладу и был ли раньше такой опыт? 14:13 Сколько раз уместно выступать с одним и тем же докладом? 26:49 Зачем бывшим русскоязычным конференциям тренд на англоязычность? 31:43 Каково Никите работается в Яндексе? 37:47 Задумывались ли ребята о переезде из Минска? 42:33 Разбор доклада Андрея про то, почему не надо становиться руководителем 59:45 Советы от Никиты и Саши Ссылки по теме: 1) Запись обсуждаемого доклада Андрея – https://youtu.be/r4txCvuHFPc?t=25646 2) Сольный выпуск с Сашей – https://soundcloud.com/frontend-weekend/fw-40 3) Сольный выпуск с Никитой – https://soundcloud.com/frontend-weekend/fw-75 4) Frontend Weekend Patreon – https://patreon.com/frontendweekend

Legendary computer scientist, web standards pioneer, and indie-web proponent Tantek Çelik is Jeffrey Zeldman's guest. The secret history of standards in our web browsers. How web standards moved from academic ideas that sometimes couldn't even be implemented to the foundation of our modern web. The rift between standards-oriented, CSS-and-accessibility-loving web developers and those who rely on powerful and sophisticated toolchains: can it be bridged? The Flash years and today. Indieweb tools and the independent web community: what it's about and how to get started. Readers versus social readers. Taking back privacy and the ownership of our content. Links for this episode:Tantek Çelik (@t) | TwitterTantek ÇelikTantek Çelik - Wikiwand5by5 | The Big Web ShowIndieWebMicro.blogMicrosub - IndieWebreader - IndieWebBrought to you by: Blockstack (The Blockstack ecosystem is hard at work and we'd love to have you, learn more and get started at blockstack.org/bigwebshow). Robinhood (Robinhood is giving you FREE stock like Apple, Ford, or Sprint to help you build your portfolio. Sign up at bigwebshow.robinhood.com).

Since Visual Studio Code burst onto the code editor scene, the steady improvements have made a number of web-related development tasks easier to handle. In this episode, we speak with web standards contributor and PM on the Visual Studio Code Kenneth Auchenberg (@auchenberg) on a wide range of topics. From VS Code's beginnings and current open source model, to Kenneth's recent experiments with Chrome headless in VS Code via browser-preview extension, this is an episode not to miss. Visit the website for This Week in Web, resources & more: https://thewebplatformpodcast.com/183-visual-studio-code Follow The Web Platform podcast on Twitter for regular updates @TheWebPlatform.

The world of web standards can be complicated and confusing, Jory Burson joins us to help make things clearer! We discuss the different standards organisations, why standards are important and why it's good for developers to get involved. Visit the website for This Week in Web, resources & more: https://thewebplatformpodcast.com/158-a-developers-guide-into-the-world-of-web-standards   Follow The Web Platform podcast on Twitter for regular updates @TheWebPlatform.

Brian Kardell (@briankardell) chats with us on Web Development and how it has evolved over the years.  We discuss the beginnings of HTML, Web standards bodies, the inception of The Extensible Web Manifesto, Chapters.io, and more. Resources Brians recent presentation on Chapters.io & Web Standards - https://www.youtube.com/watch?v=rwWEQPc5GRE Web Incubator Group - https://www.w3.org/community/wicg/ Chapters.io - http://chapters.io/ SGML > HTML > XML https://www.youtube.com/playlist?list=PLzH6n4zXuckqTQBIEuBTyjsO-Ef7562_Z Brians Blog - https://briankardell.wordpress.com/

Jeffrey Zeldman's Big Web Show guest is front-end designer Maya Benari (@mayabenari), a leading contributor to the U.S. Web Design Standards. Recently launched, and deservedly much lauded, the U.S. Web Design Standards consist of open source UI components plus a visual style guide, and are designed to create consistency and beautiful user experiences across U.S. federal government websites. Accessibility, semantics, and mobile-first responsive web design are baked in, right out of the box. Maya and Jeffrey discuss the genesis of the project, the teams behind the scenes, and why improving people's lives is sexier than building sandwich rating apps. Links for this episode:U.S. Web Design StandardsIntroducing the U.S. Web Design StandardsMaya Benari's WebsiteMaya Benari: Front End Designer18F Guides18FMaya Benari on GitHubGetting Started with U.S. Web Design StandardsBourbonBrought to you by Braintree (To learn more, and for your first $50,000 in transactions fee-free, go to BraintreePayments.com/BigWebShow).

Scott Jehl and Jeffrey Zeldman discuss the picture element: a container for multiple images. Making the emerging W3C standard picture element work in today's browsers. Polyfills and progressive enhancement. Responsible responsive design. Shim versus polyfill; srcset versus picture; the prefix wars. Balancing company projects and open source, community projects. Picturefill is a responsive images polyfill approach that web designers and developers can use today. Scott Jehl is a web designer and developer who works with the bright folks at Filament Group, where he creates websites and applications for a range of clients (including the 2012 responsive design of the Boston Globe). He is an active contributor to the open source community, frequently releasing ideas and projects on Github; a jQuery team member (most recently leading the development of the jQuery Mobile project); and the co-author of Designing With Progressive Enhancement (New Riders: 2010)

This episode was recorded 22 May 2013 live and in person at Adobe's offices in Fremont in Seattle. You can download the m4a file or subscribe in iTunes. (Or subscribe to the podcast feed.) John Nack is Principal Product Manager, Adobe Digital Video. He has a blog (definitely worth reading, especially if you use Photoshop) and is @jnack on Twitter. This episode is sponsored by Microsoft Azure Mobile Services. One of the cooler features recently added is the ability to create custom APIs. Originally you were limited to standard operations on your database tables — but now you can design any API you want. This allows you to create a full REST/JSON API that's tailored to your app, that works as efficiently as possible. (And it's all in JavaScript. Mobile Services runs Node.js. Write your apps in your favorite text editor on your Mac.) Things we mention, in order of appearance (pretty much): Adobe LiveMotion Photoshop John's Blog Kurt Vonnegut Granfalloons despair.com Cocoa 64-bit Carbon 64-bit Unfrozen Cave Man Olive Garden South Bend, Indiana Tiramisu St. Sebastian Breadsticks Monkeys 2005 Movable Type DeBabelizer GifBuilder Anarchie 1984 Mac 2001 Algonquin Hotel Apple II PCjr ASCII Art Clip Art Googly Eyes Bill Atkinson MacPaint Rorschach Test Apple II GS Great Books Quadra 840AV Quadra Ad Director SuperCard Søren Kierkegaard Immanuel Kant Notre Dame Football Windows NT HTML New York City 1998 Flash Macromedia Illustrator Navy ROTC San Francisco GoLive NetNewsWire After Effects Thomas Knoll Camera Raw Photoshop Touch Germany Philistinism Perfectionism Volkswagen Carbon-dating Web Standards SVG CSS Gus Mueller Acorn Neven Mrgan Khoi Vinh Croatia Portland JDI Healing Brush Buck Rogers Creative Cloud Facebook Smugmug WWDC Jetta Ketchup Death-march Comic Book Guy John Gruber “If you see a stylus, they blew it.” Microsoft Surface Metro UI Rahm Emmanuel: “You never want a serious crisis to go to waste.” The Mythical Man-Month Content-Aware Fill Shawshank InDesign Adobe Magazine Nike PageMaker Postscript SLR Lightroom Black & Decker Dr. Evil Loren Brichter Instagram Kickstarter NGO Tumblr Acquisition Troy Gaul Blurb The Onion: Report: 98 Percent Of U.S. Commuters Favor Public Transportation For Others Data T-1000 Syria MacApp Resource Manager John Knoll Industrial Light & Magic QuickTime OpenDoc Corba OLE SnapSeed Mac System 6 Apple events AppleScript Audio Bus 1992 “The only time you should start worrying about a soldier is when they stop bitchin'” Alan Kay: “The Mac is the first computer good enough to be criticized.” TapBots Tweetbot 2 Android Kai's Power Tools Kai Krause Fremont RUN DMC Porsche Boxster Flavawagon Google Glass Robert Scoble

In the last couple of years a deluge of new web technologies have appeared, allowing for the creation of ever richer and more immersive web applications. The FT is one of the pioneers in the use of newly minted HTML5 technologies to build web apps that are virtually indistinguishable from native apps. But using these technologies is far from easy. I'll cover some of the compelling reasons for choosing HTML5 and investing in the web platform, with a focus on offline technologies that enable web apps to run without a network connection. The examples will feature real-life code from our FT and the Economist applications, so you know that the techniques here are applicable to large, complex problems.

This week, Brian LeRoux comes on the show to talk about PhoneGap and the state of web apps. We talk device API's, technology deprecation, the need for better tools and the importance of having a beer fridge in your office.

Jeffrey Zeldman and Dan Benjamin discuss the state of the web, the evolution of Web Standards, the recent Boston AEA conference, and more. Sponsored by Webtrends and MailChimp.