Providing text alternatives for non-text content adheres to which WCAG principle?

Question: Providing text alternatives for non-text content adheres to which WCAG principle?

  • Perceivability
  • Operability
  • Understandability
  • Robustness

Explanation

This aligns with Perceivable because text alternatives make non-text content available in a form that assistive technologies can interpret. HubSpot states that images, icons, videos, and buttons that convey meaning or are interactive should have a text alternative. That allows users who rely on screen readers to access information that would otherwise be available only visually. The requirement is about making content detectable and available to different senses, which is the core purpose of Perceivable. HubSpot Developers

Why the other options are incorrect

Operability relates to using and navigating interface elements, such as keyboard navigation, not to converting non-text content into accessible text. HubSpot Developers

Understandability relates to clarity and predictability of content and interface behavior, not to whether non-text content can be perceived by assistive technology. HubSpot Developers

Robustness relates to compatibility with browsers and assistive technologies, not to providing text alternatives for non-text content itself. HubSpot Developers

Source for verification

https://developers.hubspot.com/docs/cms/best-practices/improve-existing-sites/accessibility

The answer(s) to the question is highlighted in the BOLD text above. You can also find more questions and answers related to the exams on the "HubSpot CMS for Developers II" page.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top