Tag Archives: 5-3

Jb Audras 11:46 am on September 28, 2019
Tags: 5-3   

WordPress 5.3: Accessibility focus progress report

For reference, full WordPress 5.3 release schedule is available here.

TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. tickets progress reports and next steps

For now, milestone 5.3 contains 63 accessibility focused tickets:

  • 32 tickets are closed as fixed
  • 31 tickets are still open, distributed as follows:
    • 23 defects/bugs
    • 8 blessed tasks/enhancement, reopened for iteration during 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. cycle

For easy reference, all admin interface CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site. changes are now grouped under the “5-3-admin-css-changes” keyword.

Next steps

  • Tuesday 1st, October:
    • Extra bug scrub scheduled at 16:00 UTCStart to punt defects/bugs without enough progress or still waiting for patch/testing/feedback
  • Friday 4, October: bug scrub and weekly meeting
  • Thursday 10, October (5 days before 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. 1):
    • Milestone should be cleared
    • All the approved changes should be ready for release

Any help on the remaining tickets is welcome, including testing current patches. Discussion about tickets/patches/current implementation can happens at any time on the #accessibility channel in 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).

Twenty Twenty 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) focused issues

For now, Twenty Twenty has 20 accessibility focused issues:

Any help on the remaining issues is welcome.

+coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
+make.wordpress.org/core

#5-3

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

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: 5-3, ,   

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: 5-3,   

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 8:00 pm on September 1, 2019
Tags: 5-3, , core-media,   

Accessibility Team Meeting Notes: 30 August 2019

Meeting transcript on Slack

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

There is 66 accessibility focused tickets in milestone 5.3:

  • 10 are fixed
  • 56 still need to be fixed

To help them moving forward, two additional bug scrubs are scheduled, on Tuesday 3 September 2019 at 15:00 UTC and Tuesday 10 September 2019 at 15:00 UTC.

@afercia noted that some of those tickets are close to commit. Andrea will try to commit some of them in the next days.

@joedolson won’t be able to address his own tickets until 14 September.

@anevins is going to update the #core-media tickets spreadsheet to highlight media tickets that still need some work.

Assign owners for tickets slated into WordPress 5.3 milestone

@abrightclearweb asked what ticket owners are supposed to do exactly.

@anevins: “They make sure the work gets done by either assigning the work to a practitioner (comes with pretty pleases) or by doing it themselves. They just drive the work forward.”

@joedolson: “it can including writing the patch, but doesn’t need to.”

@abrightclearweb took ownership on #47477. @kjellr will also help on that ticket if needed.

For further informations about testing a patch, see the related core handbook page. However, that assumes contributors have a working development environment. Patch can also be tested directly by applying the patch manually. @joedolson also shared a generic document on creating and applying patches (not about WordPress, but it would work).

At the moment this summary is written, there is still 10 tickets without owner in milestone 5.3. Any contributors are welcome to ask for ownership in 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) 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.

Open floor

The accessibility team discussed ticket #47149. Some comments were added in the ticket.

@afercia noted aria-controls shouldn’t be used anymore and quoted a tweet by Steve Faulkner:

In short, JAWS was the only 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 to actually use aria-controls and the implementation was just confusing. An other post was also quoted for further informations about aria-controls.

@audrasjb changed the initial 5.3 additional bug scrubs time from 14:00 UTC to 15:00 UTC to make it easier for US contributors.

#5-3, #bug-scrub, #tickets

Jb Audras 5:17 pm on August 2, 2019
Tags: 5-3, ,   

Accessibility Team Meeting Notes: 2 August 2019

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/: Support Navigation and Edit Mode

For reference, see the related pull request on Gutenberg GitHub repository.

The idea is to use tabs key to provide a way to navigate between blocks with the keyboard (navigation mode). Hitting enter switch to edit mode (you can edit 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. you navigated to). Hitting escape switch back to navigation mode.

All meeting attendees agree that this is a good improvement. It would be necessary to be extensively tested by as many persons as possible, including users of assistive technologies.

The next Gutenberg 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 release is planned for August 12th. 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 publish a call for testers with some testing scenarios to test this big improvement.

Improving the Accessibility Team feedback on Gutenberg issues and pull requests

There is a need to follow Gutenberg development on both GitHubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/ and 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/. (in coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.-editor channel), and @afercia is currently spending a lot of time to follow it’s development, sending issues and reviewing pull requests.

As @afercia said: As of today there are 37 Gutenberg issues and pull requests with the “Needs Accessibility Feedback” label. The Accessibility Team need more persons able to follow that closely.

@nataliemac volunteered to help monitoring the “Needs Accessibility Feedback” label on Gutenberg GitHub Repository.

The Accessibility Team will discuss the possibility to find ways to have sponsored contributors (even a couple hours a week would be a great sponsorship!) during the next weekly meeting.

WP Accessibility Day – organizing team & next steps

Reminder: it was previously decided to evaluate the possibility to organize a dedicated WordPress global accessibility event, like polyglots do with WordPress Translation Day (WPTD).

The idea is to organize a 24-hour virtual event all around the world with some video conferences and focused on contributing to WordPress accessibility.

A couple of weeks ago, a spreadsheet was shared so Accessibility team contributors could sign up to be involved in this organizing team.

A dozen people signed up to the organizing team: @audrasjb, @joedolson, @nataliemac, @SergeyBiryukov, @bamadesigner, @gianwild, @bdeconinck, @jaymanpandya, @kevinbazira, @robin2go, @foucciano and @ryokuhi 🎉🎉🎉

The next step is to discuss the main focuses of the event and to divide the roles between the organizing team.

Feedback on Theme Review Team’s post about supporting keyboard navigation

For reference, see the related post drafted by @poena.

@audrasjb raised a missing item: focus order that should match visual order.

If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. (Level A)

Source: Web Content Accessibility Guidelines 2.0

@nataliemac added the post should include a warning about not relying on overuse of tabindex to accomplish this.

@afercia raised another item: there is a need to clarify that the native browsers outline can be removed but only if an alternative, like an accessible focus style, is provided.

@anevins: Theme authors should also be encouraged to use the Accessibility support forum if they get stuck.

Openfloor

During the next weekly meeting, the Accessibility Team will assign owners for the 53 tickets in the 5.3 milestone.

#5-3, #gutenberg, #wordpress-accessibility-day