Description: Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s). Smart Window is a new AI-assisted browsing surface within Firefox that helps users complete tasks more efficiently by providing contextual suggestions, summaries, and actions based on the current page or user intent. Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change. All of our design work is in this Figma file: https://www.figma.com/design/5KuePTGmOEUFyCHBHCsGim/AI-Mode-%E2%80%94%C2%A0MVP-Scope-Design?node-id=23825-20&t=xRmStzJp5tONWO3P-1 How do we test this? If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc. How do we test this? 1. Setup: Enable Smart Window via feature flag or preference (e.g., browser.smart_window.enabled = true) Ensure the user is in a supported build/channel 2. Triggering the UI: Click the Smart Window toolbar button (or use keyboard shortcut if available) Alternatively, invoke via right-click/context menu (if implemented) 3. Test scenarios: Open Smart Window on a content-rich page Enter a query in the input field and submit Navigate through generated responses Use any available action buttons (copy, regenerate, etc.) Interact with suggested prompts 4. Accessibility-specific testing: • Navigate the entire UI using keyboard only (Tab, Shift+Tab, arrow keys, Enter, Escape) • Use a screen reader (e.g., NVDA, VoiceOver) to: Read input field, buttons, and generated content Verify announcements for dynamic updates (AI responses) • Test focus management: Focus moves into the panel when opened Logical focus order across elements Focus returns appropriately when closed • Check for: Proper labeling of controls Role semantics for dynamic content regions Announcements for loading and completion states When will this ship? Firefox 150, with accessibility improvements hoping to land in 151. Tracking bug/issue: Design documents (e.g. Product Requirements Document, UI spec): Engineering lead: Ed Lee Product manager: Jolie Huang The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible: https://wiki.mozilla.org/Accessibility/Guidelines Please describe the accessibility guidelines you considered and what steps you've taken to address them: WCAG AA, tried where possible on the frontend to write semantic markup and general best practices. Describe any areas of concern to which you want the accessibility team to give special attention: Looking for a comprehensive but broad testing of the product from onboarding to chatting with the assistant to using memories, etc.
Bug 2024316 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Description: Please provide an explanation of the feature or change. Include a description of the user scenario in which it would be used and how the user would complete the task(s). Smart Window is a new AI-assisted browsing surface within Firefox that helps users complete tasks more efficiently by providing contextual suggestions, summaries, and actions based on the current page or user intent. Screenshots and visual UI specs are welcome, but please include sufficient accompanying explanation so that blind members of the accessibility team are able to understand the feature/change. All of our design work is in this Figma file: https://www.figma.com/design/5KuePTGmOEUFyCHBHCsGim/AI-Mode-%E2%80%94%C2%A0MVP-Scope-Design?node-id=23825-20&t=xRmStzJp5tONWO3P-1 How do we test this? If there is an implementation to test, please provide instructions for testing it; e.g. setting preferences, other preparation, how to trigger the UI, etc. How do we test this? 1. Setup: Enable Smart Window via feature flag or preference (e.g., browser.smartwindow.enabled = true) Ensure the user is in a supported build/channel 2. Triggering the UI: Click the Smart Window toolbar button (or use keyboard shortcut if available) Alternatively, invoke via right-click/context menu (if implemented) 3. Test scenarios: Open Smart Window on a content-rich page Enter a query in the input field and submit Navigate through generated responses Use any available action buttons (copy, regenerate, etc.) Interact with suggested prompts 4. Accessibility-specific testing: • Navigate the entire UI using keyboard only (Tab, Shift+Tab, arrow keys, Enter, Escape) • Use a screen reader (e.g., NVDA, VoiceOver) to: Read input field, buttons, and generated content Verify announcements for dynamic updates (AI responses) • Test focus management: Focus moves into the panel when opened Logical focus order across elements Focus returns appropriately when closed • Check for: Proper labeling of controls Role semantics for dynamic content regions Announcements for loading and completion states When will this ship? Firefox 150, with accessibility improvements hoping to land in 151. Tracking bug/issue: Design documents (e.g. Product Requirements Document, UI spec): Engineering lead: Ed Lee Product manager: Jolie Huang The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible: https://wiki.mozilla.org/Accessibility/Guidelines Please describe the accessibility guidelines you considered and what steps you've taken to address them: WCAG AA, tried where possible on the frontend to write semantic markup and general best practices. Describe any areas of concern to which you want the accessibility team to give special attention: Looking for a comprehensive but broad testing of the product from onboarding to chatting with the assistant to using memories, etc.