Which of the following is NOT a typical role of a UI library?

• A. Providing pre-built widgets
• B. Handling layout responsiveness
• C. Replacing all HTML markup
• D. Offering consistency across UI elements

Answer: (C)

A UI library is built to speed up interface development by providing ready-made components, layout helpers, and a consistent design system. It gives you pre-built widgets you can drop in, tools to handle responsive layouts so the UI adapts to different screen sizes, and a cohesive look and feel across all UI elements.

What it does not do is replace all HTML markup. The structure of a web page—the HTML that defines headings, sections, forms, and other elements—remains essential. A UI library typically renders its components into HTML markup or templates, but you still rely on HTML to provide the underlying structure and semantics. Replacing all HTML would remove that structure and accessibility, which isn’t a typical or practical role of a UI library.