Figma has really outdone itself in demonstrating how “separate but equal is inherently unequal” applies to software.

For folks who aren’t aware, Figma does not present its content in a method screenreaders can access. In order to read a Figma at all, you need to put it into screenreader mode by entering a special command. Here is the screenreader alt text provided by Figma, telling you the special command.

Please consider presenting this design for a better screen reader experience. To do so, use the keyboard shortcut Ctrl+Alt+↩ .

What the hell is this supposed to mean?!

For folks who might be unaware of every relevant development in the emoji space since 1993 (and shame on you, really) the symbol at the end was originally called “Leftwards Arrow with Hook,” but has since been updated to be called “right arrow curving left.” These are the labels used for this symbol in the screenreader’s TTS dictionary. Thus, when a screenreader user reads this symbol, they will be told it is one of those two things. Super helpful, right?

Googling this symbol describes it like this:

An arrow pointing to the left, with a curved hook at the other end. Similar in appearance to a sideways U Turn symbol, or a reply icon in an email application.

This unfortunately does not give you the context you need, which is that the shape is equivalent to a return key. You know, the key that is shaped like an arrow facing left with a hook at the bottom? The kind that most modern keyboards don’t have?

The key combination is control + alt + enter, but for some reason, they went with a pretty looking symbol rather than writing out the word “return.” For this string specifically intended for screenreader users, who… can’t see the screen. I cannot emphasize this enough–this is the first thing you must do to use the product! Unless you perform this step the entire figma view is read as “clickable blank.”

That they chose this path, and that no one has been able to correct it, speaks volumes.

Anyway, I’m sure this whole design philosophy doesn’t have any impact on the way people think about accessibility while they are making designs in Figma, or the end products of designs that come out of Figma. It’s just a minor technical problem that needs to be solved by the technical people! Someday. Whenever they get around to it. I mean. I got around it just fine. I’m sure everyone else will too. Low pri.

In-Process is out! This week featuring the NVDA 2024.2 Release Candidate, user Arthur’s Experience in Brazil, the new Synth Settings Ring commands, and a long piece on assigning new Input gestures / keystrokes. Check it out at: https://www.nvaccess.org/post/in-process-20th-june-2024/#gestures

#Blog #NVDA #NVDAsr #ScreenReader #News #Newsletter #Accessibility