Tag Archives: team reps

Stefano Minoia 5:00 pm on December 2, 2022
Tags: , team reps   

Call for Team Rep Nomination – December 2022

As usual at this time of the year, we’re opening a call for (at least) one new 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 RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.. I’ve been Team Rep for almost two-and-a-half years, which is way longer than usual, and now it’s really time for me to step down. It’s been an incredible journey, I learned a lot, and I’m really grateful to everyone who I got to know during my term.

To learn more about the role, you can check the article about what it means to be a Team Rep. Here are the main takeaways.

  • Team Rep is an administrative role, not a Lead one.
  • Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities.
  • Someone who is a leader in a team can lead whether they are doing the team rep job or not.

Traditionally, the Accessibility Team has had two Team Reps, which allows them to share responsibilities, divide tasks and cover each other when needed. Since the election of @joesimpsonjr, we switched to having three Team Reps (at least temporarily) to reduce the burden even more.

If you want to be considered for the role or know someone who would be a great fit, you have the opportunity to nominate yourself or others by adding a comment to this post. Remember that if someone proposes your name, but you don’t feel like accepting, you should feel more than free to say no: we will consider your nomination only if you agree.

Nominations review will happen during the meeting on Friday, December 16, 2022, at 16:00 UTC. We’ll decide if and how to manage the voting round, depending on the number of submissions. During the transition period, we will support the new Team Reps to be ready and operational as soon as they feel like it.

If you have questions about the Team Rep role or the nomination process, please feel free to reach out to @alexstine, @joesimpsonjr, or me (@ryokuhi) in the comments or on 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/., either with a Direct Message or in the #accessibility channel.

Props go to @alexstine and @joesimpsonjr for reviewing this post before publication.

#team-reps
Stefano Minoia 5:30 pm on July 15, 2022
Tags: , team reps   

Call for Team Rep Nomination – July 2022

As announced during the last weekly meeting, we’re opening a call for (at least) one new 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 RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts.. I’ve been Team Rep for more than two years, which is twice the usual time, but I stayed in the role to support @alexstine and @joesimpsonjr. They are incredibly hard workers, but, right now, they are committed to many aspects of the Team and WordPress, including organizing events such as WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US and the WordPress Accessibility Day: it would be unfair to leave them alone in the role.

To learn more about the role, you can check the article about what it means to be a Team Rep. Here are the main takeaways.

  • Team Rep is an administrative role, not a Lead one.
  • Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities.
  • Someone who is a leader in a team can lead whether they are doing the team rep job or not.

Traditionally, the Accessibility Team has had two Team Reps, which allows them to share responsibilities, divide tasks and cover each other when needed. Since the election of @joesimpsonjr, we switched to having three Team Reps (at least temporarily) to reduce the burden even more.

If you would like to be considered for the role or know someone who would be a great fit, you have the opportunity to nominate yourself or others by adding a comment to this post. Remember that if someone proposes your name, but you don’t feel like accepting, you should feel more than free to say no: we will consider your nomination only if you agree.

Nominations review will happen during the meeting on Friday, August 5, 2022, at 17:00 UTC. We’ll decide if and how to manage the voting round, depending on the number of submissions. During the transition period, we will support the new Team Reps to be ready and operational as soon as they feel like it.

If you have questions about the Team Rep role or the nomination process, please feel free to reach out to @alexstine, @joesimpsonjr, or me (@ryokuhi) in the comments or on 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/., either with a Direct Message or in the #accessibility channel.

Props go to @alexstine and @joesimpsonjr for reviewing this post before publication.

#team-reps

Stefano Minoia 4:00 am on October 30, 2021
Tags: team reps   

Call for Team Rep Nominations

As announced during the last weekly meeting, all WordPress Teams have been requested to start the process to select the new Team Reps. Since I’ve been Team RepTeam Rep A Team Rep is a person who represents the Make WordPress team to the rest of the project, make sure issues are raised and addressed as needed, and coordinates cross-team efforts. for about 16 months now and @alexstine has been in the role for almost a year, this seems like the perfect time for us to step down, so that someone else can take up the role.

To learn more about the role, you can check the article about what it means to be a Team Rep. In summary,

Team Rep is a leadership role that is mostly administrative in nature; it is not a Lead role.
Letting go of the Team Rep title is not a loss of status, just a handing off of responsibilities.
Someone who is a leader in a team can lead whether they are doing the team rep job or not.

Traditionally, 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 has had two Team Reps, which is really useful because it allows them to share responsibilities, divide tasks and cover each other when needed.

If you would like to be considered for the role or know someone who would be a great fit, you have the opportunity to nominate yourself or others by adding a comment to this post. Remember that, if someone nominates you, but you don’t feel like accepting, you should feel more than free to say no: your nomination be considered only if you explicitly agree.

We’ll be reviewing nominations during the weekly meeting happening on Friday, November 12, 2021 at 17:00 UTC. Depending on the number of submissions, the eventual voting round will take place during the following week, with Team Reps being elected during the meeting happening on Friday, November 19, 2021 at 17:00 UTC.

If you have any questions about the Team Rep role or the nomination process, please feel free to reach out to @alexstine or me (@ryokuhi) in the comments or on 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/., either with a Direct Message or in the accessibility channel. Both of us have already agreed to support the new Team Reps during the transition period.

Thanks to @alexstine, who peer reviewed this post before the publication.

November 12, 2021 update

As of today, no one volunteered or nominated someone else as a possible Team Rep. Because of that, during the weekly meeting, the team agreed to extend the deadline for nomitations by one extra week.

We’ll be reviewing again nominations during the weekly meeting happening on Friday, November 19, 2021 at 17:00 UTC.

#team-reps

Jb Audras 12:47 pm on November 8, 2019
Tags: , team reps,   

Agenda for Accessibility Team Meeting: November 8th 2019

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 November 8, 2019 at 15:00 UTC.

  • Move Accessibility team meeting time according to end of daylight saving time
  • New team Representatives for 2019-2020
  • Discuss issues recently raised on accessibility 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/. channel:
    • Twenty Twenty Read more BlockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. (raised by @poena)
    • Initial focus on 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/ blocks (raised by @gziolo)

If you have any additional topics to propose, please comment below.

The Accessibility bug scrub will be held on Friday November 8, 2019 at 14:00 UTC.

This meeting is held in the #accessibility channel in the Making WordPress Slack (requires registration).

#gutenberg, #team-reps, #twenty-twenty

Jb Audras 8:18 am on October 26, 2019
Tags: team reps   

Accessibility team representatives election for 2020

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 plans to vote for new team representatives for 2020 on Friday 8 November 2019 at 15:00 UTC.

Current accessibility team reps are @joedolson, @audrasjb, and @arush. We last set representatives on October 2018, so it’s been a year with the current reps.

Team reps are responsible for posting agendas, publishing meetings summaries, and generally leading communications inside the team. They coordinate cross-team efforts and they represent the accessibility team within the WordPress project. It’s a set of tasks that needs to happens each week. One challenge of being a team representative is that they do need to keep on top of a lot of things that are simultaneously going on.

Anyone who is an active contributor in the accessibility team can be elected as team representative.

For full information about team reps responsibility, see the related post on Make/Updates.

It’s a one-year term. We must have 2 team reps at least, to ensure duties are shared.

Existing reps are eligible to run for the election; there are no term limits. @audrasjb is still interested but wants to give priority to new people. Same for @joedolson who wants to give more time to his new coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. committer status.

Feel free to comment to ask questions. If you are interested for being an accessibility team representative, please comment this post to nominate yourself to stand for election.

#team-reps

Rian Rietveld 10:23 am on January 19, 2016
Tags: , team reps,   

Summary Team Chat for January 18, 2016

Documentation

@trishasalas and @rachievee have been working to organize the docs and create some new drafts in the handbook. Work in progress.

Tickets

#34780: Updates screen: PluginPlugin 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 Theme tables improvements
We discussed removing the scope from the th and td first and then think of a way to set up the layout, not in a table but in another, more semantic way.

#34625: wp-login.php site title link points to wordpress.orgWordPress.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/
We need to research if themes and plugins would break if the title attribute on the logo is removed. Maybe an option is to have no title output by default for the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output.. @arush volunteered to own the ticket.

#35313: Remove title attributes: Posts, Pages, and CPTs screens
What to do with icons with a title attribute? For a sighted desktop user, the title attribute is the only indication what the icon means. There are many places where the link is just shown as an icon, and here the totle attribute was useful. We discussed how to solve this: we need to develop a coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. method to handle tooltips effectively. Andrea will open a ticket for this.

Color contrast: Some browsers do not support the styling of checkboxes and radio buttons. This means that in some browsers give that borders a poor contrast by default.

@afercia started to open tickets about the color contrast like #35497: List tables: Post format links improvements
@rianrietveld will make a list of all the color issues in the Admin, we can use as a reference to open new tickets.

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) guidelines for core

@joedolson had some comments on the core 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) guidelines; just a couple, minor changes for clarity. Basically well received by the core team. Joe is waiting for a few more comments from members of the core team that did not have to chance to look at them yet.

#accessibility-team-meetup, #team-reps, #weekly-meetings

Rian Rietveld 10:34 am on December 15, 2015
Tags: , team reps,   

Team meeting summary December 14, 2015

The last month, especially after WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US we’ve got a lot more people contributing to the wpa11y team.
Welcome Robert Jolly, Morten Rand-Hendriksen, Cheo Walker, Sakin Shrestha, Barret Golding, Adam Soucie, Scott Mann and Rachel Vasquez!

We want to keep all the new people involved, not make them feel lost or left out and leave.
Therefore we decided to form working groups, assign one lead and divide the new people in the workgroups, so they know what to do and who to ask for help/work. People can jump in and out of groups as work ebbs and flows.

Working groups

CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.

  • Task: Find 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) issues, write and discuss tickets on core trac and code patches for WordPress core.
  • Lead: Andrea Fercia
  • Contributors: Joe Dolson, Jeffrey de Wit, Sergey Biryukov, Cheo Walker, Trisha Salas, Adam Soucie, Robert Jolly, Rian Rietveld.

Documentation

  • Task: Write documentation about accessibility in our Handbook and on other relevant places on WordPress.orgWordPress.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/
  • Lead: Trisha Salas
  • Contributors: Joseph O’Connor, Barret Golding, Richard Senior, David Kennedy, Rachel Vasquez.
  • Joe Dolson and Robert Jolly volunteered to review written content.

Theme team

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.

  • Task: Find accessibility issues, write and discuss tickets on meta trac and code patches for the website WordPress.org and WordPress.tv
  • Lead: Joe Dolson
  • Contributors: Morten Rand-Hendriksen, Barret Golding, Trisha Salas

WordCamp themes

  • Task: Review of the WordCamp themes and help with fixing the accessibility
  • Lead: David Kennedy
  • Contributors: Jeffrey de Wit, Adam Soucie

Test team

  • Task: Test the accessibility of new and exsisting functionallity in and for WordPress core, at the request of the other workgroups and teams
  • Lead: Rian Rietveld
  • Contributors: > 75 volunteers, with different kind of assistive tecnology and/or accessibility expertise

Accessibility code standards for core

During the WCUS community summit in Philadelphia we made a start with accessibility code standards for core.
Joe Dolson put a concept for the a11y code standards together.
Please look at the concept and comment on it.

Documentation

Barret and Trisha are working on a good outine for the documentation, lots of good ideas, work in progress, more next week.

Core

The last #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)-headings ticket is #26601 Inappropriate content in headings on admin screens.
Joe Dolson will look into this, make a decision on how to solve this issue. On the WCUS contributors day we discussed this and the outcome od this was: First get the link out of the heading, without changing the visual design. And after that is committed, start the discussion of removing it conpletely from the post-new.php / post.php pages.

Next big project for 4.5: Color contrast ratio of the colors used in the WordPress Admin.
The official colors to use are on make.wordpress.org/design/handbook/foundations/colors/
Related ticket: #31234 closed Update wp-admin default colors.

We need to review them and fix contrast ratios for text and background lower than 4.5.
The tickets we file for this will be labeled #a11y-color.

Also related:
#34957 #a11y-focus: Standardizing the handling of :focus and :hover
Any feedback on this ticket for the project is appreciated by Adam Soucie

Meta

Ideas for meta.tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets from Barret:
1. the skip-to link needs to be closer to.
2. the skip-to link-text should be visible on focus.
3. the headings hierarchy is far from W3CW3C The World Wide Web Consortium (W3C) is an international community where Member organizations, a full-time staff, and the public work together to develop Web standards.https://www.w3.org/. standard.

Idea from Morten: Start a campaign to get WordCamp speakers to caption their own talks.

To-do for next week

Read and comment on Accessibility code standards for core.

Tickets that needs work/discussion
If you want to work on core, grab one of these tickets and help solving them

  • #31195: Add a user-friendly way to preview site responsiveness in the CustomizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.
  • #34625: wp-login.php site title link points to wordpress.org
  • #31195: Add a user-friendly way to preview site responsiveness in the Customizer
  • #35029: Remove title attributes: the revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. limit in the Publish box
  • #35050: Remove title attributes: PluginPlugin 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 Cards
  • #35064: Remove title attributes: options-general.php
  • #35076: Remove title attributes: the Featured ImageFeatured image A featured image is the main image used on your blog archive page and is pulled when the post or page is shared on social media. The image can be used to display in widget areas on your site or in a summary list of posts. postbox
  • #34957 #a11y-focus: Standardizing the handling of :focus and :hover
  • And every other ticket that focusses accessibility

#accessibility-team-meetup, #team-reps, #weekly-meetings

Joseph Karr O'Connor 7:21 pm on November 16, 2015
Tags: , team reps,   

Team Chat Summary November 16, 2015

Documentation

Discussion of adding information about accessible content management to either the Codex or 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) Handbook. Decided to add it to Handbook. Keyboard shortcuts will go in the Codex with a link from the Handbook.

Tickets

#34681 Consider removing the “Disable the visual editor when writing” option.
Decided to gather user experience data. Four questions to ask:

      Do you know how to switch between the visual and HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites. editor in WordPress?
      If no, please try and figure out how, and tell us how that experience was for you.
      If yes, give us your thoughts about your experience using that feature.
      Do you use the option “Disable the visual editor when writing” in your profile?

#34625: wp-login.php site title link points to wordpress.org.
Suggested fix: removing the title attribute, changing the text to ‘Powered by WordPress’, and leaving the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. on that text.

#accessibility-team-meetup, #team-reps, #weekly-meetings

Joseph Karr O'Connor 8:15 pm on August 31, 2015
Tags: accesibility, , team reps   

Team Chat Summary August 31, 2015

Headings

More work is being done on headings in admin. Jeffrey de Wit created some tickets some of which are already patched and committed. Follow the headings discussion in #accessibility on 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/..

Handbook

Devised a strategy for building out the Make WordPress Accessible Handbook. Page leaders will help others build out the handbook.

Twenty Sixteen

Twenty Sixteen is on Github. Twenty Sixteen is also available in the theme directory. It’s not in trunk yet. According to David Kennedy ” I did a 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)-ready review before it went on GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ and the directory to make sure nothing was way off accessibility-wise. It’s solid. Takashi knows the drill.” We will ask the testers to test it. David Kennedy did an #accessibility-ready audit of Twenty Sixteen.

Select2

We continued a discussion about Select2 as an alternative to the autocomplete/tagging input field types. There are two main accessibility issues: it doesn’t do a good job of providing feedback to screen readers and it requires the ‘enter’ key to begin typing for autocomplete, a non-standard interaction. The testers have tested Select2 and it is not very accessible. Rian Rietveld will collect all the data and report next week.

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. US

Several of us are submitting proposals for talks at WordCamp US and depending on funding assistance some of us will be attending. Today is the last day for submitting proposals.

#accesibility, #accessibility-team-meetup, #team-reps

Joseph Karr O'Connor 5:03 am on August 13, 2015
Tags: , team reps,   

Team Chat Summary August 10, 2015

New Structure Proposed

Rian Rietveld wrote a proposal on how to structure our work better and plan ahead longer and we discussed it. What follows is examples from the proposal.

Goals and Issues

This will be a separate page on make/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) and also a main menu item. It gives an overview of our goals for the accessibility of WordPress, the work we (want to) do, how this is organized, how we test, a roadmap for the next year and how we track the progress of issues we are working on. An example of the roadmap for release 4.4:

Release 4.4 (December 2015, Scott Taylor)
  • Finish still open issues focus from 4.3
  • Semantic heading structure Admin
  • The customizerCustomizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings.
  • Handbook
  • Twenty Sixteen (?)

Central Ideas

Some central ideas also included in the proposal are keyboard focus, work on the handbook, color contrast, system to better follow tickets including splitting up tickets among team members on which to concentrate, and continue to develop code pattern library. Much more is included in the proposal and for now we will continue to work on the proposal to make it a more formal document to cover our activities over the next year.

We also talked about the fact that having a planning document to refer to does not obviate the need to address all new features since there is a tight turn around towards the end of a cycle because that’s when the features going into the release are announced. If we don’t follow all new features we might miss one or more that advance to release at the very end.

When we have it shaped up we will add the planning documentation to this blog in the form of pages and sub-pages to make it a community resource.

#accessibility-team-meetup, #team-reps, #weekly-meetings