- From: Andrew Sutherland <notifications@github.com>
- Date: Wed, 12 Nov 2025 14:38:48 -0800
- To: w3c/FileAPI <FileAPI@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 12 November 2025 22:38:52 UTC
asutherland left a comment (w3c/FileAPI#215) Currently the File/Blob fields roughly correspond to specific (HTTP) headers you might find on a Response object. I'm not aware of any standardized HTTP headers for alternate text right now. Which I think makes sense because usually the appropriate alternate text for something like an image depends on the context in which it is being used. The literal contents of the image are not necessarily what the image represents in context and good alt text can help provide that context, even to those who can view the image but may need assistance with cultural context. If the intent is literally to provide a description of the contents of an image, it would also be good to understand how the inherent metadata formats of the file payload come into play. Like, is this something EXIF should handle for images? -- Reply to this email directly or view it on GitHub: https://github.com/w3c/FileAPI/issues/215#issuecomment-3524196925 You are receiving this because you are subscribed to this thread. Message ID: <w3c/FileAPI/issues/215/3524196925@github.com>
Received on Wednesday, 12 November 2025 22:38:52 UTC