Articles and Headings

I'm not an a11y guru, my primary interest in this list is I don't want 
to be the guy who makes a page that is really bad for accessibility, but 
I do not have JAWS or other assistive software to test my own stuff.

The thread on articles on lists and headings though, I wouldn't put an 
article in a list - to me, article is suppose to be something that can 
stand alone by itself as the only child of a body. I don't know the use 
case but that doesn't strike me as something that would be in a list. 
Maybe that's just my lack of imagination.

I don't like h1-h6 and I wish we just had one tag - I would call it 
heading. So when I write static content, I just use h1 everywhere - but 
my php when it makes the web page from my static source renumbers it and 
this is how I do it, is it appropriate for accessibility?

First child of an article or section is always a heading. Only time a 
heading is used that doesn't start a new section is when I wouldn't want 
that heading in a table of contents (my php generates that too) and in 
practice that seems to only happen in my content when it is inside an 
aside element.

With article node the first heading is set as an h1 - if there is an 
aside not in a section, the heading in the aside is an h2.

1 section level deep, first heading is set as an h2 - if there is an 
aside not child of a deeper section, the heading in it ends up as an h3

2 section level deep, first heading is set as an h3

and so on up through h6 though in practice I seem to never get past h4.

With that kind of structure, then if I did have an article in a li the 
first child would be an h1.

Is what I am doing sane or will it cause problems? If it causes problems 
for accessibility, how should I structure the headings? Since my heading 
level is done by code I can change it to a different scheme if what I am 
doing is bad for accessibility.

Thank you for your time.

Received on Friday, 21 November 2014 11:22:50 UTC