Found in the wild:

```
<a href=""
role="button"
aria-controls="drawer-detail"
id="drawer-card-animal-kingdom-link"
aria-expanded="false"
aria-label="Read More - <strong>Disney’s Animal Kingdom Theme Park</strong>">
Read More
</a>
```

Yes, that is a `<strong>` element *stuffed* into an `aria-label`.

Tell me you never fired up a screen reader without… nevermind.

@aardrian An internal system at our uni (for laundry management) has <br> inside alt attributes. I can see how this happened, there’s a page that shows laundry machine availability, where machines are represented by some kind of icons, and a textual tooltip with more detailed information appears on hover. The contents of that tooltip are used as alt text, but somebody forgot to strip out the HTML tags.
@aardrian At that same uni, there’s also what we call the “queuing system”, which is essentially a system for booking appointments. You get permission to book a slot for a specific activity, and can then pick an appropriate date and time by clicking on the calendar. Everything is labeled properly, except somebody forgot to format the timestamp in the label, and what you get as a screen reader user is the number of seconds since epoch. This information is practically useless even if you know what it means and can parse it manually, as you don’t know whether the timestamp is in UTC (as it should be), or in the Europe/Warsaw timezone, which is close enough to UTC for the timestamps to make sense either way. I had to confirm this with a sighted person, and it was the latter if I remember correctly.
@aardrian And then there’s the HR system, for requesting paid leave and such, which uses UserWay for no reason and generates image PDFs that can’t be OCRed effectively.
@miki Well, there is your reason — to falsely claim UserWay has it handled!
@aardrian Probably. THe problem is, the system, at least from a screen-reader perspective, is pretty much accessible, if not for the PDF reports which UserWay couldn’t do anything about, even if it wanted to. They don’t actually have to claim anything because the job was clearly done, and it’s definitely not what I call “accidental accessibility"