Brian Dys

Tag: Accessibility

  • Reading List: Week 5, March 2022

    Need visual mind-mapping with circles and lines? Maybe you do. But maybe you don’t. Maybe it’s just another distraction, focusing on the tools instead of your thinking.

    Write plain text files

    [ntt_rl_unsplash href=”gETBUi_oRgQ” photographer=”nadi borodina”]

    Removing the grade forced students to pay attention to my comments.

    I no longer grade my students’ work – and I wish I had stopped sooner

    [ntt_rl_unsplash href=”yMg_SMqfoRU” photographer=”Katrina Wright”]

    At a high level, the designer creates a product experience that enables each member of your target audience to complete the product journey efficiently and with minimal mental effort.

    Why Your UX Designer is Your Best Friend – The PM and UX Designer Relationship

    [ntt_rl_unsplash href=”v9FQR4tbIq8″ photographer=”Kelly Sikkema”]

    This article will first introduce you to some of the different styles used for personal names, and then some of the possible implications for handling those on the Web.

    Personal names around the world

    [ntt_rl_unsplash href=”NxCUU0lujD8″ photographer=”Jamie Street”]

  • Assistive Technologies

    • Amplified telephone
    • Font resizing / larger
    • Hearing aid
    • Screen magnification or zoom
    • Cochlear implant
    • Screen reader (e.g, JAWS, NVDA, VoiceOver, ChromeVox)
    • Cane, walker, guide animal or other walking aid
    • Braille terminal
    • Wheelchair
    • Voice Control / speech recognition Software (e.g., Dragon, Siri, Google Home, Google Assistant, Cortana)
    • Prosthetics
    • Speech generating device
    • Wearable tech (not prosthetics)
    • Speech to text (i.e., Dragon Naturally Speaking, Google Doc Voice, Typing, Windows Speech Recognition)
    • Augmentative and Alternative Communication Device
    • High contrast mode or browser color preferences
    • Sign language interpreter
    • Alternative keyboard
    • Speech-to-speech transliterator
    • Alternative mouse or stylus
    • Visual aids
    • Keyboard-only navigation (no mouse usage)
    • Writing on paper
    • Switch access or head pointer or eye tracking
    • Typing with phone or tablet or other device then showing it to others
    • Joystick
    • Caregiver (friend, relative, professional assistant / aid)
    • Teletypewriter (TTY) or Telecommunication device for the deaf (TDD)
    • Closed Captions

    Taken from a Google survey dated September 2019.

  • Putting “Skip to Content” Into Context

    Does the HTML markup of your website has an accessibility function in the form of “Skip to Content”? If yes, then you would notice that it is located at the topmost of the markup. This is as such in order to make it the first focus when using keyboard to navigate.

    Now you may ask, “Shouldn’t the document title be at the topmost of the document?”

    Not when you put this accessibility function into the context of its intended use. The user, upon arriving at your website might have come from a link or have typed a URL into the web browser. That could’ve served the purpose of document title that ensures the user where they are going to or arriving at.

    The second part of this context is the user being able to go directly to the content — skipping every element that isn’t part of their purpose for visiting the website.