alphagov / accessibility-personas Goto Github PK

When I and a colleague open scramble-letters.user.js in Google Chrome, I cannot clearly see the search results when using the Simone persona. This problem doesn't happen in Microsoft Edge.

Google Chrome:

Microsoft Edge:

Google have retired its bespoke website for ChromeVox, its screen reader.

The URL for the shortcuts (https://www.chromevox.com/keyboard_shortcuts.html) redirects to https://support.google.com/chromebook/answer/7031755 but does it in an "scary" way (through HTTP with a warning etc).
Unfortunately it's missing any mention of shortcuts on non-Chromebooks. Wherever it says 'Search' or 'Launcher' it should be 'Shift + Alt' on Windows and 'Cmd + Ctrl' on Mac.

Replace the link on Ashleigh's page and mention something about the changes for Windows and Mac keyboards.

I do like your examples, but I would love to see examples of people without permanent disabilities.

Yes, we need to feature a broad range, but:

Jim could have a broken hand and be trying to connect to your site through a laptop tethered to his phone.

Betty could be using voice commands but have construction outside her apartments.

Wendy could be using his friends computer that has a left handed mouse or keyboard.

Bob is in the early stages of MS and copes much better some days than others.

We can highlight how disability is really a human problem that affects all of us.

As far as I know GitHub Pages (looks like Liquid Filters in Jekyll support it) doesn't allow for a random function, but it would be interesting to be able to load up a Persona and not sure what random set of "normal" real world conditions apply.

How would it affect Claudia if she were trying to use her AT in a sunny room? What is it like for Ashleigh when her neighbours are having a party next door?

Let's introduce a bit of the real world into these personas.

A couple of people find Saleem's simulation too difficult to use. The simulation depends a lot on people's ability to read Pig Latin. Some people can read it quickly, others cannot read it at all.

The simulation is also further away from reality than the other simulations.
And we have tested it less than the others. During testing we found some people are fine with it and finish the tasks, others are not and give up very quickly.

Some ideas that someone on the cross-government Slack had to change the simulation:

• mix up or remove prepositions (they don’t exist in BSL)
• flip around word order in a sentence

My service team tested our development environment using the Ron persona. 2 parts of our service were difficult to read:

1. Hint text on the below page:

2. Text in the footer, particularly the email address:

As hint text and the footer are standard Design System patterns / components, I understand if there's not much that can be done to resolve these issues. I just thought I should make you aware of them 🙂

I'm currently setting up an Empathy Lab, and one thing I think I remember the GDS Empathy lab as having is some printed out information sheets about the personas. This would be super useful as the browser extensions make the persona home page hard to read in some cases.

When I went to print out the persona pages though, it came out like this:

Does this printable 'pack' exist somewhere already? I might just be missing it!

The "OpenDyslexic Font for Chrome" was pulled from the Chrome web store.
Simone uses it to change the font.
"Dyslexia Friendly" seems like a good replacement.

Problem with 'Accessibility Personas' (https://alphagov.github.io/accessibility-personas/)

Asperger’s" is an outdated & offensive term. Please update the term to Autism.

scramble-letters.user.js slows a lot of things down and can make the page lag a lot.
We found that on pages that have, for example, lots of options in a big select box. It also shows when you try to use the inspector.

Problem with 'Accessibility Personas' (https://alphagov.github.io/accessibility-personas/) - Hi there this is a content problem - When we were looking at these personas one of my team questioned the use use of the term 'Aspergers' - I believe this is not the correct terminology any more.

Problem with 'Saleem, profoundly deaf user' (https://alphagov.github.io/accessibility-personas/saleem/)

It would be better to explain what BSL is before using the acronym.

Thanks :-)

We currently have a setup for Chromebooks and one for Chrome browsers. We initially tried a setup with Windows but it had issues. Keeping things in the cloud seems to be the best way to make these setups easy to handle. But it would be good to have alternatives to Google products.

I've been thinking of adding a Firefox setup.
The biggest drawback is that there don't seem to be any screen reader (for Ashleigh) or voice control tools (for Chris) which run purely in Firefox. We could add instructions to use e.g. NVDA and Windows Speech Recognition but that would need setting up different Windows profiles and would make it less transferable.

Firefox also has Tampermonkey and Stylus extensions, so that will make most userstyle and userscript simulations work. Although that would need to be double checked.

Here are my ideas for a pure Firefox setup:

• Claudia: Change colours via browser settings (e.g. to yellow on black), zoom in 400%
• Ashleigh: Same userstyle, no idea about screen reader equivalent
• Ron: Same userstyle and userscript
• Chris: Same userstyle as the Chrome setup, no idea about voice control equivalent
• Pawel: Same userstyle and userscript, there is no annoying sound equivalent but it's not strictly necessary, same Midnight Lizard extension
• Simone: Same userscript, "OpenDyslexic" for font, "Read Aloud" instead of Select-to-Speak, couldn't find an extension which adds a tint/overlay
• Saleem: Same userscript

We are retiring the Tech Docs Template documentation at https://alphagov.github.io/tech-docs-manual.

The new Tech Docs Template documentation is at https://tdt-documentation.london.cloudapps.digital and includes all the content from the retired documentation.

Please update the link in your README when you get the chance as I don't have write access to this repo.

Christopher's profile uses a voice control extension called "Handsfree for Web". When it works it works really well, but unfortunately it is quite buggy:

• It often crashes and has to be restarted.
• Even when it's restarted, it sometimes doesn't react at all. (The microphone icon doesn't even show or it's sleeping and "wake up" doesn't work.)
• When it works fine at first, it starts to lag more and more after a while until it gets restarted.

I've looked at a lot of similar tools and this was the best I could find. Maybe it's worth looking further for a replacement. But first we should contact the author as he seems pretty responsive in the tool's forum. (I'm only waiting until this project is completely live.)

Hi team,

I noticed a potential typo on this page: https://alphagov.github.io/accessibility-personas/setup/chromebook.html#simulate-saleem-39-s-condition.

Under the 'Use Ashleigh’s assistive technology' section, it says Claudia. Should this be Ashleigh?

Best wishes,
Adrian

We've been asked a couple of times to add a colourblind persona.
Chris would be a good persona to make colourblind because his simulation is quite boring to look at.

I would simply make everything greyscale (even though I am aware that's the rarest form of colourblindness, but it's easier to implement and more effective).
Should we then also update the information about Chris on his profile on GOV.UK?