{"id":3415,"date":"2017-02-19T14:33:19","date_gmt":"2017-02-19T13:33:19","guid":{"rendered":"https:\/\/en.florianbrinkmann.de\/?p=3415"},"modified":"2020-02-09T10:59:56","modified_gmt":"2020-02-09T09:59:56","slug":"wordpress-weekly-recap-7-polyglots-plans-for-the-community-summit-and-more","status":"publish","type":"post","link":"https:\/\/florianbrinkmann.com\/en\/wordpress-weekly-recap-7-polyglots-plans-for-the-community-summit-and-more-3415\/","title":{"rendered":"WordPress weekly recap #7: Polyglots plans for the community summit and more"},"content":{"rendered":"\n

Before WordCamp Europe, in Paris, there is the community summit on June 13 and 14. The polyglots team already thought about aspects they can work on inside the team and with the other make teams.<\/p>\n\n\n\n\n\n\n\n

Accessibilitz<\/h2>\n\n\n\n

Gutenberg editor and accessibility<\/h3>\n\n\n\n

The content editor is one of the most important parts of WordPress, so of course, it has to be accessible. Like Joe Dolson writes in his post \u00bbRevising the WordPress Editor: Gutenberg and Accessibility\u00ab<\/a>, the new editor is going to be a big chance and risk at the same time from an accessibility point of view. A big change to provide a powerful editing experience to all users, and a big risk that this editing experience is not accessible, so there has to be a second-class experience for users with disabilities.<\/p>\n\n\n\n

So it is important that accessibility is part of the development. You can find more information about that in Joe\u2019s post.<\/p>\n\n\n\n

Misc<\/h3>\n\n\n\n