# Workflow & Tools Published articles for Workflow & Tools. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Martech stack audit: How to optimize your marketing toolset DevFeed: [Martech stack audit: How to optimize your marketing toolset]() Original publisher: [Read original article]() Author: Webflow Team Published: 2026-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Webflow Blog]() Topics: [Optimization](), [Automation](), [Content Management System](), [Data Management](), [Search engine optimization (SEO)](), [Figma](), [webflow]() Tags: [analytics](), [audits](), [automation](), [content](), [cost](), [data](), [design](), [figma](), [how-to](), [inspiration](), [integration](), [learn](), [marketing](), [optimization](), [seo](), [software](), [tool](), [webflow](), [workflow](), [workflow-tools]() ### AI overview A practical guide to auditing a marketing technology stack, identifying inefficient or unnecessary tools, and finding opportunities to streamline workflows, improve collaboration, and increase return on investment. ### Source excerpt Learn when and how to conduct a martech stack audit that will identify opportunities to streamline operations, improve collaboration, and save resources. ## Good designers, bad websites: a proposal DevFeed: [Good designers, bad websites: a proposal]() Original publisher: [Read original article]() Author: by Alan Dalton Published: 2026-04-23T12:57:21Z Content type: opinion Language: en Sources: [A List Apart: The Full Feed]() Topics: [User interface design]() Tags: [accessibility](), [accessibility-community-user-experience-user-research-workflow-tools](), [community](), [design](), [usability](), [user-experience](), [user-research](), [workflow-tools]() ### AI overview An opinion article arguing that accessibility must be central to website design. It discusses how designs can exclude people with different sensory, cognitive, and mobility needs, and proposes using usability heuristics to help designers recognize accessibility issues. ### Source excerpt I want to discuss accessibility because it is the most important thing for making websites. Other A List Apart articles give you innovation and insight. This article will give you homework. These are just my personal views, but they're pretty good. I want to start off with a couple of statements, and you will agree: Designers are good people. I have never heard a designer say, "I don't care if somebody can't read this text", "Not my fault if somebody can't use this device", or "Who cares if this is confusing?" Some designs exclude people. You have seen people unable to read the text on a website or app that somebody designed. You've seen people unable to use a physical device that somebody has designed. You've seen people utterly bamboozled while trying to use a service that somebody designed. So what? The first question is, "Is this life-or-death stuff?" The answer is, "Yes." In my favorite essay, This Is All There Is, Aral Balkan makes the point that pretty much everything that we design can affect life events and death events. Aral gives the example of how even a straightforward bus timetable app can affect life and death events, if we design it badly: somebody might miss a life event, such as their daughter's fifth birthday party; or somebody might miss a death event, such as the chance to say goodbye to a dying grandmother. The next--and frustrating--question is, "Why do some designs still exclude people?" After all, we know that: not everybody can see perfectly; not everybody can hear perfectly; not everybody thinks the same way; and not everybody moves the same way. I think the answer is that there's too much to recall. Consider, if you will, the wide variety of topics that A List Apart articles cover. Designers are expected to remember all of that guidance, plus all of the accessibility guidance, plus so much more. It is too much. Recognizing accessibility issues while designing I'd like to point toward one possible solution, starting from Jakob Nielsen's 10 U ## Design Dialects: Breaking the Rules, Not the System DevFeed: [Design Dialects: Breaking the Rules, Not the System]() Original publisher: [Read original article]() Author: by Michel Ferreira Published: 2025-09-26T16:48:12Z Content type: article Language: en Sources: [A List Apart: The Full Feed]() Topics: [Web](), [systems]() Tags: [component](), [design](), [design-design-systems-web-strategy-workflow-tools](), [design-systems](), [systems](), [web](), [web-strategy](), [workflow-tools]() ### AI overview The article argues that design systems should function as living languages rather than rigid component libraries. It introduces design dialects: systematic adaptations that preserve core principles while allowing context-specific patterns, helping teams solve user problems without sacrificing the system's essential grammar. ### Source excerpt "Language is not merely a set of unrelated sounds, clauses, rules, and meanings; it is a totally coherent system bound to context and behavior." -- Kenneth L. Pike The web has accents. So should our design systems. Design Systems as Living Languages Design systems aren't component libraries--they're living languages. Tokens are phonemes, components are words, patterns are phrases, layouts are sentences. The conversations we build with users become the stories our products tell. But here's what we've forgotten: the more fluently a language is spoken, the more accents it can support without losing meaning. English in Scotland differs from English in Sydney, yet both are unmistakably English. The language adapts to context while preserving core meaning. This couldn't be more obvious to me, a Brazilian Portuguese speaker, who learned English with an American accent, and lives in Sydney. Our design systems must work the same way. Rigid adherence to visual rules creates brittle systems that break under contextual pressure. Fluent systems bend without breaking. Consistency becomes a prison The promise of design systems was simple: consistent components would accelerate development and unify experiences. But as systems matured and products grew more complex, that promise has become a prison. Teams file "exception" requests by the hundreds. Products launch with workarounds instead of system components. Designers spend more time defending consistency than solving user problems. Our design systems must learn to speak dialects. A design dialect is a systematic adaptation of a design system that maintains core principles while developing new patterns for specific contexts. Unlike one-off customizations or brand themes, dialects preserve the system's essential grammar while expanding its vocabulary to serve different users, environments, or constraints. When Perfect Consistency Fails At Booking.com, I learned this lesson the hard way. We A/B-tested everything--color, copy, button sh ## Opportunities for AI in Accessibility DevFeed: [Opportunities for AI in Accessibility]() Original publisher: [Read original article]() Author: by Aaron Gustafson Published: 2024-02-07T14:00:00Z Content type: opinion Language: en Sources: [A List Apart: The Full Feed]() Topics: [Accessibility](), [Artificial Intelligence](), [alt text](), [Computer vision](), [foundation-models]() Tags: [accessibility](), [accessibility-code-content-workflow-tools](), [ai](), [alt-text](), [code](), [computer-vision](), [content](), [foundation-models](), [microsoft](), [workflow-tools]() ### AI overview The article argues that, despite serious risks and limitations, AI could support accessibility when used thoughtfully and inclusively. It focuses on computer-vision systems for generating alt text, noting their difficulty understanding image context and distinguishing meaningful images from decorative ones. The author supports human-in-the-loop workflows in which AI provides an initial suggestion that people can review and improve. ### Source excerpt In reading Joe Dolson's recent piece on the intersection of AI and accessibility, I absolutely appreciated the skepticism that he has for AI in general as well as for the ways that many have been using it. In fact, I'm very skeptical of AI myself, despite my role at Microsoft as an accessibility innovation strategist who helps run the AI for Accessibility grant program. As with any tool, AI can be used in very constructive, inclusive, and accessible ways; and it can also be used in destructive, exclusive, and harmful ones. And there are a ton of uses somewhere in the mediocre middle as well. I'd like you to consider this a "yes... and" piece to complement Joe's post. I'm not trying to refute any of what he's saying but rather provide some visibility to projects and opportunities where AI can make meaningful differences for people with disabilities. To be clear, I'm not saying that there aren't real risks or pressing issues with AI that need to be addressed--there are, and we've needed to address them, like, yesterday--but I want to take a little time to talk about what's possible in hopes that we'll get there one day. Alternative text Joe's piece spends a lot of time talking about computer-vision models generating alternative text. He highlights a ton of valid issues with the current state of things. And while computer-vision models continue to improve in the quality and richness of detail in their descriptions, their results aren't great. As he rightly points out, the current state of image analysis is pretty poor--especially for certain image types--in large part because current AI systems examine images in isolation rather than within the contexts that they're in (which is a consequence of having separate "foundation" models for text analysis and image analysis). Today's models aren't trained to distinguish between images that are contextually relevant (that should probably have descriptions) and those that are purely decorative (which might not need a description) eit