W3C home > Mailing lists > Public > public-pfwg-comments@w3.org > January to March 2008

RE: Processing requirements for secondary and seealso missing

From: Lisa Seeman <lisa@ubaccess.com>
Date: Wed, 26 Mar 2008 12:39:31 +0200
To: 'Henri Sivonen' <hsivonen@iki.fi>, public-pfwg-comments@w3.org
Message-id: <0JYC00D1S2YH1O10@mxout2.netvision.net.il>

Landmark roles such as secondary are from the XHTML roles


I think the processing requirements in this case are simple - enable
adoption to your user base needs.

It is not our thoughts  to dictate how your users need content, just to
enable you to adapt content for them.

for example , many browsers may ignore secondary

If this is a screen reader, maybe secondary content should be read after
main content

An AT for people needing simplified pages then you may want to hide
secondary , or create a table of content 

it all depends who your user is, this is  enabling semantics for adaptation.

This should also explain email "Spec is devoid of processing requirements
for states and properties"

All the best


-----Original Message-----
From: public-pfwg-comments-request@w3.org
[mailto:public-pfwg-comments-request@w3.org] On Behalf Of Henri Sivonen
Sent: Wednesday, March 26, 2008 11:29 AM
To: public-pfwg-comments@w3.org
Subject: Processing requirements for secondary and seealso missing

What are the UA processing requirements for the landmark roles 'secondary'
and 'seealso'? Please state processing requirements for the roles in the

Henri Sivonen
Received on Wednesday, 26 March 2008 10:41:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:45:57 UTC