@stevefaulkner, I can understand that. I lifted very large portions of your existing writings as evidence to justify my preference, so it seemed appropriate to ping you.
@powrsurg, no, but interest in implementing it has greatly increased, as has my general heart rate because I’m not used to advocating for things with such constant public challenge.
I see value to it, but it will cause a great deal of breakage to support. A lot of work for browsers, AT, and also search engines would need to update their algorithms to properly support it.
Well SEO follows the classical document outline algorithm. H1 gets the most importance, h2 and so on. Search engines would need to process the entire DOM to determine the actual importance level of sections to find its relative importance, which could be mistaken. You could end up with important stuff being an h22 depending on your markup.
I think Google distinguishes between importance and hierarchy. AFAICT, they reward semantic outline, and they determine importance by the context of the searcher and the context of the information within the page.
So I have an infographic as a PNG where I planned to make an image link to the PDF of the file. Should I make the alt-text the entire text of the document?
[herin] Hi, I have a simple question about the WCAG Technique G139 : https://www.w3.org/TR/WCAG20-TECHS/G139.html
Example 1: Server-side error checking
Has any one got a demo page for this implementation to share?
[karlgroves]@herin try to register for Tenon without an email or PW
[herin] Hi @karlgroves : I guess this is client side validation where you can apply aria-invalid etc
[herin] When there is an error message displayed from the server side as "No matching records found" or "Authentication failed" - this is not a field specific error
[herin] G139 says provide a link to jump to the error
[caesar] I found a picture of one, LOL
[herin] G139: Creating a mechanism that allows users to jump to errors