Re: Structured HTML Precludes aria-posinset and aria-setsize?

(Sorry for the severely delayed follow-up to this.)

Henri Sivonen wrote:
> 1) Paged views (e.g. showing 20 messages of a mailbox containing thousands 
> of messages and having only the 20 items in the DOM)

If knowing the current range and total size of the set is useful, I imagine 
it will be useful to everyone. As such, the range of items currently 
displayed should be noted in element content where it can be found by 

Using your example, I'd expect to see "Message 100 to 120 out of 1,200" or 
similar in a heading element preceeding the the messages. Putting this 
information in one place, available and accessible to all, seems to preclude 
repeating the values in specialist attributes throughout the set.

> 2) Tree grids implemented as <table>s where some rows should not 
> participate in the top level item count.
> In case #2, rows in <thead> and <tfoot> should be ignored for the count as 
> well as rows flagged as subrows.

I agree that more sophisticated counting may be necessary in more 
sophisticated structures. Specifying how UAs should count within these 
structures would preclude repeating the values in attributes throughout the 
set, as far as I can tell.

Ben 'Cerbera' Millard

Received on Wednesday, 27 August 2008 22:00:31 UTC