Comment by joshuamorton
6 years ago
Is lynx up to spec on HTML5 ARIA attributes? My understanding is that that's how accessibility is "supposed" to be done now, but if lynx hasn't been updated in a while, it might not support those HTML5 features, and thus not be standards compliant.
(edit: Someone below notes that lynx appears to incorrectly parse valid HTML5 on the google homepage, so it sounds like Lynx's lack of updates are hurting here).
> Is lynx up to spec on HTML5 ARIA attributes? My understanding is that that's how accessibility is "supposed" to be done now
No, that's not true at all and is unfortunately a common anti-pattern. Accessibility is supposed to be done by using standard HTML elements and attributes. ARIA is there to extend / fill in the blanks and to fix things when people deviate from the norm. For instance, if you have a button, you should almost always use the standard HTML <button> and only use some other element type with an ARIA role=button if it's unavoidable. And <button role=button> is redundant. Best practice is still to use the semantics defined by HTML, as it always was.
I should have been clearer, but imo correctly using html5 node types is part of correctly using html5 attributes.