4 ms·
You are correct, I am going to fix this. There is comment below where someone has a screenshot of how it looks in lynx, where CSS and JS don't exist. Instead o
by mileycyrusXOXO 7y ago
You are correct, I am going to fix this.
There is comment below where someone has a screenshot of how it looks in lynx, where CSS and JS don't exist. Instead of using CSS to swap visibility I am going to revert to how I initially had it where JS changes the text from 'disabled' to 'enabled'.
Edit: Fixed it, thank you.
- runarberg 7y ago<nitpick> I would also recommend against using the `<h1>` tag to convey the main information. Usually `<h1>` is used for the main heading—which I presume is the text ”is js enabled” which is located at the top, but wrapped inside a `<nav>`instead of a `<header>` to denote the document structor and `<h1>` to denote the text’s purpose as a main heading. Instead I would use a `<strong>` tag to convey the main information, and a nested `<b>` (the Bring attention to element) to spell the word “enabled” or ”disabled” </nitpick>
- SquareWheel 7y agoDefinitely not just a nitpick. Proper header use is important for accessibility trees and robots.
- mileycyrusXOXO 7y agoAppreciated, I took the time to make these changes this morning.