This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Scenario follows: 1. Author provides ability to get to four quadrants on a web page: 1.a. 12:00 clock, that will put focus on an element at the top of the page. 1.b. 3:00 clock, that will put focus on an element to the right of the page. 1.c. 6:00 clock, that will put focus on an element at the bottom of the page. 1.d. 9:00 clock, that will put focus on an element to the left of the page. -Devarshi
Mass move to "HTML WG"
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change. Rationale: As far as I can tell, this is a request for a browser UI feature and, in general, the spec shouldn't mandate UI.
I don't think this is a browser UI feature request. The idea is to provide ATs with appropriate hooks to enable navigation to the 4 quadrants of a webpage. Screen readers do this with landmark roles. Ctrl + Home and Ctrl + End are familiar examples using just the keyboard, and while they fall short of putting keyboard focus on top and bottom elements respectively, note the similar [enhanced] intent behind this request. (In reply to comment #3) > EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are > satisfied with this response, please change the state of this bug to CLOSED. > If you have additional information and would like the Editor to reconsider, > please reopen this bug. If you would like to escalate the issue to the full > HTML Working Group, please add the TrackerRequest keyword to this bug, and > suggest title and text for the Tracker Issue; or you may create a Tracker > Issue yourself, if you are able to do so. For more details, see this > document: http://dev.w3.org/html5/decision-policy/decision-policy.html > Status: Rejected Change Description: No spec change. Rationale: As far as I > can tell, this is a request for a browser UI feature and, in general, the > spec shouldn't mandate UI.
Can someone tell me whether this can be done using ARIA?
(In reply to comment #5) > Can someone tell me whether this can be done using ARIA? This could be achieved by marking up the desired regions using role="region" and giving each region an appropriate aria-label. So yes it can be done with ARIA. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the Editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the Tracker Issue; or you may create a Tracker Issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: No spec change.