Closed Bug 1946681 Opened 7 months ago Closed 5 months ago

Accessibility review for adding a signature in a PDF

Categories

(Firefox :: PDF Viewer, task)

task

Tracking

()

RESOLVED FIXED
a11y-review changes required

People

(Reporter: calixte, Assigned: nstroud)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

Description:
We are adding support for adding signatures in PDFs.

How do we test this?
Open any PDF, use the buttons from the toolbar.
A dialog should open asking for either a typed signature using a cursive font, or drawing a signature, or use an image.

When will this ship? Firefox 137 (tentatively)
Tracking bug/issue: bug 1942341
Design documents (e.g. Product Requirements Document, UI spec): https://www.figma.com/design/Ri2EZhwzFOxPqebpuS3bYc/PDF.js%3A-Signatures?node-id=1237-57961&m=dev
Engineering lead: Calixte Denizet

The accessibility team has developed the Mozilla Accessibility Release Guidelines which outline what is needed to make user interfaces accessible:
https://wiki.mozilla.org/Accessibility/Guidelines
Please describe the accessibility guidelines you considered and what steps you've taken to address them:
We are taking them into account while working on the feature.

Describe any areas of concern to which you want the accessibility team to give special attention:
For now the signature is added at the center of the page and then it's up to the user to move it at the right place in using its mouse or keyboard. It's up to the user to resize it in order to fit the signature area.
For people having visual impairment, it can be hard to deal with this final step.

Blocks: 1948771
No longer blocks: 1948771

refer to c0

a11y-review: --- → requested
Assignee: nobody → nstroud
Depends on: 1952558
Depends on: 1952563
Depends on: 1952567
Depends on: 1952571
Depends on: 1952573
Depends on: 1953003
Depends on: 1953008
No longer depends on: 1952563
Depends on: 1953290
Depends on: 1953298
Depends on: 1953308
a11y-review: requested → changes required

Thanks for the review! We have addressed all bugs except one S3 which we will postpone for now.

Status: NEW → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.