Update a11y guidelines

[stevepiercy]

@plone/volto-accessibility please review.

---

📚 Documentation preview 📚: https://volto--6361.org.readthedocs.build/

Docs review/ updates to make

• We should use https://volto.demo.plone.org for testing
• Review tool recommendations
• Discuss contrast
• Discuss Screen-reader testing
• Should we use "tap", "press", or "click" in language strings for that gesture across desktop and mobile devices?
• How should we denote keystrokes in language strings across operating systems? For example, in MyST:

  {kbd}`Return`
  

[netlify]

✅ Deploy Preview for plone-components canceled.

Name	Link
🔨 Latest commit	efe2ce3
🔍 Latest deploy log	https://app.netlify.com/sites/plone-components/deploys/67c4b9a9788905000874a9ed

[stevepiercy]

@Wagner3UB @JeffersonBledsoe @ichim-david would y'all please submit a PR review? Thank you!

[ichim-david]

@stevepiercy looks good, it will have to wait for the merge of the tests done at Salamina sprint in order to create the core/a11y folder. This way your statement on where to place tests is valid.

[stevepiercy]

@ichim-david @sneridagh @Wagner3UB @JeffersonBledsoe is the blocker complete, so we can merge this?

[github-actions]

Hi There! 👋

We haven't seen any activity on this pull request in a while 😴, and we want to make sure that it's still relevant. Please let us know by:

• adding a comment about what needs to be done next 💬
• updating its status and other labels 🏷️

Otherwise close this pull request. 🧹

[thet]

LGTM. Also the test location for a11y tests is in the meantime on the right place.

[thet]

@stevepiercy I rebased this PR on the current main branch. IMO it's good to merge.

[stevepiercy]

re-ping @ichim-david @sneridagh @Wagner3UB @JeffersonBledsoe @pnicolli for final review.

[Wagner3UB]

@stevepiercy These are my suggestions, just some simple ones to start with. We could talk all day about a11y best practices, but I think these are a great first step. Feel free to adapt or condense the content as you see fit.

Thank you for the collaboration, this is a huge step forward!

[stevepiercy]

@Wagner3UB sorry for the long delay. I've added your suggestions, but reformatted the items into definition lists, as those made more sense semantically than a subsection heading. Please let me know. Thank you!

[read-the-docs-community]

Documentation build overview

📚 volto | 🛠️ Build #33855128 | 📁 Comparing 3a24167 against latest (983f78e)

  🔍 Preview build  

1 file changed

± contributing/accessibility-guidelines.html

[Wagner3UB]

@stevepiercy Don’t worry about the time, you did a fantastic job. Thank you!

There’s just one small piece that may have slipped through unnoticed. Other than that, everything looks good to me.

I’ll keep this file on my end and add it to the accessibility meeting notes. I think we can make it even better going forward.

[stevepiercy]

@Wagner3UB do you mean this? 😉

https://github.com/plone/volto/pull/6361/changes#diff-ca452a13f79ce27298dba68a1d306365f5b472b89b2662f602e3a5ca4deb48ddR61-R75

[Wagner3UB]

@stevepiercy LGTM, and thank you again