Commit 7d19e748 authored by Cassandra Gould van Praag's avatar Cassandra Gould van Praag
Browse files

initial commit after cleaning fork

parent b29ca8b6
Pipeline #10668 passed with stages
in 1 minute and 52 seconds
......@@ -13,9 +13,9 @@
# you will see them accessed via {{ site.title }}, {{ site.github_repo }}, and so on.
# You can create any custom variable you would like, and they will be accessible
# in the templates via {{ site.myvariable }}.
title: Open WIN
description: A space for the WIN Open Neuroimaging Community to build and share resources
baseurl: "/pages/open-science/community/Open-WIN-Community" # Set this to /pages/<group or username>/<project name>
title: WIN Wednesdays and WIPs
description: Guidance for booking of WIN Wednesdays and WIPs
baseurl: "/pages/cassag/community/WIN-Wednesdays-and-WIPs" # Set this to /pages/<group or username>/<project name>
url: "" # Leave this alone if publishing on WIN Pages site
permalink: pretty
......@@ -30,7 +30,7 @@ exclude: ["node_modules/", "*.gemspec", "*.gem", "Gemfile", "Gemfile.lock", "pac
# include: ["docs/tests/"]
# Set a path/url to a logo that will be displayed instead of the title
logo: /assets/images/logo-owc-gold.png
logo: /assets/images/logo-win.png
# Enable or disable the site search
# Supports true (default) or false
......@@ -64,10 +64,10 @@ heading_anchors: true
# Aux links for the upper right navigation
"Join us on Slack or by Email":
- ""
# "Join us on Slack or by Email":
# - ""
"View on GitLab":
- "//"
- "//"
# Makes Aux links open in a new tab. Default is false
aux_links_new_tab: false
......@@ -94,7 +94,7 @@ last_edit_time_format: "%b %e %Y at %I:%M %p" # uses ruby's time format: https:/
# Footer "Edit this page on GitHub" link text
gh_edit_link: true # show or hide edit this page link
gh_edit_link_text: "Edit this page on GitLab"
gh_edit_repository: "" # the github URL for your repo
gh_edit_repository: "" # the github URL for your repo
gh_edit_branch: "master" # the branch that your docs is served from
# gh_edit_source: docs # the source that your files originate from
gh_edit_view_mode: "tree" # "tree" or "edit" if you want the user to jump into the editor immediately
layout: default
title: WIP guide
parent: Home
has_children: false
nav_order: 2
# WIP guide
{: .fs-9 }
A guide to preparing for your WIP
{: .fs-6 .fw-300 }
# WIN Works in Progress (WIP) Guide
*This guide is intended to be made available for WIN researchers via the intranet.*
1. [What to expect from a WIP Presentation](#1-what-to-expect-from-a-wip-presentation)
2. [Why should I do a WIP presentation?](#2-why-should-i-do-a-wip-presentation)
3. [Who should present and be present at WIP?](#3-who-should-present-and-be-present-at-a-wip)
4. [When should I present a WIP?](#4-when-should-i-present-a-wip)
5. [What should I include in my presentation?](#5-what-should-i-include-in-my-presentation)
6. [How long should my WIP presentation be?](##6-how-long-should-my-wip-presentation-be?)
7. [How do I sign up for a WIP presentation?](#7-how-do-i-sign-up-for-a-wip-presentation)
8. [Who can help me arrange and plan my WIP?](#8-who-can-help-me-arrange-and-plan-my-wip)
9. [Where does the WIP take place?](#9-where-does-the-wip-take-place)
10. [How should I promote my WIP?](#10-how-should-i-promote-my-wip)
11. [What to do after the WIP](#11-what-to-do-after-the-wip)
12. [Useful contacts](#12-useful-contacts)
## Context
The Work in Progress (WIP) meetings provide an informal and constructive forum for researchers to get feedback on planned imaging projects from a diverse WIN audience. WIPs are scheduled as part of the WIN Wednesday meetings that take place on Wednesdays 12:00 - 13:00, everyone who is affiliated with the WIN is welcome to attend these meetings.
The WIN Wednesday weekly meetings are a good opportunity to meet WIN researchers from other groups, find out more about the breadth of research being conducted at WIN, contribute to and learn from the discussion.
We invite you to attend WIPs as often as you can, and be part of these integral "WIN Culture" events. WIP presentations are advertised in the WIN Monday Message (circulated through; if you are not currently on this list please email asking to be added.
WIPs are a useful opportunity to get expert feedback on any and all research being conducted at WIN. This includes (but is not limited to):
- new imaging data acquisition
- secondary analysis
- sequence development
- new behavioural interventions
- new software applications or extensions
- new analytic techniques
- training materials
- experimental protocols
- public engagement activities
Note *all new MRI and MEG projects running at WIN are required to give a WIP presentation in order to receive approval and a project code*.
Everyone interested in giving a WIP presentation should try to schedule their presentation as early in their project as possible. *WIPs are meant for early stage work, not for projects nearing completion*.
The below information is provided to guide your preparation for and participation in WIP meetings. Please do not hesitate to contact any of the individuals listed in the [Useful Contacts](#13-useful-contacts) section if you would like to discuss any stage of the process or development of your project.
## 1. What to expect from a WIP Presentation
WIPs are an informal meeting and should be viewed as a positive opportunity for feedback from your peers. WIP attendees are reminded that discussions should be constructive, welcoming, accessible, and at all times in accordance with the [University policies on bullying and harassment]( We are all reminded that you are the expert on your topic, and we are here to support you based on our own experience. As WIP organisers, we welcome your feedback on your experience of planning and presenting your WIP, so we can improve the experience for others,
## 2. Why should I do a WIP presentation?
- To help optimise the quality of your research with feedback from broad perspectives
- To encourage you to think early about the reproducibility of your research and opportunities to share your materials.
- To encourage collaboration among WIN members, by creating opportunities to hear about the work others are doing in all disciplines.
The WIP is not a box ticking exercise, or a test. It is a way to share planned work or work in early stages with your WIN peers. A WIP presentation can provide you with valuable feedback from the amazing WIN community, who are all here to support you in doing the best research you can.
## 3. Who should present and be present at a WIP ?
Any WIN affiliated researcher undertaking a research project. This includes projects relating to:
- Analysis Research
- Physics Research
- Basic Neuroscience Research
- Clinical Research
- Cognitive neuroscience Research
The individual undertaking the majority of the data collection, analysis or content generation (as appropriate for the project being presented) should lead the presentation. In most cases this will be a student or Early Career Researcher.
PIs and Supervisors must be present to support and provide additional information where required. Named collaborators (internal and external) should ideally also be present.
You should also identify any tools (such as specific FSL packages), approaches, behavioural tasks, pulse sequences or datasets you will be using. If you think you will need additional support using these tools, outside that which is available in your research group, please contact the developers and ensure they are invited to your WIP. Please review the [WIN authorship guidelines]( for more details on this level of collaboration and the list of [WIN tools, along with tool creators](
## 4. When should I present a WIP?
It is best to give a WIP presentation as **early as possible** in your project. This will enable you to receive and incorporate valuable feedback effectively.
WIPs must be completed minimally 2 weeks before planned data collection for new MRI and MEG projects. You can present ideas for planned projects before data collection, or ethics approvals.
You are welcome to present more than one WIP. For example you could present an idea before collecting pilot data, or accessing shared datasets for analysis projects (e.g. UK Biobank), and then present again after data collection, or analysis has started, but not progressed very far. Any time you give a WIP presentation you should be at a stage where you are willing and able to incorporate feedback from the attendees.
## 5. What should I include in my presentation?
You should present an outline of your intended experiment or analysis, including a brief outline of the motivation, background or justification for the research.
A rough suggested outline of a presentation for new data acquisition is below:
- List main aim/question of the study. Provide brief background, hypotheses or describe exploratory motivations.
- List and describe tasks if applicable (Preclinical/Clinical/Cogneuro). Comment on plans to share task materials internally or externally.
- List and describe analysis methods.
- List expected results. Describe why they are expected.
- List protocol details (MRI/MEG/EEG) and comment on any existing or planned uploads to the Open Acquisition database.
- List tools/software requirements (if needed) and comment on the reproducibility or your analysis pipeline, for example plans to publish your code from the WIN GitLab instance
- List any datasets you might need access to
- Describe your plans for [sharing newly acquired data]( (imaging or otherwise) and any restrictions which may prevent sharing at this time.
## 6. How long should my WIP presentation be?
WIP presentations are allocated a **10 minute slot: 8 minutes for presentation and 2 minutes for questions.** These times are somewhat flexible, but they will be enforced if more that one WIP presentation is scheduled in a single session.
## 7. How do I sign up for a WIP presentation?
WIP presentations are booked using Calpendo. See [this guide]( for how to book your presentation.
At the point of booking your WIP you will be asked to provide the following information:
- Title of the project
- Name of presenter, Principal Investigator and collaborators. Include the Supervisor if the presenter is a student.
- A signed [speaker recording release]( The meeting will be recorded during the presentation only and not during the question and answer session. A signed release should be returned for everyone who intends to contribute to the main presentation.
WIPs can be booked up to 10 days before they are scheduled to take place. This ensures there is time to circulate notice of the WIP in the preceding Monday message, and invite guests.
## 8. Who can help me arrange and plan my WIP?
The WIN Core staff named below will be able to assist you in scheduling and promoting your WIP.
- Analysis:
- Physics: or
- Preclinical:
- Clinical OHBA:
- Clinical FMRIB:
- Clinical Neurosciences:
- Cognitive Neuroscience (MRI):
- Cognitive Neuroscience (MEG/EEG):
- All other themes or questions:
## 9. Where does the WIP take place?
- WIP meetings take place as part of the WIN Wednesday meetings on **Wednesdays between 12:00 and 13:00**
- Currently meetings take place online. Plans for hybrid and in-person meetings are currently under development.
- For online presentations please be prepared to follow the [WIN policies on the use of Zoom](, including recording of your presentation.
## 10. How should I promote my WIP?
Your WIP will be announced in the WIN Monday Message. *We recommend that you also directly contact and invite specific people who you would like feedback from, to maximise your opportunity for constructive review*.
You should consider explicitly inviting people you know who have experience with:
- Closely related experimental designs
- Similar patient populations
- Relevant physics expertise
- Relevant analysis expertise
- Relevant programming or software development expertise
If you're unsure of who to invite, please speak to one of the WIP organisers and they can help advise.
## 11. What if I'm using new resources or tools?
## 12. What to do after the WIP
- Try to incorporate any feedback you were given
- Follow up with main discussion contributors
- Always feel free to ask for more input if needed
- Get a project code if needed (or start the process)
## 13. Useful contacts
### Experimental set-up, task, equipment etc.
If you have any questions about stimulus presentation equipment please get in touch with Seb (
### MRI sequences that you will use
Please arrange to discuss your project with one of the radiographers before your WIP:
If your project has more complex physics requirements please get in touch with Stuart (
### Analysis plans
If you have any questions about analysis please contact Taylor (
### Reproducibility and output sharing plans ("open science")
The outputs of your project are more than just a paper at the end. They include your experimental protocol, your data, your code and your tasks. We can help you turn these outputs into practical tools for you and your lab to efficiently reuse.
If you have any questions relating to open science practices, including how to use the [Open WIN infrastructure](, please contact Cassandra (
### Ethics
You do not need to have ethical approval in place before you do your WIP (although it is needed before you can start your study)
If you have any questions about ethics please contact Nancy (
Pilot data can sometimes be acquired prior to obtaining your own ethical approval by making use of technical development SOPs. Please contact the radiographers to find out more (
### Core staff support
The WIN Core staff named below are happy to assist you at any stage of planning your WIP.
- Analysis:
- Physics: or
- Preclinical:
- Clinical OHBA:
- Clinical FMRIB:
- Clinical Neuerosciences:
- Cognitive Neuroscience (MRI):
- Cognitive Neuroscience (MEG/EEG):
- All other themes or questions:
layout: default
title: Open WIN Ambassadors
has_children: true
nav_order: 5
# Open WIN Ambassadors
{: .fs-9 }
Find out about our plans for the Open WIN Ambassadors scheme
{: .fs-6 .fw-300 }
The WIN Open Ambassadors will be a team of individuals who are significant contributors to the Open WIN Community. We intend to launch the Ambassador program in 2021, after we have worked with the community to devise the structure and expectations of the program.
**See the sections below or navigate on the sidebar to find out more about the proposed Open WIN Ambassadors.**
layout: default
title: Benefits for Ambassadors
parent: Open WIN Ambassadors
has_children: false
nav_order: 6
# Benefits for Ambassadors
{: .fs-9 }
Find out about how the benefits of becoming an Open WIN Ambassador
{: .fs-6 .fw-300 }
In recognition of the time, skill and expertise it takes to be an Open Ambassador, you will receive a number of benefits for taking part. These may include:
- Ambassador profiles on this repository
- Named authorship on the repository citation
- Recognition of your contribution on your annual personal development review
- Opportunities to network with likeminded colleagues internally and externally
- Opportunity to shape the policy, structure and governance of the Open WIN Community
- Career advancement and exposure
- Access to a dedicated training and development fund to support your growth in open research or a related topic
- Approved time with your line manager to contribute to these activities
- Merchandise! You want a mug?! We could get mugs! ☕️ 😅
What else would you like? We're aiming to solve the problems which you face, or your barriers to working open. Why do you want to participate? What would motivate others like you?
## Career advancement and exposure
Engaging with open research is good for your CV as many funding and fellowship applications are now requesting and recognising research outputs other than solely papers. For example, preprints, code, datasets and documentation can all be referenced with a digital object identifier (doi) and cited as research outputs. Our hope is that any user of the Open WIN Tools will be able to produce some non-traditional research outputs, however we expect that Ambassadors will stand out as deeply committed to this work.
Ambassadors will have the opportunity to devise and deliver training on these tools, and potentially lead sub-teams who are working on a specific output. These are both excellent experience and opportunities to show leadership on your CV.
Active participation in this community is also evidence of "Good Citizenship" which can be discussed in new employment and promotion applications. It may involve engaging with Senior Management on committees, and you will have the opportunity to learn about background processes in academic life which early career researchers are often not exposed to.
layout: default
title: Expectations of Ambassadors
parent: Open WIN Ambassadors
has_children: false
nav_order: 5
# Expectations of Ambassadors
{: .fs-9 }
The behaviours and activities we would like Ambassadors to commit to
{: .fs-6 .fw-300 }
We would like WIN Open Ambassadors to be aligned with the following activities:
- Commitment to learn about open research practices, understand own knowledge gaps and know where to signpost effectively
- Act as advisors/mentors to other researchers in their research groups, Department and WIN
- Advocate for open research practices an the use of Open WIN Tools in their research groups, Department and WIN
- Speak to researchers about their own experience with open research practices and infrastructure during research group and Departmental presentations and training events
- Participate in Ambassadors meetings once every two months
- Participate in termly co-working hack days where possible
- Engage in community activities for 2-8 hours per month, in addition to the above meeting schedule
In return for their time and commitment, various [rewards and incentives]( will be offered to those who become WIN Open Ambassadors.
We will work to support Ambassadors in all these activities, with communication channels, training, presentation materials and defined routes of development. This support will develop as the project grows, and you will have an open invitation to suggest any additional ways we could support you in growing our community.
layout: default
title: Goals of the program
parent: Open WIN Ambassadors
has_children: false
nav_order: 2
# What are the goals of the Ambassador program?
{: .fs-9 }
Find out about why we are running the Ambassador program and what we hoe to achieve.
{: .fs-6 .fw-300 }
Coming soon
{: .label .label-yellow }
We have created the ambassador program to ensure as many people as possible can access the sharing infrastructure created by the Open Neuroimaging Project.
We would also like to create opportunities for our community to engage learn best practice in open research, connect with each other, develop their experience and boost their CVs with open research outputs!
We also wanted to create a feedback system where our community of users can shape the environment which they work in. We are at the leading edge of these initiatives, and we firmly believe that our users are excellently positioned to contribute to the future of such efforts.
We have specific goals for engagement which are driven by the project metrics which communicated to the [External Advisory Board (EAB)]( who are tasked with providing "an external and independent view on plans and progress" of WIN. <mark> Can the 2018 EAB report be shared on intranet too? - yes. </mark>.
We also have a goal to show a year-on-year growth in understanding and engagement with open research practices, as measured by the [WIN 2019 Open Science Survey]( and the
Based on these combined drivers, our initial goals are to:
## Demonstrate infrastructure engagement
Open Data
- Number of WIN researchers with database accounts
- Percentage of WIN researchers actively using the database
- Number of scans in the database
- Number of studies in the database
- Number of studies shared across WIN
- Number of studies shared externally
- Number of external requests to access studies
Open Paradigms
- Number of paradigms published on the website, potentially number of visits to the site
- Uplift in supporting documentation standards <mark>Added by CGVP. Much of the paradigms repo is pretty near unusable as so little documentation.</mark>
Open Protocols
- Number of protocols openly published in database
- Number of visits to the database and number of downloads
- Number of citations/acknowledgements of protocols used from the database
Open Tools
- Number of FSL tools that have singularity outputs
- Number of downloads of tools with singularity outputs
- Number of publications using singularity outputs
- Number of BIDS meetings attended
Open Community
<mark>TBC and consider more</mark>
- Number of Ambassadors
- Number of users on mailing lists and number of messages <mark>Can we look back at this historically?</mark>
- Number of users (active and inactive) on slack
- Number of contributors to this repository
- Number of enquires (and responses) made to Ambassadors
- Number of attendees at hack-day
- Feedback from hack-day
## Improve awareness and experience with open research practices
- Increase in the number of open access papers immediately available
- Improve awareness of open research practices, particularly registered reports and open educational materials.
- Encourage the community to share pre-prints of their papers.
![OS-Survey 2019 slide 3](../../img/open-science-survey-results/Slide3.png)
- Appreciate the value of open science practices in career development
![OS-Survey 2019 slide 4](../../img/open-science-survey-results/Slide4.png)
- Appreciate the value of open sharing of code.
- Encourage the community to realise the value of sharing data within the current limits of our [open data policy](, and equip them with the tools and knowledge to do so.
![OS-Survey 2019 slide 5](../../img/open-science-survey-results/Slide5.png)
## Reduce barriers to engaging in open research practices
- Devise and promote positive incentives for open research within WIN.
- Clarify and communicate legal and ethical obligations fo data sharing.
- Promote and train the community to use the newly developed WIN Open Infrastructure for sharing [data](, [experimental paradigms](, [acquisition protocols]( and [analysis tools](
![OS-Survey 2019 slide 6](../../img/open-science-survey-results/Slide6.png)
![OS-Survey 2019 slide 7](../../img/open-science-survey-results/Slide7.png)
## Create and share documentation
- Empower the community to learn together as we explore these topics, and share their knowledge on this repository <mark>update when moved</mark> in the form of written documentation.
- Hold in-person and online training workshops and "hacks" where we can learn together and create documentation.
![OS-Survey 2019 slide 8](../../img/open-science-survey-results/Slide8.png)
layout: default
title: Logistics
parent: Open WIN Ambassadors
has_children: false
nav_order: 1
# Logistics
{: .fs-9 }
Find out about our proposed logistics of running and participating in the Ambassadors program
{: .fs-6 .fw-300 }
Below we have answered some questions about how the pilot Ambassadors program will be structured. Jump straight to one of the questions or go through them all!
* [How many Ambassadors will take part in the pilot program?](#how-many-ambassadors-will-take-part-in-the-pilot-program)
* [How will the Ambassadors work together?](#how-will-the-ambassadors-work-together)
* [How long will Ambassadors be in-post for?](#how-long-will-ambassadors-be-in-post-for)
* [Who can be an ambassador?](#who-can-be-an-ambassador)
* [How can I become an Ambassador?](#wow-can-i-become-an-ambassador)
# How many Ambassadors will take part in the pilot program?
In this pilot program, we will look to engage up to ten Ambassadors. Ultimately we would like to have an Ambassador in each of the WIN research groups.
# How will the Ambassadors work together?
While working on creating documentation, we would like to have teams of two people working on each of the four focus areas of the infrastructure tools and a team working explicitly on community and policies. In all these efforts, all Ambassadors will be invited to contribute to the material and efforts of other teams, if they so wish.
# How long will Ambassadors be in-post for?
The pilot program will run from September 2020 to September 2021. All recruited Ambassadors will be expected to remain engaged with the program for this period, and should have confirmed posts as WIN members during this whole period.
# Who can be an ambassador?
Anyone! Student, postdoc, core staff, professional services...
# How can I become an Ambassador?
A competitive application for this program will be launched in September 2020. As part of the application you will be expected to describe why you are interested in becoming and Ambassador, what you will bring to the Ambassadors team and wider community, and what you will gain from being an Ambassador. You will also be asked to produce a letter of confirmation from your Supervisor or line manager stating that they support your engagement with the program and will allow you time away from your existing duties to take part in events and contribute between meetings.
This diff is collapsed.
layout: default
title: Open WIN Community
has_children: true
nav_order: 4
# Open WIN Community
{: .fs-9 }
Find out about the Open WIN Community, what we're doing, and how you can be a part of this effort.
{: .fs-6 .fw-300 }
## What are we doing?
We are a community built from around 250 members of the University of Oxford [Wellcome Centre for Integrative Neuroimaging (WIN)]( Our community exists to support open and inclusive researchers, to develop the tools, policies, governance and structures we would like in place to support us in practicing open science.
We are committed to supporting transparent and reproducible research practices within WIN, to improve the efficiency and accuracy of our research, and contribute to an equitable, diverse and inclusive research environment.
**See the sections below or navigate using the sidebar to find out more about the Open WIN Community.**
## Join the community
If you are interested in learning more about open research, incorporating open research practices in your research, or developing resources to make open research at WIN easier and well incentivised, you should be member of our community!
👋 Subscribe to the [Open WIN mailing list]( to find out about events and resources as they are shared.
👋 Say "hello" on our [Slack workspace]( to follow and contribute to discussions about the [Open WIN Tools](, [events]( or plans for the community.
👋 [Comment on this GitHub repository](, add an issue or submit a pull request to suggest changes to this documentation.
👋 [Email the Open WIN Community Coordinator]( to introduce yourself, or ask a question about any aspect of this repository or the work of the Open WIN Community or Working Groups.
layout: default
title: Participation Guidelines
parent: Open WIN Community
has_children: false
nav_order: 7
# Participation Guidelines
{: .fs-9 }
How Open WIN Community members are expected to work, communicate and interact with each other, so we can all perform at our best.
{: .fs-6 .fw-300 }
## Guiding principles
We value the participation of every member of our community and want to ensure that every contributor has an enjoyable and fulfilling experience.
Accordingly, everyone who participates in the Open WIN Community is expected to show respect and courtesy to other community members at all times.
Cassandra Gould van Praag, as [Community Engagement Coordinator]( of this project, and all project members, are dedicated to a ***harassment-free experience for everyone***, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age, religion or technology choices. **We do not tolerate harassment by and/or of members of our community in any form**.
## Traditionally under-represented groups
We are particularly motivated to support new and/or anxious contributors, people who are looking to learn and develop their skills, and anyone who has experienced discrimination in the past.
We invite all members of this community to actively support the participation of under-represented individuals through recognition of our own privilege and consideration of [how we can use our privilege to benefit others](
We work closely with the [WIN Member Networks]( to ensure that the behaviours we model and the materials we produce are aligned with best practice in establishing equality, diversity and belonging.
## Formal policy
This community is designed to serve individuals affiliated with WIN, and as such these individuals will all be expected to comply with [University of Oxford Harassment Policy]( and the reporting procedures detailed in that policy.
We will begin events with a reminder of the Harassment Policy and expected behaviours. Anyone who experiences or witnesses a violation of the Harassment Policy is encouraged to address the incident directly where they feel safe to do so, or follow the reporting guidelines to escalate where necessary.
**Advice on how this policy is implemented and where you can receive support in these matters is available from the [University Equality and Diversity Unit](**
## Being a responsible bystander
In this community we value efforts to promote a positive work environment, free from intimidation and all forms of violence. We are therefore pleased to support the University in enacting the Harassment Policy by acting as responsible bystanders, and doing what we can to promote a safe and conducive work environment. We encourage all community members to be responsible bystanders.
layout: default
title: Accessibility statement
parent: Open WIN Community
has_children: false
nav_order: 8
# Accessibility statement
{: .fs-9 }
Accessibility Statement for the Wellcome Centre for Integrative Neuroimaging’s Open Science Websites
{: .fs-6 .fw-300 }
The Wellcome Centre for Integrative Neuroimaging (WIN) is committed to providing an accessible web presence that gives members of the public and members of the WIN community full access to centre information, courses and activities offered publicly through the web. Our [Equality Policy]( outlines our commitment to a culture which maintains a working, learning and social environment in which the rights and dignity of all its staff and students are respected.
This accessibility statement applies to University of Oxford, Wellcome Centre for Integrative Neuroimaging’s Open Science Websites listed below:
1. [](
2. [](
3. [](
## Our Aims
These websites are run by WIN’s Open Science team. We want as many people as possible to be able to use these websites. For example, that means you should be able to:
- Change colours, contrast levels and fonts
- Zoom in up to 300% without the text spilling off the screen
- Navigate most of the website using just a keyboard
- Navigate most of the website using speech recognition software
- Listen to most of the website using a screen reader (including the most recent versions of JAWS, NVDA and VoiceOver)
We’ve also made the website text as simple as possible to understand.
[AbilityNet]( has advice on making your device easier to use if you have a disability.
How accessible this website
We are aware that some parts of our website are not fully accessible.
These include:
- Not all images have a meaningful text alternative
- Some images include text as part of the image
- Some images do not include sufficiently detailed captions
- Hyperlinks throughout website have a low contrast