<oembed><type>rich</type><version>1.0</version><author_name>David Fleetwood - RG Admin (npub1sm…97lhy)</author_name><author_url>https://nostr.ae/npub1smwq93w6y8sd6lcsnh55ez5lag4fgnvf224k3sc6u4sejlhq0tuss97lhy</author_url><provider_name>njump</provider_name><provider_url>https://nostr.ae</provider_url><html>While not wrong, one way to address this is to not accept contributions that do not meet accessibility guidelines. When I worked for MS &amp; Amazon the guidelines were part of acceptance criteria, and if new features did not meet them they were blocked until they did.&#xA;&#xA;I know it&#39;s difficult, but projects are choosing their priorities and accessibility is not one of them. Worse, when features are designed without it as a baseline, it&#39;s very difficult to add later.</html></oembed>