Skip to content

Instantly share code, notes, and snippets.

@rynbyjn

rynbyjn/bit_tech_symposium_notes.md

Last active May 11, 2018 19:14
Show Gist options
  • Save rynbyjn/88116c8e0d5880143dc39937e9a31c9a to your computer and use it in GitHub Desktop.
Save rynbyjn/88116c8e0d5880143dc39937e9a31c9a to your computer and use it in GitHub Desktop.
Download ZIP
BIT Technology Symposium
Raw
bit_tech_symposium_notes.md

BIT Technology Symposium

Giving Accessibility a Face

Paul Seigneur (student, Golden High School)

  • Braile and speak (piece of technology that would speak braile)
  • Brailist (translator)
  • Screen Readers:
    • JAWS ($1100)
    • NVDA (free, but seems to require a donation, but windows only)
  • 75% of school related products not accessible
  • 3D printed a model of the school with raised parts for bathrooms, classrooms, etc..
  • 90 blind students in Jefferson County alone

Tips for Improving Verbalization

Roger Benz (Accessibility Program Manager, G Suite, Google)

Screen Readers:

  • Verbalization like "Button, Button, Button" is common
  • Verbalizations vary by platform (Voice Over, JAWS, NVDA, Android Screen Reader, etc..)
  • Don't tell the user what to do "Open options menu" just "Options menu"
  • "Options menu button" know that it will open an option menu
  • add collapsed and expanded attributes
  • small things are what make the biggest difference (killing mosquitos)
  • "Purchase" button should use "Buy" for brevity to reduce the amount of time it takes a reader to read it
  • changing verbalization can help to reduce the amount of time a blind person needs to hear the reader
  • 20 years of screen reader use can make the voices annoying
  • "Acquire" -> "Get"
  • "Lamp"? start/stop keyword
  • Impatient can skip over parts that are actually important
  • Put information first before describing markup with screen reader
  • "Slide 1 Verbalization" sounded good at first, but gets annoying to hear over and over "1 Verbalization" kills redundancy
  • sometimes just don't say anything (read/unread) tell them it's unread, but don't say it's read (UX)
  • when skimming around this helps to find the unread messages quickly
  • no need to tell the user that a message was "Archived" for every message archived, just move on to the next one
  • don't build and ship and wait for users to give feedback
  • adding these labels

Principals of verbalization:

  1. Make it concise (short as possible)
  2. Order content then attrs (title - type)
  3. Order of info given to user, what's the most important
  4. Sometimes not saying anything is best

Q & A

  • is there a way to soften the robot voice? blind people like it cause it can be sped up without loss (entertainment is different)
  • when we build applications what is biggest thing we miss for a sighted user using a screen reader? learn enough about the screen reader to use it and turn your screen off (limits the unconsious cheating that a sighted user does)

Inteegrating Accessible User Experience into Agency Cultures

Theresa Montano (Solutions Architect of Accessibility, State of Colorado)

Casey Carlson (Chief Enterprise Architect, State of Colorado)

Architecture and design starting off accessible.

Casey

  • Section 508: falling short of expectations
  • Technoloty Accessibility for Persons with Disabilities (OIT)
  • Law: Information technology access for individuals who are blind or visually impaired (24-85-101-104)
  • OIT Travelling Leadership Coins (recognition)
  • Process for keeping up with governing and enforcing this

Theresa

Oversees advisory board to enforce. CO initiatives:

  • Actually enforce the requirements already in place
  • Raising awareness with training
  • Validation and assessment
  • automated tools for developers (free and pay for auditing)
  • Align ADA coordinators to report up the chain
  • California initiative to have all goverment sites compliant by 2019

Major Pattens for Accessible Drag and Drop

Jesse Hausler (Principle Accessibility Specialist, Salesforce)

  • Don't use "workarounds" for accessibility
  • live region text "do what you have to do, just do it well"
  • Resize, move from list A to list B, order list
  • range slider for resizing (visually hidden, but screen readers can find it)
  • move from one list to another with an aria menu (like selects)
  • sorting a list with aria listbox with hidden live region
    • tab into list box
    • up/down to change
    • space to select (custom)
    • up/down to move
    • space to release it
    • use live regions to speak where in the list the item is while being controlled via javascript note when grabbed and placed
  • interacting with an object on a canvas
    • hidden aria live region
    • keyboard interactions:
      • separate trigger for move, resize
      • spacebar grab
      • arrow to move
      • spacebar to dropo
      • esc to cancel
  • naming of objects should be ralational to the domain of what is being changed
  • how do describe with labeling
  • Blog post
  • Code examples
  • salesforce UI (classic, lightning)

Microsoft Accessibility Journey

Erin Williams (Senior Supportability Program Manager, Microsoft)

How to move accessibility from firefighting to fire prevention

  • Bolt on vs. Built in
  • Move beyond compliance and toward usability (on top of compliance)
  • Customers want and deserve more than what most offer currently
  • Screen readers are as abundant and diverse as the browsers we use
  • User voice (3rd party tool) aka.ms/accessibilityuservoice
  • Accessibility User Research Collective - group to test MS products (accessibilityuserresearchcollective.org)
  • Dog fooding products (test it in house before you release)
  • Seemed like a talk about how to get people to help MS test their products and show off how diverse they are with disability hires
  • The high school speaker basically asked for an after high school job at MS
  • seeing ai app https://www.microsoft.com/en-us/seeing-ai/ aims to describe images/video with audio

Keynote

Dena Wainwright (VP Enterprise Digital Accessibility, Wells Fargo)

  • She's Canadian! (hockey fan, go Jets)
  • Breaking rules (assumptions and level of accessibility/lack of access)
  • Privacy can be threatened by assumptions and lack of access
  • How many people can accessibility impact (largest minority of disability) 800M world wide 57M in US
  • Least discriminatory group "We'll take anybody"
  • As you age you have a 75% chance of joining this group
  • 43M US are age 64+ with disabilities and control $11 trillion
  • How do I know when I'm done with accessibility? - fix all the things that you would want to have work
  • People with disabilities are more than 2x more likely to be unemployed
  • Access ability
  • Education, preparation and opportunity (got 1&2, but not 3)
  • Need more haptics for people with disabilities
  • Did you see me, did you hear me?

Accessibility Strikes Back

Anant Mistry (Director of Cloud Innovation, Merkle)

  • Thoughtfulness - think of everyone and how to include them as part of the greater whole
  • Number betwen 1 and 300,000 (the challenge of accessibility)
  • It's between 520 and 525 (what BIT narrows it down to)
  • Java accessibility bridge (for java apps)
  • Multiple windows not good, but if you can complete the loop to get back to where you started it's good (checkpoints are good too)
  • Implement keyboard shortcuts
  • Usability trumps accessibility
  • Fix the irritating parts of vocalization ie: "Button, Button, Button"
  • Cards against humanity has an accessibility kit
  • All BVIs know braille, right? - Nope
  • 1950 50% of kids with BVIs could read it now it's 8%
  • 3 levels of encoding Braille
  • Cards against humanity used either Braille 2 or 3 (shorthand) and is tough for most BVIs to read
  • You can get close to 100% accessibility if you start with it from scratch
  • Achieve 100% usability first
  • Keep the UI simple
  • Be mindful of over engineering accessibility
  • Tagging/labels, focus and keyboard shortcuts are your friend
  • Technology is the big equalizer
  • By embracing usability you end up with better accessibility
  • None of the technology is outright innovation, but instead needs to be implemented
  • Screen readers work in different ways. some are watching for UI updates while others are hooked into the hardware
  • "App against humanity" - developing an app that reads cards against humanity and reads them through headphones
  • Swift playground is 100% accessible (coding for BVI)

Frontier Airlines Accessibility Journey

Kevin Pennock (Director of Application Development, Frontier Airlines)

David Waidmann (Software Developer, Frontier Airlines)

How Frontier made the journey to accessibility

Why

  • 12/12/2013 Department of Transportation made them do it (had to be implemneted by 12/12/2015)
  • 4 principals of WCAG
    • Perceivable - can't be invisible
    • Operable - UI and stuff has to work
    • Understandable - understand and easy to interpret
    • Robust - be interpreted by system technologies
  • Separate site vs. Existing site (went with existing)
  • Never done with accessibility
  • BIT
    • site assessment
    • site comparison
    • training/helpdesk
    • on site work with dev & qa staff

How

  • WAVE evaluation tool (aim.org)
  • aXe https://www.deque.com/axe/ (npm & chrome extension)
  • Lighthouse https://developers.google.com/web/tools/lighthouse/ (npm & chrome extension)
  • JAWS
  • NVDA
  • Rules of ARIA:
    • Use semantic HTML as much as possible, don't repurpose other elements for this
    • Don't change native semantics unless you really have to
    • All interactive controls must be operable with the keyboard
    • Do not use role='presentation' or aria-hidden='true' true on a visible focusable element
    • all interactive elemnts must have an accessible name
  • role="dialog" aria-modal="true" allows keyboard to stop at the last element in a modal and not try to find other things below
  • Accessibility guideline
  • Hide all things accessible to not break styling for the sighted

Wrap it

  • Find a good partner for auditing and learning
  • Change mindset from "Have to" to "Want to"
  • Accessibility should be part of your SDLC (software development lifecycle)
  • Include all groups (Marketing, Design, Dev, QA, etc..)
  • Do what's best for the user
  • Work with someone who has an actual BVI
  • DoT auditing? - not sure if they do it or if it is just reactionary when complaints arise

Running Blind Team

The Running Blind Team (Unive3rsity of Denver)

Random

  • Screen Reader Survey
  • Title 3 ADA vs Title 1 ADA?
  • Blind speakers did not have slides, just voice reader content
  • Sighted users had videos (with voice reader on top)
  • Clapping for recognition vs. a show of hands
  • VoiceOver mac - has a tutorial
  • Accessing Higher Ground Conference - Westminster?
  • Sight Improve - audit company?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment