Write more takeaways

[jooyoungseo]

Following reviewers' feedback, we may want to include some more detailed takeaways of our paper in the Discussion section for the ASSETS community. For example:

1. Accessibility action research (our role as accessibility activists beyond conceptual or technical level).

2. Opportunities and challenges of improving accessibility within the open-source ecosystem, and its implication that can be applied to other open-source projects.

   • Opportunities: openness/transparency and direct end-user feedback in the dev cycle and iteration. @jooyoungseo was not employed by Microsoft, but could play an insider role and was able to closely work with the product engineers, including @meganrogge.

   • Challenges: The democratic nature could threaten the fundamental accessibility if not enough people express their needs. Since the users' feedback and bug report are critical in open-source ecosystem, the project could unintentionally neglect under-represented group's voice. Sometimes, due to the small number of users' feedback, criticality of accessibility features are under-estimated. Communication channels or methods themselves could become another accessibility hurdle (e.g., not all people are familiar with GitHub issue reporting and the process may be daunting to some end-users who may otherwise be able to provide constructive feedback).

3. Recommendation: Open-source team's empathy for the importance of accessibility is critical. Listen carefully to any small number of feedback from under-represented groups. If possible, build a rapport with the community and identify someone who can co-design the iterative accessibility improvement.

[jooyoungseo]

@meganrogge Please feel free to brainstorm more ideas in this thread.

[meganrogge]

A section on why it's critical to prioritize accessibility in an open source project:

• it is extended (forked) into many other apps, so good or bad practices/support are amplified/multiplied
• since anyone and everyone can view the code, and it inherently inspires or informs developers who inspect it, an open source project has a responsibility to advertise good, accessibility minded code

[meganrogge]

@jooyoungseo I have added the basics from this except for "Accessibility action research (our role as accessibility activists beyond conceptual or technical level)."