4 ms·
Adhere to the actual semantic meaning of HTML5 tags and browsers will handle the rest - honestly. So long as you're not using JS to swap in hidden content and
by munk-a 5y ago
Adhere to the actual semantic meaning of HTML5 tags and browsers will handle the rest - honestly. So long as you're not using JS to swap in hidden content and CSS to arbitrarily reorder content flow then even aria hints are pretty unnecessary - but adding the relevant aria attributes will make sure that screen readers have an easier time.
Not abusing the tags solves pretty much everything at this point because the browsers can't trust anyone. Just read up on HTML5 and how tags should be used... then follow that.
- zzo38computer 5y agoFor writers, that is a good idea (although I think there are a few things missing from most implementations, such as foot notes, and a table of contents window; I do have the idea of a "feature" attribute to handle such things, but it is not implemented either (although using it is harmless, since unrecognized attributes in HTML will be ignored)). CSS should mostly be not needed. For readers, it will be necessary to fix the implementation to do the working better, since not everyone will write it properly.