Skip to content

Instantly share code, notes, and snippets.

@MatMoore
Last active December 21, 2018 11:28
Show Gist options
  • Save MatMoore/fa4a7d9569cd939def8948befc0e0d91 to your computer and use it in GitHub Desktop.
Save MatMoore/fa4a7d9569cd939def8948befc0e0d91 to your computer and use it in GitHub Desktop.
Notes from (visiting) speakers at GDS

People that can not distinguish colours can understand all information

avoid instruction that rely on colour don't communicate through colour alone People that have low vision are able to see content

default text size is not too small default colour contrast is good the appearance of online content can be overridden (with browser and operating system settings) - and guidance is provided on how to do this is easy to find This also helps people experiencing a situational impairment such as bright sunlight

People that have a vision impairment and do not use the internet can get content in their preferred format

ensure you have a process in place so that you can provide large print, braille, audio CD People that use screen magnifiers and can only see part of the screen are able to use the interface

interface controls are found in a consistent location to they can be easily found where possible controls are located close together to reduce the need for horizontal scrolling the online service has been tested with a screen magnifier and with users who use a screen magnifier People that use a screenreader and/or braille device can access all online content and functionality

when content is read out it is read out in the correct order all content that is communicated visually has a text alternative (images, infographics and video) HTML is used appropriately and follows best practice so that tables and forms can be understood and used headings are provided and marked up correctly so that provide information about the content is available and can be used for navigation and to provide an overview of the content on a page everything that works with a mouse also works with the keyboard the online service has been tested with the most common screenreader and browser combinations (JAWS 16 with IE 11, NVDA with Firefox and VoiceOver for iOS with Safari) and with users who use screenreaders People that use a keyboard (rather than a mouse) can do everything that can be done with a mouse

make sure that there is visible focus make sure the appropriate HTML elements have bee used so that all links and buttons work with the keyboard make sure that any more complex interactions work with a keyboard - drag and drop, sliders etc make sure there are no keyboard traps People that cannot hear can get audio content through another sense such as sight or touch

online video needs captions and text transcript audio alerts also need a visual or haptic alert People that cannot hear are able to provide information in a way that doesn't require them to hear

online forms don't have mandatory phone number fields don't just provide telephony, provide a text alternative such as email, SMS or paper People that struggle to read and write English due to it not being their first language are able to get content in their first language

where possble provide content as HTML rather than non-HTML formats (such as PDF) so it can be easily translated using services such as Google Translate ensure content can be provides in British Sign Language, Easy Read and Welsh People that require communication support can get it and are able to use it

ensure D/deaf people that need communication support for face to face contact get the appropriate support for them (not all deaf people use British Sign Language, they may rely on lip reading or speech to text for example) if deaf communication support is needed on the telephone or internet via a rely service then it must be possible to communicate through the 3rd party. For example, if someone in a call services refuses to speak with the 3rd party how this person needing communication support expected to be able to communicate. People that struggle to read are provided with text that is simple and easy to understand

plain language no jargon abbreviations are expanded text left aligned (not justified) appearance of content can be customised (colour of text and background, font) as this makes text easier to read for some people digital content is compatible with text to speech software so the content can be heard rather than read images and video are provided to supplement text content For example, people that are dyslexic (10% of population) and people on the autistic spectrum (700,000 people in UK), people that have English as a second language or have low English literacy.

People that struggle to spell and use literacy software are able to use it with online forms

Follow form code best practice test the service with literacy software such and Read and Write People that have a speech impediment are able to communicate through a text based medium

such as email, SMS, web chat and paper People that are susceptible to seizures are not exposed to flashing content

don't autoplay any flashing content provide warnings for any flashing content People that use a wheelchair are able to access service building

ensure there are routes that do not have steps

Trained a bunch of people about how to use private/public key -> 99% people use digital. Elderly people prefer to vote online

Time saved by digitising everything -> Estonians spend < 1 hour on dealing with government a year

Services not allowed to store data if it is stored elsewhere

Citizen owns their data

All access audited and viewable by citizen

Illegal to access data without citizen granting access (some exceptions about police access)

  • feature flags have sponsors and expiry dates
  • notify on expiring
  • force conversation about value

end-end means talking to services you don't own

end-end testing means lots of end-end tests

measure time spent getting a build live. can tie this into systems to view risk from above

Acceptence testing - Dave Farley talk Pathways with stubs Don't cross org boundaries

Exploratory testing = what testers do Free up their time Testers advise devs to write better automated tests themselves

contract testing - ensures dependency is working as you expect write basic tool to load test case fire against external service should be really simple, low effort

do it early - flag provider issues

Consumer driven contract is where you share it with provider and provider writes tests against it.

smoke testing is tracer bullet "we're at least speaking the same language" "connections are working"

Montoring

business metrics operational metrics dependencies

type in name of service and get autogenerated dashboard

Release it book

5m = 650 words

each slide=story

Find aspect ratio of screen at external events

use headings

present in front of mirror

  • history
  • rehtoric
  • practical stuff

can go back and skip over slides

prepare faq... direct tricky questions to someone/where else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment