-
Notifications
You must be signed in to change notification settings - Fork 40
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
Make policy and guidance PDFs accessible #3488
Comments
Thank you to @kathycarothers for volunteering to plug through these with me! We're getting through them. |
We're plugging through them but realistically this will continue into 11.4, as there were over 200 of these. |
Still plugging through them. Work will continue into 11.4 |
Still slogging away. But getting close! |
We're ready to close this ticket as all the PDFs it covers have been saved. We've done our best to make them accessible but had a few blockers: poorly formatted original documents submitted as comments, and GPO has locked many of the 2010s federal register notices from editing. They aren't passing the accessibility check. @jjonesfec has reached out to his contact at GPO to inquire about this, but we haven't heard back yet. But at this point, the PDFs are all saved into a shared InfoDiv folder that @jason-upchurch @patphongs have been granted access to. We need to gather and doublecheck a few more things that didn't live on the Policy page in transition, and we'll do that in #3527 . |
Summary
What we are after:
As a user, I need PDFs that are accessible. As an agency, we need to ensure that PDFs are accessible and searchable.
Related issues
Background
Executive order 13892 requires the FEC to create a searchable page that contains the agency's guidance. We've decided to hold off on moving the old Policy page off transition and focus on creating a page that moves that information and fulfills the order's requirements. We do need to make the PDFs on that page accessible as many of them will be a part of the new page too. Work on this was begun in #3220 and continues in this ticket.
Completion criteria
Future work
The text was updated successfully, but these errors were encountered: