<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Accessibility on App Coding</title>
    <link>https://appcoding.com/tags/accessibility/</link>
    <description>Recent content in Accessibility on App Coding</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://appcoding.com/tags/accessibility/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Mobile Accessibility Is the Case Developers Keep Ignoring</title>
      <link>https://appcoding.com/2026/03/25/mobile-accessibility-is-the-case-developers-keep-ignoring/</link>
      <pubDate>Wed, 25 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://appcoding.com/2026/03/25/mobile-accessibility-is-the-case-developers-keep-ignoring/</guid>
      <description>&lt;p&gt;The accessibility argument is made with sufficient frequency in developer conferences and engineering blog posts that it has acquired the character of something everyone agrees with and nobody acts on. Apps ship with missing accessibility labels, unlabeled buttons, broken VoiceOver navigation, and dynamic type support that was added for text elements but forgotten for layout constraints. The gap between the accessibility investment that development teams describe as important and the accessibility state of their shipped applications is among the widest in software development.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
