E-mail List Archives
Re: screen reader announcing clickable
From: Paul Collins
Date: Sep 14, 2016 7:11PM
- Next message: Jamous, JP: "Re: holding software vendors accountable for accessibility"
- Previous message: Jim Homme: "Re: holding software vendors accountable for accessibility"
- Next message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: screen reader announcing clickable"
- Previous message in Thread: Jim Homme: "Re: screen reader announcing clickable"
- View all messages in this Thread
Hi Aaaron
Thanks, that's a very good point - Interesting to know that because the
event has been delegated by the parent div, therefore JAWS decides that all
child elements now have a click event assigned.
If you are still struggling to solve it, It would be good to look at the
code and to get an understanding of why and how the click event is being
applied to the div, as there might be a few solutions and it's might be
down to the limitations of what you can change in your codebase, Nick.
Thanks,
Paul
On 15 September 2016 at 07:34, Aaron Cannon < <EMAIL REMOVED> >
wrote:
> The stopPropagation and preventDefault methods can only be called once
> an event handler has been fired. Unfortunately, the screen reader
> makes the determination of what it thinks is clickable long before
> this happens, so I'm afraid that these methods aren't likely to be of
> much help.
>
> Aaron
>
> On 9/14/16, Paul Collins < <EMAIL REMOVED> > wrote:
> > Hi Nick,
> >
> > Without being able to see the code and how the click handler is
> > implemented, I am assuming the click event is bubbling up the dom tree to
> > the parent DIV, when the paragraphs are clicked.
> >
> > If so, it would be worth looking into the following two Javascript DOM
> API
> > events and how JAWS deals with them:
> >
> > event.stopPropogation:
> > https://developer.mozilla.org/en/docs/Web/API/Event/stopPropagation
> > event.preventDefault:
> > https://developer.mozilla.org/en/docs/Web/API/Event/preventDefault
> >
> > Hope that will be of some help, feel free to ask more questions!
> >
> > Cheers,
> > Paul
> >
> > On 14 September 2016 at 16:09, Brandon Keith Biggs <
> > <EMAIL REMOVED> > wrote:
> >
> >> Hello,
> >> The clickable element means that everything inside it will be clickable.
> >> It
> >> doesn't matter if anything is attached to it, it is clickable. I'm not
> >> sure
> >> if there is any way for a screen reader to recognize if something
> happens
> >> when an element is pressed, but I doubt it. If that clickable didn't
> show,
> >> a screen reader user would never know anything in that element was
> >> clickable.
> >> The only way to get rid of this is to just wrap the part that will get a
> >> click in a clickable div and remove the event from higher up the tree.
> >> Thanks,
> >>
> >>
> >> Brandon Keith Biggs <http://brandonkeithbiggs.com/>
> >>
> >> On Tue, Sep 13, 2016 at 8:59 PM, Nick Allan <Nick.Allan@visionaustralia.
> >> org>
> >> wrote:
> >>
> >> > Hi all
> >> > I'm doing some testing on a web page where a section has paragraphs of
> >> > text that all announce clickable when you arrow through it using jaws.
> >> > There is a div a few levels up in the dom that has a click event
> >> > attached
> >> > to it according to firebug in firefox.
> >> > I assume this is why the text is saying clickable. Is there any method
> >> > to
> >> > stop a screen reader announcing clickable other than verbosity
> settings
> >> in
> >> > the screen reader? clicking on the text doesn't actually do anything.
> >> >
> >> > Any suggestions would be welcome.
> >> >
> >> >
> >> >
> >> >
> >> > Nick Allan
> >> > Specialist Support
> >> > Vision Australia
> >> > 454 Glenferrie road
> >> > Kooyong Vic. 3144
> >> > P: 1300 84 74 66
> >> > www.visionaustralia.org<http://www.visionaustralia.org>
> >> >
> >> >
> >> > [http://www.visionaustralia.org/images/default-source/
> >> > Email-signature-banners/digital-accessibility-toolkit.
> >> > jpg?Status=Temp&sfvrsn=4] <http://www.visionaustralia.
> org/business-and-
> >> > professionals/digital-access-consulting/accessibility-toolkit>
> >> >
> >> > Vision Australia's Accessibility Toolkit - Resources to help
> businesses
> >> > understand and implement digital accessibility
> www.visionaustralia.org/
> >> > accessibilitytoolkit
> >> >
> >> > ABN: 67 108 391 831 ACN: 108 391 831
> >> >
> >> > Vision Australia, supporting people who are blind or have low vision
> to
> >> > live the life they choose. This email (including its attachments) is
> >> > confidential and may contain legally privileged material or personal
> >> > information. If you are not a named addressee you must not use,
> >> > disclose,
> >> > copy, disseminate or print the email or any information in it. If you
> >> have
> >> > received this email in error please notify us immediately and delete
> the
> >> > email and any copies. Vision Australia is not responsible for any
> >> > changes
> >> > made to a document other than those made by Vision Australia or for
> the
> >> > effect of the changes to the document's meaning. Vision Australia
> >> > accepts
> >> > no liability for any damage caused by this email or its attachments
> due
> >> to
> >> > viruses, interference, interception, corruption or unauthorised
> access.
> >> > > >> > > >> > > >> > > >> >
> >> > >> > >> > >> > >>
> > > > > > > > > >
> > > > >
- Next message: Jamous, JP: "Re: holding software vendors accountable for accessibility"
- Previous message: Jim Homme: "Re: holding software vendors accountable for accessibility"
- Next message in Thread: Moore,Michael (Accessibility) (HHSC): "Re: screen reader announcing clickable"
- Previous message in Thread: Jim Homme: "Re: screen reader announcing clickable"
- View all messages in this Thread