Conclusion and Additional Challenges Using a screen reader for the first time can be both exciting and frustrating. To contextualize the experience, ask yourself these questions: What were you most surprised by in your experience of using a screen reader? Can you imagine advantages to using a screen reader, as compared to using the device visually? Were there any assumptions you made before using a screen reader that are no longer valid? Thank you for participating in the session, or for reading this tutorial. We leave you with two further challenges in case you'd like to continue to test yourself. Challenge #1: Eyes-Free Assuming that you're not yourself print disabled, you were able to benefit from seeing all the elements on the screen while using Voiceover. In this exercise, you'll try to repeat the accessibility check, but without being able to see the screen. To do this exercise, turn on the Screen Curtain feature in Voiceover, which blanks out the screen. To do this, while Voiceover is activated, take three fingers and tap on the screen three times. Challenge #2: Bug Report Did you find something not-so-accessible while testing your app or website? Now it's time to do something about it. Try to file a bug report or otherwise share your experience with the development or accessibility team responsible for the app or website. To file the report, try these steps in order: Research the app or website to see if there is an accessibility submission form (relatively rare) or accessibility email address (slightly less rare) for the organization responsible for the app or website. Research the app or website to find an email address at which to file general bug reports. Do a search for the app or website on GitHub, where public development work is often done. If you find a repository for the app or website, file an issue on GitHub. Does the app or website have a customer service line or email? Try reaching out. Is the organization behind the app or website on social media? Try dropping them a line on Twitter or Instagram. Feel free to tag @psmyth01 and I'll likely retweet you. Trying to communicate accessibility issues to organizations is important, but often frustrating, work. If you're part of an organization with an app or website, how easy is it to file an accessibility issue with you?