This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
What is the primary purpose of the accessibility tree in relation to screen readers?
To provide extra visual elements for low-vision users
To represent interactive elements for the user interface
To convey information about the structure and content of a web page to screen readers
To enhance the appearance of a web page
Which ARIA attribute would you use to provide a text alternative for an icon in SVG format?
aria-live
aria-label
aria-hidden
aria-labelledby
What is the role of the alt attribute in an <img> tag?
To provide extra styling to images
To add captions to the image
To provide a text alternative for the image
To change the size of the image
Which of these tools can be used for manual testing of screen reader support?
Accessibility Insights for Web
Windows Narrator
Browser Debugger
Accessibility Inspector for Mac
What is the key difference between custom controls and semantic controls in terms of screen reader support?
Custom controls automatically support screen readers without more coding.
Semantic controls require manual ARIA attributes to be accessible.
Custom controls may need ARIA attributes and scripting to be accessible.
Semantic controls are inaccessible by default to screen readers.
You must answer all questions before checking your work.
Was this page helpful?
Need help with this topic?
Want to try using Ask Learn to clarify or guide you through this topic?