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/12).
+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: 'Styleguide'
+weight: 5
+---

pages/docs/community/styleguide/accessibility.md

@@ -0,0 +1,46 @@
+---
+title: Accessibility
+description: This style guide explains how to include accessibility in 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.
+
+### Language
+- Be clear and concise when writing. Avoid the use of complex language or technical jargon. For example, instead of using "*MQTT Server Binding*," it could be simplified to "*Protocol-specific information for an MQTT server*," or "*WebSockets Operation Binding*" can be explained as "*Protocol-specific information for WebSockets operation*."
+- 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 upon the first use in your documentation, and always spell out any signs or symbols.
+- Structure your text in a uniform format by maintaining consistent structure throughout your docs. Accurately provide clear and concise descriptions of AsyncAPI concepts and elements as referenced throughout the documentation. 
+
+### Links
+- Use descriptive and meaningful link text. For example, do not use phrases like *click here* or *follow this link* instead use *see*.
+- Make sure your links or URLs are valid and redirect to the correct destination.
+- Use internal links when referring to a section within the same documentation. External links, on the other hand, should be utilized when referencing additional resources from different websites.
+- When using external links, ensure your referencing information is relevant to your documentation. If you're referring to external resources or documentation, please ensure they meet the appropriate standards for AsyncAPI.
+
+### Multimedia
+- When adding alt text, providing clear and descriptive information is essential. Avoid using generic terms like "*diagram*," "*image,*" or "*code*", and instead provide specific details such as "*Diagram of a server concept*" or "*Code snippet showing CLI usage*".
+- Always use text rather than images, unless necessary. For instance, when explaining complex technical concepts, images convey information better. 
+- Use WebP instead of PNG, SVG, 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.
+
+### User Interface (UI)
+- Use the correct terminologies for UI elements. Avoid using phrases like "*click here*" or "*this button*", and instead opt for descriptive labels such as "*next button*" or "*Go back*". This will allow users to understand the functionality of each UI element better.
+- Format tables correctly and keep the text within the grid. This involves using table headers and row/column headers. Make sure tables are user-friendly, easy to navigate, and understandable.
+-  Add icons to describe a function. Use the aria-label attribute when unsure of the icon name. This attribute provides a text alternative to elements that lack accurate descriptions.
+
+## Colors
+- It is important to choose color contrasts that ensure user-readability.
+- Diagrams and images must always [follow and respect the accessibility rules](https://webaim.org/resources/contrastchecker/).