Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add accessibility remediation request form and button #2694

Open
carakey opened this issue Nov 7, 2024 · 2 comments · May be fixed by #2696
Open

Add accessibility remediation request form and button #2694

carakey opened this issue Nov 7, 2024 · 2 comments · May be fixed by #2696
Assignees
Labels
Accessibility Priority: High These are issues that should be prioritized for upcoming development efforts User Experience

Comments

@carakey
Copy link

carakey commented Nov 7, 2024

Descriptive summary

This ticket is part of the larger ADA Title II compliance effort.

Users should be able to request an accessible version of a work, with as little burden to them as possible. This ticket is to add an accommodation request pathway: "Request Accessible Version" button on work pages, which leads to a pre-populated form, which triggers an email to SA admins for remediation and follow up.

See the implementation of this from UNC in the Carolina Digital Repository: example work + request form.

I can follow up with specific language to use.

@carakey carakey added Priority: High These are issues that should be prioritized for upcoming development efforts User Experience Accessibility labels Nov 7, 2024
@lamtu1 lamtu1 self-assigned this Nov 22, 2024
@lamtu1
Copy link
Contributor

lamtu1 commented Nov 25, 2024

Hi @carakey, I wanted to follow up with you on this:

I would like to know how you want the language is use in the accessibility request form to have when the user click the button on the work?

What type of field(s) would the page have and which information needed to be pre-populated? And also I was wondering if the button placement below is good when ask for the request? Thank you!

Image

@carakey
Copy link
Author

carakey commented Nov 26, 2024

Hi @lamtu1 --

  1. The button placement looks good to me.
  2. Here is a mockup of the form with fields and text (at least preliminary; approved by @mellinma) https://docs.google.com/document/d/1ClbH1C8Mk7RRCr1-crK1RYhMMMXMxbch3GEBgMIooyM
  3. If possible we would like to have the form built/hosted in Drupal as part of the library website so that we could extend its use to other systems beyond SA.
    • To make that work, we would need to do email notification routing based on the system, so wondering if that works at all and if it can be derived from the Link field or if we would need a separate field, such as selecting the system from a dropdown. (Probably getting ahead of myself.)
    • You asked about pre-populating fields. It would be great to have the referring URL populate the Link field, but it seems like that may get complicated in Drupal / if used for multiple systems.

@lamtu1 lamtu1 linked a pull request Nov 27, 2024 that will close this issue
11 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accessibility Priority: High These are issues that should be prioritized for upcoming development efforts User Experience
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants