<?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>Accessibility on The Dangling Pointer</title><link>https://aaron.blog/tags/accessibility/</link><description>Recent content in Accessibility on The Dangling Pointer</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 17 Apr 2014 16:52:10 +0000</lastBuildDate><atom:link href="https://aaron.blog/tags/accessibility/index.xml" rel="self" type="application/rss+xml"/><item><title>Stop Being Lazy with Accessibility</title><link>https://aaron.blog/stop-being-lazy-with-accessibility/</link><pubDate>Thu, 17 Apr 2014 16:52:10 +0000</pubDate><guid>https://aaron.blog/stop-being-lazy-with-accessibility/</guid><description>&lt;p&gt;I'm making  a pledge as a software developer to think of accessibility with every change I make.  My first step was to turn on iOS' VoiceOver and test everything I'm working on with it.  In the first five minutes of using it, I've discovered so many necessary improvements to make the app even useful for someone who has trouble seeing.  There are many more accessibility tools than VoiceOver (like Dynamic Type) that should also be on your list to try.  Baby steps.&lt;/p&gt;</description></item></channel></rss>