🎨 Palette: Improve Drop Area Toggle Accessibility and Tooltips on WelcomePage - #348
🎨 Palette: Improve Drop Area Toggle Accessibility and Tooltips on WelcomePage#348D3M-Sudo wants to merge 5 commits into
Conversation
Synchronize Gtk.AccessibleState.EXPANDED state and tooltip on WelcomePage's drop_button based on the revealed state of the drop area. Initialize state on widget load and reset it on cleanups. This provides proper feedback to screen readers (similar to aria-expanded) and enhances overall UX.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
Synchronize Gtk.AccessibleState.EXPANDED state and tooltip on WelcomePage's drop_button based on the revealed state of the drop area. Initialize state on widget load and reset it on cleanups. This provides proper feedback to screen readers (similar to aria-expanded) and enhances overall UX. Fix the welcome page widget test to handle translation lookup gracefully in the test assertions.
Synchronize Gtk.AccessibleState.EXPANDED state and tooltip on WelcomePage's drop_button based on the revealed state of the drop area. Initialize state on widget load and reset it on cleanups. This provides proper feedback to screen readers (similar to aria-expanded) and enhances overall UX. Fix the welcome page widget test to handle translation lookup gracefully in the test assertions using robust partial/localized matching to avoid locale-specific discrepancies in CI.
Synchronize Gtk.AccessibleState.EXPANDED state and tooltip on WelcomePage's drop_button based on the revealed state of the drop area. Initialize state on widget load and reset it on cleanups. This provides proper feedback to screen readers (similar to aria-expanded) and enhances overall UX. Fix the welcome page widget test to handle translation lookup gracefully in the test assertions using robust partial/localized matching to avoid locale-specific discrepancies in CI. Add explicit verbose print diagnostics to test_drop_button_toggle.
Synchronize Gtk.AccessibleState.EXPANDED state and tooltip on WelcomePage's drop_button based on the revealed state of the drop area. Initialize state on widget load and reset it on cleanups. This provides proper feedback to screen readers (similar to aria-expanded) and enhances overall UX. Fix the welcome page widget test to handle translation lookup gracefully in the test assertions using robust partial/localized matching to avoid locale-specific discrepancies in CI. Add explicit verbose print diagnostics to test_drop_button_toggle. Add verbose traceback reporter to conftest.py's exit handler to bypass os._exit() report suppression.
💡 What:
Added dynamic synchronization of
Gtk.AccessibleState.EXPANDEDand tooltips ondrop_buttonaccording to the active expanded/collapsed state of the drop area revealer onWelcomePage.🎯 Why:
Buttons that toggle collapsible content are more intuitive when they inform screen readers of their state (using the GTK equivalent of
aria-expanded). This makes the interaction significantly more accessible.♿ Accessibility:
Dynamically updates
Gtk.AccessibleState.EXPANDEDand tooltips (Drop image here/Hide drop area) to keep assistive technologies in sync. Updated existing tests to verify tooltip behavior on interaction and reset.PR created automatically by Jules for task 1985093721640091881 started by @D3M-Sudo