Event JSON
{
"id": "3435da187b4e8c91c29d2e24675e4847d3acf361a35517124e7f6b91a8571e7f",
"pubkey": "07a648585957014513af1ea1b4be958643522100af23293d8c84977b2840b4d7",
"created_at": 1695924022,
"kind": 1,
"tags": [
[
"p",
"2fd7551ebb45c06cd85bd4e9391b8399866b82e36755fcf20d8739497692c930",
"wss://relay.mostr.pub"
],
[
"p",
"fddf487eea9db57a6e320f80e5cb63de50bedf539695a41c0d447be6c23643e1",
"wss://relay.mostr.pub"
],
[
"e",
"811c8d90a0fafb3b8689612d3f7c3ff0f3f592b7ade287d89a2a366087828f83",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://dragonscave.space/users/jscholes/statuses/111144076723460423",
"activitypub"
]
],
"content": "nostr:npub19lt4284mghqxekzm6n5njxurnxrxhqhrva2leusdsuu5ja5jeycq66qfjk Windows screen readers will communicate the field as normal, but with an additional read-only state. Other responses seem to indicate that VoiceOver doesn't do so well at that. As far as I know, a read-only `\u003cinput\u003e` is removed from the tab order, and it can be helpful to add it back in if the information is important and the field is part of a form. Otherwise, it will almost certainly be missed.",
"sig": "c225e9421f8f3eb4ce9f8e1dfa86eb31c1d3064e1037c2acfb1cb0b9aedac2b122b35c4388fd38ebfc575dad9ebccb25c5cd0b2815384a49dd239bd7bd9fb441"
}