In building accessible UIs, which practice is recommended?

• A. Use divs for all structure to simplify styling.
• B. Use HTML semantics for structure; style with CSS; add ARIA only when necessary and maintain logical DOM order.
• C. Rely on ARIA roles for semantics instead of native HTML elements.
• D. Place elements out of DOM order to prioritize visuals.

Answer: (B)

Accessible UIs rely on native HTML semantics to convey structure to assistive technologies. When you mark up content with semantic elements like header, nav, main, article, aside, and button, screen readers understand the roles, relationships, and order of the page without extra hints. Styling should be handled with CSS, keeping presentation separate from meaning so the structure remains clear to assistive tech. ARIA should be reserved for situations where native HTML cannot express a needed concept, and you should always maintain a logical DOM order so that the reading and keyboard navigation flow matches what users see on the screen. Using divs for everything strips away meaning, relying on ARIA roles instead of native elements can be fragile and misapplied, and placing elements out of DOM order disrupts accessibility and keyboard usability.