Open Bug 1927115 Opened 1 year ago Updated 20 days ago

Why Paused information should read differently (by screen readers) when pausing from a step vs pausing from a continue

Categories

(DevTools :: Debugger, enhancement, P3)

Product:
DevTools
Component:
Debugger
Type:
enhancement

Tracking

(Not tracked)

People

(Reporter: bomsy, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

In Bug 1843320 the WhyPaused is turned into a live region, which also contains source and location information

From comment https://phabricator.services.mozilla.com/D223928#7808007
Should we differentiate between how the voice is read when pausing from a Continue vs pausing from a Step.
The Continue case would benefit from the full readout of the source and location information, as you might be coming from a totally different context (i.e source, location), but the Step case (at least when the function scope doesn't change) would probably be okay with something as simple as "[Paused at] Line N" and so on, since the context is fairly obvious.

Summary: Why paused information should read differently (by screen readers) when pausing from a step vs pausing from a continue → Why Paused information should read differently (by screen readers) when pausing from a step vs pausing from a continue
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.