How to stop screen reader(Narrator) from reading password field in QML
-
Hi I have developed a QML app for windows 10 where windows narrator can reads contents of my app (Screen). Now i want narrator not to read text i am entering in password field . can someone help in managing this ?
I have tried same with QLinedit where if i set lineedit to password mode and start typing narrators says hidden and whereas in case of TextInput it reads the keys i type even i set it to echoMode: TextInput.Password .
TextInput{
width: 240
text: ""
font.family: "Helvetica"
font.pointSize: 20
color: "blue"
focus: true
Accessible.name: ""
Accessible.description: ""
Accessible.passwordEdit: true
Accessible.ignored: trueechoMode: TextInput.Password
} -
@Ajay-Krishna hi
i have never used it, but maybe you can set Accessible.ignored: true on your password field ? -
@Ajay-Krishna
what do you use as input field?
TextInput for example has an echo mode property that, when set (TextInput.Password ) should not allow the screenreader to read the content -
Hi @J-Hilk and @LeLev I tried this example its not working . Screen reader still spells the text I type
TextInput{
width: 240
text: ""
font.family: "Helvetica"
font.pointSize: 20
color: "blue"
focus: true
Accessible.name: ""
Accessible.description: ""
Accessible.passwordEdit: true
Accessible.ignored: trueechoMode: TextInput.Password }
-
@Ajay-Krishna there is also a bool property called passwordEdit , try set it to true
https://doc.qt.io/qt-5/qml-qtquick-accessible.html#passwordEdit-prop -
@LeLev i have tried with password edit too . It is not showing any difference in behaviour .
-
@Ajay-Krishna which Qt version do you use?
-
@Ajay-Krishna
you answered 1/2 of the question, what -bug fix- patch version of Qt 5.12May be important, if we talk about a potential bug in Qt 🤷♂️
-
@J-Hilk said in How to stop screen reader(Narrator) from reading password field in QML:
what -bug fix- patch version of Qt 5.12
QMake version 3.1
Using Qt version 5.12.0Is there anything i want to check ?
-
It is bug in Qt. Please look at the bug