Skip to main content
replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
Source Link

We've had a couple of questions recently about semantic HTML. One was migrated to Stack Overflow, an the other is moving in that direction.

Obviously, questions about how to write code to implement a UI are off-topic. The majority of HTML questions asked on Stack Overflow would not fit here.

But when the question isn't about how to write HTML so that it looks right or works right in a GUI browser, but rather about the semantics of the markup, doesn't it qualify as an accessibility question?

We've had a couple of questions recently about semantic HTML. One was migrated to Stack Overflow, an the other is moving in that direction.

Obviously, questions about how to write code to implement a UI are off-topic. The majority of HTML questions asked on Stack Overflow would not fit here.

But when the question isn't about how to write HTML so that it looks right or works right in a GUI browser, but rather about the semantics of the markup, doesn't it qualify as an accessibility question?

We've had a couple of questions recently about semantic HTML. One was migrated to Stack Overflow, an the other is moving in that direction.

Obviously, questions about how to write code to implement a UI are off-topic. The majority of HTML questions asked on Stack Overflow would not fit here.

But when the question isn't about how to write HTML so that it looks right or works right in a GUI browser, but rather about the semantics of the markup, doesn't it qualify as an accessibility question?

edited tags
Link
Source Link

Are questions about semantic HTML on topic?

We've had a couple of questions recently about semantic HTML. One was migrated to Stack Overflow, an the other is moving in that direction.

Obviously, questions about how to write code to implement a UI are off-topic. The majority of HTML questions asked on Stack Overflow would not fit here.

But when the question isn't about how to write HTML so that it looks right or works right in a GUI browser, but rather about the semantics of the markup, doesn't it qualify as an accessibility question?