<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Cancel Button &#8211; Fountn</title>
	<atom:link href="https://fountn.design/resource-tags/cancel-button/feed/" rel="self" type="application/rss+xml" />
	<link>https://fountn.design</link>
	<description>Curated design resources. No clutter. Just flow.</description>
	<lastBuildDate>Wed, 21 May 2025 20:13:25 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9</generator>

<image>
	<url>https://fountn.design/wp-content/uploads/2024/03/cropped-Default-150x150.png</url>
	<title>Cancel Button &#8211; Fountn</title>
	<link>https://fountn.design</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Basic best practices for buttons</title>
		<link>https://fountn.design/resource/basic-best-practices-for-buttons/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 23 Sep 2024 09:53:49 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=4157</guid>

					<description><![CDATA[Buttons are a fundamental element of web design, yet they are often overlooked or mishandled. Caroline Jarrett outlines seven basic button best practices that every designer should follow. Although buttons may seem like a small design element, getting them right is essential for creating intuitive, user-friendly digital experiences. By following these seven best practices, designers [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Where to put buttons on forms</title>
		<link>https://fountn.design/resource/where-to-put-buttons-on-forms/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 23 Sep 2024 09:52:38 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=4156</guid>

					<description><![CDATA[Button placement on forms is a crucial aspect of user experience that is often overlooked or prioritized based on aesthetics alone. However, the strategic positioning of buttons can make or break a form and, ultimately, the user&#8217;s overall experience. Adam Silver delves into the best practices for button placement, drawing insights from research and expert [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Cancel vs Close: Design to Distinguish the Difference</title>
		<link>https://fountn.design/resource/cancel-vs-close-design-to-distinguish-the-difference/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 23 Sep 2024 09:51:12 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=4154</guid>

					<description><![CDATA[Distinguishing between the &#8220;cancel&#8221; and &#8220;close&#8221; actions is crucial to avoid losing users&#8217; work. The ambiguous &#8220;X&#8221; icon often represents both actions, leading to confusion and frustration when users inadvertently lose their progress. Designers must be aware of the multiple meanings of the &#8220;X&#8221; icon and take steps to disambiguate between &#8220;close&#8221; and &#8220;cancel&#8221; actions, [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Should “cancel” be a button or a link?</title>
		<link>https://fountn.design/resource/should-cancel-be-a-button-or-a-link/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 23 Sep 2024 09:49:57 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=4152</guid>

					<description><![CDATA[Plainly and straightforwardly, Karim Maassen argues that the &#8220;cancel&#8221; option in web applications should be presented as a link rather than a button. The key reasoning is that cancelling an action is akin to navigating back to a previous state, rather than performing a new action. Karim Maassen explains that links are typically used for [&#8230;]]]></description>
		
		
		
			</item>
		<item>
		<title>Why “Cancel” should be a link, and not a button</title>
		<link>https://fountn.design/resource/why-cancel-should-be-a-link-and-not-a-button/</link>
		
		<dc:creator><![CDATA[Ozan Öztaskiran]]></dc:creator>
		<pubDate>Mon, 23 Sep 2024 09:48:45 +0000</pubDate>
				<guid isPermaLink="false">https://backup.fountn.design/?post_type=resource&#038;p=4150</guid>

					<description><![CDATA[Karim Maassen delves into the ongoing debate surrounding using buttons versus links for the &#8220;cancel&#8221; functionality in user interfaces. It argues that when users are presented with a &#8220;cancel&#8221; option, this should be a link rather than a button. The rationale is that canceling an action is not a data manipulation but navigation between different [&#8230;]]]></description>
		
		
		
			</item>
	</channel>
</rss>
