Bugzilla

(In reply to Meg Viar from comment #6)
> (In reply to Negin from comment #5)
> > I believe this is unrelated to the feature callout tour. I've set the tour to complete and used VO to tab through the content and it skips the content that has a `.zap-card` class (which is the synced tabs section that causes the VO to read through the content in a "random way" since it isn't reading over that section).
> > 
> > I believe this is happening because .zap-card is using pseudo element/:before which skips the synced tabs section because it's not focusable. I've verified this by trying to tab through the content and it's not possible to tab/focus in on that section with or without the feature tour being rendered.
> > 
> > I think this bug may be more suited for the firefox view team as I'm not sure how they'd like to proceed with that decorative element/how they'd like to make it more accessible?
> 
> Which OS  / screen reader are you using? When I use the built in screen reader on Windows 11, it starts reading the Firefox View page, then switches to the callout when it appears, and then resumes reading the page where it left off (so I don't actually see the behavior described in this bug). One issue I _do_ see is that it then reads the Feature Callout screen content a second time when it reaches it in the page after resuming reading page content.
> 
> On MacOS when tabbing through Firefox View with Voiceover the content of the tab pickup box is _not_ read (likely for the reasons you described above @negin). 
> 
> :ayeddi originally reported this issue in bug 1788253. Anna, do you recall which OS/screenreader you used when you saw the issue described in this bug?

as I recall it, the reading order behavior was buggy on both WinOS+NVDA and macOS+VO and, as you mentioned above, the macOS-specific issue was separate issue observed during testing, not related to the reading order of the callout vs the page.

Let me know if you need any additional info on the reading order behavior and/or need retesting (I'm back online)

(In reply to Meg Viar from comment #6)
> (In reply to Negin from comment #5)
> > I believe this is unrelated to the feature callout tour. I've set the tour to complete and used VO to tab through the content and it skips the content that has a `.zap-card` class (which is the synced tabs section that causes the VO to read through the content in a "random way" since it isn't reading over that section).
> > 
> > I believe this is happening because .zap-card is using pseudo element/:before which skips the synced tabs section because it's not focusable. I've verified this by trying to tab through the content and it's not possible to tab/focus in on that section with or without the feature tour being rendered.
> > 
> > I think this bug may be more suited for the firefox view team as I'm not sure how they'd like to proceed with that decorative element/how they'd like to make it more accessible?
> 
> Which OS  / screen reader are you using? When I use the built in screen reader on Windows 11, it starts reading the Firefox View page, then switches to the callout when it appears, and then resumes reading the page where it left off (so I don't actually see the behavior described in this bug). One issue I _do_ see is that it then reads the Feature Callout screen content a second time when it reaches it in the page after resuming reading page content.
> 
> On MacOS when tabbing through Firefox View with Voiceover the content of the tab pickup box is _not_ read (likely for the reasons you described above @negin). 
> 
> :ayeddi originally reported this issue in bug 1788253. Anna, do you recall which OS/screenreader you used when you saw the issue described in this bug?

as I recall it, the reading order behavior was buggy on both WinOS+NVDA and macOS+VO and, as you mentioned above, the macOS-specific issue was separate issue observed during testing, not related to the reading order of the callout vs the page.

Let me know if you need any additional info on the reading order behavior and/or need retesting (I'm back online)

UPD:
the reading order would be seen either by letting a screen reader keep reading the entire content of the page after opening it, or by navigating in a read-all mode of a screen reader:
- VoiceOver: `shift`+`ctrl`+`option`+`Right Arrow` aka `VoiceOver + Right Arrow`
- NVDA: `Down Arrow` to read next element OR `Ins`+`Down Arrow` to read all elements from this point on the page