Are there still times when manually adding your own definitions can help? (E.g. in the case of the JSON example I provided. Even though that's one of many examples that could be thought of, that involve making the SR confused.)
There might be some extreme cases, but the JSON example is another case of not needing to do anything. There's enough context in the native semantics of the elements you're using to display the code example, as well as the surrounding content.
Less is more definitely feels weird at first, but it's important to remember by not over-describing you're making things better. Here's another good post on this topic.
Are there still times when manually adding your own definitions can help? (E.g. in the case of the JSON example I provided. Even though that's one of many examples that could be thought of, that involve making the SR confused.)
There might be some extreme cases, but the JSON example is another case of not needing to do anything. There's enough context in the native semantics of the elements you're using to display the code example, as well as the surrounding content.
Less is more definitely feels weird at first, but it's important to remember by not over-describing you're making things better. Here's another good post on this topic.
Alright.
Though, how do if I know I'm using the right elements for screenreaders?