The above assumption is based on your idea that dom updates like show/ hide are announced to a screen reader (after the initial page load). Do you have evidence this is the case?
On Nov 11, 5:38 am, Scott González <[EMAIL PROTECTED]> wrote: > I don't see a need for this, since screen readers don't need to be > able to read content that's supposed to be hidden. When the content > is supposed to be viewable, it will be shown and beaccessibleby the > screen reader. > > We're currently fixing the accessibility issues that accordion > has:http://ui.jquery.com/bugs/ticket/3553 > > On Nov 10, 1:50 pm, dave <[EMAIL PROTECTED]> wrote: > > > I'm curious what is required to change the use of display:none to > > something similar to text replacement, which seems to be more > >accessiblefor screen readers. so instead of display:none hiding > > inactive panels, hide by adding the following class: > > > .display-none { > > position:absolute; > > left:-999px; > > width:900px; > > > } > > > From my reading, it seems screen readers do not render elements with > > display:none applied. > > > On Oct 24, 7:48 am, Jon dotjay Gibbins <[EMAIL PROTECTED]> wrote: > > > > Hi Karl, > > > > jQuery UI adds a tabindex of 0 to theaccordionheaders (e.g. > > > .ui-accordion-header). It looks like Jörn Zaefferer is on the case and > > > removing these tabindex attributes:http://tinyurl.com/6ay79c > > > > I just ran a quick test and it seems Firefox has some weird behaviour > > > concerning child elements of elements which have tabindex="0" that > > > aren't normally tabbable. In fact, looking at bugzilla.mozilla.org, it > > > seems Firefox has quite a few tabindex anomalies. :) > > > > Anyway, if I have <h2 tabindex="0"><a href="#foo">Accordion1</a></ > > > h2>, I can't get at the link inside the heading when tabbing > > > *forwards*, but I can when I Shift+Tab through the page. Firefox won't > > > let you tab through theaccordionproperly because of this. > > > > You can "undo" the tabindex that UI sets by calling this after > > > youraccordionset up and Firefox will love you again: > > > $('.ui-accordion-header').attr('tabindex',''); > > > > You might also consider setting these tabindex attributes to -1, which > > > allows elements that aren't usually focussable (e.g. <h*>) to receive > > > focus, but a tabindex of -1 is not recognised by all browsers and may > > > invalidate your page. Even with that, the elements would not appear in > > > the page's tab order anyway, only allow you to focus those elements > > > using JavaScript. > > > > Jon > > > > On Oct 24, 8:49 am, TSG <[EMAIL PROTECTED]> wrote: > > > > > Hi all, > > > > > I've used the excellent themeroller to grab some code for anaccordion > > > > control and have it running fine on my local machine (so no example to > > > > point you too). I was surprised to find that in Firefox 3 the > > > >accordiondoesn't work via the keyboard - it's fine in Safari and > > > > (shock, horror) IE7. > > > > > Does anyone have any insight on this? Is it FF, ui.js or do I need to > > > > add a parameter or something to the config? Ideally, I'd like to add > > > > event: "mouseover" and still have it keyboard-accessiblebut I assume > > > > you can't stack events? > > > > > Thanks in advance, keep up the good work! > > > > > Regards, Karl > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery UI" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/jquery-ui?hl=en -~----------~----~----~----~------~----~------~--~---
