Conversation
|
You've modified Claude Code configuration files. These files contain the shared configuration for all contributors. Please revert this change if unintended. ONLY modify these files if you need to change shared configurations that apply to everyone and have discussed this change with the TW team. To override the Claude settings locally, use For example, if you're changing AWS_PROFILE: Create or edit {
"env": {
"AWS_PROFILE": "your-sandbox-name"
}
} |
| - Consider if context + image together make the image informative or decorative | ||
|
|
||
| 3. **STEP 3 - Apply W3C decision tree** | ||
| - **Technical docs assumption:** Images are informative unless obviously decorative |
There was a problem hiding this comment.
My assumption is always the other way around. I believe that you should understand the documentation if the images were removed.
But I know everyone else thinks the opposite way, as described here, so I won't start the argument all over again. 😁
| 3. **STEP 3 - Apply W3C decision tree** | ||
| - **Technical docs assumption:** Images are informative unless obviously decorative | ||
| - Categorize as: UI screenshot, procedural step, diagram, code example, graph, or configuration screen | ||
| - Only use `alt=""` if certain the image is pure decoration (borders, spacers, decorative backgrounds) |
There was a problem hiding this comment.
But I do think
| - Only use `alt=""` if certain the image is pure decoration (borders, spacers, decorative backgrounds) | |
| - Only use `alt=""` if certain the image is pure decoration (borders, spacers, decorative backgrounds, duplication of surrounding textual information) |
| 3. **STEP 3 - Apply W3C decision tree** | ||
| - **Technical docs assumption:** Images are informative unless obviously decorative | ||
| - Categorize as: UI screenshot, procedural step, diagram, code example, graph, or configuration screen | ||
| - Only use `alt=""` if certain the image is pure decoration (borders, spacers, decorative backgrounds) |
There was a problem hiding this comment.
Should this be in STEP 4 where the alt text is being generated. It shouldn't impact the categorization?
|
|
||
| 3. **STEP 3 - Apply W3C decision tree** | ||
| - **Technical docs assumption:** Images are informative unless obviously decorative | ||
| - Categorize as: UI screenshot, procedural step, diagram, code example, graph, or configuration screen |
There was a problem hiding this comment.
| - Categorize as: UI screenshot, procedural step, diagram, code example, graph, or configuration screen | |
| - Categorize as: UI screenshot, procedural step, diagram, code example, graph, decorative, or configuration screen |
| - Focus on what information it communicates, not what it looks like | ||
|
|
||
| **Decorative images (rare in technical docs):** | ||
| - Pure visual styling with no informational value → use `alt=""` |
There was a problem hiding this comment.
Not what W3C says. It actually says
For example, the information provided by the image might already be given using adjacent text, which is why I don't think they are as rare as you think.
What happens if you tell Claude this instead of "pure visual styling"?
2 participants
No description provided.