Closed
Bug 408877
Opened 18 years ago
Closed 15 years ago
Form controls always listed before anchors in tab order, regardless of stated order in the HTML.
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: rjc, Unassigned)
Details
Attachments
(1 file)
|
209 bytes,
text/html
|
Details |
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; YPC 3.2.0; MathPlayer 2.0; SV1; (R1 1.5); .NET CLR 1.1.4322)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007121805 Minefield/3.0b3pre
Attached is a simple page with one anchor and one form control. the anchor comes before the form control.
Run jaws and open the page.
Press control+home to move to the top.
Press tab and jaws will read the form control, not the anchor, even though the anchor comes first on the page.
Reproducible: Always
Steps to Reproduce:
See above.
1.
2.
3.
Expected Results:
I expect that the tab order should reflect the order of elements in the HTML stream, unless a explicit tabindex greater than zero is used on an element or elements.
| Reporter | ||
Comment 1•18 years ago
|
||
Updated•18 years ago
|
Assignee: nobody → aaronleventhal
Component: Disability Access → Disability Access APIs
Product: Firefox → Core
QA Contact: disability.access → accessibility-apis
Comment 3•15 years ago
|
||
Marco, can you confirm the bug?
Comment 4•15 years ago
|
||
The HTML in this testcase is invalid. At the closing </a, the > sign is missing. Invalid bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Updated•15 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•