> > one more thing is, I am working on an accessibility extension. > Great. What will it include?
> Is there any documentation on how to support keyboard accessibility in > Firebug? > There is a long article about accessibility in our wiki<http://getfirebug.com/wiki/index.php/Accessibility>, though it's already quite old. > I could able to figure out some parts of the code in Firebug which related > to accessibility like firebug/accessible/a11y.js. > I do have couple of questions like when do we add keyboard support to the > Firebug panels and the toolbar-buttons inside those panels? > When you click the *Enable Accessibility Enhancements* option, the preference a11y.enable is toggled. updateOption(name, value) inside *a11y.js * will be notified about the change and calls set(enable, chrome). This method in turn calls performEnable(chrome), which sets several key listeners and the class useA11y, which indicates, that the accessibility is enabled. Describing that I have to say, that I am not the person, that implemented the accessibility features in Firebug and I just had a fast look on how it works right now. For further questions Hans Hillen will be the right person to talk to, which is the creator of the a11y part and currently starting to refactor the whole a11y system<https://wiki.mozilla.org/Firebug/WeeklyUpdates/2011-11-15#Accessibility_.28a11y.29>used in Firebug to modularize it and make it easier to reuse. Therefore I added him as CC. Sebastian -- You received this message because you are subscribed to the Google Groups "Firebug" 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 https://groups.google.com/forum/#!forum/firebug
