Opened 7 years ago

Last modified 2 years ago

#15905 open defect

Dialog: IE + JAWS - Problem distinguishing content of a modal dialog from the underlying parent page

Reported by: nsskumar Owned by:
Priority: undecided Milestone: 1.15
Component: Accessibility Version: 1.8.0
Keywords: Cc: mikeb
Blocked By: Blocking:

Description

We are using JAWS 13 for testing/validating accessibility.

Dojo version 1.8 IE 9

When using IE, If a modal dialog is opened using Dojo Dialog, user is able to see and navigate (INSERT + F5)through all the tab focusable elements including the underlying parent page.

Steps to duplicate this issue

  1. Save the attached testModal.html in your local drive
  2. Run JAWS 13
  3. Open testModal.html in IE9 (select allow blocked content if you get the warning)
  4. Press TABs to reach/select “Modal Dialog(Dojo)” button
  5. Press Enter to open the Modal dialog which contains a simple form with 2 fields Name & Location
  6. Press Tab , now the cursor will be in Location Field
  7. Press INSERT+F5 , you will get a list of 4 focusable elements on the modal dialog + “Modal Dialog(Dojo) button” which exists on the underlying parent page. This button should not be listed, since it exists on the parent page and user cannot select this element.

Attachments (1)

testModal.html (1.5 KB) - added by nsskumar 7 years ago.

Download all attachments as: .zip

Change History (9)

Changed 7 years ago by nsskumar

Attachment: testModal.html added

comment:1 Changed 7 years ago by Douglas Hays

Cc: mikeb added
Component: Dijit - FormAccessibility
Owner: Douglas Hays deleted
Status: newassigned

comment:2 Changed 7 years ago by bill

#15906 is a duplicate of this ticket.

comment:3 Changed 7 years ago by bill

Summary: IE + JAWS - Problem distinguishing content of a modal dialog from the underlying parent pageDialog: IE + JAWS - Problem distinguishing content of a modal dialog from the underlying parent page

See also #15370, and especially #12479.

comment:4 Changed 7 years ago by mikeb

Hello, I tried doing this in IE8, and could not reproduce the error? Can you confirm? If this is the case then it seems like this is an issue specific to IE9.

comment:5 Changed 6 years ago by nsskumar

We came across this issue using JAWS 13 & IE9 Now We are able to reproduce this issue again on JAWS 14 & IE9

comment:6 Changed 6 years ago by bill

Milestone: tbdfuture
Status: assignedopen

comment:7 Changed 3 years ago by dylan

Milestone: future1.12

comment:8 Changed 2 years ago by dylan

Milestone: 1.131.15

Ticket planning... move current 1.13 tickets out to 1.15 to make it easier to move tickets into the 1.13 milestone.

Note: See TracTickets for help on using tickets.