First, could Fedora Accessibility Working Group join meetings with the Fedora DEI Team? Second, what would a 12-18 month vision look like for accessibility improvements in Fedora to propose for a Council Objective?
First, the folks leading a new look at accessibility needs in Fedora are doing interesting work. It aligns with the goals of the Fedora DEI Team. It would be a win for us to team our efforts together and support each other in reaching project goals. Combining our meetings would bring a diverse group of people together to discuss common areas of interest.
Second, a Council Objective gives us a format to scope 12 to 18 months of work in the project. This could include an accessibility research review and dissemination of that research. An Objective would also help align Fedora contributors together on a common effort. We could propose this to the Council together with a logic model. The Objective would need to specify whether it would focus on Fedora Linux software accessibility, Fedora Community contributor accessibility, or both.
This ticket follows a discussion that @siddharthvipul1 and I were having in a check-in call.
This issue is opened as a place to hold the discussion about joining our meetings and proposing a Council Objective. We need to engage with both teams on this approach as it could impact our workflows and reduce duplicative work.
Here is a hypothetical roadmap:
Discussed in 2022-11-07 meeting (video).
We missed @ekidney for this discussion, but @sarah-thornton, @rikardgn, and I had a discussion about this concept, what an Objective could look like, and some places we could turn to inside Fedora as good starting places for possible output.
Some notes from our discussion are below:
to comment on this ticket.