<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Andrés Llinás' blog]]></title><description><![CDATA[Andrés Llinás' blog]]></description><link>https://blog.andresllinasr.com</link><generator>RSS for Node</generator><lastBuildDate>Tue, 14 Apr 2026 00:43:58 GMT</lastBuildDate><atom:link href="https://blog.andresllinasr.com/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Why Accessibility Matters: Making the Web Inclusive]]></title><description><![CDATA[Hey there! I am Andrés Llinás, a Colombian front-end developer. My area of expertise is creating front-end assets. From button style to scripting for mass web changes, or simply contributing so that more people may love the web as much as I do, I've ...]]></description><link>https://blog.andresllinasr.com/why-accessibility-matters-making-the-web-inclusive</link><guid isPermaLink="true">https://blog.andresllinasr.com/why-accessibility-matters-making-the-web-inclusive</guid><category><![CDATA[Accessibility]]></category><category><![CDATA[development]]></category><category><![CDATA[Web Development]]></category><category><![CDATA[Frontend Development]]></category><dc:creator><![CDATA[Andrés Llinás]]></dc:creator><pubDate>Sat, 25 May 2024 23:42:32 GMT</pubDate><enclosure url="https://cdn.hashnode.com/res/hashnode/image/upload/v1716688303294/0e02e411-49c5-4af1-bf83-e2d6e0ca9527.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Hey there! I am Andrés Llinás, a Colombian front-end developer. My area of expertise is creating front-end assets. From button style to scripting for mass web changes, or simply contributing so that more people may love the web as much as I do, I've been working as a developer at HubSpot for a couple years now, and they take accessibility as no joke on their web team.</p>
<p>I must admit that I previously knew little to nothing about accessibility issues, but it has drawn my attention. So now it is my turn to answer some of the questions I wish I had known when I first started with this chapter. I became fascinated by the new lessons I learned about how people interact with what I create.</p>
<h2 id="heading-what-does-accessibility-mean">What does accessibility mean?</h2>
<p>Accessibility is commonly disregarded in web design and development, despite the fact that it's just as crucial as building inclusive physical surroundings. Think about the ways we promote accessible sidewalks, braille signage, and ramps. Our virtual worlds need to be no different!</p>
<h2 id="heading-how-does-bad-accessibility-looks-like">How does bad accessibility looks like?</h2>
<p>Imagine receiving a book with pages missing or jumbled out of order—that's what bad accessibility online feels like. It's like piecing together a story that doesn't quite make sense, missing out on essential details, and feeling disconnected from the full experience others effortlessly enjoy. Imagine trying to follow a recipe without being able to read the ingredient labels because they're in tiny, blurry print. That's what bad accessibility feels like for many disabled users online. For people with disabilities, it's not just about annoyance; it's like being locked out of key data or services, just because the web wasn't built with everyone in mind.</p>
<h2 id="heading-so-whos-responsible-for-making-the-web-accessible">So, who's responsible for making the web accessible?</h2>
<p>Web accessibility is a team effort involving developers, designers, content creators, accessibility specialists, standards organizations, and even lawmakers. Developers and designers follow guidelines like WCAG, content creators make materials accessible, and specialists provide audits and training. Standards organizations set guidelines, and lawmakers enforce regulations. User feedback is crucial for making the web accessible to everyone.</p>
<iframe src="https://giphy.com/embed/0ozmBje9bTxfPlKO7m" width="480" height="480" class="giphy-embed"></iframe>

<h2 id="heading-now-should-you-make-your-website-accessible">Now, should you make your website accessible?</h2>
<p>Absolutely! Enhancing accessibility not only broadens your audience but also significantly improves the user experience, boosts your site's SEO, aids in legal compliance, and showcases your commitment to social responsibility. Prioritizing continuous accessibility enhancements is a win-win for both your users and your business, ensuring that everyone can access and interact with your digital presence seamlessly.</p>
<p>"Accessible" is a broad term because it covers various needs and technologies, ensuring everyone, including people with disabilities, can use your site. This includes tools like screen readers (e.g., JAWS, Talkback and NVDA), voice recognition software (e.g., Dragon NaturallySpeaking), and alternative input devices (e.g., eye-tracking systems).</p>
<h2 id="heading-are-you-developing-accessible-websites">Are you developing accessible websites?</h2>
<p>If this is your first time asking yourself this question, the answer is likely no. Developing accessible websites requires ongoing effort and attention to detail, from considering user testing to implementing features like alt text, color contrast, keyboard navigation, semantic HTML, accessible forms, responsive design, ARIA roles, and thorough testing.</p>
<h2 id="heading-some-resources">Some resources</h2>
<ul>
<li><p><a target="_blank" href="https://adrianroselli.com/2019/02/uncanny-a11y.html">Adrian Roselli Blog</a></p>
</li>
<li><p><a target="_blank" href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">WGAC 3 Draft</a></p>
</li>
</ul>
]]></content:encoded></item></channel></rss>