<?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 Mari Galicer.</title>
    <link>/tags/accessibility/</link>
    <description>Recent content in accessibility on Mari Galicer.</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 01 Sep 2019 05:44:12 +0000</lastBuildDate><atom:link href="/tags/accessibility/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>A primer on web accessibility</title>
      <link>/posts/accessibility/</link>
      <pubDate>Sun, 01 Sep 2019 05:44:12 +0000</pubDate>
      
      <guid>/posts/accessibility/</guid>
      <description>How we made aclu.org more accessible Let&amp;rsquo;s be real: the state of accessibility on the web is abysmal. On the bright side, there is room for radical improvement.
One of the most important realizations I had when doing research on accessible web development was that you can&amp;rsquo;t just add some ARIA tags and alt text and call it a day. Rather, developing for accessibility means a working towards degrees of improvement for a diverse set of users, often involving difficult tradeoffs.</description>
    </item>
    
  </channel>
</rss>
