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

Disclaimer Example Publication #3179

Closed
11 tasks done
Tracked by #138
djgarr opened this issue Sep 18, 2019 · 8 comments
Closed
11 tasks done
Tracked by #138

Disclaimer Example Publication #3179

djgarr opened this issue Sep 18, 2019 · 8 comments
Assignees
Milestone

Comments

@djgarr
Copy link
Contributor

djgarr commented Sep 18, 2019

Work on during the second week of 10.5 after the November 12 release.

Summary

What we're after:
To present the regulated community with disclaimer examples for the real world.

Related issues

Completion criteria

  • Create image blocks using example template with embedded video capability
  • Incorporate OGC comments and edits
  • Ensure images are sized properly for wagtail
  • Add images to wagtail
  • Draft captions for examples using approved language
  • Check accessibility of the video example @JonellaCulmer
  • Review disclaimer caption language and verify content guide compliance
  • OGC review of caption language. Update (if needed) based on input
  • Add fundraising invite example to fundraising page as well
  • Publish examples
  • Insert examples in "Advertising and disclaimer" page
@djgarr djgarr mentioned this issue Sep 18, 2019
12 tasks
@djgarr djgarr self-assigned this Sep 18, 2019
@djgarr djgarr added this to the Sprint 10.4 milestone Sep 18, 2019
@dorothyyeager
Copy link
Contributor

OGC would like to ensure we add some language to the disclaimer page itself regarding the full name requirement. They also suggested making the name of the campaign less simplistic to better illustrate that it's a full name.

For the full name requirement, we could crib from the language approved for page on making independent expenditures:

“A disclaimer notice must contain the full name of the individual, group, political committee, corporation, or labor organization that paid for the communication, along with any abbreviated name it uses to identify itself.”

They also would like us to reference IRS requirements but not craft them into our examples. Here's approved language from the Candidate Guide:

IRS Notice Requirements
Section 6113 of the Internal Revenue Code requires political committees whose gross annual receipts normally exceed $100,000 to include a special notice on their solicitations to inform solicitees that contributions are not tax deductible.

We could insert that language as the side text for the solicitation image.

@djgarr
Copy link
Contributor Author

djgarr commented Nov 14, 2019

Updated completion criteria with next steps following call

@djgarr djgarr modified the milestones: Sprint 10.5, Sprint 10.6 Nov 14, 2019
@dorothyyeager
Copy link
Contributor

We've sent the disclaimer captions to OGC for review.

@djgarr
Copy link
Contributor Author

djgarr commented Nov 19, 2019

OGC reviewed examples. Just had one minor edit. Change has been updated in wagtail

@johnnyporkchops
Copy link
Contributor

@djgarr - You can change the width of the video frame to 80% to match the surrounding paragraphs by changing the CSS width attribute of the .vidframe class from 100% to 80%.

@JonellaCulmer
Copy link
Contributor

JonellaCulmer commented Nov 19, 2019

@djgarr Just want to document what we talked about.

As @johnnyporkchops mentioned above we were going to modify the size of the video to 80%. At 100% it's a bit imposing and at 80% it's in better alignment with the content.

We also talked about making the first sentence that describes how to use the video a separate paragraph from the rest of the text, to help distinguish it and make it clear that it's a playable video.

Everything else looks good. Thanks!

@johnnyporkchops
Copy link
Contributor

johnnyporkchops commented Nov 20, 2019

Once we establish a final (or MVP) for this, we should move the CSS into our SCSS instead of have it in the html block. This would require a PR, so we could do a followup issue--I could do it this sprint. It could probably go in components/_responsive-object.scss

@djgarr
Copy link
Contributor Author

djgarr commented Nov 21, 2019

I published the examples just now. The examples are now live on www.fec.gov

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants