This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 28610 - 4.2.7.1 Steps for Defining a Logical Navigational Structure
Summary: 4.2.7.1 Steps for Defining a Logical Navigational Structure
Status: RESOLVED INVALID
Alias: None
Product: ARIA
Classification: Unclassified
Component: Practices (show other bugs)
Version: 1.1
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Matt King
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-05 19:10 UTC by James Nurthen
Modified: 2018-05-14 17:53 UTC (History)
0 users

See Also:


Attachments

Description James Nurthen 2015-05-05 19:10:06 UTC
Comment from Stefan

4.2.7.1  Steps for Defining a Logical Navigational Structure

- We have a fundamental issue regarding ARIA roles form and group.

To make it brief, say you have a nested fieldset scenario. You cannot nest two divs with role=form since form derives from HTML concept of form and there nesting of forms is forbidden. If you use role group instead (related concept fieldset according to ARIA spec) you violate ARIA best practices since according to spec group is intended for other purposes. 

And AT? In Jaws landmarks dialog, labelled divs with role=form are perfectly displayed, whereas divs with role=group aren't (since they are no landmarks). 

So bottom line: when you want to use div with role=form  (not role=region!) as nested "fieldset" replacement (which we do since it has great benefit for logical nav structure) make clear in your text that this is perfect, although it violates a base concept from HTML.
Comment 1 James Nurthen 2018-05-14 17:53:17 UTC
Don't have this section any more