docs: new accessibility page

pages/docs/community/_section.md

@@ -0,0 +1,4 @@
+---
+title: 'Community'
+weight: 5
+---

pages/docs/community/index.md

@@ -0,0 +1,25 @@
+---
+title: Overview
+weight: 2
+---
+
+## Community: Guidelines and resources around community.
+
+Welcome to AsyncAPI **Community**! Our Community section documents the community guidelines and resources.
+
+<Remember>
+
+## Contribute to the AsyncAPI Community section
+Code isn't the only way to contribute to OSS; Dev Docs are a **huge** help that benefit the entire OSS ecosystem. At AsyncAPI, we value Doc contributions as much as every other type of contribution. ❤️
+
+To get started as a Docs contributor:
+1. Familiarize yourself with our [project's Contribution Guide](https://github.com/asyncapi/community/blob/master/CONTRIBUTING.md) and our [Code of Conduct](https://github.com/asyncapi/.github/blob/master/CODE_OF_CONDUCT.md).
+2. Head over to our [AsyncAPI Docs Board](https://github.com/orgs/asyncapi/projects/8).
+3. Pick an issue you would like to contribute to and leave a comment introducing yourself. This is also the perfect place to leave any questions you may have on how to get started. 
+4. If there is no work done in that Docs issue yet, feel free to open a PR and get started!
+
+### Docs contributor questions
+Do you have a documentation contributor question and you're wondering how to tag me into a GitHub discussion or PR? Never fear!
+
+Tag me in your AsyncAPI Doc PRs or [GitHub Discussions](https://github.com/asyncapi/community/discussions/categories/docs) via my GitHub handle, [`alequetzalli`](https://github.com/alequetzalli) 🐙.
+</Remember>

pages/docs/community/styleguide/_section.md

@@ -0,0 +1,4 @@
+---
+title: 'Community'
+weight: 5
+---

pages/docs/community/styleguide/accessibility.md

@@ -0,0 +1,42 @@
+---
+title: Accessibility
+description: This style guide explains how to include accessibility into the documentation.
+weight: 20
+---
+
+# Accessibility
+
+At AsyncAPI, we strive to make our documentation/content inclusive, accessible, and unbiased to everyone. We encourage all contributors to have diversity and inclusivity in mind when writing. To ensure this, we have provided an overview of general guidelines to follow.
+
+## Language
+- Be clear and concise when writing. Avoid the use of complex language, technical jargon, and verbose explanations.
+- Keep paragraphs and sentences short, simple, and to the point.
+- Always maintain a uniform structure. Use descriptive headings and subheadings to make navigation easy.
+- Use inclusive language and always keep the reader in mind when writing. 
+
+
+## Text
+- Use the appropriate heading hierarchy. H1 is used for the main heading while H2 to H6 are used for subsection headings. 
+- Properly align text for easy readability.
+- Avoid using camel case or any unnecessary fonts and formatting.
+- Define acronyms or abbreviations and always spell out any signs or symbols.
+- Structure your text in a uniform format. 
+
+## Links
+- Use descriptive and meaningful link text. For example, do not use phrases like *click here* or *follow this link* instead use *see*.
+- Always use an external link icon if a link opens up in a new tab.
+- Make sure your links or URLs are valid and redirect to the correct destination.
+
+## Multimedia
+- Alt text must be clear and descriptive. Not more than 50 characters.
+- Always use text rather than images, unless necessary.
+- Use SVG instead of PNG or JPEG. It retains quality.
+- Provide transcripts and captions for video content.
+- Make sure your captions can be translated into various languages.
+- Avoid auto-playing media, always provide controls.
+
+## UI 
+- Use the correct terminologies for UI elements.
+- Format tables correctly and keep the text within the grid.
+-  Use basic HTML for button elements.
+-  Add icons to describe a function. Use the aria-label attribute when unsure of the icon name.