Accessibility bridging between .NET MAUI and Avalonia is currently limited.

Nowhere near production ready, got it.

MikeCodesDotNET an hour ago | parent | next [-]

This is the first preview release. It’s targeting a preview of .NET 11, which should help you understand that it’s not intended to be used in production right now.

We don’t expect this to graduate from a preview until November. There’s plenty of time to sort out Accessibility.

▲

siwatanejo 2 hours ago | parent | prev [-]

Almost nobody needs accessibility; let's be realistic, it's obviously not a priority. The priority is to put this out the door (MVP style).

▲

skeeter2020 an hour ago | parent | next [-]

Unfortunately too many developers share your perspective. I'd be surprised if anyone building commercial software would move ahead without accessibility support though because, 1. it's required by law in many situations, and 2. it makes good business sense.

▲

saidnooneever an hour ago | parent | prev [-]

this was down voted but its correct. even if as a human j disagree and it sounds mean, this is how people think in general..too bad, but too true. accessibility will come after 'launch'.

▲

skeeter2020 an hour ago | parent [-]

If they mean "only a small subset of your users need accessibility support" this might be true, but I haven't worked for a organization selling software in the past 20+ years that hasn't needed to provide support, and those orgs are the audience for a .net cross-platform UI solution, so in that case they are wrong; almost everyone "needs accessibility support".

	▲	saidnooneever an hour ago \| parent [-]
		provide support on a product and accessibility are really different things. accessibility is like implementing braille and things for deaf and colourblind etc. support is resetting password and helping with accounts etc. so one is to get a certain category of users to be able to access your site in the general sense. the other (support) is about helping people who already can access your site or service.