This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
We should discuss this at some point. It makes sense to expose landmark mappings for static html, but what about something interactive like a div with role="checkbox" when script is turned off? My feeling is that it isn't the job of the browser to 'guess' at a way to fail gracefully here.
July 22, F2F in Boston: In the absence of scripts, landmarks are still useful. But what would role=checkbox mean? Not the browser's job to make decision - go ahead and map it.
Add note at beginning of role mapping table. Something like, ARIA roles may not make sense in the absence of scripts but go ahead an map them anyway.
Added this text to bullet 1 before the Role Mapping table: Also note that some WAI-ARIA roles may not make sense in the absence of author-supplied scripts but user agents must map them anyway.