I don’t have a screen reader installed so I cannot try it but I can guess how it can screw with it. However I agree with Monkey With A Shell here. It’s not realistic for all users to follow semantics, this can only be solved with a better software.
While I use markdown daily, apparently there are still things I don’t know about it. Well, I mostly learn them when I need them but still. So, I could use — (speech dash) instead of -, which I assume wouldn’t cause a problem with a screen reader. There is no way for me to remember its shortcut on the keyboard, but it seems Markdown already covered this with — which ends up rendered as —.
Thanks for making me noticing about it, learned something new today.
It’s not realistic for all users to follow semantics
Not realistic for users to write lists the normal way that doesn’t look wrong?
I don’t know guys
-first
-second
-third
looks obviously bad whereas
- first
- second
- third
looks right.
Then you see the rendered result in preview.
I don’t think this is asking much.
If you weren’t trying to write a list, though, then I don’t know what you were doing & I doubt a chat bot will either: could you link to an example of what you were trying to do?
For all you know, I’m a chat bot not figuring out your intent.
No technology is about to fix PEBKAC.
I think the bottom line is if you write lists normally, then everything else including accessibility will turn out right without you needing to understand the intricacies.
muhyb@programming.dev 1 day ago
How is it breaking accessibility?
lmmarsano@lemmynsfw.com 1 day ago
Good question: for basic accessibility, structure should be conveyed, which adds
The web supports programmatic relationships through correct markup, so the technique using semantic elements to mark up structure applies, specifically by using ol, ul and dl for lists or groups of links or the markdown equivalent.
If you want to experience this yourself, then put on a blindfold, use a screenreader & compare your “list” to mine.
muhyb@programming.dev 1 day ago
I don’t have a screen reader installed so I cannot try it but I can guess how it can screw with it. However I agree with Monkey With A Shell here. It’s not realistic for all users to follow semantics, this can only be solved with a better software.
While I use markdown daily, apparently there are still things I don’t know about it. Well, I mostly learn them when I need them but still. So, I could use
—(speech dash) instead of-, which I assume wouldn’t cause a problem with a screen reader. There is no way for me to remember its shortcut on the keyboard, but it seems Markdown already covered this with—which ends up rendered as—.Thanks for making me noticing about it, learned something new today.
lmmarsano@lemmynsfw.com 1 day ago
Not realistic for users to write lists the normal way that doesn’t look wrong? I don’t know guys
looks obviously bad whereas
looks right. Then you see the rendered result in preview.
I don’t think this is asking much.
If you weren’t trying to write a list, though, then I don’t know what you were doing & I doubt a chat bot will either: could you link to an example of what you were trying to do? For all you know, I’m a chat bot not figuring out your intent. No technology is about to fix PEBKAC.
I think the bottom line is if you write lists normally, then everything else including accessibility will turn out right without you needing to understand the intricacies.