<?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 Ricardo Ferreira on Medium]]></title>
        <description><![CDATA[Stories by Ricardo Ferreira on Medium]]></description>
        <link>https://medium.com/@r.sousa21?source=rss-8c17076b8057------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*NyfZCI-I0MeihEO3Ub-uBA.jpeg</url>
            <title>Stories by Ricardo Ferreira on Medium</title>
            <link>https://medium.com/@r.sousa21?source=rss-8c17076b8057------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 01:38:06 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@r.sousa21/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[Product League @ GSAS24 Global Software Architecture Summit]]></title>
            <link>https://blog.product-league.com/product-league-gsas24-global-software-architecture-summit-05e468520b8d?source=rss-8c17076b8057------2</link>
            <guid isPermaLink="false">https://medium.com/p/05e468520b8d</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[outsystems]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ricardo Ferreira]]></dc:creator>
            <pubDate>Tue, 26 Nov 2024 09:18:11 GMT</pubDate>
            <atom:updated>2024-11-26T09:23:23.989Z</atom:updated>
            <content:encoded><![CDATA[<p>By <a href="https://medium.com/@diogoolival1">Diogo Olival</a>, <a href="https://medium.com/@ivogoncalves">Ivo Gonçalves</a> and <a href="https://medium.com/@r.sousa21">Ricardo Ferreira</a></p><figure><img alt="A picture of the 3 Product League members at GSAS24" src="https://cdn-images-1.medium.com/max/1024/1*UQt2SmXTzS9fZTFpcCZTGQ.png" /></figure><p>The Global Software Architecture Summit (GSAS) is an annual event held in Barcelona, Spain, attracting software architects, engineers, and technology leaders from around the world. GSAS serves as a pivotal platform for advancing the discipline of software architecture, enabling participants to gain insights into the latest industry trends, tools, and methodologies. The event combines learning, networking, and collaboration to enhance the skills and knowledge of professionals involved in designing and maintaining modern software systems.</p><p>The 2024 edition of GSAS, held from October 14–16, spotlighted several emerging trends and best practices in software architecture. This year’s discussions focused on topics such as the impact of <strong>AI on software architecture</strong>, <strong>domain-driven design (DDD)</strong>, <strong>micro-frontends</strong>, <strong>serverless architectures</strong>, and <strong>green software</strong>. Experts from around the globe shared real-world case studies and explored how modern systems can be optimized for performance, scalability, and environmental sustainability.</p><p>At this year’s summit <strong>Product League </strong>was represented by Ricardo Ferreira, Ivo Gonçalves, and Diogo Olival, marking the company’s second consecutive year at GSAS.</p><p>GSAS 2024 once again positioned itself as a leading event in the world of software architecture, bringing together thought leaders to inspire and educate professionals shaping the future of software development and architecture.</p><h3>Hero’s Highlights</h3><p>From the 13 talks presented this year, our heroes’ favorites were:</p><h4><strong>Ivo Gonçalves: Complexity &amp; Modularity: The Yin and Yang of Socio-Technical Design by Sonya Natanzon</strong></h4><p>I received great feedback about GSAS from colleagues who attended last year’s conference. Since I’m relatively new to Software Architecture, I had some reservations about participating — I was worried I might struggle to understand the concepts and leave without getting much value. However, I was pleasantly surprised. Not only did I manage to follow most of the sessions, but I also found myself relating to many of the topics discussed.</p><p>One major takeaway from the conference was that software architecture is fundamentally about making trade-offs — a point emphasized across multiple sessions.</p><p>A standout session for me was “Complexity &amp; Modularity: The Yin and Yang of Socio-Technical Design,” presented by Sonya Natanzon (Vladik Khononov co-created the session but could not attend). The talk explored modularity and complexity in software, addressing both the technical aspects and their impact on organizational social structures.</p><p>This session resonated with me deeply because it addressed issues I have encountered firsthand — multiple times, in fact. Now, however, I feel better equipped to handle these challenges.</p><p>Understanding the relationship between social and technical design principles is an effective way of architecting better systems.</p><figure><img alt="A picture of Sonya Natanzon presenting at the GSAS24 stage" src="https://cdn-images-1.medium.com/max/1024/1*LGzIMSd3JCMQhQ-V6nHRWg.png" /></figure><h4>Ricardo Ferreira: What Makes Software Architecture So Intractable by Neil Ford</h4><p>My expectations were high going into the conference, and we all know how important first impressions are, right? Well, Neal Ford was the perfect choice to kick things off. His opening talk, “What Makes Software Architecture So Intractable?” was not just engaging, it set the tone for the rest of the event.</p><p>He highlighted that an architect’s main job is to perform trade-off analysis, summing it up in his “First Law of Architecture”: “Everything in software architecture is a trade-off. If you haven’t found a trade-off yet, you probably just haven’t spotted it.”.</p><p>A great example he shared that really resonated with me was about abstraction. While it can be incredibly useful, it introduces volatility because it often needs ongoing adjustments to fit evolving needs, which can lead to instability. You really need to weigh the trade-off. Abstraction might not always be the best choice, and it depends heavily on the specific situation and what you’re trying to achieve.</p><p>I also really liked how Ford made it clear that architecture isn’t about one-off decisions, it’s an ongoing, evolving process. It’s all about weighing those trade-offs every step of the way.</p><p>As a final remark and a clear message to the industry, Ford warned about the upcoming “AI tsunami” in the development process, advising caution as AI becomes more integrated into our workflows.</p><p>It was a pleasure to learn from such a respected professional, and his insights made the talk a perfect opener for the conference.</p><figure><img alt="A picture of Neil Ford presenting at the GSAS24 stage" src="https://cdn-images-1.medium.com/max/870/1*GJniPBMmYRjjH328KBTJQQ.png" /></figure><h4><strong>Diogo Olival: AI as a Software Architect Assistant by Avraham Poupko</strong></h4><p>It was my first year at the event and the expectations were high mainly because the subject matter was about Software Architecture coexisting with Artificial Intelligence.</p><p>The event was particularly inspiring, highlighting a diverse range of perspectives on software design, scalability, and the evolving role of architects in a rapidly changing tech landscape. As someone deeply invested in the intersection of leadership and technical development, I found the conference to be an enriching experience, sparking thought-provoking discussions and actionable takeaways.</p><figure><img alt="A picture of Avraham Poupko presenting at the GSAS24 stage" src="https://cdn-images-1.medium.com/max/1024/1*WnMOR7ziNtlGlatwhjeyiQ.png" /></figure><p>One of the standout moments of the conference for me was Avraham Poupko’s presentation on AI as a Software Architecture Assistant. For me, Poupko was one of the best communicators that passed through the GSAS stage. He delivered a brilliant presentation where he explored the typical question of “Will AI replace Humans?” in what regards to Software Architecture. His approach was both innovative and pragmatic, highlighting the boundaries between AI and a Software Architect, and addressing the how Software Architects could take advantage of artificial intelligence to facilitate their day-to-day tasks, designing, building, and scaling software systems.</p><figure><img alt="A picture of Avraham Poupko presenting at the GSAS24 stage" src="https://cdn-images-1.medium.com/max/1024/1*xEfdGZd5eVM7JVityZwQzw.png" /></figure><p>Poupko’s insights bridged the gap between theoretical AI applications and their practical integration into real-world systems, emphasizing the need for architects to adapt their methodologies in the face of AI’s transformative potential. His compelling arguments and real-world examples underscored the importance of leveraging AI to enhance decision-making, optimize system efficiency, and anticipate future challenges in software development.</p><h3><strong>Wrapping Up: GSAS 2024</strong></h3><p>GSAS 2024 was a fantastic experience, filled with insights, inspiration, and great conversations. From learning about the trade-offs in architecture to exploring AI’s role in our work, the summit left us with plenty to think about and apply.</p><p>We’re excited to take these lessons forward and can’t wait to see what GSAS 2025 has in store. Until next time!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=05e468520b8d" width="1" height="1" alt=""><hr><p><a href="https://blog.product-league.com/product-league-gsas24-global-software-architecture-summit-05e468520b8d">Product League @ GSAS24 Global Software Architecture Summit</a> was originally published in <a href="https://blog.product-league.com/">ProductLeague</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Demystifying Web Accessibility]]></title>
            <link>https://blog.product-league.com/demystifying-web-accessibility-f9a322289138?source=rss-8c17076b8057------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9a322289138</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[outsystems]]></category>
            <category><![CDATA[wcag]]></category>
            <dc:creator><![CDATA[Ricardo Ferreira]]></dc:creator>
            <pubDate>Tue, 19 Mar 2024 10:24:55 GMT</pubDate>
            <atom:updated>2024-04-11T09:32:25.973Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Demystifying Web Accessibility: </strong>A Gateway to Inclusive Design with OutSystems — Part 1</h3><p>Welcome to the inaugural article of this series aimed at demystifying web accessibility! It’s important to understand from the start that <strong>accessibility is a transformative force</strong>, leveling the digital playing field and benefiting both individuals and businesses. Technology isn’t just a convenience, it’s a lifeline, especially for those navigating the digital realm with unique challenges.</p><p>However, here’s the secret: crafting accessible content isn’t only about inclusion, it’s about creating better websites overall! Businesses embracing accessibility not only extend their reach but also enhance user experiences for everyone, making the digital landscape more vibrant, user-friendly, and inclusive.</p><p>As we embark on this journey, it’s important to acknowledge the diverse spectrum of disabilities that individuals may face. Some of these disabilities are more obvious than others, but it’s important to at least be aware of them all. Therefore, <strong>this first article will provide an overview of various types of disabilities</strong>, allowing readers to explore the ones they find most interesting or wish to learn more about. <strong>So feel free to jump directly to the disabilities that spark your curiosity or those you’re less familiar with.</strong> Let’s dive in!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SbVp3fbl_zaY1Qstw6Fojw.png" /></figure><h3><strong>Understanding disabilities and the importance of Web Accessibility</strong></h3><p>In today’s digitally interconnected world, <strong>the importance of technology in our daily lives is undeniable</strong>. Simple tasks like shopping, banking, working, or even entertainment, are easily accomplished with just a few clicks on a device. However, let’s take a moment to consider a different perspective by imagining embarking on the journey to fulfill these tasks without the aid of digital technology. Picture yourself getting ready, planning outings, and overcoming various obstacles that may seem minor to some. Now envision undertaking these same tasks with additional challenges — being visually impaired, having mobility issues, or facing temporary disabilities. The struggles become more than just daunting, they transform into overwhelming obstacles in an already challenging world.</p><p><strong>Digital technology</strong>, for many, is a superhero squad that<strong> levels the playing field</strong>. It transforms ‘cannot’ into ‘can’ and offers the hope of a smoother, more manageable life. Digital tools like <strong>screen readers, voice commands, or specialized applications</strong> unlock a world of possibilities, making tasks that seemed unattainable, suddenly feasible. However, amid this remarkable transformation, we encounter a harsh reality: inaccessible websites and apps that alienate those who need these digital superheroes the most. <strong>When technology isn’t inclusive, it leaves behind millions</strong> who rely on these digital lifelines. It deprives them of experiences and opportunities that others take for granted. It’s about time we changed this narrative. Ensuring accessibility isn’t just about convenience, it’s about rewriting the story of inclusion and empowerment. It’s about giving these heroes the tools they need to conquer their daily quests.</p><h3><strong>Types of disabilities</strong></h3><p>There are a lot of different types of disabilities, but not all of them affect the ability a person has to navigate in the digital realm. A great example are individuals without legs, they can still use a computer without a problem. However, for those with disabilities that do impact their digital interaction, assistive technologies play a crucial role, much like a wheelchair aids mobility for those unable to walk.</p><p>Similarly, in the digital world, assistive technologies play their role. For instance, a blind individual relies on a screen reader, while a deaf person benefits from captions or transcripts. <strong>However, it’s crucial to note that while these technologies are invaluable, they don’t completely compensate for the disability they address.</strong> Just as a wheelchair can’t ascend stairs without a ramp, a screen reader’s effectiveness is limited if web applications are constrained by design elements that limit its functionality.</p><p>One exemplary figure illustrating the power of assistive technologies is the renowned physicist<strong> Stephen Hawking</strong>. Despite living with ALS, a degenerative neuromuscular disease that gradually deteriorated his voluntary muscle control, Hawking made groundbreaking contributions to the field of science and cosmology. <strong>His ability to communicate and engage with the world was only possible thanks to the assistive technologies</strong> <strong>he utilized. </strong>Modern technology serves as a transformative force, unlocking doors to a world of possibilities for those facing physical limitations.</p><figure><img alt="Stephen Hawking using assistive technologies" src="https://cdn-images-1.medium.com/max/1024/1*8pPYbuh6UTtZlOcq6WQMgA.jpeg" /><figcaption>Stephen Hawking using his assistive device</figcaption></figure><p><strong>Vision disabilities</strong></p><p>Among the most recognized disabilities requiring special attention in web design, visual impairments stand out, presenting unique challenges for web accessibility. Let’s take a closer look at three main categories: <strong>blindness, low vision, and color blindness</strong> — and discover the tools that make their online experience smoother.</p><p><strong>1. Blindness:</strong></p><p>Individuals with complete blindness rely on <strong>screen readers</strong> that convert on-screen content into speech or <strong>braille output</strong>. For websites and applications to be accessible, they must be compatible with screen readers, which often means having descriptive <strong>alt text</strong> for images and well-<strong>structured content</strong> that screen readers can interpret accurately. Consideration of <strong>keyboard navigation</strong> is also vital, as blind users heavily depend on keyboard commands to navigate websites.</p><figure><img alt="Braille output — Photo by Elizabeth Woolner" src="https://cdn-images-1.medium.com/max/1024/1*n8_XeXeDXboofI9GRhJhhw.jpeg" /><figcaption>Braille output — Photo by <a href="https://unsplash.com/pt-br/@elizabeth_woolner?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">Elizabeth Woolner</a></figcaption></figure><p><strong>Design considerations:</strong></p><p>Textual Representation of Content:</p><ul><li>Present all content in text or provide text equivalents like alt text for images to aid screen reader users.</li></ul><p>Avoid Sole Reliance on Visual Attributes:</p><ul><li>Information should not solely rely on visual characteristics like color, spatial layout, or text formatting as screen readers may not translate such details.</li></ul><p>Keyboard Accessibility:</p><ul><li>Ensure all functionalities can be accessed exclusively via the keyboard, considering the nuances in keyboard behaviors when screen readers are enabled.</li><li>Keyboard navigation serves as a primary mode for blind users, offering more effective means to navigate than a mouse.</li></ul><p>Structured Markup:</p><ul><li>Utilize proper markup with structured elements such as headings, landmarks, and semantic tags like lists and tables.</li><li>Screen reader users navigate and comprehend content through that structured markup.</li></ul><p>Custom Controls and Accessibility Attributes:</p><ul><li>Custom controls should possess appropriate labels, roles, values, and responsive changes to enhance screen reader comprehension.</li><li>Adding ARIA (Accessible Rich Internet Applications) attributes supplies necessary information about custom controls that might lack inherent semantic elements.</li></ul><p>Immediate Feedback for Screen Reader Users:</p><ul><li>Provide immediate feedback to screen reader users after any action, ensuring acknowledgment of successful or unsuccessful operations.</li></ul><p>Video Accessibility:</p><ul><li>Videos lacking comprehensive audio content should include audio descriptions explaining visual elements to aid blind users in understanding the visual aspects.</li></ul><p>Mobile Device Accessibility:</p><ul><li>Ensure all features on mobile web pages are accessible via click actions as screen readers don’t support custom swipe actions.</li></ul><p><strong>2. Low Vision:</strong></p><p>For individuals with low vision, navigating digital content often involves utilizing <strong>screen magnifiers</strong>, opting for<strong> larger text</strong>, or seeking out <strong>high-contrast interfaces</strong>. Crafting interfaces with <strong>resizable text</strong>, <strong>clear typography</strong>, and <strong>adjustable color contrast </strong>can significantly improve their experience. <strong>Avoiding</strong> elements that cause <strong>glare or flickering</strong>, and offering <strong>customizable display settings</strong>, are additional measures that greatly enhance accessibility for this user group.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LP7XxgEDur0A5wn1lG6Cjw.jpeg" /><figcaption>Low vision representation — Photo by <a href="https://unsplash.com/pt-br/@dtravisphd?utm_content=creditCopyText&amp;utm_medium=referral&amp;utm_source=unsplash">David Travis</a></figcaption></figure><p><strong>Design considerations:</strong></p><p>Enable Pinch-to-Zoom:</p><ul><li>Avoid disabling the pinch-to-zoom feature (&lt;meta name=”viewport” content=”user-scalable=no”&gt;) as it restricts low vision users from using screen magnifiers to properly view content on web pages.</li></ul><p>Contrast for Text Accessibility:</p><ul><li>Low contrast can impede readability for users with low vision, making it essential to maintain sufficient contrast between text and background elements.</li></ul><p>Visible Focus and Hover States:</p><ul><li>Provide visible :focus and :hover states for links, buttons, and controls to assist low vision users using keyboards or mice.</li><li>Enhanced CSS states aid users in tracking keyboard/mouse focus, facilitating navigation and interaction on the web page.</li></ul><p>Clear Interface Distinction:</p><ul><li>Create a distinct visual contrast between content (such as text) and interactive controls (like buttons and links) in the user interface.</li><li>A clear separation between content and controls assists users with low contrast vision, ensuring elements are easily distinguishable and actionable on the web page.</li></ul><p><strong>3. Color Blindness:</strong></p><p>Color blindness affects how individuals perceive colors, making it challenging to differentiate certain tones. Designing with consideration for <strong>color contrast and using additional cues beyond color</strong>, such as labels, patterns, or icons, helps users distinguish between elements without relying solely on color.</p><p>Color blindness alters how individuals interpret colors, making it difficult to distinguish between certain tones. By designing with careful attention to <strong>color contrast </strong>and incorporating additional cues like <strong>labels</strong>, <strong>patterns</strong>, or <strong>icons</strong>, users can differentiate between elements without solely relying on color.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5Fa2BoiBVKuEirjqEvHMTQ.jpeg" /><figcaption>Red-Green Color Blind Test</figcaption></figure><p><strong>Design consideration:</strong></p><p>Color-Independent Information:</p><ul><li>Ensure all information can be comprehended without reliance on color distinction, particularly considering the challenge colorblind individuals face with reds and greens. It’s essential to supplement color with text or symbols to ensure universal comprehension.</li></ul><p><strong>4. Deafness</strong></p><p>While much of online content remains accessible for individuals with auditory disabilities due to the prevalence of visual or text-based formats, the rising popularity of multimedia like video and audio requires a greater focus on inclusivity. To address this, two primary tools are commonly employed: <strong>transcripts</strong> and <strong>captions</strong>.</p><figure><img alt="A deaf man staring at the camera" src="https://cdn-images-1.medium.com/max/1024/0*35_F9j2n2ySdZ0XO" /><figcaption>Deaf person — Photo by <a href="https://unsplash.com/@onesmallsquare?utm_source=medium&amp;utm_medium=referral">Sharon Waldron</a></figcaption></figure><p><strong>Transcripts</strong> are crucial for accessibility in pre-recorded audio content. They encapsulate dialogues, narrations, and significant sound cues, allowing individuals to consume content at their own pace. For those who read slower or are deaf-blind, transcripts provide essential access. In video content, <strong>synchronized captions</strong> become indispensable, transcribing spoken words and aligning with specific moments.</p><p><strong>Design considerations:</strong></p><p>Captioned Videos:</p><ul><li>All videos should include captions to aid individuals who are deaf.</li><li>Captions convey critical dialogues, narration, and significant sounds, ensuring inclusive access to audio-visual content.</li></ul><p>Transcripts for Audio-Only Content:</p><ul><li>Provide transcripts for all audio-only content to cover dialogue, narration, music cues, and sound effects.</li><li>Transcripts serve as an essential alternative format for comprehensively conveying audio information, benefiting individuals with auditory disabilities.</li></ul><p>Sign Language Interpretation:</p><ul><li>Consider providing sign language interpretation for videos.</li><li>For individuals whose primary communication mode is sign language, this offers an alternative and preferred means of accessing content compared to captions and transcripts.</li></ul><p><strong>5. Motor disabilities</strong></p><p>Motor disabilities are a wide spectrum, from temporary challenges due to injury to severe limitations in limb movement. Individuals with such disabilities <strong>use various assistive technologies, combining software and hardware</strong> to facilitate their interaction with digital interfaces. These adaptations vary greatly and serve to the unique needs of each individual.</p><figure><img alt="Photo of several accessibility devices" src="https://cdn-images-1.medium.com/max/1024/0*WjdbqtGhQxIY5MF3" /><figcaption>Assistive technologies — Photo by <a href="https://unsplash.com/@elizabeth_woolner?utm_source=medium&amp;utm_medium=referral">Elizabeth Woolner</a></figcaption></figure><p><strong>Design considerations:</strong></p><p>Keyboard Accessibility:</p><ul><li>Ensure all website functions can be accessed solely via the keyboard.</li><li>People with motor disabilities may lack fine motor skills required for mouse navigation, so enabling keyboard-only usage is crucial for inclusivity.</li></ul><p>Visible Focus and Hover States:</p><ul><li>Implement visible :focus and :hover states for links, buttons, and controls.</li><li>Sighted keyboard users rely on these states to navigate web content effectively, enhancing these states aids in navigation and interaction, aligning with accessibility guidelines.</li></ul><p>Session Time-Out Alerts:</p><ul><li>Warn users before session expiration and offer options to extend.</li><li>Individuals with motor disabilities may need extra time for interaction; providing sufficient warning and extension options accommodates their pace and needs.</li></ul><p>Large Click Targets:</p><ul><li>Optimize click targets (links, buttons, controls) for larger size.</li><li>Users with tremors or motor difficulties benefit from larger click areas, enhancing their ability to accurately interact with web elements and mitigate accidental selections.</li></ul><p><strong>6. Speech Disabilities</strong></p><p>Speech disabilities involve <strong>difficulties</strong> in <strong>producing or organizing speech sounds</strong>, making articulation and fluency challenging. These disabilities can originate from various factors, including genetics, learning difficulties, hearing impairments, and medical conditions like autism spectrum disorder, traumatic brain injury, stroke, and certain cancers affecting the mouth or throat.</p><figure><img alt="Person using Augmentative and Alternative Communication device" src="https://cdn-images-1.medium.com/max/1024/1*_4Z5efLEknXLhwA0nPbytA.jpeg" /><figcaption>Augmentative and Alternative Communication</figcaption></figure><p><strong>Types of Speech Disabilities</strong></p><ul><li><strong>Stuttering:</strong> Involuntary repetitions, prolongations, or blocks in speech sounds.</li><li><strong>Cluttering:</strong> Rapid, inconsistent speech lacking proper rhythm and grammar.</li><li><strong>Apraxia:</strong> Difficulty coordinating muscles for speech, often requiring multiple attempts to articulate words.</li><li><strong>Dysarthria:</strong> Impaired speech due to brain damage, resulting in slurred or slow speech.</li><li><strong>Speech Sound Disorders:</strong> Challenges in producing specific speech sounds, categorized as articulation or phonemic disorders.</li><li><strong>Articulation Disorders:</strong> Difficulty in physically producing speech sounds, causing omissions, substitutions, or distortions.</li><li><strong>Phonemic Disorders:</strong> Difficulty distinguishing speech sounds, affecting word meaning.</li><li><strong>Non-vocal:</strong> Complete inability to produce a speaking voice.</li></ul><p><strong>Communication Options</strong></p><p>Augmentative and Alternative Communication (AAC) offers diverse means for individuals with speech disabilities to communicate beyond oral speech. It’s divided into two types:</p><ul><li><strong>Unaided AAC utilizes nonverbal communication</strong> like body language, facial expressions, gestures, and sign language.</li><li><strong>Aided AAC involves tools</strong>, either electronic or non-electronic, from communication boards and books to sophisticated electronic devices generating computer-based voices. These tools, categorized as low-tech or high-tech aids, assist in message storage and retrieval, based on electricity requirements.</li></ul><p><strong>Design considerations:</strong></p><p>Avoid Sole Reliance on Voice Input:</p><ul><li>Dependence on voice input (e.g., in mobile apps, custom widgets, games, etc.) creates barriers for individuals with speech disabilities.</li><li>Due to difficulties in producing voice sounds or using mouth muscles, providing alternative means of communication such as chats, forms, or email becomes essential.</li></ul><p><strong>7. Cognitive Disabilities</strong></p><p>Cognitive disabilities come in different forms, ranging from conditions present at birth to those acquired through injury, infection, or chemical imbalances. These disabilities vary widely, with each person’s experience being unique.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HuQu04SSOZB-hFuK" /><figcaption>Photo by <a href="https://unsplash.com/@jeshoots?utm_source=medium&amp;utm_medium=referral">JESHOOTS.COM</a></figcaption></figure><p><strong>Types of Cognitive Disabilities:</strong></p><ul><li><strong>Limited Comprehension:</strong> Individuals may struggle with understanding complex ideas, metaphors, or abstract language. While excelling in specific cognitive functions like memory, they might encounter challenges in social or emotional skills.</li><li><strong>Low Tolerance for Cognitive Overload:</strong> Some face frustration or stress in complex situations, needing simplicity. Too many choices overwhelm, freezing their decision-making abilities.</li><li><strong>Limited Problem-Solving Skills:</strong> Certain cognitive disabilities obstruct problem-solving abilities. Tasks requiring complex actions, like deciphering CAPTCHAs, represent significant challenges.</li><li><strong>Short-Term Memory Loss:</strong> Difficulty retaining new information causes users to forget steps in online processes, affecting tasks like purchasing or account setup.</li><li><strong>Attention Deficit:</strong> Individuals struggle to maintain focus, getting distracted easily, especially by online ads, leading to difficulty completing tasks.</li><li><strong>Difficulty Reading:</strong> Varied reading abilities exist, ranging from lower reading levels to complete inability to read. Illustrations or audio supplements assist those facing reading challenges.</li><li><strong>Difficulty Understanding Math:</strong> Math anxiety or an actual inability to process mathematical concepts due to cognitive limitations are common challenges faced by individuals with cognitive disabilities.</li></ul><p><strong>Design considerations:</strong></p><p>For Users with Lower Comprehension:</p><ul><li>Simplify the interface and content to enhance understanding.</li><li>Keep video and audio content concise.</li><li>Limit on-screen choices and incorporate help features.</li><li>Design for ease of use and conduct usability tests, including users with cognitive disabilities.</li></ul><p>For Users with Memory Loss:</p><ul><li>Retain information consistently across screens and within the navigation flow.</li><li>Integrate help features for easier navigation.</li><li>Maintain website predictability to aid users with memory loss, avoiding complex structures.</li><li>Fatiguing or complicated sites may disorient users.</li></ul><p>For Users with Distractibility:</p><ul><li>Minimize or remove distractions such as ads, carousels, intrusive audio, or video.</li><li>Excessive distractions can cause users to miss critical information, lose focus, or feel overwhelmed.</li></ul><p><strong>8. Reading disabilities</strong></p><p>Individuals with cognitive disabilities often face <strong>challenges with reading</strong>, ranging from difficulties reading below their age-level peers to an inability to read altogether. <strong>Providing</strong> aids such as <strong>illustrations or audio supplements</strong> can assist those struggling with reading comprehension.</p><p>Furthermore, dyslexia, a common reading disability, presents its own set of challenges. While individuals with dyslexia may have strong conceptual cognitive abilities, they struggle with visual text encoding, leading to difficulties in spelling and word recognition. Dyslexic readers often experience letters appearing to move, switch, or rearrange while reading, affecting their comprehension. <strong>Implementing alternative formats and considering text presentation</strong> can greatly improve accessibility for these users.</p><figure><img alt="Dyslexia representation with several examples" src="https://cdn-images-1.medium.com/max/1024/1*F4E_2haK-6cYj7PNhgiN_g.jpeg" /><figcaption>Dyslexia representation</figcaption></figure><p><strong>Design considerations:</strong></p><p>For Users with Difficulty Reading (e.g., dyslexia)</p><ul><li>Supplement text content with illustrations, videos, or audio alternatives.</li><li>Individuals facing difficulty in reading text benefit from information presented through images, audio, or video formats.</li><li>Opting for slightly lower contrast colors (e.g., dark grey against white/off-white) rather than the highest contrast (e.g., black on white) may facilitate easier text reading and reduce strain on the eyes.</li></ul><p><strong>9. Seizures</strong></p><p>Seizures are disruptions in brain electrical impulses, affecting information processing and voluntary muscle control. These episodes can lead to convulsions, posing risks of injury. They can result from various factors such as brain injury, dehydration, sleep deprivation, infections, fevers, drug influences, or exposure to <strong>flashing lights</strong> — a particular concern for web developers.</p><p>Photo-Epileptic Seizures involve flashing or strobe effects in videos or animations, triggering seizures in susceptible individuals. Web accessibility for seizure disorders emphasizes <strong>avoiding intense flashing lights</strong> in videos or animations to prevent potential seizures. <strong>Designers should refrain from content flashing more than three times per second.</strong></p><figure><img alt="Person layed on the floor, representation of a seizure episode" src="https://cdn-images-1.medium.com/max/630/1*q1g9cMnMWaSGy3v2LAm-SA.jpeg" /><figcaption>Seizures</figcaption></figure><p><strong>Design considerations:</strong></p><p>Flashing Light Sequences:</p><ul><li>Using flashing, blinking, or flickering content that occurs more than 3 times per second can trigger photo-epileptic seizures in susceptible users.</li></ul><h3><strong>Recap and our path forward</strong></h3><p>Whew! If you’ve made it this far, congratulations! You’ve navigated through a whirlwind tour of web accessibility! It’s now important to pause and reflect on the valuable insights gained thus far.</p><p><strong>Understanding the unique requirements of each disability is vital into laying the foundation for inclusive design. These considerations are not merely guidelines but a call to action</strong>, <strong>let’s all embed accessibility into the core of our development practices!</strong></p><p>But our journey doesn’t end here, it’s just the beginning! In the next article of our series, we’ll dive deeper into accessibility guidelines, laws, and debunking myths and misconceptions surrounding accessibility. So stay tuned and see you on Part II!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9a322289138" width="1" height="1" alt=""><hr><p><a href="https://blog.product-league.com/demystifying-web-accessibility-f9a322289138">Demystifying Web Accessibility</a> was originally published in <a href="https://blog.product-league.com/">ProductLeague</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resize an iFrame - A simple solution]]></title>
            <link>https://blog.product-league.com/resize-an-iframe-a-simple-solution-384f48511936?source=rss-8c17076b8057------2</link>
            <guid isPermaLink="false">https://medium.com/p/384f48511936</guid>
            <category><![CDATA[iframe]]></category>
            <category><![CDATA[iframeresizer]]></category>
            <category><![CDATA[responsive-design]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[outsystems]]></category>
            <dc:creator><![CDATA[Ricardo Ferreira]]></dc:creator>
            <pubDate>Fri, 21 Apr 2023 12:59:04 GMT</pubDate>
            <atom:updated>2023-04-21T16:57:29.495Z</atom:updated>
            <content:encoded><![CDATA[<h4>Using iFrameResizer library in OutSystems</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*LeBXlUDg62VBI8WYR7G6Qw.jpeg" /></figure><p>Have you ever been tasked with something that seemed simple at first, but turned out to be more complex than expected? In this article, I want to share a story about a recent project that involved embedding a cross-origin page within an iFrame, and the challenge of resizing the iFrame to fit its content. Read on to learn how we overcame this challenge using the iFrameResizer library in OutSystems.</p><figure><img alt="In the animated gif, a child is shown attempting to force a square peg into a round hole. Despite repeated attempts, the peg simply won’t fit. Eventually, the child gives up and opens a nearby box, tossing the peg inside. This serves as a humorous reminder that sometimes, it’s better to try a different approach rather than forcing something that simply won’t work." src="https://cdn-images-1.medium.com/max/144/1*KIe5fS9a_kTN66qJNcvCYQ.gif" /></figure><p><strong>The challenge:</strong></p><p>We needed to embed a cross-origin page within an iFrame. It would need to fit between the header and footer, adjusting automatically the height to its content. It would also need to be responsive, adapting both to screen resizes and changes within the nested page content height.</p><p><strong>The extra challenge:</strong></p><p>The same-origin policy is a critical security mechanism that restricts how a document or script loaded by one origin can interact with a resource from another origin. Since we had a nested page from a different origin, we would need to find a solution compliant with it.</p><p><strong>Note:</strong> You can read more about same-origin policy and the associated challenges here: <a href="https://developer.mozilla.org/en-US/docs/Web/Security/Same-origin_policy">MDN Web Docs — Same-origin policy</a></p><p><strong>The solution:</strong></p><p><a href="https://github.com/davidjbradshaw/iframe-resizer"><strong>i</strong></a><a href="https://github.com/davidjbradshaw/iframe-resizer"><strong>Frame Resizer</strong></a><strong> — </strong>This library enables the automatic resizing of the height and width of both same and cross-origin iFrames to fit their contained content. It provides a range of features to address the most common issues while using iFrames.</p><p>It will provide you a wide range of options, methods and events that will certainly make your life easier when dealing with iFrames. You can check them here:</p><p><strong>Parent Page API — </strong><a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/parent_page/options.md">Options</a>, <a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/parent_page/events.md">Events</a>, <a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/parent_page/methods.md">Methods</a></p><p><strong>Child Page API — </strong><a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/iframed_page/options.md">Options</a>, <a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/iframed_page/events.md">Events</a>, <a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/iframed_page/methods.md">Methods</a></p><p><strong>How we did it?</strong></p><p>1. We loaded a <a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/src/iframeResizer.contentWindow.js">script</a> in the page nested within the iFrame. In our case, since that page was provided by a third-party, we requested them to add it. Quoting the official documentation <em>“This file is designed to be a guest on someone else’s system, so has no dependencies and won’t do anything until it’s activated by a message from the containing page.”</em></p><p>2. We loaded a second <a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/src/iframeResizer.js">script</a> on the page hosting the iFrame. In the example below its possible to see the script being set as required in the screen that will contain the iFrame.</p><figure><img alt="Script being loaded into the page in Service Studio (OutSystems). It’s added as resource and then set as required script for that page." src="https://cdn-images-1.medium.com/max/550/1*rB_4k6o7PMZFT60XPI9EfA.png" /></figure><p>3. We added a class to the iFrame, this facilitated the element selection both on the CSS and the iFrameResizer initialization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/1*jB-pyPOeGUd2ls6bI2s4Ig.png" /></figure><p>4. We added the suggested CSS to the iFrame.</p><pre>.iframe-oracle-content {<br>   width: 1px;<br>   min-width: 100%;<br>}</pre><p>5. We initiated the iFrameResizer. For that we’ve used the iFrame’s wrapper block’s OnReady event. Here you’ll be able to define a few options, depending on your needs. (<a href="https://github.com/davidjbradshaw/iframe-resizer/blob/master/docs/parent_page/options.md">See options</a>)</p><p><strong>Important note: </strong>Don’t use the iFrame’s widget id as selector when initializing. Due to the way OutSystems manages the element’s ids, (i.e. they are generated, and therefore subject to change between compilations) it won’t work properly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nkJ7XNUFneXXcdQWzkp11g.png" /></figure><p>And that’s all it takes to get your iFrame working seamlessly — easy, right?</p><figure><img alt="Leonardo Di Caprio toast meme" src="https://cdn-images-1.medium.com/max/550/1*ogg1e_ktq6jIPWVDo3922w.jpeg" /></figure><p><strong>And how does iFrameResizer overcomes the cross-domain limitations?</strong></p><p>Using a technique called “postMessage”. This is a feature of modern web browsers that allows different windows or iFrames to communicate with each other, even if they are from different domains.</p><p>iFrameResizer uses postMessage to establish a communication channel between the parent window and the iFrame. When the iFrame’s content changes, it sends a message to the parent window with information about its new size. The parent window receives this message and updates the size of the iframe accordingly.</p><p>Since the communication is initiated by the iframe itself, rather than the parent window, it can bypass the cross-domain security restrictions. Cool, right?</p><p><strong>Conclusion</strong></p><p>Embedding a cross-origin page within an iFrame can be a challenging task, especially when it comes to resizing the iFrame to fit its content. However, with the iFrameResizer library, this challenge becomes much easier to overcome. This can save you significant time and effort, and enable you to focus on delivering great user experiences within your app. So if you’re struggling with resizing iFrames in OutSystems, give iFrameResizer a try and see how it can simplify your development process.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=384f48511936" width="1" height="1" alt=""><hr><p><a href="https://blog.product-league.com/resize-an-iframe-a-simple-solution-384f48511936">Resize an iFrame - A simple solution</a> was originally published in <a href="https://blog.product-league.com/">ProductLeague</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>