Don't do: <h1><img src alt="ACME logo">ACME</h1>.
A better example is when a site has little stock photo thumbnails with article titles on a navigational page. The screen reader can read the title text; knowing what’s in the thumbnail adds nothing.
Images should only have alt text when they contain “real” content (for example if it is an original photo that is relevant to the associated story).
<h1><img src alt="ACME logo">ACME</h1>
What gets rendered and read is what you would never want ACME logoACME
If you don't have or use actual text nearby then you just do this: <h1><img src alt="ACME"></h1>[0] https://developer.apple.com/design/human-interface-guideline...
The "EMERGENCY SOS" slider and "I'm OK" button give more examples of the "straightforward and direct" language that the article text references. I also learned something about that feature itself (besides that it existed in the first place) - Apple's design choices to make the "SOS" a slider, followed by a larger/easier to press button for "I'm OK". Even though it wasn't related to the point of the article, it was information that I wouldn't have learned had I just read that alt-text.
Is this part of accessibility guidelines for alt-text? Shouldn't they convey the same information, whether it's in image or text form, even if it's not directly relevant to the point of an article?
I can also imagine that people have different preferences - maybe some want all the information like I mentioned, whereas others don't want to distract from the point of what they're reading. I wonder which way the alt-text guidelines lean in practice.