<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Wcag on Scholion</title><link>https://scholion.thluiz.com/tags/wcag/</link><description>Recent content in Wcag on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Mon, 16 Nov 2026 15:09:12 +0000</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/wcag/index.xml" rel="self" type="application/rss+xml"/><item><title>How we stopped making excuses and started improving Basecamp’s accessibility</title><link>https://scholion.thluiz.com/notes/how-we-stopped-making-excuses-and-started-improving-basecamp/</link><pubDate>Sun, 05 Jul 2020 14:11:28 +0000</pubDate><guid>https://scholion.thluiz.com/notes/how-we-stopped-making-excuses-and-started-improving-basecamp/</guid><description>Basecamp made web accessibility a priority in 2017 by folding it into QA, learning WCAG, and treating accessibility issues as bugs. The work gained traction through ongoing testing and team buy-in.</description></item></channel></rss>