Category Archives: Agenda

Enrique Sánchez 5:20 pm on November 21, 2019  

Agenda for Accessibility Team Meeting 22 November 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 22, 2019, 16:00 UTC.

  • Continue conversation on initial Gutenberg block focus
  • 5.3.1 scope
  • Path forward for 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) color schemes
  • Notice to discourage use of IE11
  • Global WP a11y Day

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

The Accessibility bug scrub will be held on Friday, November 22, 2019, 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).

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

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:   

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

Jb Audras 1:16 pm on September 27, 2019
Tags:   

Accessibility Team Meeting Agenda: 27 September 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 27 September 2019 at 15:00 UTC.

  • Progress on WordPress 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets (and next bug scrubs)
    • Discuss CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes related to links focus style (it’s now just a dotted outline)
    • Links focus style on the admin menu needs improvements (barely visible)
    • Twenty Twenty
  • Upcoming Bug scrubs
  • Information: 23 September 2019 was the first stage of the European Union directive on accessibility of the websites and mobile applications of public sector bodies

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

The Accessibility bug scrub will be held on Friday 27 September 2019 at 14: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).

#5-3

Jb Audras 7:47 pm on September 12, 2019
Tags: , ,   

Accessibility Team Meeting Agenda: 13 September 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 13 September 2019 at 15:00 UTC.

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

The Accessibility bug scrub will be held on Friday 13 September 2019 at 14: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).

#5-3, #gutenberg, #twenty-twenty

Jb Audras 12:30 pm on September 6, 2019
Tags: ,   

Accessibility Team Meeting Agenda: 7 September 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 7 September 2019 at 15:00 UTC.

  • Discussion about 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/ recent post: Defining Content Block Areas
  • Progress report on WordPress 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets
  • WordPress 5.3: assign owners for tickets assigned to WordPress 5.3 milestone
  • Open floor

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

The Accessibility bug scrub will be held on Friday 7 September 2019 at 14: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).

#5-3, #gutenberg

Jb Audras 10:27 am on August 30, 2019  

Accessibility Team Meeting Agenda: 30 August 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 30 August 2019 at 15:00 UTC.

  • Progress report on WordPress 5.3 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets
  • WordPress 5.3: assign owners for tickets assigned to WordPress 5.3 milestone
  • Open floor

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

The Accessibility bug scrub will be held on Friday 30 August 2019 at 14:00 UTC. That bug scrub will be specifically focused in tickets with design keywords.

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).

Jb Audras 7:01 pm on August 28, 2019
Tags:   

WordPress 5.3 accessibility focused bug scrub schedule

WordPress 5.3 is planned to be released on Tuesday 12 November 2019 with a 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. 1 on Monday 23 September 2019.

Given the large amount of 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) tickets in the milestone (75+ TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets, with 57 still open tickets as of today), two additional accessibility bug scrubs are planned:

These bug scrubs will be specifically focused on technical issues with current Trac tickets.

Regular weekly bug scrubs are still planned each Friday at 14:00 UTC.

#bug-scrub

Jb Audras 9:09 am on August 23, 2019  

Accessibility Team Meeting Agenda: 23 August 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 23 August 2019 at 15:00 UTC.

  • 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/ Custom Select proposal: for reference, see the related GitHub issue and specifically this comment
  • WordPress 5.3: Assign owners for tickets assigned to WordPress 5.3 milestone
  • Open floor

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

The Accessibility bug scrub will be held on Friday 23 August 2019 at 14: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).

Jb Audras 8:40 pm on August 1, 2019  

Accessibility Team Meeting Agenda: 2 August 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 2 August 2019 at 15:00 UTC.

  • Support Navigation and Edit Mode
    (for reference, see the related pull request on Gutenberg GitHub repository)
  • Improving the Accessibility Team feedback 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/ issues and pull requests
  • WP Accessibility Day – organizing team & next steps
  • Feedback on Theme Review Team’s post about supporting keyboard navigation
    (for reference, see the related draft post)
  • Open floor

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

The Accessibility bug scrub is intended to be held on Friday 2 August 2019 at 14: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).