These are the weekly notes for the Accessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Team meeting that happens on Fridays. You can read the full transcript on our Slack channel and find the meeting’s agenda here.
Advancement status of Trac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets, Gutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ issues and team’s goals for WordPress 5.8
During the last but one meeting, the team agreed to have a general check on how the team’s work for WordPress 5.8 is progressing: the goal is to keep better track of what areas need more help and to decide if extra meetings or bug-scrubs are needed.
Trac Tickets
Here’s the situation for Trac tickets at the time of the meeting.
- All tickets milestoned for 5.8 have an owner
- Eight tickets are Feature Requests or Enhancements and, as such, should be committed in core Core is the set of software required to run WordPress. The Core Development Team builds WordPress. by the Feature Freeze date (May 25, 2021); during the bug-scrub before the meeting, the team reviewed all but two of them
- Nine tickets are marked as Bugs or Blessed Tasks, but there are two extra weeks after Feature Freeze date to commit them
While the team has done a good job at reviewing tickets, more contributors or more time would be of great help to solve these issues. Unfortunately, this is one of the biggest issues that the team is facing, but there’s little that can be done to improve this. Anyway, as the situation is under control at the moment, the team agreed not to plan any extra bug-scrubs.
Gutenberg Issues and Pull Requests
Version 10.5 of the Gutenberg plugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party was released on Wednesday, April 28. The second go / no go test for Full Site Editing should have taken place on Tuesday, April 27, but the final decision about whether Full Site Editing will be included in WordPress 5.8 and at what scope was still pending at the time of the meeting. Contributors are invited to monitor the Make WordPress Core blog to check for updates.
More in general, the only accessibility issue included in the list of “WordPress 5.8 Must Haves” issues was solved two days prior to the meeting.
At the time of the meeting, there were 211 issues / Pull Requests with the “Accessibility (a11y Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility))” label and 77 issues / Pull Requests with the “Needs accessibility feedback” label. Some team members have been asked to review if some of the older issues are still relevant, hopefully they would find time in the near future.
Team Goals
@ryokuhi still have to start updating the page with instructions on how to test Gutenberg for accessibility: updated instructions will be ready at the latest by the Feature Freeze date.
Work on documentation has slowed down a bit and there are no updates, but work on it can happen also outside of the release cycle, so it’s not a big issue.
Open floor
@joedolson asked for feedback on the latest patch in the ticket to Remove infinite scrolling from the media grid.
@ryokuhi posted the proposal to add a new workflow keyword to exclude tickets until review is needed. The Core team was cross-posted and the link shared during dev-chat.
#meeting-notes
