You're working on a critical feature release with a tight deadline, but a major accessibility bug is reported in an existing, widely used component. How do you prioritize addressing the bug versus completing the new feature, and what steps do you take to manage stakeholder expectations?

Employ a RICE (Reach, Impact, Confidence, Effort) framework. First, assess the accessibility bug's 'Impact' (severity, legal compliance, user base affected) and 'Reach' (how many users encounter it). Simultaneously, evaluate the 'Impact' and 'Reach' of the new feature. 'Confidence' in solutions for both, and 'Effort' required. Prioritize based on RICE score, typically favoring critical accessibility issues due to legal and ethical implications. Communicate the RICE analysis to stakeholders, explaining the trade-offs and proposing a revised timeline for feature release, potentially with a phased approach or a temporary workaround for the bug.

I'd apply a modified RICE framework to prioritize. First, I'd immediately assess the accessibility bug's severity and scope: Is it a WCAG violation? How many users are affected? What's the legal/reputational risk? This determines its 'Impact' and 'Reach'. Concurrently, I'd evaluate the new feature's 'Impact' (business value, user benefit) and 'Reach'. I'd then estimate 'Effort' for both. Critical accessibility bugs often take precedence due to legal compliance and ethical obligations, even over high-value features. For stakeholder management, I'd communicate transparently, presenting the RICE analysis and explaining the rationale for prioritization. I'd propose a revised timeline, suggesting a hotfix for the accessibility issue first, followed by the feature. If the feature is truly time-sensitive, I'd explore a temporary workaround for the bug or a phased feature rollout, ensuring all parties understand the trade-offs and revised expectations.