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 28163 - Browsing mode recommendations/requirements don't reflect reality
Summary: Browsing mode recommendations/requirements don't reflect reality
Status: NEW
Alias: None
Product: ARIA
Classification: Unclassified
Component: Spec (show other bugs)
Version: 1.1
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: James Craig
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-07 16:58 UTC by Dylan Barrell
Modified: 2015-03-07 16:58 UTC (History)
0 users

See Also:


Attachments

Description Dylan Barrell 2015-03-07 16:58:59 UTC
There is a distinction in practice between the role of "link" and the behavior suggested in the spec with respect to switching to application mode, does it make sense for the link role to inherit from widget?

A similar issue arises with respect to the row and gridcell roles - these typically are interacted-with in table navigation mode which is not application mode. However, when creating interactive grids (like Excel, Numbers) it makes sense to be able to switch into application mode automatically. Should a new attribute be introduced to allow this to be specified because these roles are likely to be (and do in practice get) used for both scenarios.