jacob35

Hello Kaushik,

Thank you doing the test. I agree that it seems like a theme issue. In fact, I did some testing with the Blockbase theme earlier today, and it’s appearance and behavior exactly matches your blank test theme. Therefore, there is probably a custom template or styling in Twenty Twenty-One and Twenty Twenty-Two that causes the problem.

I’ll mark this thread as resolved.

Hello Kaushik,

Thank you for the CSS code! On the Storefront test site, I was able to replace background: red; with outline-style: solid;, and now I have a working keyboard focus indicator. Category 1 in my original post is now resolved.

But I’m not sure about Category 2. Is there any way to tell whether that issue lies in the Twenty Twenty-One and Twenty Twenty-Two themes or in the default WooCommerce checkout template itself?

Hello MayKato,

Thank you for the information. That does not seem to be the cause of the issue, though. To test, I added some sample code for radio buttons from the W3C into the “Simple radio button test” post on my test sites. When I tab into the radio button group on this sample page, note that the first option gets highlighted with a square indicator, as shown in this screenshot.

This lets me know that keyboard focus has moved into the radio button group. That is what’s missing from the WooCommerce payment method selection.

My question has been answered in the following topics:

• Will TT1 Blocks be accessibility-ready in the future?
• Is Blockbase an accessibility-ready theme?

Thank you for the helpful information.

OK, thank you.

Hi Carolina,

Thank you for the quick response. Do I understand correctly that while there are no current plans to put the theme through an accessibility review, it still intends to follow WCAG?

Here’s the reason for my concern. I’m starting to build my portfolio website, but I’ll be using it most frequently about a year (or two) into the future. I’m assuming that Full Site Editing will be production-ready by that time, so I’d like to use it to have greater design control. I’m wondering if development is on track for the theme to be production-ready with full accessibility support by that time. (No worries if it won’t be; classic themes are always an option.) Or will TT1 Blocks always be an experimental theme for testing the Gutenberg plugin?

OK, will do. Thank you.