Skip to main content

Disability in UX, Hosted by Twitter

With moderation by Theresa Mershon, Director of Design Systems, learn why accessibility and intersectionality are essential for designers and how the industry could use a lesson. We'll be hosting four external guests across the UX spectrum to share their thoughts and experiences.

Also, sign translation by Kevin L. Mogg and Susie Kahl.

Here's a bit about me; I use captions everywhere I can.



Even before an illness distorted the hearing in my left ear, I enjoyed reading the words more than listening to the people.

As I foray further into the world of UX feedback, I was happy to receive an invitation to this online event.

Mershon admits that the splash page for the event was not accessible. Also, apparently, the job listings page for Twitter. This is not to shame anyone, but the point out that everyone has things to learn. They are quickly working to fix the latter.

There was discussion on how the COVID-19 virus is disproportionately affecting black people, and the black disabled community.


The audio tweets that were released in June were not accessible to deaf and hard of hearing people, something that panelist Ashlee Boyer had brought up on the platform when it was released.

Mershon: "There were many allies on the other side of the door that were excited to leveraged the conversation that had surfaced on our platform. I was looking at what our platform does best, which is amplified marginalized voices."

There is now dedicated, mandated support around accessibility on the Twitter Team.

Resources mentioned:



Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory