Summary: We have finished our accessibility work and are nearly done with our localization/internationalisation work! PyPI is accessible and standards-compliant, and users will soon be able to use the site in Brazilian Portugese, Japanese, and (soon) other languages as well.
Accessibility:
Thank you to @nlhkabu – our GitHub milestone has 83 closed issues & PRs – for fixing Warehouse to comply with WCAG and other guidelines. We are standards-compliant and plan to continue regularly checking with community members to learn more ways to improve.
Localisation:
We are nearly done with the technical work here! Volunteers can now use Weblate’s platform to translate parts of the PyPI interface, and soon we will deploy support for Brazilian Portugese, our first language with 100% coverage. Here’s a screenshot of what users will get to see soon, once we finish a small amount of deployment and policy work:
Japanese will be next as volunteers have also fully translated Warehouse’s UI into Japanese! Thanks to all our translators, especially Rafael Fontenelle who has done a ton of Brazilian Portugese translation!
(A full translation means that all the strings that Warehouse produces for the user – buttons, menus, standard labels, etc. – are available in multiple languages. This doesn’t mean that the Project Descriptions/READMEs of individual projects will be available in multiple languages.)
Since our last update: we chose and integrated with a localization framework (pyramid.i18n and pybabel) in our codebase, chose and integrated with a translations platform (Weblate), replaced our English strings with translatable ones, added a language switcher UI in our page footer, and reached out to our community for translations. According to Weblate’s statistics, we have 738 source strings (most of which we had to convert from hardcoded). See the milestone on GitHub for more – thanks to @woodruffw and @nlhkabu for leading this work. We anticipate finishing that last bit of policy and deployment work, and thus this milestone, within a week or two.
You can help:
- If you read/write a language that’s not English, go ahead and get started translating! Heads-up @pradyunsg and @encukou!
- Help us review some pull requests from newer contributors: on template rendering, and developer documentation.
We’re looking forward to continuing to ship components of our project as we progress. Once the translation work goes live on PyPI we’ll be publicizing it in a lot of places (you’ll be seeing one or two emails to pypi-announce in the next several weeks, about the security, accessibility, AND internationalization work). And, as always, you can read our notes at our wiki page.
With this update we’re bringing our Open Technology Fund-supported work to a close, and progress on this feature shifts into volunteer mode. The contract project has taken a bit longer than we expected but we’re so happy to have made PyPI more secure, accessible, and usable for everyone. Thanks again to the OTF for making this work possible! And thanks to Will, Nicole, @EWDurbin, @dustin, @dstufft, @yeraydiazdiaz, and everyone else who contributed by coding, designing, testing, asking and answering questions, reporting bugs, translating, spreading the word, documenting, and just using the service.