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 here.
NOTE: We need YOUR help. Stefano cannot facilitate our next three weekly Bug Scrubs (March 24th, March 31st, and April 7th) and we need someone to step in and help. Please reach out here or on our Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. channel if you can facilitate the Bug Scrub on these dates. Thanks in advance.
Updates from the working groups
Only groups that provided updates are shown below.
@ryokuhi provided the following statistics:
- There are 10 tickets in the Awaiting Review queue, all reviewed at least once.
- There are 2 open tickets in the 6.2 Milestone (one about the About Page and the other about the dashboard banner for 6.2). 18 accessibility tickets have been committed so far in the next major release A set of releases or versions having the same major version number may be collectively referred to as “X.Y” -- for example version 5.2.x to refer to versions 5.2, 5.2.1, and all other versions in the 5.2. (five dot two dot) branch of that software. Major Releases often are the introduction of new major features and functionality..
- We have already started reviewing tickets in the 6.3 milestone, to get a general idea about what to focus on during the next release. There are at the moment 15 tickets in the milestone, and since last week we reviewed 11 of them.
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/ Team
@annezazu shared the following update for discussion:
- I want to note the navigation section of browse mode. While it’s removed for 6.2, it’s going to continue in 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 and it would be excellent to continue the feedback cycle there to make sure it’s super robust for 6.3. It’s also part of setting the stage for reintroducing content editing for 6.3! Additional discussion by @alexstine and @joedolson can be found at this timepoint on Slack.
Media and Meta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
@joedolson provided the following updates on Media and Meta for discussion:
- Media: starting to scrub through and add tickets to the 6.3 milestone, will possibly have more to add by the meeting.
- Meta: there’s a new slack channel #website-redesign that may make it easier to track the planning for the ongoing redesign of WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/. anybody interested in that should probably join that channel.
@ryokuhi asked: Due to Daylight Savings Time in certain areas, are we going to keep the same UTC time for bug scrubs and meetings? Also, we’re beginning to get a general idea of what we’ll have to do in the incoming months and should discuss. For example, specific tickets require special attention, we’ll bring them up during future meetings.
@joesimpsonjr mentioned being flexible to those who aren’t or are adversely impacted by Daylight Savings Time (changing or keeping times the same).
We’ll keep the meeting time the same unless someone raises a concern.
NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.
Read the full discussion in the Open Floor section of the meeting’s transcript.