Issue Design: Screen Reader (HP,T)

Summary

This issue is to make sure that the platform can be used with a screen reader. This is to make it more accesible for a people with diverse needs, as well as to meet some of the preferences of members of the community.

Who can help

This requires technical skills to accomplish. As an element of the design though, anyone is welcome to review.

Community Sources

This was highlighted by a number of community members in focus group discussions. Some mentioned screen readers specifically, while others mentioned more generally the importance of the platform being accesible to a wide range of users with diverse needs, e.g.:

(A d): “the words used, or any writing used” should be “well-spaced out and in a good font that anyone could read - and obviously a screen reader could pick out as well”

More can be found in the community recommendations folder

User story

 As a: Designer  I would like to show the community a wireframe design of the screen reader functionally across components developed so far. This will demonstrate the function of the screen reader which will be activated by a screen reader toggle on / off button. The screen toggle will then be taken forward for developers to prototype as required. So that the community can provide feedback on the wireframe design, which can be taken into the prototype design stage on the project board as a concepts to ensure the platform is being developed in the correct way

Acceptance Criteria:

Review issue designs, research and wireframes take onto board for prototyping as required priority.

Define how this user story will close

Notes:

Associated pull request - Sprint 5 MVP Structure (File Management Demo)  Components to design - wireframe and then share with developers

Current Status: Considerations Design - Design Research Wireframes Interactive & Dev Ref Research

Diversity and Inclusion: creating metrics

We need metrics to ensure that we are reaching and empowering a diverse group.

Compile list of groups who could support diversity in project and help identify gaps
Onboard collaborators
Co-design metrics
Publish metrics on GitHub repo
Measure project in relation to metrics

(Could also potentially create a workshop with Insight group members?)

Consult with Autism Researchers

We need to consult with a wide range of autism researchers to understand how to best build the platform from their perspective.

Presentation metaphors

Overview

As a project participant
I want relevant metaphors
So that I can get a better understanding of project goals and feel more involved

Idea

On one of the presentation slides, there was a visual metaphor for iterative development of a skateboard, bicycle and car. The idea is to have the final vehicle be a train, with multiple carriages representing the different ways that people can be affected by autism.

User Story from OS (24-02-2020) #2

As an autistic user

I would like

the platform to last for a long time

Because...

it can expand and grow in a positive way

Acceptance criteria

There is a plan in place for after the official involvement and funding ends
There is a community around the platform
There is clear documentation and on boarding processes

Notes

Associated pull request:
Current status:

Updates

Volunteer out-reach

Overview

As a person affected by autism
I want to be made aware of the project
So that I can contribute and enrich the project

Idea

There's a question over how to encourage community participation. A couple of ideas are as follows:

out-reach for autistic schools / learning support, to see if younger people want to participate
out-reach for support workers

Accessibility - Contrast Function

As a developer

I would like
A wireframe design and justification that showcases a modular prompt option to alter the contrast etc, with a accessibility panel to prompt the user that they can use a series of accessibility options including contrast, background colour changer, font size increaser.

Review owner:
Internal development team 
Alan Turing

User Feedback Labels:
Accessibility
Accessibility Panel 
Contrast

Document how Open Humans links into the project platform

As a developer
I want a document to detail how the platform can work with Open Humans
So that I understand how the information is stored and retrieved.

Acceptance Criteria
Be able to login and log out
Store experience data information
Create an md file in the repository

Ideas centre

Overview

As a person affected by autism
I want to be made aware of relevant developments
So that I can have a better quality of life

Idea

Technology and general ideas about how to best live continually develop, but people aren't necessarily made aware of developments that may be relevant to them. The idea is to have an ideas centre or something similar, that can be used as a central place to look for these developments

Add contributors

We have a contributors.md file that lists all our community members..... although maybe its better to merge this into one table in the README file as made by the all-contributors bot.

This issue will always stay open as a place for us to update that table 😺

Investigate other platforms recommended by collaborators

Brain in Hand

Add Autistica's language guide to our code of conduct

Here's the link: https://www.autistica.org.uk/about-us/media-communications-guide

Issue Design: Explain principle of Open Humans in wireframe

Summary

The external login via open humans and the whole concept of authorisation of data usage for projects might be confusing without further explanation. The wireframe should include information and instructions regarding this process.

Suggestions for tasks that can fix this issue

short and easy to understand information text about the concept of open humans and why the login is performed via an external platform
short instructions on how the registration and authorisation process works
possibly a more extended help function
possibly the text describing the authorisation on open humans should be revisited to make it shorter and easier to understand

Who can help

Anyone interested in explaining processes in a short and easy way :)

Decide on landing page strapline

Multiple people from focus groups and user testing sessions have mentioned that they would like a strap line throughout the platform, while others think it would clutter the layout too much.

This is a question for everyone:

Would you like a strapline?
Any suggestions for straplines?

All best,

Georgia

Issue Design: Explain principle of Open Humans in wireframe

Summary

The external login via open humans and the whole concept of authorisation of data usage for projects might be confusing without further explanation. The wireframe should include information and instructions regarding this process.

Suggestions for tasks that can fix this issue

short and easy to understand information text about the concept of open humans and why the login is performed via an external platform
short instructions on how the registration and authorisation process works
possibly a more extended help function
possibly the text describing the authorisation on open humans should be revisited to make it shorter and easier to understand

Who can help

Anyone interested in explaining processes in a short and easy way :)

Experience Page Improvements - Upload

I would like
A wireframe design and justification that showcases a improvement to the experience page with the further explanation for the user about what the Upload feature is. Add a upload section - Upload Modular Panel Explaining what its function is and that the user has a number of options:

Options

Upload by image only
Upload by text
Upload by audio

Use another term instead of Upload - Submit Media (Present User Options) - Media Messaging - Submit Media.
Make the upload functionality more of a integral part of the experience page form - more part of the input form.

Fujitsu Wireframe design: upload image

As a Fujitsu developer

I would like

A wireframe design and justification that showcases the upload image hand platform component

Because...

I would like show to the wider community a Fujitsu design concept for the platform

Acceptance criteria

Axure updated with the final UI design for the component
A picture/screenshot image of the final UI design of the component held within Axure
Justification of the component design available in Github repository as an md file

Review owner:

Internal development team
Alan Turing

Accessibility - More Selective Screen Reader

A wireframe design and justification that builds on the current showcase of the screen reader feature for accessibility. The screen reader will need to be more selective in its functionality. Have a button that would allow the user to select a particular block of text clearly.

OS Meeting - Feedback and Ideas

With regards to the platform - make sure the information is simplified.
Make it a meaningful, clear statement as to how the support can be useful, to motivate people to take part.
For those involved who are autistic or familiy members, run a demonstration which shows the goals and aims of the project as well as contribution.
Make sure that the messages are clear and unambiguous - some more things could be jotted down or bulletted - get feedback on what people like and dislike.

For the platform, suggest asking consent to alter words if the information is sensitive - don't wannt to cause distress. Remind people when they access this platform, that they may encounter distressing experiences, and subjective views which might be upsetting. Inform people, caution risk.

Have a notice for people entering the platform - you don't want to mislead anyone.

Make FG database searchable

Make sure that the FG summaries can be easily searched and make the most of the metadata !

Create a community involvement strategy

I think it would be great to write a community involvement strategy and publish it on GitHub. I think this should include information on:

What are your thoughts? It would be great to have feedback on whether to include other information, or if you have any input on any of these topics.

Thanks everyone!!

Sprint 6 User Feedback Reviewed Works

Sprint 6 User Feedback Pages Reviewed Links With Images

1-Landing Page
https://c6q95y.axshare.com/#g=1&p=0-home-light-non-newsletter-lang-drop__1___1_&view=b
1-Landing Page Image

2-Open Humans Login
https://c6q95y.axshare.com/#g=1&p=oh-login&view=b
2-Open Humans Login Images

3-Enter Experience
https://c6q95y.axshare.com/#g=1&p=3_-_add-event-across-device&view=b
3-Enter Experience Image

4-Rating Scales
https://c6q95y.axshare.com/#g=1&p=add-event-messaging&hi=1
4-Rating Scale Images

5-Views
https://c6q95y.axshare.com/#g=1&p=5-event-views-together&view=b
5-Views Toggle Images

Cross-organisation web links

Overview

As a platform user
I want to be able to easily access related resources
So that I can find out more about other conditions that may affect me

Idea

Multiple conditions may affect someone alongside autism (for example, dyslexia and ADHD). The idea is to have a section of the app that links to other sites that specialise in these areas, which will help people explore things that may affect them

Assess and report accessibility of the project for all user groups

As a general user

I would like to...

know how accesible the project is

Because...

so that I can know how to take part and if I am able to

Acceptance criteria

The accessibility requirements of all user groups are identified and documented
The project's accessibility is assessed for each user group
The assessment is clearly written and communicated on GitHub

Source of user story

This was a contribution from autistic person via the Google form.
The acceptance criteria was developed by @fjThomasStanley.

Notes

Associated pull request:
Current status:

Updates

Monitor diversity of participation in the citizen science project

We need to think about diversity and inclusion in recruitment. In previous focus groups we’ve made some attempts to make sure the group is at least slightly diverse when it comes to ethnic minorities, gender, and parent/autistic people ratios, but our instrument has been researcher discretion. Maybe longer term we need to think through more how we might measure this, and put in the protocol strategies to proactively engage to redress disbalances? (We need to do this actively to reflect our values). This might be something worth considering when developing a future iteration of the ethics protocol.

Make it easier for contributors to give their consent

Summary

We need to make it easier for people to provide their signature when giving their consent to take part in user testing. This is based on feeedback from an autistic participant who took part in user testing, and wanted to

Date Due by

This would be a great thing to do for the first round of user testing when the normal sprint cycle resumes in September.

Suggestions for tasks that can fix this issue

There are lots of options for this. Most participants have printed out their consent forms and then scanned them, but this isn't possible for everyone and can be time consuming and awkward.

Docusign might make this easier.

There are also other options such as using the "draw" tool on Microsoft word or the Whiteboard tool on Zoom. Providing step by step instructions to using these in the emails we send out might help.