Which accessibility technique is used to assist with dynamic content when semantic markup alone is insufficient?

• A. CDN caching
• B. ARIA where necessary
• C. DNS over TLS
• D. Token-based authentication

Answer: (B)

When content changes dynamically and native HTML semantics don’t cover it, you need a way to explicitly communicate those changes to assistive technologies. ARIA where necessary provides attributes that describe roles, states, and live updates, so screen readers understand what’s happening and how to interact with the element. This is used to fill gaps where the built-in HTML vocabulary falls short, especially for complex widgets, dialogs, or content that updates without a full page reload. For example, using aria-live lets updates in a region be announced to the user, aria-expanded indicates whether a collapsible section is open, and appropriate roles (like role="dialog" or role="button") help AT convey the element’s purpose. The key practice is to prefer native HTML semantics first and only add ARIA attributes when needed to convey information that HTML alone cannot. The other options don’t address accessibility for dynamic content: CDN caching is about performance, DNS over TLS is about network privacy, and token-based authentication is about security.