Confirmed users, Bureaucrats and Sysops emeriti
722
edits
GavinSharp (talk | contribs) m (Reverted edits by Firefoxer2011 (Talk) to last revision by Surkov.alexander) |
|||
(8 intermediate revisions by 2 users not shown) | |||
Line 1: | Line 1: | ||
#REDIRECT [[MDC:Accessibility:XForms]] | |||
<small>[[Accessibility |<< Back to Accessibility Home Page]]</small> | <small>[[Accessibility |<< Back to Accessibility Home Page]]</small> | ||
== | = Intoduction = | ||
Assistive technologies API for XForms is supported starting from Firefox 3 (Gecko 1.9). Implementation of accessible objects for XForms elements is based on top | |||
of the existing object hierarchy introduced in the Mozilla accessibility module. XForms elements behavior is implemented in accordance with [http://www.mozilla.org/access/toolkit-checklist accessible toolkit checklist]. This article provides a short documentation how accessibility is handled in Gecko for XForms. | |||
= Get Build = | |||
Subsections below explain how you can obtain accessible XForms-enabled build. These are either downloading latest build of firefox or building it yourself. | |||
== Downloading Builds == | |||
For Firefox, you may directly download the nighly "trunk" build of | |||
Firefox and install the XForms extension | |||
which lives in 'xpi' directory of the build. Note, XForms accessibility | |||
is implemented only on trunk. | |||
Trunk builds are not considered stable and should not be installed on | |||
top of the Firefox used for daily browsing. | |||
Currently we have verified that XForms accessibility is working on the | |||
Windows platform, and Linux testing has not yet been done, although | |||
everything should work and is ready to be tested. | |||
You will find trunk builds of Firefox at [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/ ftp.mozilla.org], trunk builds of XForms extension (Windows) at [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/windows-xpi/ ftp.mozilla.org] or trunk builds of XForms extension (Linux) [http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/linux-xpi/ ftp.mozilla.org]. | |||
== Build It Yourself == | |||
If you would like to build firefox/seamonkey yourself then please ensure | |||
your config file has | |||
the following option "ac_add_options | |||
--enable-extensions=default,xforms,schema-validation". | |||
= How To Test = | |||
There are two approaches to test XForms accessibility. The first is to use | |||
and assistive technology such as a screen reader, or an accessibility | |||
testing tool, to make sure XForms elements have proper accessible objects. Or | |||
you may be guided by [http://www.mozilla.org/access/toolkit-checklist toolkit checklist] to check keyboard navigation for XForms controls. | |||
You can try the following link to test XForms accessibility: | |||
* visual XForms elements in XHTML document at [https://bugzilla.mozilla.org/attachment.cgi?id=251493 bugzilla.mozilla.org] | |||
* visual XForms elements in XUL document at [https://bugzilla.mozilla.org/attachment.cgi?id=251497 bugzilla.mozilla.org] | |||
* you can see XForms sample tests at [http://www.mozilla.org/projects/xforms/samples.html Mozilla XForms project] | |||
* there are set of tests at [http://beaufour.dk/xftst/ beaufour.dk] | |||
* W3C's XForms test at [http://www.w3.org/MarkUp/Forms/Test/XForms1.0/Edition2/front_html/XF102edTestSuite.html w3.org] | |||
= Keyboard Navigation Issue = | |||
== Navigation Sequence == | |||
Though XForms spec declares <code>navindex</code> attribute to define the navigation sequence (see [http://www.w3.org/TR/xforms/slice8.html#attrs-ui-common 1.0 specs] or [http://www.w3.org/TR/xforms11/#attrs-ui-common 1.1 specs]) but Rich Schwerdtfeger (<small>Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board</small>) gave some clarification about <code>navindex</code>. He wrote: | Though XForms spec declares <code>navindex</code> attribute to define the navigation sequence (see [http://www.w3.org/TR/xforms/slice8.html#attrs-ui-common 1.0 specs] or [http://www.w3.org/TR/xforms11/#attrs-ui-common 1.1 specs]) but Rich Schwerdtfeger (<small>Distinguished Engineer, SWG Accessibility Architect/Strategist Chair, IBM Accessibility Architecture Review Board</small>) gave some clarification about <code>navindex</code>. He wrote: | ||
<blockquote>Navindex was in XForms - it was stripped out as it was believed the focus model was dependent on the content which used it. So, yes we don't care about navindex in XForms. If you use xhtml1.x use tabindex. If you use Xhtml2 use nextfocus.</blockquote> Therefore since Mozilla XForms works in XHTML (1.x) or XUL documents only then we use <code>tabindex</code> instead. Note, we support <code>-moz-user-focus</code> style neither for XHTML or XUL. | <blockquote>Navindex was in XForms - it was stripped out as it was believed the focus model was dependent on the content which used it. So, yes we don't care about navindex in XForms. If you use xhtml1.x use tabindex. If you use Xhtml2 use nextfocus.</blockquote> Therefore since Mozilla XForms works in XHTML (1.x) or XUL documents only then we use <code>tabindex</code> instead. Note, we support <code>-moz-user-focus</code> style neither for XHTML or XUL. | ||
== | = AT API = | ||
== Accessible properties == | |||
This section describes common rules how accessibility properties are formed for forms control elements. | This section describes common rules how accessibility properties are formed for forms control elements. | ||
Line 123: | Line 166: | ||
Used in combination with event listeners to display a message to the user when the specified event occurs (see the [http://www.w3.org/TR/xforms/slice10.html#action-info spec], the [http://developer.mozilla.org/en/docs/XForms:User_Interface_Elements:Message docs]). The <code>message</code> element has <code>alert</code> role. | Used in combination with event listeners to display a message to the user when the specified event occurs (see the [http://www.w3.org/TR/xforms/slice10.html#action-info spec], the [http://developer.mozilla.org/en/docs/XForms:User_Interface_Elements:Message docs]). The <code>message</code> element has <code>alert</code> role. | ||
= Resources = | |||
Below you will find a list of XForms/Accessiblity resources: | |||
* Mozilla accessibility project at [http://www.mozilla.org/access/ mozilla.org] | |||
* XForms specification at [http://www.w3.org/TR/xforms/ w3.org] | |||
* Mozilla XForms project at [http://www.mozilla.org/projects/xforms/ mozilla.org] | |||
* UI XForms elements references at [http://developer.mozilla.org/en/docs/XForms:User_Interface_Elements devmo] |