ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
julio7359 has joined #wayland
julio7359 has quit [Remote host closed the connection]
Company has joined #wayland
julio7359 has joined #wayland
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
privacy has quit [Quit: Leaving]
iomari891 has quit [Read error: No route to host]
Dami_Lu has quit [Remote host closed the connection]
iomari891 has joined #wayland
Dami_Lu has joined #wayland
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
ghishadow has joined #wayland
garnacho has quit [Ping timeout: 480 seconds]
mxz__ has joined #wayland
mxz___ has joined #wayland
codebam has joined #wayland
<codebam>
does using a vulkan layer perform better than using egl?
mxz_ has quit [Ping timeout: 480 seconds]
mxz has quit [Ping timeout: 480 seconds]
mxz___ is now known as mxz
glennk has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
narodnik2 has joined #wayland
narodnik has quit [Ping timeout: 480 seconds]
julio7359 has quit [Ping timeout: 480 seconds]
julio7359 has joined #wayland
Ermine has quit [Remote host closed the connection]
Ermine has joined #wayland
coldfeet has joined #wayland
kelnos has quit [Remote host closed the connection]
kelnos has joined #wayland
coldfeet has quit [Remote host closed the connection]
kts has joined #wayland
ghishadow has quit [Remote host closed the connection]
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
teh1[m] has quit [Quit: Client limit exceeded: 20000]
Dami_Lu has joined #wayland
fmuellner has joined #wayland
kts has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
Brainium has joined #wayland
narodnik2 has quit []
coldfeet has joined #wayland
rv1sr has quit [Ping timeout: 480 seconds]
<tkna>
Hi. Is there any way by design to get a screen reader (a system that reads text information aloud) such as Gnome Orca to work on Wayland, even through root privileges? A friend of mine gave up his longtime familiar Linux desktop because of the inability to use a screen reader on Wayland and started using Windows on QEmu. https://tech.lgbt/@xogium/110507457689374019
<tkna>
That is almost the same as not being able to see the display for those who can see. Is there anything that can be done about it?
<ifreund>
tkna: based on my understanding, this is an issue with toolkits rather than wayland. Gnome Orca uses dbus to communicate with applications it seems, none of the data going into Gnome Orca passes through Wayland...
<tkna>
ifreund: Does that mean, by any chance, that screen readers such as Orca could be solved in principle if they were compatible with Wayland?
<mclasen>
orca works fine on wayland
<mclasen>
well, 'fine'
<ifreund>
tkna: I'm saying that as far as I know, wayland has nothing to do with the operation of Orca
<mclasen>
it has plenty of X assumptions built in
<colinmarc>
I've never used a screen reader, but wouldn't it have to know the position of windows in the compositor space?
<mclasen>
but that is mostly about input handling and global coordinates
<mclasen>
all those things are in the process of being addressed
<tkna>
ifreund, mclasen: Oh, I see. I thought that in exchange for thorough security measures, they were designed in principle not to be able to use screen readers, but I take it that is not the case?
<mclasen>
screen readers are privileged clients
<mclasen>
and they will have to use some private protocols to interact with the compositor
<mclasen>
because making some of those things impossible for ordinary clients is very much a design goal of wayland
<Company>
this is all not a technical issue, but an issue with manpower
<tkna>
mclasen: I don't know much about orca, etc., as I have never used them, but I wonder if they are currently available in Wayland as well.
<mclasen>
I can turn on orca on this Wayland system today
<Company>
the accessibility community spent its available time improving the situation on Xorg and never got around to porting to Wayland
<Company>
and the Wayland community spent its time improving Wayland and never got around to porting accessibility
<Company>
and now accessibility doesn't work on Wayland
<mclasen>
improvements on X is a nice of saying "try their best to slow the decay"
<mclasen>
there is new a11y infrastructure in development
<tkna>
I see, so you are saying that Wayland is possible by design and there is a vision for its realization, but that it is currently not fully usable because screen readers are not ready for Wayland due to a lack of manpower.
<mclasen>
some of the assumptions in 20 year old a11y plumbing are no longer valid in Wayland, and some people are hard at work to replace that infrastructure with one that is built from the ground up with Wayland in mind
<Company>
"screen readers aren't ready for" sounds like this is a screen reader problem, but it's a whole stack problem
<Company>
compositors, screen readers and the infrastructure are all having issues
kts has joined #wayland
<Company>
and probably toolkits/apps, too - because once you touch infrastructure, they also need changes
<mclasen>
yeah, the 'new a11y infrastructure effort' includes wayland protocols, compositor support and a new gtk a11y backend
<tkna>
So there is no problem with Wayland's specifications, and if the screen reader is developed sufficiently, the visually impaired will be able to use the Wayland desktop through that screen reader.
<tkna>
It is the screen reader that needs to be developed, not each application that needs to support a screen reader individually, right?
<Company>
that's the goal at least
<mclasen>
there needs to be some client-side support. the bulk of it goes into a toolkit, so apps don't have to care
<mclasen>
but they do need to make sure their content is properly labeled, for example
<tkna>
mclasen: Oh I see. You mean like an appropriate label for a screen reader to read. If a developer, who relies solely on sight, puts a label like “Button12” on an invisible part, a visually impaired person will not know what button it is. So the client needs to follow certain a11y or other rules to solve that problem.
<mclasen>
yes
<tkna>
I see. Unfortunately, it is currently unusable, but it is possible in principle, and the methodology and vision for a solution are largely in place. I understood that the rest will be solved someday depending on manpower and time.
<tkna>
ifreund, mclasen, colinmarc, Company: I am relieved for the moment. Thanks for your kind words.
<tkna>
> <Company> "screen readers aren't ready for" sounds like this is a screen reader problem, but it's a whole stack problem compositors, screen readers and the infrastructure are all having issues and probably toolkits/apps, too - because once you touch infrastructure, they also need changes
<tkna>
Ah, I see. Is it a complicated situation with each of these problems throughout the whole thing, not just the sclin reader? It may take a lot of time, so for now we need to use X11, Windows, macOS, etc. I'm just saying that it will be done someday. Thanks.
fmuellner has quit [Ping timeout: 480 seconds]
<mclasen>
"it will be solved" is the wrong attitude though - the situation can be improved if the people most affected by it become involved and work on it
<tkna>
mclasen: Yes, I know. Sorry. Initiative is important. If users contribute, improvements will go faster. Thanks.
privacy has quit [Remote host closed the connection]
rasterman has quit [Quit: Gettin' stinky!]
Guest2338 has quit [Ping timeout: 480 seconds]
TheCaptain82970403198578471379 has joined #wayland
squibid has joined #wayland
squibid has quit []
squibid has joined #wayland
squibid has quit []
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
kts has quit [Ping timeout: 480 seconds]
cool110 has joined #wayland
cool110 is now known as Guest2494
<mclasen>
Company: its easy enough to determine "only foreground" for symbolics while handling the svg, and to write it back into the symbolic.png
<Company>
(wrong channel)
<mclasen>
grr
fmuellner has joined #wayland
rv1sr has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
coldfeet has quit [Remote host closed the connection]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
paulk has quit [Remote host closed the connection]
paulk has joined #wayland
paulk has quit [Remote host closed the connection]
paulk has joined #wayland
sewn has joined #wayland
<sewn>
were the roadblocks for openbsd support only the build process? or are there other factors to make it possible?