Tag Archives: accessibility-ready

joesimpsonjr 6:30 pm on September 22, 2023
Tags: accessibility-ready, ,   

Accessibility Team Meeting Notes: September 15, 2023

These are the bi-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 here or see the full meeting schedule.

Updates from the working groups

Only groups that provided updates are shown below.

Team Updates

General:

  • @joedolson shared that this team scrubbed all of the bugs slated for 6.4. There are a few that will definitely not make it, but 5 of the remaining 16 open tickets are almost ready to go; a couple others are still pretty viable. And there’s a need to test things!

Gutenberg:

  • @annezazu shared this update: Hallway hangout this week: https://make.wordpress.org/core/2023/08/21/hallway-hangout-improving-accessibility-in-the-site-editor/
  • Big convo around the use of inert and exploring alternatives: https://github.com/WordPress/gutenberg/issues/54369
  • Finally, there are two in progress features I want to flag for feedback: Patterns: add categories to user created patterns & Global Styles/Typography: Managing fonts. They are still in progress for 6.4 so great time to test and give feedback! There’s also this recent issue opened: Improve Link Control accessibility.

Media:

  • This team has mostly finished a couple of follow-ups to the admin editor redesign from 6.3, one committed, one pending testing.
  • There are two other issues that still might get completed in this cycle; as well as some ongoing work related to images in 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/.
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.: Provided feedback on the filtering tools being built for the showcase, and there are a bunch of designs being shared in #website-redesign that could stand a look.
  • There are quite a few updates in #website-redesign; look at the posts from Nick Diego for a lot of links;
  • @Nick Diego mentioned that the updates to the Showcase are almost ready for an accessibility review. When it’s ready, he will be sure to reach out to the team.

Themes:

  • @poena shared this update from the Themes team:
  • In the theme Twenty Twenty-Four, there are still templates that have not been completed, so the theme is still not ready for full or final accessibility testing, but it moves very fast, so it might be ready at the time of the meeting. The lead devs mentioned that they will let the accessibility team know when it is ready for testing;
  • The heading levels should be mostly sorted. One template has two H1 headings which is not ideal;
  • The decorative asterisks which are announced by screen readers have not been replaced yet;
  • The footer links have been improved but requires a Gutenberg PR to be merged. Aside: WordPress 6.4 alpha and Gutenberg trunk is recommended for testing. @joedolson shared an open issue on the filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. component:
  • https://github.com/WordPress/wporg-mu-plugins/issues/419 Re: Themes update – While the theme is not ready for full accessibility testing, that doesn’t mean that there’s no room for feedback; just do any testing with the awareness that this is a project in active development. There’s already been quite a bit of accessibility feedback. If @poena can share the Gutenberg PR that needs to be merged, I’d be interested in seeing that.
  • @poena shared this follow-up link https://github.com/WordPress/gutenberg/pull/54418

Open Floor

  1. @joedolson shared that open office hours start Wednesday, September 20th Please spread the word! https://make.wordpress.org/accessibility/2023/09/13/accessibility-office-hours/ The goal here is to help answer people’s questions about accessibility in general terms, disassociated from specific issues or tickets, so that the general understanding of accessibility in the community is raised.
  2. He’s also started a post about the accessibility liaison/allies plan that we discussed at the Community Summit. I’d appreciate some additional eyes on the post: https://make.wordpress.org/accessibility/wp-admin/post.php?post=16274&action=edit. At the moment, I’m planning on letting people set up meetings with me to discuss their team needs – mostly because the logistics of doing that many group meetings would be difficult. However, if anybody wants to join me, I’m happy to invite others.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility-ready, #design

joesimpsonjr 8:11 pm on July 17, 2023
Tags: accessibility-ready,   

Accessibility Team Meeting Notes: July 7, 2023

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

Updates from the working groups

Only groups that provided updates are shown below.

Team Updates

  • Gutenberg: @annezazu who provided this update for the Gutenberg working group: Passing on this post hot off the press: https://make.wordpress.org/core/2023/07/03/real-time-collaboration/ Otherwise, everything is all about 6.3! Trying to triage as much as possible to get issues into the 6.3 board (like this: * https://github.com/WordPress/gutenberg/issues/52254 or this:https://github.com/WordPress/gutenberg/issues/52253). Following the instructions for the Help Test WordPress 6.3 post will go a long way.
  • General: @joedolson shared the following updates for a couple of working groups: Joe committed or punted all tickets scheduled for 6.3 last week. Most remaining open issues are at risk, but punting to 6.4 isn’t the end of the world. On themes, I’ve got @Maja Benke connected to @kafleg to start her working on accessibility ready reviews

Open Floor

  • No updates to share at this time.

  • NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility-ready, #design

joesimpsonjr 10:20 pm on June 16, 2023
Tags: accessibility-ready,   

Accessibility Team Meeting Notes: June 16, 2023

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

Updates from the working groups

Only groups that provided updates are shown below.

All Team Updates

  • Media: @joedolson committed the redesign of the admin image editor earlier this week.

  • General: He has punted a number of tickets to 6.4, but have a significant handful that are ready or nearly-ready to commit.

  • Themes: At WCEU, Joe talked to Maja Benke about taking on the task of reviewing themes for accessibility-ready tags, so she’s going to start getting trained in on that task and will interface with the theme review team to help on that. This is important since the theme review team is low on accessibility knowledge right now.

  • 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/: The site editor needs testing; we’re moving in very close to the end of the cycle, and there are a lot of new features that need some attention. Please install Gutenberg and play with all the new features. Particularly look for any focus losses, controls that aren’t working from the keyboard, or focus moves that should happen and don’t (e.g., opening a modal then not being placed inside it).

  • @sabernhardt shared the following MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. team update: Please review the pull request on 4730.

  • @alexstine shared this update for comment: https://github.com/WordPress/wporg-mu-plugins/issues/405 and for async review: https://github.com/WordPress/gutenberg/issues/51126#issuecomment-1594825674

Open Floor

  • WCEU 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 Onboarding — At 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/. at WCEU, the team onboarded a few additional people to review 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. output & Maja Benke wrote up a draft of a document for us to post to help people know the process they should follow when testing block output. Will document soon.

  • Is it possible to change our meeting time? — Also, Maja Benke requested that we once again consider changing our meeting time – she would like to attend, but our current time is not good for her. And, honestly, our current time isn’t really good for anybody in Europe – Friday evening is just not a great time for people to attend a meeting. We should give this serious thought. Other team members, like @poena, are also routinely unable to attend. Because we have members in the US Pacific time zone, we can’t move a lot earlier reasonably, but we could change to a different day, so that European attendees aren’t having to start off their weekend with a voluntary meeting…

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

#accessibility-ready, #design

joesimpsonjr 6:32 pm on June 15, 2023
Tags: accessibility-ready,   

Accessibility Team Meeting Notes: June 2, 2023

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

Updates from the working groups

Only groups that provided updates are shown below.

Documentation and General Teams

@joedolson has been focused on scrubbing older 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/ issues in bug scrubs; trying to get some of the early concerns re-addressed and establish status updates and has several patches nearing readiness to commit; awaiting some feedback.

Media Team

@joedolson mentioned needing needing opinions on [#50523] (https://core.trac.wordpress.org/ticket/50523). He’s requested feedback from #design and hoping to get it soon.

Themes Team

@joedolson reviewed three #accessibility-ready theme candidates last week, to help the themes team out. Anyone interested in training on how to review, contact Joe.

Open floor

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. Europe is next week and we talked about 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/.. Also talked about WordPress Community Summit and being invited.

NOTE: If you’d like to have a topic added to the agenda for our next meeting, please mention it in the comments of upcoming agenda.

Joe Dolson 9:22 pm on January 21, 2016
Tags: accessibility-ready,   

Updates to WordPress theme accessibility guidelines

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)-ready guidelines for WordPress themes were updated today. There are no explicit changes to the requirements, but the order of the guidelines has been changed so that it corresponds more effectively to how it makes sense to run tests on the guidelines.

Additionally, I’ve added some information on how to run tests for each guideline into the guidelines, so that theme developers are more easily able to find information on how to self-test when they’re creating an accessibility-ready theme.

Review the guidelines.

#accessibility-ready, #themes-2

Joe Dolson 5:41 pm on December 4, 2014
Tags: accessibility-ready   

Theme Accessibility Meeting Notes

We had a great meeting to discuss the future of theme accessibility. You can review the complete transcript of the chat in Slack.

We discussed many of the aspects of what it will take to make 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) a requirement for themes – it’s a long process, but we agreed that this is possible. We started by discussing where the most appropriate place is to publish our kick off article, which is going to give three examples of areas where theme authors can improve the accessibility of their themes immediately. It will be published either on Make/Themes or here on Make/Accessibility, followed by an extensive effort to share in the community.

Next we discussed the fledgling repository for WordPress-specific code examples for accessibility. The repository already exists at GitHub, so it’s just a matter of writing code and organizing it. David Kennedy will take the lead on developing that resource.

Moving on, we discussed how to organize theme accessibility information and advice into the Theme handbook structure. We concluded that a conversation about how that fits in is needed, and I’ll have that with Tammie Lister before we decide exactly what those documents will be, as well as moving the existing Accessibility guidelines around in the theme reviewer’s handbook.

Morten Rand-Hendriksen reviewed the original plan sketched out at the community summit to give people who weren’t there a basic understanding of the conversation.

This brought up a conversation about future handling of the ‘accessibility-ready’ tag and how we should share information in the WordPress theme repository about whether a theme has been reviewed for accessibility. Right now, it’s fairly moot given the small number of themes that have been reviewed, but by the time accessibility becomes a requirement, it will be important to start labeling, to take the onus off end-users to discover whether their theme will allow them to meet their country’s legal requirements for accessibility.

Both these issues will need to be proposed to the theme review team, so we’ll be working on writing a precise proposal that can be taken to that team and be voted on. The important thing with the proposal is clarity.

Finally, we discussed theme reviewer training. I’ll set up a date with Tammie to work through the process with her, but will ultimately need to do something that’s less one-on-one, either through a detailed written document or a video training resource. This training process would be greatly helped by having the code repository fleshed out, so that those code examples are available to reviewers and theme developers.

#accessibility-ready

Joe Dolson 3:39 pm on June 24, 2014
Tags: accessibility-ready,   

Draft guide for accessibility-ready reviewers

To go along with the accessibility-ready guidelines, I’ve been working on a document to help people who want to help perform 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) reviews on themes. This document is targeted at members of the accessibility team who want to help support the review process by checking themes for accessibility.

Please provide comments, so I can edit them into the most helpful guide they can be!

Theme Accessibility Guide for Reviewers

#accessibility-ready, #themes-2

Joe Dolson 9:02 pm on April 15, 2014
Tags: accessibility-ready,   

Update on accessibility-ready theme tag

We’re gradually working the kinks out of the process. There was an oversight in the automated process that added 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)-ready keyword to themes, so that only new themes were automatically getting the keyword, and not updated themes that added it. That’s been fixed, which will improve our ability to note themes that need to go through the review process.

There’s a lot of support for the process, and the theme review team is invested in making this work, but I could use some backup in actually doing the reviews. Even if you don’t have the accessibility background, let me know if you’re interested: I’m happy to provide training to make sure you’ve got the knowledge it takes to do this review.

#accessibility-ready, #themes-2

Joe Dolson 11:14 pm on February 8, 2014
Tags: accessibility-ready,   

Want to participate in reviewing WordPress themes for…

Want to participate in reviewing WordPress themes 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)-ready tag? There’s a tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. keyword for that! Themes awaiting an accessibility-ready review.

#accessibility-ready, #themes-2

Joseph Karr O'Connor 7:14 am on December 5, 2013
Tags: , accessibility-ready, ,   

IRC Meeting: December 4, 2013

Discussion about Analysis of what gets into the alt and title attributes when adding an image into a page/post by @grahamarmfield. Excellent work.

Discussion about what is needed to move Create new tag: accessible-ready @sams suggested that we should find an owner and get it in as soon as 3.9 development opens. He also suggested that we look at the patch in #21442 to see what’s needed.

Though we have had some new recruits to the team in the last week, we are still woefully understaffed compared to the speed, breadth, and depth of WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. development. We will continue to contribute where we can and are looking for more team members with deeper coding skills to help move some of the issues along.

#accessibility, #accessibility-ready, #team-reps, #weekly-meetings