<?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" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Juliarandonsavaris on Medium]]></title>
        <description><![CDATA[Stories by Juliarandonsavaris on Medium]]></description>
        <link>https://medium.com/@juliasavaris?source=rss-4450bfdb1d83------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*Yg6UN_kZiV5-b4Fe</url>
            <title>Stories by Juliarandonsavaris on Medium</title>
            <link>https://medium.com/@juliasavaris?source=rss-4450bfdb1d83------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:01:35 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@juliasavaris/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Acessibilidade e WCAG 2.2: É tarefa do designer ou do desenvolvedor?]]></title>
            <link>https://medium.com/@juliasavaris/acessibilidade-e-wcag-2-2-%C3%A9-tarefa-do-designer-ou-do-desenvolvedor-d0f69613f65d?source=rss-4450bfdb1d83------2</link>
            <guid isPermaLink="false">https://medium.com/p/d0f69613f65d</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[wcag]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Juliarandonsavaris]]></dc:creator>
            <pubDate>Wed, 04 Nov 2026 14:58:22 GMT</pubDate>
            <atom:updated>2026-11-04T14:58:22.609Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oWJg5AdIUUoJLKAmE3BZdA.png" /></figure><p><strong>Desvendando quais diretrizes e critérios de sucesso da WCAG 2.2 são responsabilidade do UX/UI designer</strong></p><p>As Diretrizes de Acessibilidade para Conteúdo Web ou WCAG foram<br>desenvolvidas pelo W3C ou World Wide Web Consortium, uma organização<br>internacional sem fins lucrativos fundada em 1994 por Tim Berners-Lee (inventor da World Wide Web), a fim de promover uma arquitetura consistente e capaz de acomodar o ritmo acelerado de progresso nos padrões da web para a criação de sites, navegadores e dispositivos.</p><p>As Diretrizes de Acessibilidade para Conteúdo Web (WCAG) estão atualmente na <a href="https://www.w3c.br/traducoes/wcag/wcag22-pt-BR/"><strong>versão 2.2</strong></a>, lançada em novembro de 2024, sendo que a <a href="https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/">versão 3 já está em desenvolvimento</a>, porém, a previsão é que leve ainda alguns anos para ser concluída e substituir efetivamente a versão 2.</p><p>A WCAG funciona como um <strong>compilado de diretrizes</strong> que não necessariamente faz distinção do domínio (se visual, funcional ou programático). Apesar de ter materiais com <a href="https://www.w3.org/WAI/tips/designing/">dicas de aplicação de acessibilidade para designers</a> (<em>inclusive recomendo muito o acesso para quem está começando a estudar sobre!</em>), para quem busca se aprofundar no assunto, é imprescindível ler todas as diretrizes e compreender <strong>o que está ao seu alcance direto</strong>, o que é preciso<strong> colaborar com o time de desenvolvimento</strong> e o que <strong>só pode ser executado pelos programadores</strong> (mas que podemos educar o time sobre e alinhar os requerimentos).</p><p>Mas antes de identificarmos as diretrizes pertinentes, caso você seja novo(a) ao universo da WCAG, aqui vão alguns conceitos importantes:</p><h4><strong><em>Princípios:</em></strong></h4><blockquote><em>Todos os critérios e diretrizes da WCAG estão classificados dentro de um dos 4 princípios estabelecidos, são eles:<br></em><strong><em>1. Perceptível: </em></strong><em>estabelece que as informações e os componentes da interface devem ser apresentados de forma que possam ser percebidos pelos usuários;<br></em><strong><em>2. Operável: </em></strong><em>determina que os componentes da interface e a navegação sejam passíveis de operação;<br></em><strong><em>3. Compreensível: </em></strong><em>estipula que as informações e operações da interface devem ser de fácil entendimento;<br></em><strong><em>4. Robusto:</em></strong><em> afirma que o conteúdo deve apresentar robustez suficiente para ser interpretado por qualquer software que facilita a interação do usuário final com o conteúdo, incluindo tecnologias assistivas.</em></blockquote><h4><strong><em>Nível de conformidade:</em></strong></h4><blockquote><em>Classificados em A, AA ou AAA. <br></em><strong><em>Nível A: </em></strong><em>corresponde ao mais básico, sendo considerado essencial para, uma vez que a não conformidade acarreta sérios problemas de acessibilidade que podem impedir pessoas com deficiência de utilizar o conteúdo. <br></em><strong><em>Nível AA:</em></strong><em> contempla uma maior diversidade de contextos de uso e é considerado o nível </em><strong><em>mais recomendado</em></strong><em> pela maioria dos especialistas na área. <br></em><strong><em>Nível AAA</em></strong><em> :reune os padrões mais rigorosos de acessibilidade, os quais, embora possam não ser aplicáveis ou realistas em todos os cenários, constituem um objetivo a ser visado para atingir a excelência em acessibilidade digital.</em><br><strong>*Vale lembrar que as diretrizes de cada níveis são cumulativas, ou seja, o nível AA são diretrizes nível A + as exclusivas do AA.</strong></blockquote><p>Agora sim, podemos destrinchar quais critérios são de competência dos product e UX/UI designers.</p><p>Vale lembrar que essa classificação foi feita <strong>pessoalmente por mim</strong> e com base nos seguintes parâmetros: <br>1. Foram <strong>excluídos todos os critérios que preveem conhecimento de desenvolvimento ou uso de programação</strong>;<br>2. Foram <strong>excluídos</strong> todos os critérios que se relacionam com <strong>conteúdo de áudio, vídeo e animações mais complexas</strong> (visto que estes não são possíveis de serem atingidos em um protótipo de média ou alta fidelidade em plataformas de prototipação como o Figma);<br>3. Critérios que dependem de algum recurso externo, como por exemplo, o<br>aumento do tamanho da tipografia de corpo de texto, foram contemplados <strong>pois influenciam em decisões de layout</strong> e devem ser consideradas durante o processo de design;<br>4. Critérios que abrangem o campo do UX Writing, tal qual a escrita de<br>textos alternativos para imagens foram incluídos.</p><h3>1. PERCEPTÍVEL</h3><iframe src="https://flo.uri.sh/visualisation/30643836/embed" width="700" height="575" frameborder="0" scrolling="no"><a href="https://medium.com/media/cb2b9b5fae22866b3bec116308f88557/href">https://medium.com/media/cb2b9b5fae22866b3bec116308f88557/href</a></iframe><h3>2. OPERÁVEL</h3><iframe src="https://flo.uri.sh/visualisation/30644330/embed" width="700" height="575" frameborder="0" scrolling="no"><a href="https://medium.com/media/58e5d1c087fcb4b2eceac957c802108e/href">https://medium.com/media/58e5d1c087fcb4b2eceac957c802108e/href</a></iframe><h3>3. COMPREENSÍVEL</h3><iframe src="https://flo.uri.sh/visualisation/30644412/embed" width="700" height="575" frameborder="0" scrolling="no"><a href="https://medium.com/media/b251eb939a9877ec3676f72dce242a59/href">https://medium.com/media/b251eb939a9877ec3676f72dce242a59/href</a></iframe><p>E aí, gostou de saber mais a fundo as diretrizes que os product/UX/UI designers tem conexão direta e poder de atuação?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d0f69613f65d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[UX, Craft and Pottery: a reflection]]></title>
            <link>https://medium.com/@juliasavaris/ux-craft-and-pottery-a-reflection-7aee86537d50?source=rss-4450bfdb1d83------2</link>
            <guid isPermaLink="false">https://medium.com/p/7aee86537d50</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[pottery]]></category>
            <dc:creator><![CDATA[Juliarandonsavaris]]></dc:creator>
            <pubDate>Tue, 29 Sep 2026 18:46:45 GMT</pubDate>
            <atom:updated>2026-09-29T18:46:45.819Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ChjOuVK5GDT-9TAzTPxJjw.png" /></figure><p>I’ve been hearing and reading a lot about the craft of UX and UI design lately, mainly because of the way AI is changing everything about the tech industry and how things are built. So, I started to think about craft and how I see it in my daily life. I’ve always been into DIY and crafty things, but my main hobby (that I can understand the value of craft better) is <strong>pottery</strong>.<br> <br>So, I’ve been an amateur potter for over three years now. I have started taking classes in 2023 for hand-building techniques (opening, plaques, pinch pots, coils, etc.). A year later, I’ve switched my classes over to learning how to make pieces on the potter’s wheel (<em>you may have the movie Ghost as a reference for how it looks like, or maybe you’ve seen a funny TikTok video of someone getting a piece ruined when it flies off the wheel unexpectedly</em>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IOKNscX-fHLSTbQihcxzYg.jpeg" /><figcaption><strong>For reference, here&#39;s a lump of clay on the wheel before I started modeling it</strong></figcaption></figure><p>Anyway, the main thing about ceramics is that it has a really strict process and phases you <strong>cannot change or skip</strong>. Basically, you have the following steps: you model your piece, you let it dry completely, you fire it in a specialized kiln one time, you glaze it, and you fire it again. Of course, there are exceptions, but 99% of the time this is the standard. Plus, if you do something wrong, the whole piece may explode during firing (<em>OK, it’s rare, but the chances are never zero</em>).<br> <br> When you compare it to the design process, they could not be more different. The double diamond, the design thinking, lean UX, and almost any other methodology of design you name will probably have in common one thing: being <strong>iterative</strong>. You can go back, change, improve, iterate, test, rebuild, test again, cut parts, add parts, basically turn it inside out if needed.</p><p>To sum it up, the main difference is that a digital product <strong>is never truly “done” or definitive</strong>. It can always be changed or improved (<em>thank you, digital space, for allowing that!</em>). On the contrary, even though you can recycle a piece of pottery before firing it (<em>you just rehydrate the clay</em>), you can no longer (or very limitedly) alter it once it comes out of the final firing (<em>and it is also </em><strong><em>not recyclable</em></strong><em> once it gets fired</em>).</p><p>But the thing is, this is the<strong> perspective of the designer/artist</strong> in the creation of the artifact. When we think about the <strong>user’s perspective</strong>, they can behave quite similarly.</p><h4>While both digital systems and pottery pieces can be decorative, mostly, final products are mainly utilitarian, useful tools. For the user, the digital product is in fact “final”, as he has no power to change what has been developed and coded, as well as the owner of a ceramic bowl cannot change its shape without breaking it into pieces.</h4><p>Even though they are in their final form for the end user, <strong>nothing is stopping them from using it in a new way</strong>. The WhatsApp designers can’t stop you from using a chat with yourself to take notes or do a grocery shop list. A pottery artist can’t stop you from using a mug as a pencil holder or a plant pot. The creativity here lies in finding new functions without changing the shape or the core, as it is out of limits for the user. It is the kind of creativity of imagination and repurposing, rather than a strategic, building-block sort of creativity.</p><p>I guess the conclusion is that the craft process is exclusive to the designer and artist in both cases, but that is not exactly the core of the product.</p><h4>An ugly pottery mug is still functional, as well as an ugly or generic system can still work. But the excellence of craft can go further than the aesthetic, it is how well thought and made the thing was. We can argue that a mass-produced mug is as functional as a handmade one, as well as a AI-generated website can be as functional as a human-designed one. But that feeling, the experience of using the product, this is where the craft shines.</h4><p>I think that’s why we think so much about craft in UX/UI now. The craft has been separated from the building process because of new tools, such as AI (now responsible for automating the construction), and the craft has now occupied the role of “<strong>the soul of the product</strong>”. A machine will not, and cannot, produce a soul to a project. And as we get even more flooded with AI-generated websites, apps, and everything else, I hope the art of craft will shine brighter, as the light in the end of the tunnel for why designers matter, and why <strong>a well-made human work will always be worth it.</strong></p><p><em>If you&#39;ve read this far, thank you for your time. I hope you enjoyed my text.</em></p><p><em>100% Human-made (with love) from Brazil</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7aee86537d50" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>