3 ms·
> Here's the list of guarantees compilers make about the outcomes of undefined behavior: > That's the whole list. No, I didn't forget any items. Yes, seriously
by chrismorgan 4y ago
> Here's the list of guarantees compilers make about the outcomes of undefined behavior:
> That's the whole list. No, I didn't forget any items. Yes, seriously.
I’m a little disappointed there isn’t an empty <ol> or <ul> in the middle there. I imagine screen readers would announce something like “list, zero items”.
- obi1kenobi 4y agoPost author here. I'm very curious about the screen reader idea. If you or someone else is able to confirm what a good screen reader might do currently / what it might do with an empty list element, I'll happily update the post to whatever is the better behavior. I wish there were a best practices doc + a matching linter for accessibility things like this.
- seanwilson 4y agoI just tested "<ol></ol>" in VoiceOver on Mac and nothing gets read. Different screen readers are notoriously inconsistent though. > I wish there were a best practices doc + a matching linter for accessibility things like this. This sounds like it was meant to be a fun tweak/joke for screen readers but it's accessible without. So it's not practical to automate a lot of accessibility checks like this one because it depends on context and there's subjectivity to it, similar to visual design and text readability. The best way to get more of a feel for this is to try a popular screen reader for your OS, do the tutorial, and try it on the page yourself.
- radicalism 4y ago> Different screen readers are notoriously inconsistent though. In other words, UB!
- grogers 4y agoImplementation defined