to be precise, when a collection of items are marked up as a list the setsize property is exposed via accessibility APIs (refer to aria-setsize for explanation http://www.w3.org/TR/wai-aria/states_and_properties#aria-setsize) -- Regards SteveF HTML 5.1 <http://www.w3.org/html/wg/drafts/html/master/> On 11 November 2013 15:27, Léonie Watson <tink@tink.co.uk> wrote: > Jukka K. Korpela wrote: > "A <ul> element contains a sequence of <li> elements. It can be called a > collection, but so what? Calling it a sequence or list or collection does > not really change anything." > > No, calling it a collection doesn't change anything. The fact that it is a > collection, and the fact that that information is conveyed to screen > readers through the browser's accessibility API, is the pertinent fact. > > "I fail to see what impact this would have on software and users. The > number of items is no more (and no less) definite than in the other case. > (And a browser cannot tell the number without parsing and counting the <li> > elements, just as it can count <a> elements.)" > > The nav and ul elements are already supported by browsers and screen > readers. The breadcrumb is a design pattern based on elements according to > their current spec definitions. > > > > Léonie. > > > > >
Received on Monday, 11 November 2013 16:22:59 UTC