Add Accessibility Coding Standards

I would move 'Hide Content properly to a page in the Accesible coding standards guide. I would go further and move Accessible Methods for Hiding Content to that page. At least that is what I am thinking right now. It is only a suggestion and needs some more thought.

I would tend to agree with this. Looking one level up at https://www.drupal.org/docs/accessibility → , the only page that stands out to me there is the "Hide Content Properly" page, when placed next to the other sub-pages in that section. It is more of a one-off recipe, and I'd want to be looking for a more well organized repository of recipes (eg as part of Coding Standards). I think this could be covered by adding a link to the accessibility coding standards from the top level accessibility docs page, and moving the content on "Hide Content Properly" into the Accessibility Coding Standards.

I would also want to see way more code snippets, decorated with an appropriate level of explanation. No opinion on how long the page should be versus splitting things out into sub-pages. I guess thats a separate topic that could be had once more example code snippets are added?

Maybe there should be a sub-section in the Coding Standards that goes into detail about the accessibility coding affordances and best practices that Drupal provides out of the box: like visually-hidden class, like using semantic html for landmarks when possible, like how to get a unique id (in preprocess and twig template for components that use aria-labelledby attribute.

I think we should break up the suggested page into sub pages. This will make it easier to maintain in the long run. As the pages grow they become hard to navigate and splitting them up takes a fair bit of work and can lose history. I'd like to prevent that.

I am thinking along these lines:

Accessibility (Guide)
With the following sub pages

• Keys goals. - put this on the Accessibility guide. But may need tweaking as the description is limited to 1000 chars. If that doesn't work then a new page.
• Technical Standards - This is repeating information on Accessibility core gate → . Should we change the core gate document to link to this new section?
• Best Practices - new page
• Implementation - a new page, change title to 'Accessibility coding standards'. Still need to discuss the 'hidden content property;
• Testing your work - a new page, change title to 'Testing'.

I'm absolutely in favour of adopting these principles, but they're not coding standards. Coding standards are to do with how the source code is written and laid out. These are to do with how Drupal functions for users.

How about calling the page "Accessibility Requirements" instead of "Accessibility Coding Standards"? They are more akin to functional requirements.

Agree with @quietone in #9 regarding linking from the Accessibility core gate to here (or vice-versa):

Technical Standards - This is repeating information on Accessibility core gate. Should we change the core gate document to link to this new section?

Currently, the pages are out of sync. This document states WCAG 2.1 AA, Accessibility core gate states WCAG 2.2 AA.

Sorry, I mistook this page on Drupal accessibility → as the core gate.

That page says:

The Drupal Accessibility Team and project governance will follow the latest recommended release of the WCAG guidelines (WCAG 2.2 AA).

This needs to be converted to the new coding standards issue template. That will including adding proposed text.