nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Consent codes for accessibility

Sarah Trebilcock Johnson

Hi all,

We have several constituents who have expressed a preference for receiving our email newsletter as a PDF, as it makes it easier for them to use a screen reader. We are planning to track this preference using consent codes, and I am wondering if anyone has best practices they could share for tracking accessibility communications preferences.

Thanks!

Find more posts tagged with

Data Entry

Comments

Dan Snyder

@Sarah Trebilcock Johnson I think you are on the right track using consent here. At the end of the day you are looking to track a communication preference and that is what consent was built for. It will also allow you to query on the solicit code created as part of adding the consent record. I think people often think of solicit codes as “Do Not…" but they can be things like “Send Magazine” or “Send PDF Newsletter”.

Laura Neidhold

@Sarah Trebilcock Johnson
I agree with Dan that I think you're on the right track. My org uses solicit codes or consent codes for both "do this" and "don't do this" in regard to communication. What's always helpful for me to think about when I'm setting up something new is how do you plan to query on these people each time your newsletter goes out? And is there a place you have to record this type of process for future team members?