<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title></title>
    <description/>
    <link>https://speakerdeck.com/chandracarney</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/chandracarney.rss"/>
    <lastBuildDate>2015-05-04 12:30:50 -0400</lastBuildDate>
    <item>
      <title>How to Develop with Accessibility in Mind</title>
      <description>What does accessibility entail as it is related to the web? Most developers don't consider that someone with any variety of impairments may use their applications and don't think about what this experience may be like for someone who has an impairment. The current trend is to push access-driven design to the end of feature building, but we will explore why this needs to be a top priority.
</description>
      <media:content url="https://files.speakerdeck.com/presentations/e8ee36f94ae94cd983de764ca80e30ce/preview_slide_0.jpg?4743154" type="image/jpeg" medium="image"/>
      <content:encoded>What does accessibility entail as it is related to the web? Most developers don't consider that someone with any variety of impairments may use their applications and don't think about what this experience may be like for someone who has an impairment. The current trend is to push access-driven design to the end of feature building, but we will explore why this needs to be a top priority.
</content:encoded>
      <pubDate>Tue, 21 Apr 2015 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/chandracarney/how-to-develop-with-accessibility-in-mind</link>
      <guid>https://speakerdeck.com/chandracarney/how-to-develop-with-accessibility-in-mind</guid>
    </item>
  </channel>
</rss>
