Enrique Sánchez 6:25 pm on January 24, 2020
Tags:   

Accessibility Team meeting notes for January 24 2020

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.

Update on 5.4 TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets

@audrasjb has organized a schedule to run additional bug scrubs in preparation for the 5.4 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. Last week we were at 40 accessibility focused tickets still open in the milestone, and today we are at 36 open tickets.

We were all reminded that 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 is planned for February 11, 2020, and it is our deadline for committing patches into coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress..

The next bug scrub is planned for Tuesday, January 28 at 17:00 UTC.

Update on the last WPAD planning meeting

Last week we held out third planning meeting for the WordPress Accessibility Day in the #accessibility-events channel in Slack. The team reports that the event organization is taking shape, and we’re considering September 26, 2020, as our intended date.

We’ve considered other WordPress events and mayor global holidays to define this date. That being said, we’d like to let it sit for a couple more weeks in case we’ve missed an important event or holiday.

Big thanks to @joedolson and everyone else who’s volunteered for the organizing team.

Please head over to the #accessibility-events channel in Slack to find out when then next planning meeting will be.

Follow up of the 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/ 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. focus project

Work is underway, and the next steps are converting the team’s observations into actionable GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ issues in the Gutenberg repository.

Help with testing the navigation block

The design team has asked for our help with performing accessibility testing on the navigation block in the editor. @nrqsnchz will coordinate a document where those available to help can add their feedback and observations.

#meeting-notes

Enrique Sánchez 7:01 pm on January 23, 2020
Tags:   

Accessibility Team Meeting Agenda: January 24, 2020

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, 24 January 2020 at 16:00 UTC.

  • Update on 5.4 tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets
  • Update on the last WPAD planning meeting
  • Follow up of the 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/ 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. focus project
  • Help testing the navigation block
  • Open floor

The Accessibility bug scrub will be held on Friday, 24 January 2020 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

Jb Audras 3:25 pm on January 19, 2020
Tags: 5.4,   

WordPress 5.4 accessibility focused bug scrubs agenda

WordPress 5.4 is planned to be released on March 31, 2020, 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 February 11, 2020.

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 (around 40 open tickets on Trac), the accessibility team added few bug scrubs to help moving them forward:

These bug scrubs will be specifically focused on technical issues with TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets and GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ issues that are milestoned for WordPress 5.4.

Regular weekly bug scrubs are still planned every Fridays at 15:00 UTC.

#5-4, #bug-scrub

Enrique Sánchez 6:32 pm on January 17, 2020
Tags:   

Accessibility Team meeting notes for January 17, 2020

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.

Summary of the second WordPress Accessibility Day planning meeting

Earlier this the week we had our second planning meeting. Planning is well underway and the team has reached out to outside sources for help in order to make some key decisions.

The proposed dates for the next meeting have been posted in the #accessibility-events channel in 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/..

Dates for the upcoming 5.4 bug scrubs

In addition to our weekly bug scrub that happens every Friday at 15:00 UTC, we will be facilitating an addition bug scrub meeting on Tuesdays at 17:00 UTC, to address all TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets and GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ issues for the 5.4 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software..

Continue conversation on 5.5 focuses

As previously discussed, the team would like to start planning and working on our focuses for the 5.5 release. It’s been suggested we start work an accessible color schemes for wp-admin and start looking at the Full-site editing work that is ongoing in the Gutenberg repository in GitHub.

#meeting-notes

Enrique Sánchez 10:00 pm on January 16, 2020
Tags:   

Accessibility Team Meeting Agenda: January 17, 2020

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, 17 January 2020 at 16:00 UTC.

  • Summary of the second WordPress Accessibility Day planning meeting.
  • Dates for the upcoming 5.4 bug scrubs.
  • Continue conversation on 5.5 focuses.

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

The Accessibility bug scrub will be held on Friday, 17 January 2020 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

Joe Dolson 12:09 am on January 16, 2020
Tags:   

WP Accessibility Day: planning meeting 2

WP 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) Day planning continued on Tuesday, 14 January, 2020

Slack transcript

Design: Site, logo, hosting, etc.

@nrqsnchz volunteered to pair with somebody on design.

@ryokuhi verified that Global WordPress Translation Day was hosted by Siteground; @jbaudras will check with WP Translation day organizing team about how that was set up.

@joedolson checked domain options, @audrasjb will also check with WP Translation day team about securing the domain.

Still need additional volunteers to work on design. Would like a team of at least three people to plan architecture, build, and design.

Event Content

@joedolson proposed using a model similar to ID24 (inclusive design 24); 24 hours, one talk per hour. Content will be selected from open submissions world-wide. Essentially a single-track, single-topic 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. running virtually for 24 hours.

Talks would probably be 30-40 minutes. Have live emcees who can chat with and do mini-interviews with speakers, handle q & a.

Use members of organizing team or 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) team to handle emcee duties.

Speaker Selection

@vicent, @ryokuhi, @joedolson, and @bdeconinck volunteered to help with speaker selection. Further volunteers are welcome!

Local event coordination

We’ll want to list local events that are associated with WP Accessibility Day, such as viewing events or other related events.

  • Need to be able to provide information to organizers setting up events on accessible event spaces
  • Need to list accessibility features of events on site (e.g., live signing, audio enhancement, description services, etc.)
  • Should have minimum requirements for events re: accessibility of event space.

Briefly discussed live translation services & post-event internationalization of content, but tabled the conversation as out-of-scope.

Next meeting:

Dates are proposed in the #accessibility-events 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; please vote on options.

Enrique Sánchez 11:19 pm on January 10, 2020
Tags:   

Accessibility Team meeting notes for 10 January 2020

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.

Update on the next WordPress Accessibility Day planning meeting

The next WPAD meeting will be held on Tuesday, January 14, 2020, 16:00 UTC on the #accesibilty-events channel in the Make WordPress Slack (account required). Read this post for a summary of the kickoff meeting that took place on Tuesday, December 17th 2019.

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. Asia 2020 accessibility contributor table

At least one member of the accessibility team is planning on attending WordCamp Asia 2020 next month, this means we’ll be able to host an accessibility contributor table.

Action plan for the 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/ focus research work

We need feedback on the observations gathered from the research and testing the accessibility team did on the various focus handling flows in Gutenberg blocks.

The team wants to validate these observations before moving on to creating issues on the Gutenberg repository on GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/.

Focuses for 5.4 and 5.5

The team agreed to have additional bug scrubs to address tickets and issues for the 5.4 releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software.. More information on when these bug scrubs will happen will be shared as soon as possible.

For 5.5, the team would like to work on a bigger project, such as the idea of developing accessible color schemes for wp-admin.

Open Floor

Help is needed providing more information and media references on Joseph Karr O’Connor Wikipedia page. Joseph passed away last week. He was a former team representative and an outstanding member of the web accessibility community.

#meeting-notes

Joe Dolson 2:06 am on January 10, 2020  

Goodbye, Joseph Karr O’Connor

Joseph Karr O’Connor, also known to the WordPress community as @AccessibleJoe, passed away peacefully on Friday, January 3rd, 2020.

Joe made his first post here on September 5th, 2013, when he became 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 representative, taking over from Mel Pedley, who stepped away from WordPress at that time.

I was first introduced to Joe in late 2012. We were working on parallel but separate projects – he was promoting the plan to develop a collection of accessible WordPress themes, called the Cities project, while I was working with Mel Pedley and the Theme Review team to define the collection of guidelines that formed the seed of today’s accessibility-ready program for WordPress themes.

Joe was an amazing people person – gentle and kind, and always able to be calm in the face of difficult conversations.

The WordPress Accessibility Team would not be what it is today without Joe’s leadership and patience, although his health forced him to step down from his leadership role in late 2015, and reduce his role further after continuing health issues in 2016.

Thank you to Joe, and all our best wishes to his wife Linda and his daughter Siobhan. We hope that they know that Joe will always hold a place in our hearts and in the history of WordPress.

Joe has requested that gifts in his honor be made to The Aurelia Foundation, which provides community-based day programs to people with developmental disabilities, including his beloved daughter.

Enrique Sánchez 9:15 pm on January 9, 2020
Tags:   

Accessibility Team Meeting Agenda: January 10, 2020

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, 10 January 2020 at 16:00 UTC.

  • Update on the WordPress Accessibility Day meeting.
  • 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. Asia 2020 contributor table.
  • Action plan for the 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/ focus research work.
  • Focuses for 5.4 and 5.5.

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

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

Jb Audras 5:41 pm on January 3, 2020  

Accessibility Team Meeting Notes: 3 January 2020

Meeting transcript on Slack

Update on the WordPress 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) Day

The project kickoff meeting took place on Tuesday, December 17th. The meeting summary is available.

Proposed date for the next WordPress Accessibility Day meeting is Tuesday 14 January 2020 at 16:00 UTC in the #accessibility-events 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. If you would like to propose another meeting date, please comment in the meeting summary post.

Update on the 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/ focus handling research work

Last month, the accessibility team made some testing on how Gutenberg handles focus on the various blocks. Thanks @enrique, @markdubois, @vicent, @gziolo, @audrasjb and @joedolson for their contribution.

@joedolson completed the focus handling tests & written up observations on it in a document.

Next steps:

  • Publish the summary on Make/Accessibility
  • Open related issues on Gutenberg GitHubGitHub GitHub is a website that offers online implementation of git repositories that can 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/ repository

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. Asia – contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/.

WordCamp Asia will host a contributor day and plan to set up an Accessibility table. All accessibility team members who plan to attend the WordCamp are welcome to volunteer to lead the table. Please comment below if you are interested.

Accessibility team goals for WordPress 5.4

@audrasjb: It would be great to define a primary focus for the team, for the next major releaseMajor 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., WordPress 5.4. It’s not mandatory to have a main focus, but with 5.3 the primary goal of the team was the Admin CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes and it was quite effective.

@sabernhardt added one goal would be fixing more issues from the Gutenberg audit (maybe not primary focus though).

@nataliemac asked if it’s possible for accessible color schemes to be a focus for 5.4.

Accessible color schemes is a very nice project but it will probably have to wait for 5.5 in August, as 5.4 development must to be almost completed in 4 week. The idea is to plan major goals for 5.5 in the next few weeks and to focus on smaller tasks (TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets and Gutenberg issues) for 5.4.

This Trac report can be used to pick up small focuses for 5.4. On Gutenberg side, that would be nice to address a couple of issues from the audit.