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

Accessibility Team meeting notes for 22 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.

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

The team continued the discussion about where initial focus should land on the different types of blocks available 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. For example, some blocks such as text-based blocks have a clearly defined editable area, which makes it obvious where focus should land. This however is not the case with a variety of blocks where text is not the primary element.

The team agreed to investigate and document initial focus on all the available blocks in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. and post findings on a newly created spreadsheet that contains a list of all the blocks. We’ll revisit the list during the next meeting and evaluate our progress.

5.3.1 scope

The team’s goal for 5.3.1 is to address any immediate regressions introduced on 5.3. The tickets that need special attention are #48585, #48598, #47142, #47069 and #48420. Help with testing, patches and providing feedback is welcome.

Accessible color schemes

The team continued the discussion from the previous meeting about having color schemes in wp-admin that address specific accessibility needs. We think this could be a great feature proposal for 5.4 or 5.5.

The team agreed that we should start with a 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 that will reside in the accessibility team’s GitHub repository.

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

  • Elect New team Representatives for 2019-2020
  • Assign new team & contributor badges
  • WordPress 5.3 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.: comments, concerns, updates.

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

The Accessibility bug scrub will be held on Friday November 15, 2019 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 Meeting notes from 8 November 2019

Meeting transcript on Slack

Election of new team reps

Discussed responsibilities of a 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.. Since we failed to account for the time change prior to this meeting, we opted to delay the election until 11/15, to get back to a clear schedule and maximize attendance.

Gathered nominees: @audrasjb nominated himself, @nataliemac nominated @afercia and @nrqsnchz. @afercia declined the nomination.

@nrqsnchz was not present at this point in the meeting.

If we end up with only two candidates, the vote will be a formality; but nominations remain open until 16:00 UTC on 15 November 2019.

Adjust meeting time due to daylight savings change

@joedolson proposed changing the meeting to 16:00 UTC instead of 15:00 UTC, shifting the bug scrub an hour later, as well.

Agreed unanimously.

Update team and contributor badges on profiles

Due to time, postponing until 15 November. Members who need badges given opportunity to state that; will discuss next week, then pass assignments on.

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.

Issue with the starter content in Twenty Twenty not conforming to 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)-ready standards regarding ‘read more’ links.

Argument was that there is no meaningful text because they are demo links. Accessibility team agreed that demo links should have equivalent demo text describing their purpose. None of the content is meaningful, but it should still demonstrate best practices.

Briefly also discussed the problems with all caps text in screen readers.

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

This is an old issue with no final decision. Not all blocks handle focus assignment the same way. Some blocks have clearly defined main editable areas, others don’t. Lack of consistency makes behavior unpredictable.

Couple proposals: Set initial focus on editable region for simple blocks (paragraph, heading) and set initial on focus on whatever wrapper is labeled with aria-label, in other cases. Alternately: do nothing. No artificial movements of focus on any blocks.

Proposed systematically identifying the patterns currently used and trying to identify why a given pattern is used. Created spreadsheet to review blocks and focus movements.

WordPress Accessibility Meeting notes for 25 October 2019

Meeting transcript on Slack

Update on WP 5.3 Progress

@audrasjb reported that reactions from the French 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/. team on admin CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes have been pretty good. Feedback also from Jetpack/WooCommerce teams who’ve fixed a few minor things, but reactions generally positive.

@afercia reported that an un-named large 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 had to fix a few minor glitches related to custom form controls. Also noted that these changes cause some issues with custom selects such as select2 or chosen.

Continuing work on CSS: #48420

Ticket to standardize form control heights and alignments. Patch already exists, but didn’t make it in time for RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge.. These problems have existed since WP 3.8; in WP 3.7 form controls were aligned consistently.

Need some feedback from design to make decisions about inconsistent border radii and 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/.

Agreed to schedule this for 5.4-early, with the possibility that we’d try to push it into 5.3.1.

Update on 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) at WCUS

@nataliemac Reported that @rianrietveld and @nrqsnchz would be helping her in her workshop, which is just finishing up prep.

@nrqsnchz reported that he’s got a plan for format and activities at the contributor table. @nataliemac will also be at the contributor table.

Proposal: cancel team meeting for 1 November

We’ve routinely cancelled meetings that occur during WCEU or WCUS, and we’ll do that for this date as well. Many members would be unable to attend.

Proposal: Change team reps at meeting 8 November

Team reps haven’t changed since October 2018; we’ll plan to vote in reps at meeting on 8 November. @audrasjb will make a post to announce this. Existing reps are still eligible to run; there are no term limits.

Open Floor

@afercia would like to remove Segoe UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing. from the system fonts stack per #48423. Reasoning: Segoe UI has significantly different leading boundaries from other fonts, creating layout issues in vertically centered contexts like input fields.

Agenda for Accessibility Team Meeting for 25 Oct 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 25 October 2019 at 15:00 UTC.

  • Update on WP 5.3 RC2.
  • Continuing work on admin CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. (#48420)
  • Accessibility at WCUS update
  • Proposal: Cancel meeting for Nov. 1, 2019 due to WCUS
  • Advance notice: Proposal to discuss team representatives for the next year at Nov. 8th, 2019 meeting. If you have thoughts on the topic or interest being a team representative, please plan on attending that meeting.

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

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

Agenda for Accessibility Team Meeting for 8 November 2019

Note: there will be no 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 1 November 2019.

This is the proposed agenda for the weekly accessibility team meeting on Friday 8 November 2019 at 15:00 UTC.

  • Discuss & Elect Accessibility Team representatives for next year.
  • Update Team & Contributor profile badges (last updated 12 April 2019).
  • WCUS report
  • WordPress 5.3: pre-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 comments & status.

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

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

WordPress Accessibility Meeting Notes for 27 Sept 2019

Meeting transcript on Slack

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

31 open tickets in 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) focus remaining. There are a total of 138 open tickets in the 5.3 milestone. 6 tickets relating to contrast and focus have been reopened for continuing work. 32 tickets in the accessibility focus have been fixed.

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 link focus style

After the focus and contrast changes, the link focus style is a dotted outline. This is a regression against the previous 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., which used a blue glow focus. Discussed options and agreed that switching to a solid outline and adding and outline offset of 2 pixels will improve. Also noted that the admin nav menu is using the same color as the main focus, needs to be reversed.

This change will also need to be ported to GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/, and that may not be able to happen by 5.3.

Off-agenda: discussion on whether we have time to complete changes.

@karmatosed raised a question whether we should focus on moving continuing changes to 5.4 rather than attempt to complete this for 5.3

After discussion, generally agreed that the continuing changes for focus and contrast are minor tweaks, and while there are a large number of tweaks, we should have time to complete them.

Noted that while release candidateRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. status closes trunk to new enhancements, tweaks to the contrast changes are bugs, and can continue through the RCRelease Candidate A beta version of software with the potential to be a final product, which is ready to release unless significant bugs emerge. stage.

Next accessibility bug scrub

Next bug scrub will happen on Tuesday 1 October 2019 at 16:00 UTC in the #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 Status

Twenty Twenty has 9 accessibility labelled issues awaiting attention. @poena raised the menus as the biggest concern, needing review. There’s a PR by @acalfieri waiting to land on the menus – we’ll take a look at it after this is finished.

New EU accessibility standards

Note: on 23 September 2019, the first stage of the European Union directive on accessibility of websites and mobile applications came into force. This stage requires all public sector new websites to be accessible. Existing websites have until 23 September 2020 to be made accessible; all public sector mobile apps have until 23 June 2021.

The EU directive uses WCAGWCAG WCAG is an acronym for Web Content Accessibility Guidelines. These guidelines are helping make sure the internet is accessible to all people no matter how they would need to access the internet (screen-reader, keyboard only, etc) https://www.w3.org/TR/WCAG21/. 2.1 at level AA as their reference for a harmonized standard.

After WordPress 5.3, we will discuss updating the WordPress accessibility standards to WCAG 2.1. This was last discussed in October 2018, and was inconclusive.

WordPress Accessibility Meeting Notes for 20 Sept 2019

Meeting transcript on Slack

Open Floor

There was no set agenda for this meeting.

The meeting opened with a discussion of ticket #30180. The ticket, while not of itself a crucial task, was a kicking off point for a deeper conversation about trying to work more effectively across teams.

This was a complicated conversation, so in this summary I aim to do my best to convey the essence of the conversation, primarily focusing on the experience from within 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. For a detailed picture, please read the meeting transcript.

The overall point was the difficulty the accessibility team in specific – and all teams in general – have had in making progress on tasks that fall across other team’s responsibilities. This is particularly difficult in the more specialized areas of code, such as the Media Library, where specific knowledge of the inner workings are more rare.

The problem we would like to solve is, at root, the challenge of balancing goals with labor in a realistic manner. We, as a team, have very limited time that can be committed to any given task as well as having expertise primarily in accessibility, which may not benefit us mechanically when working in a specific idiosyncratic technology. To help meet goals, we have tried to work with other teams to delegate responsibility on tickets to people with more specialized experience, while remaining available to consult on the results.

The experience we have had with this has been poor, leaving us feeling that our only ability to accomplish goals is the technical tasks we have the bandwidth to complete ourselves. While many people do step forward and help, this doesn’t result in an overall feeling of forward momentum.

Among the challenges shared are the fact that many contributors to the project cannot plan their time effectively due to the lack of a structure 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. schedule. While employees of a company will have their hours structured such that they can dedicate the necessary time to a project after that project is scheduled, voluntary contributors inevitably have other responsibilities and commitments. Short notice of a release schedule does not allow those contributors to arrange their availability such that they can contribute in a healthy manner.

The meeting discussed four separate major challenges:

  1. Meeting specific goals for the accessibility tickets planned for WordPress 5.3.
  2. Communicate more effectively across teams.
  3. Component maintainence priorities.
  4. Release scheduling and the budgeting of goals over time.

It is important to us, as a team, to state that this is a problem we see throughout the WordPress project, and is not unique to this release or to our team. We don’t feel that these problems reflect individual failures; it’s the result of a systematic failure stemming from a lack of collaborative processes and insufficient opportunity to plan during the times between releases.

Better long-term planning and better release schedule pre-planning to set goals and define the capabilities across teams would be a critical step in making each team be more capable of meeting their individual goals.

The Accessibility Team would like to continue to move forward to work across teams to make this a better experience. We’re continuing to explore ways to improve the process through cross-team collaborations and shared meetings, and hope that we can all collaborate more effectively with improved processes.