<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Web on (jw) Joe Whitsitt</title>
    <link>https://joe.whitsitt.org/tags/web/</link>
    <description>Recent content in Web on (jw) Joe Whitsitt</description>
    <image>
      <title>(jw) Joe Whitsitt</title>
      <url>https://joe.whitsitt.org/static/images/adrien-olichon--aOsCcTJXWY-unsplash.jpg</url>
      <link>https://joe.whitsitt.org/static/images/adrien-olichon--aOsCcTJXWY-unsplash.jpg</link>
    </image>
    <generator>Hugo -- 0.146.0</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Dec 2019 01:00:00 +0000</lastBuildDate>
    <atom:link href="https://joe.whitsitt.org/tags/web/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A case against social media timeline widgets</title>
      <link>https://joe.whitsitt.org/social-embeds/</link>
      <pubDate>Sat, 07 Dec 2019 01:00:00 +0000</pubDate>
      <guid>https://joe.whitsitt.org/social-embeds/</guid>
      <description>&lt;p&gt;We get it all the time at my work. &amp;ldquo;Can I put my Facebook timeline on my website?&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Absolutely not. Here is why.&lt;/p&gt;
&lt;h2 id=&#34;they-are-generally-inaccessible&#34;&gt;They are generally inaccessible&lt;/h2&gt;
&lt;p&gt;At work, we strive maintain websites that are WCAG 2.0 compliant. Most of these timeline widgets lack the neccessary accomodations to make them accessible to all.&lt;/p&gt;
&lt;h2 id=&#34;they-dont-blend-in-with-your-websites-look-and-feel&#34;&gt;They don&amp;rsquo;t blend in with your website&amp;rsquo;s look and feel&lt;/h2&gt;
&lt;p&gt;They are usually difficult to design around and stick out like a sore thumb unless your site uses the same color scheme.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
