Hi,
Working with the semantical HTML5 elements I keep feeling aversion to the extra
elements I am producing. Like the nav element, using it as a container for a
menu in an list does not feel as an advantage, I never needed a container for
the list before. I trained myself in keeping the code
Hi Frances,
I think you might be missing some of the semantics. I might include a
list in a page, such as a list of references, or a friend list where
each friend was linked to their public profile - but those aren't
navigation links. The nav / element tells search engines etc. what
this
On 11/22/11 6:32 AM, Frances de Waal wrote:
Hi,
Working with the semantical HTML5 elements I keep feeling aversion
to the extra elements I am producing. Like the nav element, using it
as a container for a menu in an list does not feel as an advantage,
I never needed a container for the list
Hi Phil,
Yes, you are right, and screenreaders have the opportunity to skip the nav, for
instance. It is just that when I work with this I keep having the feeling it is
a bit overdone and I keep looking for some logic to simplify things. So I
wonder how others deal with this, maybe something I
Thank you, David, good to know, I am afraid this is an example of what made me
pose this question :). Suppose time will solve it all!
Frances
Op 22 nov 2011, om 16:52 heeft David Hucklesby het volgende geschreven:
On 11/22/11 6:32 AM, Frances de Waal wrote:
Hi,
Working with the
On 11/22/11 6:32 AM, Frances de Waal wrote:
,,, and that a nav element around a simple
list is not adding anything to it but creating more code.
Of course it's adding something: semantics beyond that of a generic
list, which provides no metadata about what it contains.
Personally, I say
