WebA11y Slack Community
When meeting with a vendor for the first time, we often recommend that vendors join the WebA11y Slack community as there are industry experts and plenty of resources for vendors either starting their accessibility journey or that need to mature their accessibility skills. The WebA11y Slack community is by invitation only and has over 15,000 members. The Digital Experience team can provide vendors with access to the community.
Aria
Vendors often use aria-label incorrectly to add additional information to buttons and labels. It should only be used to provide the accessible name, not a detailed description of the interactive element. Here are two good articles to share with vendors, one covering how adding a description to an aria-label can create issues for speech recognition users and the other around privacy issues that can happen using aria-label to provide additional context:
Card Design
Card designs often fail to account for screen reader, keyboard only, and text-to-speech software. We recommend using the Card design that Scott O'Hara provides as it separates all the content on the card so that the Heading and border of the card can be used to activate a card link, while any content in the card that provides a description is not part of the interactive element, which allows users to select specific content within the card and provides screen reader users with a better listening experience as they don't have to hear all the content in the card at once.
Notifications
GitHub's accessibility team has provided guidance on what to use instead of Toasts:
Overlays
Overlays are a privacy, security, and accessibility legal risk as companies try to use them to fix the accessibility of their products with the injection of one line of code from an external third party company. They do not actually work, can impact the actual security of data, and violate privacy laws.