Accessibility (A11y)

[fernandolguevara]

View it

[fiatjaf]

Shouldn't we wait for this to be implemented somewhere? I think it would probably fit better in a client-specific locally-stored settings page or NIP-78, at least for now. We can standardize it later.

[fernandolguevara]

@fiatjaf It would be convenient to move this information to the user metadata event, this information can be shared with your network to generate a more inclusive experience the intention is other than a client-specific setting locally-stored

[Semisol]

I think you meant to put this in the JSON content of kind 0.

[fernandolguevara]

my thought was to place the a11y information in the event tags

[IngwiePhoenix]

Hello, visually impaired Nostr user here. :)

I just read the specification and honestly, and bluntly speaking, this feels rather useless. Specifying accessibility settings and preferences is one thing, but the biggest problem is about implementing them actually in a client - be it aria-*-tags or alike. In most situations, the user already uses external tools such as screenreaders and alike to enhance the web experience. All the respective client has to do is adequately implement the proper features - of which there are, admittedly, a whole lot.

Those a11y settings at best can serve as a hint, but in most to many situations do nothing specific. Showing subtitles in videos requires the video to even have them, and most video players already interact with the browser and OS setting to provide optimal experiences.

Sorry if this comes across as harsh; but since I am very much disabled myself and grew up in this environment since day 1, I think I am very much able to tell you a thing or two ;) Again, I do not mean to be rude - just plain honest.

The idea is nice and the thought counts. But I do not see a future for this, as the actual implementation relies on the respective clients and varies drastically.

Thanks for the idea and I hope I didn't come across as too mean! ^^

Kind regards,
Ingwie