Firefox:2.0 Accessibility: Difference between revisions

← Older edit

Firefox:2.0 Accessibility (view source)

Revision as of 06:14, 27 July 2006

26 bytes added , 27 July 2006

m

fixed typo

Linuxmigration

16

edits

@@ Line 1: / Line 1: @@
-(My first ever Wiki edit, please excuse poor quality)
+* Accessibility of XUL widgets should be reviewed? (Ben Goodger mentioning focus selections on the widgets in the preferences window)
+* Keyboard customization (functionality from the keyconfig extension)
+* Text-rendering mode like Opera would be good? Also a useful tool for developers for testing semantic markup. This would help boost people's enthusiasm for supplying accessible sites by making testing far faster (Lynx isn't always that easy to setup and configure)
+* New buttons on toolbar customization sheet for increase / decrease font size and/or other accessibility options
+* A fit to window-width option (as in Opera) would come in handy to eliminate horizontal scrolling
-*Accessibility of XUL widgets should be reviewed? (Ben Goodger mentioning focus selections on the widgets in the preferences window)
+== Crazy blind dude recommendations, in addition to previous: ==
-*Keyboard customization (as mentioned elsewhere)
+* Attempt to work with Freedom Scientific and GW Micro to sort out screen reader "issues" to work with the most mainstream products (JAWS, Window-Eyes) better.
-*Text-rendering mode like Opera would be good? Also a useful tool for developers for testing semantic markup. This would help boost people's enthusiasm for suppling accessible sites by making testing far faster (Lynx isn't always that easy to setup and configure)
+* Implementation of VoiceXML similar to Opera in the Firefox and Thunderbird projects respectively, maybe even Sunbird/Calendar.
-*New buttons on toolbar customization sheet for increase / decrease font size and/or other accessibility options?
+* Seek a better solution as an alternative to MSAA compliance (here's hoping).
+* Develop a better way for browser to recognize security verification schemes that are inherently inaccessible because of their garbled visual nature and provide an alternative means of verification through the browser.
-<h2> Crazy blind dude recommendations, in addition to previous: </h2>
-<li> Attempt to work with Freedom Scientific and GW Micro to sort out screen reader "issues" to work with the most mainstream products (JAWS, Window-Eyes) better. </li>
-<li> Implementation of VoiceXML similar to Opera in the Firefox and Thunderbird projects respectively, maybe even Sunbird/Calendar. </li>
-<li> Seek a better solution as an alternative to MSAA compliance (here's hoping). </li>
-<li> Develop a better way for browser to recognize security verification schemes that are inherently inaccessible because of their garbled visual nature and provide an alternative means of verification through the browser. </li>