Event JSON
{
"id": "217abf0590343e8f736efc00fcae425cdb6e90f5fea3b2d93fe27036f375f64e",
"pubkey": "d8bb2a8fbc36ca5eb031e14893a3eea132b0864f7b2aac6fde8e4df9d32f4588",
"created_at": 1724004597,
"kind": 1,
"tags": [
[
"t",
"ui"
],
[
"t",
"development"
],
[
"t",
"design"
],
[
"t",
"usability"
],
[
"proxy",
"https://mas.to/@markwyner/112984365313610202",
"web"
],
[
"t",
"a11y"
],
[
"t",
"accessibility"
],
[
"proxy",
"https://mas.to/users/markwyner/statuses/112984365313610202",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mas.to/users/markwyner/statuses/112984365313610202",
"pink.momostr"
],
[
"-"
]
],
"content": "You know when you’re trying to click a tiny little link and you have to be diligent to get your aim right? Frustrating, to be sure. That’s a usability issue. But if you have mobility impairments, it’s an accessibility issue.\n\nOne little code consideration can make all the difference.\n\nhttp://markw.rites.markwyner.com/usability-accessibility-and-the-clickable-area-of-buttons\n\n#Accessibility #Design #Development #A11y #Usability #UI",
"sig": "5fd6ee4d9c40bead35347ceebc11f9105dc5c80b384678a7e248e0a803970622f80891fa5442d4f858a6ea3ddc694f2ee0ca05cf18d85e088597ae7523e524d6"
}