Read on Twitter
Stop using fonts that aren’t AODA compliant. 
Stop sending tweets that aren’t AODA compliant. Stop using Twitter’s voice feature. Also, using 100 emojis in a row is annoying for people using screen readers.
Educate yourself: https://aoda.ca/what-are-aoda-standards/
Stop sending tweets that aren’t AODA compliant. Stop using Twitter’s voice feature. Also, using 100 emojis in a row is annoying for people using screen readers. Educate yourself: https://aoda.ca/what-are-aoda-standards/
Designing for users on the autistic spectrum
Don't:
use bright contrasting colours
use figures of speech and idioms
create a wall of text
make buttons vague and unpredictable - for example, Click here
build complex and cluttered layouts
Don't:
use bright contrasting colours
use figures of speech and idioms
create a wall of text
make buttons vague and unpredictable - for example, Click here
build complex and cluttered layouts
Designing for users of screen readers
Don’t:
only show information in an image or video
spread content all over a page
rely on text size and placement for structure
force mouse or screen use
write uninformative links and heading - for example, Click here
Don’t:
only show information in an image or video
spread content all over a page
rely on text size and placement for structure
force mouse or screen use
write uninformative links and heading - for example, Click here
Designing for users with low vision
Don't:
use low colour contrasts and small font size
bury information in downloads
only use colour to convey meaning
spread content all over and force horizontal scrolling when text is magnified to 200%
separate actions from their context
Don't:
use low colour contrasts and small font size
bury information in downloads
only use colour to convey meaning
spread content all over and force horizontal scrolling when text is magnified to 200%
separate actions from their context
Designing for users with dyslexia
Don't:
use large blocks of heavy text
underline words, use italics or write capitals
force users to remember things from previous pages
rely on accurate spelling - use autocorrect or provide suggestions
put too much information in one place
Don't:
use large blocks of heavy text
underline words, use italics or write capitals
force users to remember things from previous pages
rely on accurate spelling - use autocorrect or provide suggestions
put too much information in one place
Resources to learn #AODA:
https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/
https://www.queensu.ca/accessibility/how-info/social-media-accessibility
https://accessibility.blog.gov.uk/2016/09/02/dos-and-donts-on-designing-for-accessibility/
https://www.queensu.ca/accessibility/how-info/social-media-accessibility
Accessibility on Twitter:
Place any hashtags or @mentions at the end of the tweet. This allows a screen reader to voice the main content of the tweet more clearly in the beginning, and saving the service-specific speak for the end (the parts that sound confusing).
Place any hashtags or @mentions at the end of the tweet. This allows a screen reader to voice the main content of the tweet more clearly in the beginning, and saving the service-specific speak for the end (the parts that sound confusing).
Avoid using unfamiliar acronyms or “text-speak” that would sound strange if read by a screen reader. If space allows, try to spell out the acronyms or use full words to better convey the information.
Use "CamelCase" for multiple words for hashtags.
Use "CamelCase" for multiple words for hashtags.
If your phone has built-in text-to-speech (VoiceOver for iPhone) or a text-to-speech app, try listening to your tweet prior to distribution so you know how your message would be conveyed to a person who is blind.
Did I miss anything, @_HigherEdSocial?
Did I miss anything, @_HigherEdSocial?
