Opened 13 years ago

Closed 12 years ago

#2709 closed defect (fixed)

screen reader issues with number spinner

Reported by: Becky Gibson Owned by: Sam Foster
Priority: high Milestone: 0.9
Component: Accessibility Version: 0.9
Keywords: Cc:
Blocked By: Blocking:

Description

After pressing the up or down arrow three or four times in the number spinner, the JAWS screen reader speaks "graphic xxx" (where xxx represents a number that is unique to each arrow) after speaking the updated number value. Since the arrows are not created using graphics and there are not any images on the page without alt text, I'm not sure where the graphic interpretation is coming from?

Change History (8)

comment:1 Changed 13 years ago by Becky Gibson

Status: newassigned

comment:2 Changed 12 years ago by Becky Gibson

Milestone: 0.9M20.9

comment:3 Changed 12 years ago by Becky Gibson

Owner: changed from Becky Gibson to ptbrunet
Status: assignednew

comment:4 Changed 12 years ago by ptbrunet

On hold until Owen resolves the background image / CSS issues. See #3071.

comment:5 Changed 12 years ago by ptbrunet

#3071 is far enough along now that work on this defect can proceed.

comment:6 Changed 12 years ago by ptbrunet

Owner: changed from ptbrunet to Sam Foster

comment:7 in reply to:  description Changed 12 years ago by Sam Foster

Replying to becky:

After pressing the up or down arrow three or four times in the number spinner, the JAWS screen reader speaks "graphic xxx" (where xxx represents a number that is unique to each arrow) after speaking the updated number value. Since the arrows are not created using graphics and there are not any images on the page without alt text, I'm not sure where the graphic interpretation is coming from?

hi Becky, is this resolved now? I'm not sure if this is an old issue pre-dating the Owen and then I did for beta, or something since then.

thanks Sam

comment:8 Changed 12 years ago by Becky Gibson

Resolution: fixed
Status: newclosed

I retested on July 16 trunk build and JAWS is working correctly so have closed. This issue was previous to the style changes and with the change to remove focus to the arrow keys and new implementation of arrows is no longer an issue.

Note: See TracTickets for help on using tickets.