Accessibility Team Meeting Agenda: January 3, 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 3 January 2020 at 16:00 UTC.

  • Team updates
  • Accessibility team goals for WordPress 5.4:
    • Primary focus for this 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.
    • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. / TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets
    • 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/ / 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
  • Open floor

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

The Accessibility bug scrub will be held on Friday 3 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).

WordPress Accessibility Day: kickoff meeting notes

Slack transcript of the meeting

The initial planning meeting for the proposed 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) event occurred on Tuesday, December 17th 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.

Goals of the Event

What do we hope to achieve with this event?

  • Build awareness in the WordPress community around accessibility
  • Develop the accessibility knowledge of the members of the WordPress community

Outcomes

  • Things to measure: participants, number of live events, participation follow-up behaviors
  • Can we set practical numeric goals with no prior comparison? Perhaps specific goal setting is a thing for a repeat WPA11y Day.
  • Consider possible goal targets as we develop the event further.

Logistics

We made the decision to plan a 24 hour event, world-wide. Currently planning is targeted towards a date in late September, to avoid collisions with major WordPress releases, WordCamps Asia, EU, and US, and to also try and avoid the probable date for ID24.

A secondary goal is to prepare a mini-event to promote this as part of Global Accessibility Awareness Day (GAAD) 2020.

Naming

The official name of the event will be ‘WordPress Accessibility Day’.

The next meeting is tentatively proposed for Tuesday January 14th 2020 at 16:00 UTC. In the next meeting we’ll further examine the logistics, refine the timeline, and begin to discuss content.

Accessibility Team meeting notes for 13 December 2019

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.

Meeting plans for remainder of December 2019

The team agreed to take a break from meetings and bug scrubs for the remainder of December 2019 and a such, today was our last meeting and bug scrub of the year.

The team was also reminded of the WordPress Global Accessibility Day initial planning meeting, which will be held on Tuesday 17 December 2019 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.

Easier testing of 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/ PRs with gutenberg.run

http://gutenberg.run is a service by @aduth that provides temporary live preview sites for Gutenberg pull requests.

This will allow us to view and test Gutenberg PRs without the need to have a local development environment set up and running. Testing and providing feedback should be much easier for a lot of us.

It’s important to note that http://gutenberg.run is a work in progress, and as such some bugs can happen. The project is open sourceOpen Source Open Source denotes software for which the original source code is made freely available and may be redistributed and modified. Open Source **must be** delivered via a licensing model, see GPL., so if you want to report bugs or follow along on its development, you can do so in the project’s GitHub repository.

Status and follow up plans for the Accessibility Audit project board 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/

The team was reminded of the Gutenberg Accessibility Audit project board on GitHub which was created after the WP Campus accessibility audit that was performed earlier this year.

We noticed how 60 issues have already been closed, 8 are in progress and 27 are still in the To do list.

Now that gutenberg.run is available, we hope that the team can provide the necessary testing and feedback and make some progress on these issues.

Updates on the team’s current projects

@joedolson updated the team on the progress that has been made on the research work of focus handling in Gutenberg blocks we started recently.

Joe noted that now that most of the initial research has been done, some patterns are starting to emerge and we’ve been able to identify predominant behaviors and oddities.

Joe will collate the list and ask follow-up questions to some of the testers for clarification. We’ll add screen-reader testing to the research so we can identify how each scenario is announced.

We also revisited the idea that came up recently of adding accessible color schemes to wp-admin. Now that we have access to the GitHub and SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. 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 repositories we are in a position to make progress.

The team agreed to come back to this project next year after the break.

Open Floor

On the topic of accessible color schemes, @steelwagstaff shared some previous accessible color scheme work done for PressBooks that should be useful to the team.

#meeting-notes

Changes to the meeting calendar for the rest of 2019

As discussed during today’s meeting, 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 will be taking a break from meetings and bug scrubs for the remainder of December 2019. Today was our last meeting and bug scrub of the year.

This means that there will be no meetings and bug scrubs on December 20 and December 27.

We will return to regular schedule on Friday, January 3 2020.

WP Global Accessibility Day

The initial planning session for the proposed WP Global 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 will happen on Tuesday 17 December 2019 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.

All are welcome to participate – registration and an account in the WordPress Slack instance are required. Instructions on joining the WordPress Slack.

Meeting agenda (in Google Docs).

This is an early planning session, so come prepared with a open mind and lots of ideas!

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

  • Meeting plans for remainder of December 2019
  • Easier testing of 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/ PRs with gutenberg.run
  • Any updates and follow up plans for the team’s current projects
  • Status and follow up plans for the Accessibility Audit project board on GitHub

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

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

#agenda

Accessibility Team meeting notes for 6 December 2019

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.

Proposed times for the Global WP Accessibility Day initial planning meeting

A set of dates have been proposed for the upcoming planning meeting for the Global WP Accessibility Day. Folks interested in participating are encouraged to join 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/. (requires registration) and vote for a date.

Advancing the 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. Interface

At last week’s meeting, we brought up this Gutenberg GitHub issue that is exploring the current constrains of the block’s toolbar and is proposing some updates that will make it more usable and robust. Being a long issue that goes into a lot of depth, we agreed last week to give everyone some time to digest it and revisit the topic during this meeting.

Those who had time to review it shared their thoughts. The conversation also touched on process and how there’s still room for improvement when it comes to these kind of proposals.

Folks are encouraged to leave feedback and comments on the issue.

Updates 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

We revisited the research work that started a few weeks ago on focus handing of Gutenberg blocks. The team made a lot of progress and we’ll revisit the topic next week once we’ve had more time to go over the results.

New Welcome Guide modal in Gutenberg

This pull request from the Gutenberg GitHub repo was brought up because there are still some implementation issues that need to be addressed.

It was suggested that the modal component be set with a role=dialog, and since we can’t predict what kind of content will live within the modal, a role=document be used for the content.

The team also discussed usability issues present on the modal. All this feedback has been summarized and added to the PR.

WAI-ARIA compliant custom select

While extensive accessibility testing has been performed on this component, there are still improvements to be made.

The conversation also touched on accessibility testing process and documentation and ways we could improve it. We agreed to explore the idea of creating documentation for baseline accessibility testing procedures and expectations.

#meeting-notes

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

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

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

#agenda

Accessibility Team meeting notes for 29 November 2019

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.

Notice to discourage use of IE11

The team discussed this Trac ticket that proposes to encourage users, through a message or notification, to upgrade from IE11.

The team agreed that having a permanently dismissible notice is a good idea but we should however be mindful of folks who can’t upgrade due to work requirements or version of assistive technologyAssistive technology Assistive technology is an umbrella term that includes assistive, adaptive, and rehabilitative devices for people with disabilities and also includes the process used in selecting, locating, and using them. Assistive technology promotes greater independence by enabling people to perform tasks that they were formerly unable to accomplish, or had great difficulty accomplishing, by providing enhancements to, or changing methods of interacting with, the technology needed to accomplish such tasks. https://en.wikipedia.org/wiki/Assistive_technology being used. Ending support for IE11 should be a separate issue.

Remove aria-label from links

We also discussed this GitHub PR that is attempting to fix a problem when creating a link in the 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. editor and is set to open on a new tab.

Currently, the link gets an aria-label with the link’s label and a string appended that indicates that the link will open in a new browser tab. The issue is that the appended string is not being set to the document’s language, but to the language wp-admin is set to.

The team agreed that removing the currently broken functionality to add the aria-label is good first step, but would like to see a solution implemented as well.

We think that making the string visible would be ideal, since all users would benefit from this piece of information. It should also be set to the document’s language, because this string will be used in a public context.

Advancing the block interface

This recent 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/ GitHub issue that explores refinements to the block toolbar was shared with the team for awareness. It’s a long read, so we’ll revisit the item next week once everyone has had time to digest it.

Global WordPress Accessibility Day

We revisited the idea of having a global WordPress accessibility day. This had been discussed earlier in the year and a spreadsheet for those interested in participating was created.

Since this was discussed a while ago, we ask those who had already signed up to confirm their participation, or remove themselves from the spreadsheet if they won’t be participating anymore.

Anyone who’s not on the list and wants to participate is welcome to add their details.

The organizing team will be coordinating to set up a planning meeting. Folks are also welcome to join the #accessibility-events 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).

#meeting-notes

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

  • Notice to discourage use of IE11
  • Remove aria-label from links
  • Advancing the Block Interface
  • Global WP 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) Day

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

There will not be an accessibility bug scrub this week.

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