[skeeter2020]

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]

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.

[tacticus]

> accessibility is like implementing braille and things for deaf and colourblind etc.

or

- larger fonts

- Better contrast controls,

- Non abstract art iconography,

- larger buttons and keyboard navigation,

- understanding that there are many types of colourblindness with different requriements,

- the ability to set lightmode on your app and website due to the issues reading text for anyone with astigmatisms,

- reducing the amount of animation or motion blur

The range of what accessibility is isn't small and some of it is going to be required for the vast majority of products. Also accessibility requirements change over time. eyes and hearing degrade. the desire to waste energy trying to find some stylish button that has no border and almost no contrast to indicate where it is goes away

[saidnooneever]

sure, its much more likely even than your examples too...

was there a point you wanted to make or did you just want to elaborate on what accessibility means? im sure google can churn up tons more examples if u need em....