Ability to add alt text to profile pictures #249

New issue

Open

opened 2022-11-03 23:05:48 +00:00 by Beefox · 2 comments

Beefox commented

2022-11-03 23:05:48 +00:00

Im not entirely sure how AP would handle this, but a way for profile pictures to have alt text feels important for the fediverse and accessability, and as far as im aware no software allows for this, so lets be the first

👍 1

ilja commented

2023-01-15 16:35:44 +00:00

Contributor

AP-wise I guess the same as with an attachment. Add a name key (in this case to the icon property) and use that.

{
  "@context": [
    "https://www.w3.org/ns/activitystreams",
  ],
  "icon": {
    "type": "Image",
    "name": "a cool looking me",
    "url": "https://instance.tld/media/my-pfp.jpeg"
  },
}

And I guess using name instead of e.g. summary or content is (besides consistency with attachment) because it's explicitly plain text https://www.w3.org/TR/activitystreams-vocabulary/#dfn-name.

AP-wise I guess the same as with an attachment. Add a `name` key (in this case to the icon property) and use that. ``` { "@context": [ "https://www.w3.org/ns/activitystreams", ], "icon": { "type": "Image", "name": "a cool looking me", "url": "https://instance.tld/media/my-pfp.jpeg" }, } ``` And I guess using `name` instead of e.g. `summary` or `content` is (besides consistency with attachment) because it's explicitly plain text <https://www.w3.org/TR/activitystreams-vocabulary/#dfn-name>.

Oneric referenced this issue

2024-04-28 22:13:52 +00:00

RFC: database scheme for media uploads #765

Oneric commented

2024-09-18 22:18:59 +00:00

Member

Pleroma recently merged alt text support for profile pictures and banners. In the interest of compatibility and simplicity for clients we prob should at least match the external API field names (but we’ll also want to add a third one for profile backgrounds)

Ref.: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4227

Pleroma recently merged alt text support for profile pictures and banners. In the interest of compatibility and simplicity for clients we prob should at least match the external API field names *(but we’ll also want to add a third one for profile backgrounds)* Ref.: https://git.pleroma.social/pleroma/pleroma/-/merge_requests/4227

No milestone

No project

No assignees

3 participants

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: AkkomaGang/akkoma#249

No description provided.