[Tracking issue] Enhance accessibility-ready guidelines with classic vs. block theme information and examples how to achieve the guidelines #332

• I've checked the existing issues for this change

URL
Page URL: https://wpaccessibility.org/docs/accessibility-ready/ and all subpages

Title
Guidelines for the WordPress accessibility-ready tag, and all subpages

What Needs Editing?
While working through the new accessibility-ready theme guidelines I noticed that the guidelines explain the what and why, but not how to implement any of the requirements. While I understand that the guidelines have been written with the testing process in mind, I think it would be helpful to add technical details on how to implement the requirements for both the tester and the theme developer who might have to fix these things.

For example regarding examples, the Skip to content links are a good example. While in classic themes you need to manually add them to the templates, for block themes it is as simple as adding a group around the Content block and setting the group to use the <main> element and WordPress itself will generate a skip link as a main element is found.

Under the Meaningful landmark roles and names section, from a developer perspective it is not clear what to actually do in block themes, especially as additional attributes cannot be added to the elements. My understanding is that it's sufficient enough to use the appropriate HTML tags like header, footer, main etc. but the guidelines do not clarify that.

Another example would be that some things are not applying to block themes anymore as things are handled by Core, labelled form fields could be one if a theme does not add any additional form elements, or the navigation-widgets mentioned under Meaningful landmark roles and names.

In the theme testing workshop held by Equalize Digital on May 21st, an attendee raised an issue with a theme she was testing, as she tried to assign the menu locations but couldn't, as the theme she tested was a block theme and not a classic theme. Block themes work differently than classic themes, so there should be different testing instructions, especially for those who are new to the testing process.

With this ticket I want to start the discussion about how we can implement these information alongside the requirements. Pinging @joedolson to connect the dots for the questions I asked in Slack and in the workshop :)