Accessibility/2016 sprint
 | This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
What
[edit]The Wikimedia foundation's Vision Statement reads:
Imagine a world in which every single human being can freely share in the sum of all knowledge. That's our commitment.
We often think of this in terms of languages, geographies and even socioeconomic status. But to truly deliver on this commitment we also need to make it possible for people of varying physical ability to share in the amazing work our community has undertaken. To advance this aspect of our vision, the foundation's iOS team is spending a dedicated block of time on improving the accessibility of the Wikipedia app for the visually impaired.
Who
[edit]Although the iOS team is dedicating a focused period to this effort, we are not alone! We've been working with Austin Seraphin, a blind iOS consultant and developer to ensure we are fixing the right things and informed by expert user opinion. See phabricator:T148435.
Most importantly we're also looking for help from...YOU
How you can participate
[edit]- On Thursday, November 3rd, watch our publicly streamed brown bag on the state of Wikipedia accessibility on web and iOS: https://www.youtube.com/watch?v=GsE0PpQkBcI
- Participate in person at the Philadelphia CocoaHeads Side Project Saturday event on October 29th
- If you are an iOS developer, we welcome code contributions! To get going check out our Github page here. And all our accessibility tasks are described on our Phabricator task board.
- If you are a web or Android developer, check out this task board for accessibility across the wikimedia projects
- If you use features like VoiceOver, Dynamic Type or other iOS accessibility features, sign up for our beta and help us test our work.
When
[edit]Events are all happening the week from Friday, October 28th through Friday November 4th. Please see the links above for specific times/venues. BUT, we welcome improvements, suggestions and code contributions in this area at any time!