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:

• 13 are closed as fixed
• 7 are still open

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