Closed Bug 1797795 Opened 2 years ago Closed 2 years ago

Ensure that feature callout surface remains accessible when in use on pdf.js

Categories

(Firefox :: Messaging System, enhancement, P2)

Product:
Firefox
Component:
Messaging System
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Iteration:
112.2 - Feb 27 - Mar 10

People

(Reporter: jprickett, Assigned: jprickett)

References

(Blocks 1 open bug)

Details

The scope of this bug is to keep track of, and implement any accessibility fixes necessary for using the Feature Callout surface with pdf.js.

Assignee: nobody → jprickett
Status: NEW → ASSIGNED
Iteration: --- → 108.2 - Oct 31 - Nov 11
Iteration: 108.2 - Oct 31 - Nov 11 → 109.1 - Nov 14 - Nov 25
Iteration: 109.1 - Nov 14 - Nov 25 → 109.2 - Nov 28 - Dec 9

Has anyone from accessibility been looped in for input on this?

Flags: needinfo?(jprickett)

I spoke with Jamie Teh about this, and since the callout exists outside of the document of the element it is pointing to, there is no way to actually make this accessible. Although suboptimal, we have the goahead to land this provided the callout text sufficiently describes the elements that they're calling out.

Flags: needinfo?(jprickett)
Priority: P1 → P2
Iteration: 109.2 - Nov 28 - Dec 9 → 110.1 - Dec 12 - Dec 23
Iteration: 110.1 - Dec 12 - Dec 23 → 110.2 - Dec 26 - Jan 6
Iteration: 110.2 - Dec 26 - Jan 6 → 110.3 - Jan 9 - Jan 13
Iteration: 110.3 - Jan 9 - Jan 13 → 111.1 - Jan 16 - Jan 27
Iteration: 111.1 - Jan 16 - Jan 27 → 111.2 - Jan 30 - Feb 10
Iteration: 111.2 - Jan 30 - Feb 10 → 112.1 - Feb 13 - Feb 24
Iteration: 112.1 - Feb 13 - Feb 24 → 112.2 - Feb 27 - Mar 10
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.