What is progressive enhancement and why is it critical in UID?

• A. Start with a high-end feature set and degrade for older browsers
• B. It is not necessary in UID
• C. Start with a baseline accessible experience and progressively add features for capable browsers; ensures core functionality works for all users
• D. It means adding features only after user consent

Answer: (C)

Progressive enhancement centers on building a strong, accessible foundation first and then adding enhancements for browsers and devices that can support them. In UID this means designing with semantic HTML, proper structure, accessible navigation, and baseline functionality so every user—even those on assistive tech, low bandwidth, or older devices—can use the interface. Once the baseline works well, you can layer in enhancements like JavaScript-driven interactivity, responsive layouts, and richer media for capable browsers, without breaking functionality for others. This approach preserves core usability, improves performance, and supports inclusivity. For example, a form should submit and be validated with standard HTML and server checks; client-side validation or dynamic UI feedback is added only as an enhancement for users with capable browsers. The other options misrepresent the idea: starting with high-end features and degrading for older browsers undermines accessibility, claiming UID doesn't need it ignores inclusive design, and tying enhancements to user consent changes the purpose.