{"version":"1.0","type":"rich","provider_name":"Acast","provider_url":"https://acast.com","height":250,"width":700,"html":"<iframe src=\"https://embed.acast.com/$/653769c09c713d0012562f78/6a2f1360685069f99fb81742?\" frameBorder=\"0\" width=\"700\" height=\"250\"></iframe>","title":"MOSE Short 35 - A Cool Feature to You, a Life-changing Functionality for Someone Else","thumbnail_width":200,"thumbnail_height":200,"thumbnail_url":"https://open-images.acast.com/shows/653769c09c713d0012562f78/1781470498360-eb03d48e-bb5d-42e1-9ef8-f1e26967eec5.jpeg?height=200","description":"<p>You need to make sure that you treat improvements in your project the right way. Some improvements are features as they bring new functionality. However, when the new functionality makes existing functionality available for people with disabilities, then it's not a feature that got implemented, it's a critical bug that got fixed.</p><p><br></p><p>In this segment of the My Open Source Experience podcast Mike Gifford talks about the mindset shift in the Drupal community to start treating accessibility gaps as bugs and in cases as critical bugs.</p><p><br></p><p>Learn more about:</p><p>- GitHub's Readme newsletter</p><p>- Marking something as a bug doesn't give it a priority automatically</p><p>- You need like-minded people and leadership buy-in to move things forward in a focus area</p><p>- Dark mode, a sad story</p><p>- A fun feature, like adding motion on screens can make someone sick and should be easy to turn off</p><p>- The potential in new tech to improve accessibility</p><p><br></p><p>#opensource #community #collaboration #experience #podcast</p>","author_name":"Ildiko Vancsa"}