TapType v3.0 is out! This release includes two of the most requested features.
French language support: Full AZERTY layout with a 50,000 word dictionary and all announcements translated.
Traditional keyboard mode: A new way to use TapType without swiping. Every tap types a character immediately. Visible buttons for space, delete, enter, shift, numbers, and emoji are built into the keyboard surface. Word predictions appear at the top, tap one to accept it. Hold and drag to explore keys with no delay. Two-finger tap opens the mode selector through the prediction bar. Enable it in Settings, Keyboard, Traditional keyboard.
The traditional mode still uses the same spatial layout under the hood, so your muscle memory carries over. It just removes the need to learn swipe gestures before you can start typing.
Also new in v3.0: delete by character setting. Up-down swipe gesture for newline. Emoji favourites now use up-down swipe instead of long press. Bug fixes for foldable device passthrough, word deletion after cursor movement, and repeated character announcements. The entire app is fully localized in English, German, Spanish, and French.
Download: https://github.com/aaron-gh/taptype-releases/releases/tag/v3.0
TapType is a free Android keyboard for blind users. No visible keys, you tap where QWERTY keys would be from muscle memory, and a spatial algorithm predicts the intended word. Fully accessible with TalkBack.
#TapType #Accessibility #A11y #Android #Blind #ScreenReader #TalkBack #Keyboard
Release TapType 3.0 Β· aaron-gh/taptype-releases

TapType v3.0 β€” Release Notes French language support TapType now supports French with a full AZERTY layout, 50,000-word frequency dictionary, and all keyboard speech, announcements, and UI fully tr...

GitHub

Which of these would make the best sticker?
Poll in the next post in thread.

#html #semantics #a11y #accessibility

FIRESIDE CHATS

Steve in conversation with accessibility grifters, losers and practioners

YouTube
Why Purchasing an Android Device Is Not Easy for a Totally Visually Impaired Person

Many people look for Android devices as they are cost-effective than iOS. However, they are not easy for blind people due to varied experien...

Why USB Headset Could Be an Essential Tool for Your Independence as a Visually Impaired User

Hello everyone, If you are a totally visually impaired person, a USB headset can be very helpful for achieving most tasks and getting you o...

GitHub - webhintio/hint: πŸ’‘ A hinting engine for the web

πŸ’‘ A hinting engine for the web. Contribute to webhintio/hint development by creating an account on GitHub.

GitHub
On Link Underlines

TL;DR: In general, I recommend underlining links in body content. In the absence of a better style appropriate for a specific site, this is the way to go. Overview It is amazing to me how this suggestion causes so much angst and fighting. Designers often argue that they look ugly,…

Adrian Roselli
was reminded that i filed this at the end of last year... just over 3 months in, the search combobox on @mdn is still borked, sadly... https://github.com/mdn/fred/issues/1175 #a11y [Demonstration video: using Chrome + NVDA. after entering "test", results appear but NVDA remains silent. going through the results, NVDA just announces "test" for each option rather than the visible text of the result/option.]
Majority of B.C.'s courthouses inaccessible, unsafe for intimate partner violence victims: report https://www.cbc.ca/news/canada/british-columbia/rise-womens-legal-centre-courthouses-9.7142514 #a11y
Majority of B.C.'s courthouses inaccessible, unsafe for intimate partner violence victims: report | CBC News

A new report from a non-profit has found that a majority of B.C.'s courthouses are unsafe for victims of intimate partner violence, and often fail to meet accessibility standards. The report from Rise Women's Legal Centre found that, out of 73 courthouses that were studied, 42 per cent didn't include enough space for someone in a wheelchair or crutches.

CBC

Links need more than just a color change to distinguish them.

If your solution is `font-weight: 500`, don’t be surprised when you get dinged for 1.4.1 Use of Color.

`500` often renders no differently than the default (`400`). It’s adversarial conformance.

Use an underline.

#accessibility #a11y