In D17936#478833, @ognarb wrote:

Hello @chempfling, I saw that you was involved with accessibility around KDE. I would love to get some feedback on the accessibility of this website http://docs.carlschwan.eu.

I already know about the accessibility problem with the language picker (I will change it), but I would love to get more feedback and improvement ideas to make the documentation more accessible.

I just read the comments in the blog announcement about the KDE goals and just found a interested guy.

Thanks a lot for your comment.
I consider that proper accessibility is one of the thing that is/was lacking in Elisa and should be taken for granted.

you are completly right.
A11y is important in enterprise sector. thats why i created T11074 its very needed and its already too long out of scope

By the way: Thanks for care about accessibility! this is awsome :).

I added an Issue for adding the notification role:
https://bugreports.qt.io/browse/QTBUG-76333

Here some update from the a11y side:

• We just prepared an Accessibility section in our HIG (Human interface Guidelines), what are ready to land. Issue T11040

https://invent.kde.org/websites/hig-kde-org/merge_requests/22

• I just brought up the idea to make accessibility as an main goal for 2019. See Issue T11074

This is ready to land.
https://invent.kde.org/websites/hig-kde-org/merge_requests/22

Thanks for clearification :) . Again what learned.
Looks good to me!

@lavender thanks for helping out with the text :). i m not the "best" english speaker XD.

+1 here :).
additional, phabricator is not very accessible to blind people what prevent them to dive in for help

In T11054#187796, @lavender wrote:

Should we have input methods as a goal or maybe something a bit more broad such as Accessibility?

i think you don't need the
"Accessible.onPressAction"
stuff when you use

• onPressed

insteed of :

• onClicked

In T11041#187327, @broulik wrote:

It's on purpose they don't get focus as they should never interrupt you. We need to find a way to address this in some way without jeopardizing the default usecase.

I found an example extension for gnome-shell. It sends the clipboard (when it changes) to orca using ATK to make orca announce the clipboard change.

In T11041#187327, @broulik wrote:

It's on purpose they don't get focus as they should never interrupt you. We need to find a way to address this in some way without jeopardizing the default usecase.

I got information that there is some financal support for stuff like that.
but i m too late :/. So i will not stay at plasma sprint.
still my plan is to have an A11y sprint.

In D21608#474960, @ngraham wrote:

In D21608#474936, @chempfling wrote:

an small thing we need to take care, is that also the current active element gets the focus. screenreaders react to the "focus:true" property to present the current active element.
in Kickoff this is an issue. I will test this here next couple of days.
Thanks!!! :).

In fact that was just improved/fixed yesterday in D21081!

Woe :) cool this looks very promising.
you can just add Plasma Accessibility i will try to review then as soon as i find time :)
thanks for care about that :).

Is reviewed. i need to merge this.

In T10837#182826, @gladhorn wrote:

Hi, I very much think we should meet :) The Plasma sprint is a good option, since we can then influence the right people. Do you think it would be possible to travel to Valencia for you Chrys?

If we add the desktop frame we should add the desktop icons as well or/and maybe the "normal icons".

Seems that the scheduled week has a lot of holidays here in germany. so i may be able to join you for several days.

this is a bad week for me as there are a lot of familiy internal stuff like birthdays and stuff.
But I would be happy to join you guys. let me give a talk to my girlfriend and familiy first. If i can join, I assume could not join for all the week as i have already scheduled my per year vocation to other dates.

@davidedmundson, ping?

I close this and keep the outstanding issues on track in T10836 as the initial bits are working now.

@gladhorn maybe you want to review my patch when you find a quite minute :).

In T10099#182472, @gladhorn wrote:

The initial implementation was written, but lacked testing by actual users. I guess setting the terminal role should be rather simple (just setting the property in the right place). I haven't looked at this in ages, let me know if you want help :)

In T10019#182504, @gladhorn wrote:

You can build Qt and run Kate with the patched Qt version. Sadly the change to Qt needs more work and I haven't gotten around to it for a long time :(

Maybe it would be a good idea to merge all the ATK roles with the QT ones? So we could provice all needed roles?
there is stuff what might be nice for other places as well. like ATK_ROLE_ICON.

https://mail.gnome.org/archives/orca-list/2019-April/msg00032.html

3. and way to access the volume is still needed. i assigned a key activate it.

seems to work mostly now with plasma 5.15

will get fixed by D20449
no more changes are needed then.
i mark this as done as the real problem isnt the a11y label and role

will get fixed by D20449

Can i test this or help somehow to get this reviewed/ merged?

@davidedmundson, was you already able to take a look at your existing patches? whould be sad if those getting lost :) as this is very imprtaint for a11y stuff :).

Works in KDE Plasma 5.15 with orca master, will be available with next orca version thanks @gladhorn !

I was got invited at an LAN party yesterday. this made me find a way to enable zoom for KWin while gaming!

https://phabricator.kde.org/D7780

In T9885#168848, @nicolasfella wrote:

In T9885#168844, @gladhorn wrote:

Is this task about the desktop part or the android app?

Both.

Okular starts an bug bounty:
https://andrewcrouthamel.wordpress.com/2018/11/21/kde-bugsquad-okular-bug-day-on-november-27th-2018/