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

Better guidance on make consent inclusive and accessible #1274

Merged
merged 5 commits into from
Jan 23, 2024

Conversation

johnwaterworth
Copy link
Contributor

Strengthen the guidance on make consent materials and processes inclusive and accessible.

Talk about what we do, not what you should do.
Copy link

netlify bot commented Jan 23, 2024

Deploy Preview for laughing-payne-b9fbd2 ready!

Name Link
🔨 Latest commit f35ae81
🔍 Latest deploy log https://app.netlify.com/sites/laughing-payne-b9fbd2/deploys/65afdf45a0eb6e00072d461d
😎 Deploy Preview https://deploy-preview-1274--laughing-payne-b9fbd2.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Add a new section on Making consent materials inclusive and accessible
Copy link
Contributor

@ZuleimaMR ZuleimaMR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i have left a comment in line 94, everything else looks/reads good.


Make sure the research data and associated consent records have the same participant identifier. Do not include participant names or other personal identifiers in [the document names](https://playbook.dxw.com/user-research/taking-care-of-research-data/#identifying-research-data-clearly).
We make sure the research data and associated consent records have the same participant identifier. And we do not include participant names or other personal identifiers in [the document names](https://playbook.dxw.com/user-research/taking-care-of-research-data/#identifying-research-data-clearly).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

except the department for education required us to do this. do we need to say that when the client wants this, then we do it?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you mean participant names? That's strange. It's bad practice. If we're asked again we should question it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, I agree, thank you so much for raising this, they made us fill in a spreadsheet where we had to write their names, role and participant number and details of which phase they participated in. Even when the spreadsheet was accessible to specific people, they made us do this. Thanks to your comment, i think we need to raise this and I would like to know how to challenge this to the client without coming across as uncooperative or difficult. Or what would be the exceptions if any or are we not doing exceptions of this at all?

Copy link
Contributor

@ZuleimaMR ZuleimaMR left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have added comments to three lines

Fix a typo.
Remove link for inclusive language until we've added that content.
Add a note on disposing of paper consent forms.
@johnwaterworth johnwaterworth merged commit 7a927a2 into main Jan 23, 2024
6 checks passed
@johnwaterworth johnwaterworth deleted the johnwaterworth-patch-2 branch January 23, 2024 15:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants