X-post: Proposal: A WordPress Project Contributor Handbook

X-comment from +make.wordpress.org/updates: Comment on Proposal: A WordPress Project Contributor Handbook

Accessibility Team Meeting Agenda: March 12, 2021

This is the proposed agenda for the weekly AccessibilityAccessibility 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 on Friday, March 12, 2021 at 16:00 UTC.

  • Meeting time change following daylight saving time introduction
  • Improvement of onboarding for new contributors
  • Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, March 12, 2021, at 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Accessibility Team Meeting Notes: March 5, 2021

These are the weekly notes for the AccessibilityAccessibility 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.

Review of accessibility team’s goals for WordPress 5.8

Following the pubblication of the call for WordPress 5.8 Accessibility Team’s goals, a discussion about the proposed goals should have taken place.

Some team members missed the post and it wasn’t clear if existing goals were to be reported again, so no comments to propose new or existing goals were added to the post.

According to the news about the changes to the release plan for 2021, WordPress 5.8 release will be postponed to July 2021, which gives a few more weeks for development: because of that, the team agreed to postpone the discussion about team goals for two weeks. Also, @ryokuhi agreed to summarize goals identified earlier and to add a comment to the call for team’s goals.

Open floor

@Estelaris asked for feedback from the team regarding the redesign of HelpHub (WordPress support documentation for end users). In particular, she asked for feedback on improving the use of the hashtag (#) symbol, which can be found next to each section heading and that links to that same heading, allowing for easy copy-and-paste of a link to that section of the documentation. After some discussion, the team was able to identify the issues of the current design and implementation and some possible paths to improve it. @Estelaris will do some more research and will write a P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at https://make.wordpress.org/. post, x-posting the Accessibility Team for reference.

@Hauwa Abashiya asked for some extra quick review of the accessibility standards.

#meeting-notes

Accessibility Team Meeting Agenda: March 5, 2021

This is the proposed agenda for the weekly AccessibilityAccessibility 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 on Friday, March 5, 2021 at 16:00 UTC.

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, March 5, 2021, at 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Accessibility Team Meeting Notes: February 26, 2021

These are the weekly notes for the AccessibilityAccessibility 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.

Updates from working groups

  • Documentation and Accessibility Patterns: updating the existing accessibility standards document. Publishing information about WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 changes. Plan is still to publish the document around the 5.7 release.
  • Media: most 5.8 priorities set. Planning to scrub all old tickets. The most notable change is removing infinite scroll from the media library.
  • Themes: no progress on workshop lesson plans. Two Accessibility Ready tagged themes went live.
  • GutenbergGutenberg 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/: persistent list view continues to be a topic of discussion. Full site editing second call for testing. Internet Explorer 11 support could be ending. Post going live Monday or soon after.
  • Design: no updates.
  • MetaMeta 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.: no updates.
  • General: Twenty-one tickets fixed in 5.7.

Call for WordPress 5.8 accessibility team’s goals

The post has been published and is ready for your feedback: Accessibility Team’s goals for WordPress 5.8 and beyond

Open floor

#meeting-notes

Accessibility Team’s goals for WordPress 5.8 and beyond

After the first Release CandidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. of WordPress 5.7 was shipped on February 23, the AccessibilityAccessibility 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 is looking into setting goals for the next release.

The 5.8 development cycle is yet to be defined: according to the original plan, WordPress 5.8 potential release date would be June 8, 2021, but a discussion about having four major releases in 2021 is ongoing and the release date is yet to be confirmed.

Nevertheless, the Accessibility Team wants to be ready when the release cycle will be announced, so this is a good time to start to collect ideas on possible team’s goals.

As such, we invite you to leave a comment below and propose which accessibility improvements you’d like to see shipped with WordPress 5.8. The discussion to identify major team goals will be held during the next weekly meeting, happening on Friday, March 5, 2021 at 16:00 UTC in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

During the 5.7 release cycle, the team decided to improve its workflow by creating seven working groups, focusing respectively on Design, Documentation, Media, MetaMeta 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., General, GutenbergGutenberg 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/, and Themes. The new team structure helped in moving issues faster, so we’re going to follow the same scheme also for WordPress 5.8. This means that the final choice about goals and targets will be in the hands of each working group, but you’re still invited to share your ideas, take part in the discussion and suggest what to prioritize.

If a certain goal won’t be selected for the 5.8 release, it can always be included in the list that will be created for the 5.9 release.

As the number of releases planned for 2021 is probably going to be reduced, the release cycle may be longer and some larger projects might make it into the list of the release goals. Anyway, if you think that solving a specific issue or adding a new feature may require work that spans over multiple releases, let us know so that we can try to coordinate and help you get the job done.

If you have any questions, feel free to drop them in the comments below or in the #accessibility channel on Slack.

#5-8, #goals

Accessibility Team Meeting Agenda: February 26, 2021

This is the proposed agenda for the weekly AccessibilityAccessibility 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 on Friday, February 26, 2021 at 16:00 UTC.

  • Updates from working groups
  • Call for WordPress 5.8 accessibility team’s goals
  • Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, February 26, 2021, at 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Accessibility Team Meeting Notes: February 19, 2021

These are the weekly notes for the AccessibilityAccessibility 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.

Final review of WordPress 5.7 goals

  • Accessibility: most tickets have already been handled.
  • Media: starting to plan 5.8 goals.
  • Documentation and Accessibility Patterns: no updates on progress. @joedolson said he would shift some of his focus in to writing WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 docs now that we’ve arrived at RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.. Contributions always welcome. Plan is to have docs done by 5.7 release. Contribute here.
  • WidgetWidget A WordPress Widget is a small block that performs a specific function. You can add these widgets in sidebars also known as widget-ready areas on your web page. WordPress widgets were originally created to provide a simple and easy-to-use way of giving design and structure control of the WordPress theme to the user. Screen: @joedolson created a TRAC ticket. Next week we’ll discuss timeline.
  • Learn WordPress: meeting notes from yesterday.
  • Themes: no update to share.

Open floor

#meeting-notes

Accessibility Team Meeting Agenda: February 19, 2021

This is the proposed agenda for the weekly AccessibilityAccessibility 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 on Friday, February 19, 2021 at 16:00 UTC.

  • Final review of WordPress 5.7 goals
  • Open floor

If you want to have a topic added to the agenda, please mention it in the comments of this post.

The Accessibility Team bug scrub will be held on Friday, February 19, 2021, at 15:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/. (requires registration).

#agenda

Accessibility Team Meeting Notes: February 12, 2021

These are the weekly notes for the AccessibilityAccessibility 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.

Updates from working groups

  • Documentation: updating the existing documents for accessibility standards to provide better guidance. Publishing information about WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 changes. Track progress in the WCAG 2.1 WP Update Google Document.
  • Media: #47120 will be committed before betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 3; #50105 will be deferred to 5.8-early. It’s almost there, but it’s a major UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. change that would require a significant push to have ready by Tuesday, and should really sit in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. for longer. Joe Will probably commit as soon as alpha opens for 5.8, however. All media tickets are either committed or already bumped to later.
  • Themes: Accessibility Ready tag reviews in progress, a couple days out of the week. Working on developing workshop on Learn WordPress.
  • Design: good progress with design/A11yAccessibility 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) joint bug scrub.
  • MetaMeta 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.: a Meta TRACTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. ticket worth checking out: Category archives pages : accessibility improvement (HTML)
  • General: during the bug scrub, we reviewed the five tickets with milestone 5.7 that are still open. 16 tickets in the milestone have been closed.

Open floor

  • WordPress 5.8 is open for development, now is a good time to start coming up with accessibility goals.
  • The next Learn working group meeting is being held in #training on Thursday, 18 February 2021, 19:00 UTC.
  • @mgifford will be giving a presentation at the DC Drupal meetupMeetup All local/regional gatherings that are officially a part of the WordPress world but are not WordCamps are organized through https://www.meetup.com/. A meetup is typically a chance for local WordPress users to get together and share new ideas and seek help from one another. Searching for ‘WordPress’ on meetup.com will help you find options in your area. group about the accessibility of the new White House website (built with WordPress). If possible, consider attending! Drupal NoVA: 10 Things We Can Learn from the New WhiteHouse.gov on Accessibility

#meeting-notes