You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For content that has gone under a stringent certification review process having this information displayed on the initial Accessibility Page is important to promote the discover of certified accessible material, instead of having this information buried in the "additional accessibility information".
3rd party certification like LIA and Benetech's GCA (Global Certified Accessible) program have been around for years and is a recognized and trusted to ensure accessibility.
In the section of Conformance if the title has a certifierCredential either the textual information or if applicable an image (logo/stamp) with alt text description of the certification be presented to the user in this section.
The text was updated successfully, but these errors were encountered:
In August 24, 2023 meeting, the group resolved to keep 3rd party certifier information in the main accessibility metadata instead of placing it in additional metadata.
Addressed, see Example 13 in November draft: Conformance statements that meets accepted accessibility standards followed by detailed conformance information
For content that has gone under a stringent certification review process having this information displayed on the initial Accessibility Page is important to promote the discover of certified accessible material, instead of having this information buried in the "additional accessibility information".
3rd party certification like LIA and Benetech's GCA (Global Certified Accessible) program have been around for years and is a recognized and trusted to ensure accessibility.
In the section of Conformance if the title has a certifierCredential either the textual information or if applicable an image (logo/stamp) with alt text description of the certification be presented to the user in this section.
The text was updated successfully, but these errors were encountered: