Per :ayeddi - "When the `about:firefoxview` is opened, the screen reader focus jumps to the onboarding callout, which is expected (I assume), but when the screen reader completes reading its content, it proceeds to read the main page content from the middle - from the Colorways section and then to the Recently closed one. This will cause users missing the top of the page, incl. the synced tabs."
Bug 1790382 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.
Per :ayeddi - "When the `about:firefoxview` is opened, the screen reader focus jumps to the onboarding callout, which is expected (I assume), but when the screen reader completes reading its content, it proceeds to read the main page content from the middle - from the Colorways section and then to the Recently closed one. This will cause users missing the top of the page, incl. the synced tabs." See `featureCallout.mjs` for feature callout code.
Per :ayeddi - "When the `about:firefoxview` is opened, the screen reader focus jumps to the onboarding callout, which is expected (I assume), but when the screen reader completes reading its content, it proceeds to read the main page content from the middle - from the Colorways section and then to the Recently closed one. This will cause users missing the top of the page, incl. the synced tabs." - "on MacOS the dialog title is not announced by VoiceOver - the code looks good, so this is likely more general bug?" - "When Close button is activated, the programmatic focus lands inconsistently somewhere on the page to any item that was under the Close button. It is expected that the focus would return to the top of the page, if the user did not navigate the page prior to getting on the onboarding popup. But if the user wandered around, the best place to return the focus would be the last focusable element before the onboarding popup was injected in the DOM or on the topmost element right after it, i.e. when the last popup is dismissed, the focus could be placed on the aside section for Colorways, for instance with the tabindex="-1" on the Independent Voices heading, so the user does not miss any piece of the content after the dismissal" See `featureCallout.mjs` for feature callout code.
Per :ayeddi - "When the `about:firefoxview` is opened, the screen reader focus jumps to the onboarding callout, which is expected (I assume), but when the screen reader completes reading its content, it proceeds to read the main page content from the middle - from the Colorways section and then to the Recently closed one. This will cause users missing the top of the page, incl. the synced tabs." - "on MacOS the dialog title is not announced by VoiceOver - the code looks good, so this is likely more general bug?" See `featureCallout.mjs` for feature callout code.