Piotr Komoda

Accessibility consultant and tester. I specialize in desktop and mobile web accessibility. I also test iOS and Android apps.

[Piotr Komoda @Pitreck]

@brandonleblanc Also, alt texts shouldn't contain subjective information like super amazing

[Piotr Komoda @Pitreck]

@brandonleblanc That's not how you use alt text. It should be description of what is visible on the picture, so blind people (like myself) would have the same information as sighted ones. So if the picture show someone wearing shoes, it should be in the description. #a11y

[Piotr Komoda @Pitreck]

@alpuzz @kellylford They also list accessibility improvements in the release notes for the player, but vmware player was already accessible, so there wasn't much to improve.

[Piotr Komoda @Pitreck]

@madebygoogle i can guess what it's all about, but it would be a lot easier if you would add image description to your twitt. I'm blind, but I'm highly interested in your products. Especially Pixel 4a and upcoming Google TV. Also, where do I click? :-)

[Piotr Komoda @Pitreck]

@intel To be clear, at the registration page for todays event you mentioned that you are commited to the accessibility. I would be really thankful if you would improve accessibility for the blind people. Thanks in advance!

[Piotr Komoda @Pitreck]

@intel Thanks for todays launch event! I really wish you would work a little on your accessibility. I wasn't able to access video player controls with my screen reader during todays live stream. #a11y #fail

[Piotr Komoda @Pitreck]

@stevefaulkner How about tagline or strapline!?

[Piotr Komoda @Pitreck]

@MSFTEnable It's fixed! Thank you so much! Finally Swiftkey is working correctly on my Android phone. Thanks for your help in fixing this issue :-)

[Piotr Komoda @Pitreck]

@MSFTEnable Thank you. Do I still have to report it to the Google accessibility support, or will you pass it to them if it turns out to be the problem on their part?

[Piotr Komoda @Pitreck]

@MSFTEnable Sure, it's English US for swiftkey and English United States for Talkback. System language is English, region is set to United States.

[Piotr Komoda @Pitreck]

@MSFTEnable You say that you can't replicate this issue. May I ask what phone are you using?

[Piotr Komoda @Pitreck]

@MSFTEnable Yes, and I mentioned it because on Android talkback doesn't speak typed keys on secure fields, e.g. passwords. You have to use headphones to hear what you type. So it looks like swiftkey is treating url bar as a secure field.

[Piotr Komoda @Pitreck]

@MSFTEnable Hi, thanks for your reply. What do you mean by audio device? This problem occurs only when using speaker built-in into the device. For the record, I'm using Huawei phone which has swiftkey included by default and it is set as the default keyboard.

[Piotr Komoda @Pitreck]

@MSFTEnable Here is the video

[Piotr Komoda @Pitreck]

@MSFTEnable Steps to reproduce:
1. Open Firefox browser
2. Start typing in the url bar
3. When moving the finger over the swiftkey keyboard keys, talkback doesn't announce the key name. It just says "period".

[Piotr Komoda @Pitreck]

@MSFTEnable That's odd, It's happening from the beggining since I've got this phone. There were multiple updates to Firefox and swiftkey since then. Currently it's swiftkey 7.5.6.4, firefox 68.9.0, android 10 build 10.0.0.195. The issue doesn't occur when I use the phone with the headphones.

[Piotr Komoda @Pitreck]

@BrettJephson @PacktPub Thank you, good luck! Looking forward to your future books and workshops :-)

[Piotr Komoda @Pitreck]

@PacktPub @phildcpickering Please don't forget about #a11y Blind and visually impaired users also would like to learn some code :-)