This document provides a list of links to all accessibility articles on the Mozilla Developer Network.
Found 240 pages:
# | Page | Tags and summary |
---|---|---|
1 | Accessibility | Accessibility, Guide |
Accessibility in Web development means enabling as many people as possible to use Web sites, even when those people's abilities are limited in some way. Here we provide information on developing content to be accessible. | ||
2 | ARIA | ARIA, Accessibility, Web |
Accessible Rich Internet Applications (ARIA) defines ways to make Web content and Web applications (especially those developed with Ajax and JavaScript) more accessible to people with disabilities. | ||
3 | ARIA Live Regions | ARIA, Accessibility, ariaLive |
In the past, a web page change could only be spoken in entirety which often annoyed a user, or by speaking very little to nothing, making some or all information inaccessible. Until recently, screen readers have not been able to improve this because no standardized markup existed to alert the screen reader to a change. ARIA live regions fill this gap and provide suggestions to screen readers regarding whether and how to interrupt users with a change. | ||
4 | ARIA Screen Reader Implementors Guide | ARIA, Accessibility |
This is just a guide. Live region markup is a complex area which is somewhat open to interpretation. The following is intended to provide implementation guidance that respects screen readers developers' need to try different things. The intention is to strike a balance between providing useful guidance on how to use the markup's intended meaning while supporting live regions as an area for screen readers to innovate and compete. | ||
5 | ARIA Test Cases | ARIA, Accessibility |
For each example we test the "Expected" results with assistive technologies, for each browser that AT supports WAI-ARIA in. Where a failure occurs we will test the browser for API incorrectness, using tools such as MSAA Inspect. This must be done in order to determine where to file a bug (browser or AT). | ||
6 | ARIA guides | ARIA |
Accessible Rich Internet Applications (ARIA) defines ways to make the Web more accessible to people with disabilities. A few guidelines to follow that ensure better accessibility, like using drag and drop for placement of the widgets. | ||
7 | Forms | ARIA, Accessibility |
The following pages provide various techniques for improving the accessibility of web forms: | ||
8 | Basic form hints | ARIA, Accessibility, Forms |
When implementing forms using traditional HTML form-related elements, it is important to provide labels for controls and to explicitly associate a label with its control. When a screen reader user navigates a page, the screen reader will describe form controls, but without a direct association between the control and its label, the screen reader has no way of knowing which label is the correct one. | ||
9 | Multipart labels: Using ARIA for labels with embedded fields inside them | ARIA, Accessibility, Guide, NeedsContent, label |
The solution is in an ARIA attribute called aria-labelledby. Its parameter is a string that consists of the IDs of the HTML elements you want to concatenate into a single accessible name. | ||
10 | alerts | ARIA, Accessibility, Forms, Web |
You have a form — a contact form, for example — that you want to put some accessible error checking into. Common problems include e-mail addresses that are not valid, or a name field that does not contain at least a first name or a surname. | ||
11 | How to file ARIA-related bugs | ARIA, Bugzilla |
The state of ARIA technology has always depended on the community. If you notice an implementation issue, please take a little time and let the developers know. Here's where to file bugs: | ||
12 | Using ARIA | ARIA, Accessibility |
The techniques below describes each composite role as well as their required and optional child roles. | ||
13 | ARIA Technique Template | Accessibility |
No summary! | ||
14 | Using the alert role | ARIA, Accessibility, Advanced, CSS, Example, HTML, NeedsContent, alerts, role configuration, wcag1.2.1, wcag3.3.1 |
The alert role is used to communicate an important and usually time-sensitive message to the user. When this role is added to an element, the browser will send out an accessible alert event to assistive technology products which can then notify the user about it. The alert role is most useful for information that requires the user's immediate attention, for example: | ||
15 | Using the alertdialog role | ARIA, Accessibility, CodingScripting, HTML, NeedsContent, Role, Web Development, agent, alertdialog, alerts, modal, user, userAgent |
The alertdialog role is used to notify the user of urgent information that demands the user's immediate attention. As the name implies, alertdialog is a type of dialog. This means that most of the instructions provided in the 'using the dialog role' technique are applicable to the alertdialog role as well: |
||
16 | Using the aria-activedescendant attribute | Attribute, NeedsContent, Property |
This article describes the aria-activedescendant property. | ||
17 | Using the aria-describedby attribute | ARIA, Accessibility, Attribute |
The aria-describedby attribute is used to indicate the IDs of the elements that describe the object. It is used to establish a relationship between widgets or groups and text that described them. This is very similar to aria-labelledby: a label describes the essence of an object, while a description provides more information that the user might need. |
||
18 | Using the aria-invalid attribute | ARIA, Accessibility, Attribute, CodingScripting, HTML, JavaScript, NeedsContent, Role, agent, alert, user, userAgent |
The aria-invalid attribute is used to indicate that the value entered into an input field does not conform to the format expected by the application.This may include formats such as email addresses or telephone numbers. aria-invalid can also be used to indicate that a required field has not been filled in.The attribute should be programmatically set as a result of a validation process. |
||
19 | Using the aria-label attribute | ARIA, Accessibility, CodingScripting, HTML, NeedsContent, Reference, Référence, agent, aria-label, user, userAgent |
The aria-label attribute is used to define a string that labels the current element. Use it in cases where a text label is not visible on the screen. If there is visible text labeling the element, use aria-labelledby instead. |
||
20 | Using the aria-labelledby attribute | ARIA, Accessibility, NeedsContent, broken link |
The aria-labelledby attribute contains the element IDs of labels in objects such as input elements, widgets, and groups. The attribute establishes relationships between objects and their labels. Assistive technology, such as screen readers, use this attribute to catalog the objects in a document so that users can navigate between them. Without an element ID, the assistive technology cannot catalog the object. |
||
21 | Using the aria-orientation attribute | ARIA, Accessibility, Attribute |
The aria-orientation attribute is used to indicate whether an element is oriented horizonally or vertically. | ||
22 | Using the aria-relevant attribute | ARIA, Accessibility, NeedsExample, ariaLive, attri |
The aria-relevant attribute is an optional value used to describe what types of changes have occurred to an aria-live region and of which are relevant and should be announced. Any change that is not relevant acts in the same manner it would if the aria-live attribute were set to off . |
||
23 | Using the aria-required attribute | ARIA, Accessibility, NeedsContent |
The aria-required attribute is used to indicate that user input is required on an element before a form can be submitted. This attribute can be used with any typical HTML form element; it is not limited to elements that have an ARIA role assigned. |
||
24 | Using the aria-valuemax attribute | ARIA, Accessibility |
The aria-valuemax attribute is | ||
25 | Using the aria-valuemin attribute | ARIA, Accessibility, NeedsContent |
The aria-valuemin attribute is used to define the minimum value allowed for a range widget such as a slider, spinbutton or progressbar. If the aria-valuenow has a known maximum and minimum, the author SHOULD provide properties for aria-valuemax and aria-valuemin .The value of aria-valuemin MUST be less than or equal to the value of aria-valuemax . |
||
26 | Using the aria-valuenow attribute | ARIA, Accessibility, NeedsContent |
The aria-valuenow attribute is used to define the current value for a range widget such as a slider, spinbutton or progressbar. If the current value is not known, the author should not set the aria-valuenow attribute. If the aria-valuenow has a known minimum and maximum value, authors should set the aria-valuemin and aria-valuemax attributes. |
||
27 | Using the aria-valuetext attribute | ARIA, Accessibility, Attribute |
The aria-valuetext attribute is used to define the human readable text alternative of aria-valuenow for a range widget such as progressbar, spinbutton or slider. |
||
28 | Using the article role | ARIA, Accessible, NeedsContent |
The article role is used to identify a section of a page that forms an independent part of a document, page or site. Examples of an article include web log posts, newspaper or magazine articles and use-submitted comments. It is independent in that its contents could stand alone, for example in syndication. | ||
29 | Using the banner role | NeedsContent |
No summary! | ||
30 | Using the button role | ARIA, Accessibility, NeedsContent |
The button role should be used for clickable elements that trigger a response when activated by the user. On its own, role="button" can make any element (e.g. <p>, <span> or <div>) appear as a button control to a screen reader. Additionally, this role can be used in combination with the aria-pressed attribute to create toggle buttons. |
||
31 | Using the checkbox role | ARIA, Accessibility, NeedsContent, Role, Rôle |
The checkbox role is used for checkable interactive controls. If an element uses role="checkbox" it is required for that element to also have a aria-checked attribute that exposes the checkbox's state to assistive technology. While the native HTML checkbox form control can only have two checked states ("checked" or "not checked"), a role=checkbox element can expose three states through aria-checked : |
||
32 | Using the dialog role | ARIA, Accessibility, NeedsContent, Web Development |
The dialog role is used to mark up a DHTML based application dialog or window that separates content or UI from the rest of the web application or page. Visually, dialogs are generally placed on top of the rest of the page content using an overlay. Dialogs can be either non-modal (it's still possible to interact with content outside of the dialog) or modal (only the content in the dialog can be interacted with). |
||
33 | Using the group role | ARIA, Accessibility, NeedsContent |
This technique demonstrates how to use the group role and describes the effect it has on browsers and assistive technology. | ||
34 | Using the link role | ARIA, Accessibility, NeedsContent |
This technique demonstrates how to use the link role and describes the effect it has on browsers and assistive technology. | ||
35 | Using the listbox role | ARIA, Accessibility, NeedsContent |
This technique demonstrates how to use the listbox role and describes the effect it has on browsers and assistive technology. | ||
36 | Using the log role | ARIA, Accessibility, NeedsContent |
This technique demonstrates how to use the log role and describes the effect it has on browsers and assistive technology. |
||
37 | Using the presentation role | NeedsContent |
No summary! | ||
38 | Using the progressbar role | ARIA, Accessibility, NeedsContent, NeedsExample |
This technique demonstrates how to use the progressbar role. |
||
39 | Using the radio role | NeedsContent |
No summary! | ||
40 | Using the slider role | ARIA, Accessibility, NeedsContent |
This technique demonstrates how to use the slider role. | ||
41 | Using the status role | ARIA, Accessibility, NeedsContent |
This technique demonstrates how to use the status role and describes the effect it has on browsers and assistive technology. | ||
42 | Using the switch role | ARIA, Accessibility, NeedsContent, Role, Rôle |
Technical review completed. Editorial review completed. | ||
43 | Using the textbox role | ARIA, Accessibility, NeedsContent |
The textbox role is used to identify an element that allows the input of free-form text. |
||
44 | Using the toolbar role | NeedsContent |
No summary! | ||
45 | Web applications and ARIA FAQ | ARIA, Accessibility, Guide |
WAI-ARIA is the Accessible Rich Internet Applications specification from the Web Accessibility Initiative at the W3C. ARIA provides a means to make web applications and widgets more accessible to a diverse range of users, including those who use assistive technologies such as screen readers or magnifiers. | ||
46 | widgets | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
47 | overview | Accessibility, JavaScript, Landing, NeedsUpdate |
Here's a look at working examples and best practices in building accessible JavaScript widgets. | ||
48 | AT APIs Support | AT_APIs, Accessibility |
This documentation explains how makers of screen readers, voice dictation packages, onscreen keyboards, magnification software and other assitive technologies can support Gecko-based software. We provide for them the support of these products on Windows, Linux/Unix and OS X platforms. | ||
49 | AT-SPI | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
50 | AT-SPI Document Attributes | AT_APIs, Accessibility |
You can obtain document attributes by Document::getAttributes method. |
||
51 | AT-SPI Events | AT_APIs, Accessibility |
Proposed mapping AT-SPI Events to Gecko Events. | ||
52 | AT-SPI Object Attributes | AT_APIs, Accessibility |
AT-SPI exposes object attributes by Accessible::getAttributes method. |
||
53 | AT-SPI Roles | AT_APIs, Accessibility |
Below you will find the table of AT-SPI roles and how they are mapped to Gecko roles. | ||
54 | AT-SPI States | AT_APIs, Accessibility |
The table below shows how AT-SPI states are mapped to Gecko states. | ||
55 | AT-SPI Text Attributes | AT_APIs, Accessibility |
AT-SPI has Text::getAttributes() method to get text attributes. |
||
56 | Find the Window and Load the Document | AT_APIs, Accessibility |
No summary! | ||
57 | MSAA Relations | AT_APIs, Accessibility |
No summary! | ||
58 | Supported AT SPI Interfaces | AT_APIs, Accessibility |
No summary! | ||
59 | Differences | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
60 | MSAA Features We Do Not Support | AT_APIs, Accessibility |
For the most part, where we support an MSAA feature, we have tried to duplicate Internet Explorer's use of it. | ||
61 | Gecko | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
62 | Gecko Relations | AT_APIs, Accessibility, Gecko |
Below you will find a list of supported relations by Gecko. Relation constants are defined in nsIAccessibleRelations interface ( | ||
63 | Gecko Roles | AT_APIs, Accessibility, Reference, Référence |
This page offers a list of accessible roles used in Gecko. Role constants are defined in the nsIAccessibleRole interface. |
||
64 | ROLE AUTOCOMPLETE | AT_APIs, Accessibility |
No summary! | ||
65 | ROLE CAPTION | AT_APIs, Accessibility |
No summary! | ||
66 | ROLE DOCUMENT FRAME | AT_APIs, Accessibility |
No summary! | ||
67 | ROLE EDITBAR | AT_APIs, Accessibility |
No summary! | ||
68 | ROLE ENTRY | AT_APIs, Accessibility |
No summary! | ||
69 | ROLE FOOTER | AT_APIs, Accessibility |
No summary! | ||
70 | ROLE FORM | AT_APIs, Accessibility |
No summary! | ||
71 | ROLE GLASS PANE | AT_APIs, Accessibility |
No summary! | ||
72 | ROLE HEADER | AT_APIs, Accessibility |
No summary! | ||
73 | ROLE HEADING | AT_APIs, Accessibility |
No summary! | ||
74 | ROLE HTML CONTAINER | AT_APIs, Accessibility |
No summary! | ||
75 | ROLE ICON | AT_APIs, Accessibility |
No summary! | ||
76 | ROLE LABEL | AT_APIs, Accessibility |
No summary! | ||
77 | ROLE LAYERED PANE | AT_APIs, Accessibility |
No summary! | ||
78 | ROLE LISTBOX | AT_APIs, Accessibility |
No summary! | ||
79 | ROLE OPTION PANE | AT_APIs, Accessibility |
No summary! | ||
80 | ROLE PAGE | AT_APIs, Accessibility |
No summary! | ||
81 | ROLE PARAGRAPH | AT_APIs, Accessibility |
No summary! | ||
82 | ROLE PASSWORD TEXT | AT_APIs, Accessibility |
No summary! | ||
83 | ROLE REDUNDANT OBJECT | AT_APIs, Accessibility |
No summary! | ||
84 | ROLE RICH OPTION | AT_APIs, Accessibility |
No summary! | ||
85 | ROLE RULER | AT_APIs, Accessibility |
No summary! | ||
86 | ROLE SECTION | AT_APIs, Accessibility |
No summary! | ||
87 | ROLE TOGGLE BUTTON | AT_APIs, Accessibility |
No summary! | ||
88 | ROLE TREE TABLE | AT_APIs, Accessibility |
No summary! | ||
89 | ROLE VIEWPORT | AT_APIs, Accessibility |
No summary! | ||
90 | ROLE_ACCEL_LABEL | AT_APIs, Accessibility, Reference, Référence |
Represents a label control that has an accelerator. | ||
91 | ROLE_ALERT | AT_APIs, Accessibility, Reference, Référence |
Represents an alert or a condition that a user should be notified about. Assistive technologies typically respond to the role by reading the entire onscreen contents of containers advertising this role. Should be used for warning dialogs, etc. | ||
92 | ROLE_ANIMATION | AT_APIs, Accessibility, Reference, Référence |
Represents an animation control, which contains content that changes over time, such as a control that displays a series of bitmap frames. | ||
93 | ROLE_APPLICATION | AT_APIs, Accessibility |
Represents a main window for an application. Also refer to ROLE_APP_ROOT . |
||
94 | ROLE_APP_ROOT | AT_APIs, Accessibility, Reference, Référence |
An object which is used to allow input of characters not found on a keyboard, such as the input of Chinese characters on a Western keyboard. | ||
95 | ROLE_ARROW | AT_APIs, Accessibility, Reference, Référence |
Represents an arrow in one of the four cardinal directions. | ||
96 | ROLE_BORDER | AT_APIs, Accessibility, Reference, Référence |
Represents a window border. | ||
97 | ROLE_BUTTONDROPDOWN | AT_APIs, Accessibility |
Represents a button that drops down a list of items. | ||
98 | ROLE_BUTTONDROPDOWNGRID | AT_APIs, Accessibility, Reference, Référence |
Represents a button that drops down a grid. | ||
99 | ROLE_BUTTONMENU | AT_APIs, Accessibility, Reference, Référence |
Represents a button that drops down a menu. | ||
100 | ROLE_CALENDAR | AT_APIs, Accessibility, NeedsContent, Reference, Référence |
A calendar that lets the user select a date. | ||
101 | ROLE_CANVAS | AT_APIs, Accessibility, Reference, Référence |
Represents a control that can be drawn into and is used to trap events. | ||
102 | ROLE_CARET | AT_APIs, Accessibility, Reference, Référence |
Represents the system caret. The role is supported for caret. | ||
103 | ROLE_CELL | AT_APIs, Accessibility, Reference, Référence |
Represents a cell within a table. Also, see ROLE_TABLE . |
||
104 | ROLE_CHARACTER | AT_APIs, Accessibility, Reference, Référence |
Represents a cartoon-like graphic object, such as Microsoft Office Assistant, which is displayed to provide help to users of an application. | ||
105 | ROLE_CHART | AT_APIs, Accessibility |
Represents a graphical image used to represent data. | ||
106 | ROLE_CHECKBUTTON | AT_APIs, Accessibility, Reference, Référence |
Represents a check box control. | ||
107 | ROLE_CHECK_MENU_ITEM | AT_APIs, Accessibility, Reference, Référence |
Represents a menu item with a check box. | ||
108 | ROLE_CHROME_WINDOW | AT_APIs, Accessibility, Reference, Référence |
Frame role. A top level window with a title bar, border, menu bar, etc. It is often used as the primary window for an application. | ||
109 | ROLE_CLOCK | AT_APIs, Accessibility, Reference, Référence |
Represents a control that displays time. | ||
110 | ROLE_COLOR_CHOOSER | AT_APIs, Accessibility, Reference, Référence |
Represents a specialized dialog that lets the user choose a color. | ||
111 | ROLE_COLUMNHEADER | AT_APIs, Accessibility, Reference, Référence |
Represents a column header, providing a visual label for a column in a table. Also refer to ROLE_TABLE . |
||
112 | ROLE_COMBOBOX | AT_APIs, Accessibility, Reference, Référence |
Represents a combo box; an edit control with an associated list box that provides a set of predefined choices. | ||
113 | ROLE_COMBOBOX_LIST | AT_APIs, Accessibility, Reference, Référence |
A list of items that is presented using a combobox. | ||
114 | ROLE_COMBOBOX_OPTION | AT_APIs, Accessibility, Reference, Référence |
A item of list that is shown by combobox. | ||
115 | ROLE_CURSOR | AT_APIs, Accessibility, Reference, Référence |
Represents the system mouse pointer. | ||
116 | ROLE_DATE_EDITOR | AT_APIs, Accessibility, Reference, Référence |
Represents control whose purpose is to allow a user to edit a date. | ||
117 | ROLE_DESKTOP_FRAME | AT_APIs, Accessibility, Reference, Référence |
A desktop pane. A pane that supports internal frames and iconified versions of those internal frames. | ||
118 | ROLE_DESKTOP_ICON | AT_APIs, Accessibility, Reference, Référence |
An iconified internal frame in an ROLE_DESKTOP_PANE . Also refer to ROLE_INTERNAL_FRAME . |
||
119 | ROLE_DIAGRAM | AT_APIs, Accessibility, Reference, Référence |
Represents a graphical image used to diagram data. | ||
120 | ROLE_DIAL | AT_APIs, Accessibility, Reference, Référence |
Represents a dial or knob whose purpose is to allow a user to set a value. | ||
121 | ROLE_DIALOG | AT_APIs, Accessibility, Reference, Référence |
Represents a dialog box or message box. | ||
122 | ROLE_DIRECTORY_PANE | AT_APIs, Accessibility, Reference, Référence |
A directory pane. A pane that allows the user to navigate through and select the contents of a directory. May be used by a file chooser. Also refer to ROLE_FILE_CHOOSER . |
||
123 | ROLE_DOCUMENT | AT_APIs, Accessibility, Reference, Référence |
Represents a document window. A document window is always contained within an application window. | ||
124 | ROLE_DROPLIST | AT_APIs, Accessibility |
Represents the calendar control. | ||
125 | ROLE_EQUATION | AT_APIs, Accessibility, Reference, Référence |
Represents a mathematical equation. | ||
126 | ROLE_FILE_CHOOSER | AT_APIs, Accessibility, Reference, Référence |
A file chooser. A specialized dialog that displays the files in the directory and lets the user select a file, browse a different directory, or specify a filename. May use the directory pane to show the contents of a directory. Also refer to ROLE_DIRECTORY_PANE . |
||
127 | ROLE_FONT_CHOOSER | AT_APIs, Accessibility, Reference, Référence |
A font chooser. A font chooser is a component that lets the user pick various attributes for fonts. | ||
128 | ROLE_GRAPHIC | AT_APIs, Accessibility, Gecko, Reference, Référence |
Represents a picture. | ||
129 | ROLE_GRIP | AT_APIs, Accessibility, Reference, Référence |
Represents a special mouse pointer, which allows a user to manipulate user interface elements such as windows. For example, a user clicks and drags a sizing grip in the lower-right corner of a window to resize it. | ||
130 | ROLE_GROUPING | AT_APIs, Accessibility, Reference, Référence |
Logically groups other objects. There is not always a parent-child relationship between the grouping object and the objects it contains. | ||
131 | ROLE_HELPBALLOON | AT_APIs, Accessibility, NeedsContent, Reference, Référence |
Displays a Help topic in the form of a tooltip or help balloon. | ||
132 | ROLE_HOTKEYFIELD | AT_APIs, Accessibility, Reference, Référence |
Represents a hot-key field that allows the user to enter a combination or sequence of keystrokes | ||
133 | ROLE_IMAGE_MAP | AT_APIs, Accessibility, NeedsContent, Reference, Référence |
An image map, which has child links representing the areas. | ||
134 | ROLE_IME | AT_APIs, Accessibility, Reference, Référence |
An object which is used to allow input of characters not found on a keyboard, such as the input of Chinese characters on a Western keyboard. | ||
135 | ROLE_INDICATOR | AT_APIs, Accessibility, Reference, Référence |
Represents an indicator, such as a pointer graphic, that points to the current item. | ||
136 | ROLE_INTERNAL_FRAME | AT_APIs, Accessibility, Reference, Référence |
A sub-document. | ||
137 | ROLE_IPADDRESS | AT_APIs, Accessibility, Reference, Référence |
Represents an edit control designed for an Internet Protocol (IP) address. The edit control is divided into one section for each octet of the IP address. | ||
138 | ROLE_LINK | AT_APIs, Accessibility, Reference, Référence |
Represents a link to something else. This object might look like text or a graphic, but it acts like a button. | ||
139 | ROLE_LIST | AT_APIs, Accessibility, Reference, Référence |
Represents either: | ||
140 | ROLE_LISTITEM | AT_APIs, Accessibility, Reference, Référence |
Represents an item in a list. See also ROLE_LIST . |
||
141 | ROLE_MENUBAR | AT_APIs, Accessibility, Reference, Référence |
Represents the menu bar (positioned beneath the title bar of a window) from which menus are selected by the user. | ||
142 | ROLE_MENUITEM | AT_APIs, Accessibility |
Represents a menu item, which is an entry in a menu that a user can choose to carry out a command, select an option. | ||
143 | ROLE_MENUPOPUP | AT_APIs, Accessibility, Reference, Référence |
Represents a menu, which presents a list of options from which the user can make a selection to perform an action. | ||
144 | ROLE_NOTHING | AT_APIs, Accessibility, Reference, Référence |
Used when the accessible doesn't have a strongly defined role. | ||
145 | ROLE_OPTION | AT_APIs, Accessibility, Reference, Référence |
An option in a listbox. | ||
146 | ROLE_OUTLINE | AT_APIs, Accessibility |
Represents an outline or tree structure, such as a tree view control, that displays a hierarchical list and allows the user to expand and collapse branches. | ||
147 | ROLE_OUTLINEITEM | AT_APIs, Accessibility, NeedsContent, Reference, Référence |
Represents an item in an outline or tree structure. | ||
148 | ROLE_PAGETAB | AT_APIs, Accessibility, Reference, Référence |
Represents a page tab, it is a child of a page tab list. Also refer to ROLE_PAGETABLIST . |
||
149 | ROLE_PAGETABLIST | AT_APIs, Accessibility, Reference, Référence |
Represents a container of page tab controls. Also refer to ROLE_PAGETAB |
||
150 | ROLE_PANE | AT_APIs, Accessibility, Reference, Référence |
Represents a pane within a frame or document window. Users can navigate between panes and within the contents of the current pane, but cannot navigate between items in different panes. Thus, panes represent a level of grouping lower than frame windows or documents, but above individual controls. | ||
151 | ROLE_PARENT_MENUITEM | AT_APIs, Accessibility, Reference, Référence |
Represents a menu item, which is an entry in a menu that a user can choose to display another menu. | ||
152 | ROLE_POPUP_MENU | AT_APIs, Accessibility, Reference, Référence |
A temporary window that is usually used to offer the user a list of choices, and then hides when the user selects one of those choices | ||
153 | ROLE_PROGRESSBAR | AT_APIs, Accessibility, Reference, Référence |
Represents a progress bar, dynamically showing the user the percent complete of an operation in progress. | ||
154 | ROLE_PROPERTYPAGE | AT_APIs, Accessibility, Reference, Référence |
Represents a property sheet. | ||
155 | ROLE_PUSHBUTTON | AT_APIs, Accessibility, Reference, Référence |
Represents a push button control. | ||
156 | ROLE_RADIOBUTTON | AT_APIs, Accessibility |
Represents an option button, also called a radio button. It is one of a group of mutually exclusive options. All objects sharing a single parent that have this attribute are assumed to be part of single mutually exclusive group. | ||
157 | ROLE_RADIO_MENU_ITEM | AT_APIs, Accessibility, Reference, Référence |
Represents a radio button that is a menu item. | ||
158 | ROLE_ROOT_PANE | AT_APIs, Accessibility, Reference, Référence |
A root pane. A specialized pane that has a glass pane and a layered pane as its children. Also refer to ROLE_GLASS_PANE and ROLE_LAYERED_PANE . |
||
159 | ROLE_ROW | AT_APIs, Accessibility, Reference, Référence |
Represents a row of cells within a table. Also, see ROLE_TABLE . |
||
160 | ROLE_SCROLLBAR | AT_APIs, Accessibility, Reference, Référence |
Represents a vertical or horizontal scroll bar, which is part of the client area or used in a control. | ||
161 | ROLE_SCROLL_PANE | AT_APIs, Accessibility, Reference, Référence |
A scroll pane, which is an object that allows a user to incrementally view a large amount of information. Its children can include scroll bars and a viewport. Also refer to ROLE_VIEW_PORT . |
||
162 | ROLE_SEPARATOR | AT_APIs, Accessibility, Reference, Référence |
Used to visually divide a space into two regions, such as a separator menu item or a bar that divides split panes within a window. | ||
163 | ROLE_SLIDER | AT_APIs, Accessibility, Reference, Référence |
Represents a slider, which allows the user to adjust a setting in given increments between minimum and maximum values. | ||
164 | ROLE_SOUND | AT_APIs, Accessibility, Reference, Référence |
Represents a system sound, which is associated with various system events. | ||
165 | ROLE_SPINBUTTON | AT_APIs, Accessibility, Reference, Référence |
Represents a spin box, which is a control that allows the user to increment or decrement the value displayed in a separate "buddy" control associated with the spin box. | ||
166 | ROLE_SPLITBUTTON | AT_APIs, Accessibility, Reference, Référence |
Represents a toolbar button that has a drop-down list icon directly adjacent to the button. | ||
167 | ROLE_SPLIT_PANE | AT_APIs, Accessibility, Reference, Référence |
A split pane, which is a specialized panel that presents two other panels at the same time. Between the two panels is a divider the user can manipulate to make one panel larger and the other panel smaller. | ||
168 | ROLE_STATICTEXT | AT_APIs, Accessibility |
Represents read-only text, such as labels for other controls or instructions in a dialog box. Static text cannot be modified or selected. | ||
169 | ROLE_STATUSBAR | AT_APIs, Accessibility, NeedsUpdate, Reference, Référence |
Represents a status bar, which is an area at the bottom of a window that displays information about the current operation, state of the application, or selected object. The status bar has multiple fields, which display different kinds of information. | ||
170 | ROLE_TABLE | AT_APIs, Accessibility, Reference, Référence |
Represents a table that contains rows and columns of cells, and optionally, row headers and column headers. Also refer to the following roles: ROLE_COLUMNHEADER , ROLE_ROWHEADER , ROLE_COLUMN , ROLE_ROW , ROLE_CELL . |
||
171 | ROLE_TABLE_COLUMN_HEADER | AT_APIs, Accessibility, Reference, Référence |
The header for a column of a table. It looks this role is dupe of ROLE_COLUMNHEADER . |
||
172 | ROLE_TABLE_ROW_HEADER | AT_APIs, Accessibility, Reference, Référence |
The header for a row of a table. It looks this role is dupe of ROLE_ROWHEADER . |
||
173 | ROLE_TEAR_OFF_MENU_ITEM | AT_APIs, Accessibility, Reference, Référence |
A menu item used to tear off and reattach its menu. | ||
174 | ROLE_TERMINAL | AT_APIs, Accessibility, Reference, Référence |
Represents an accessible terminal. | ||
175 | ROLE_TEXT_LEAF | AT_APIs, Accessibility, Reference, Référence |
Represents selectable text that allows edits or is designated read-only. | ||
176 | ROLE_TITLEBAR | AT_APIs, Accessibility, Reference, Référence |
Represents a title or caption bar for a window. | ||
177 | ROLE_TOOLBAR | AT_APIs, Accessibility, Reference, Référence |
Represents a toolbar, which is a grouping of controls (push buttons or toggle buttons) that provides easy access to frequently-used features. | ||
178 | ROLE_TOOLTIP | AT_APIs, Accessibility |
Represents a tooltip that provides helpful hints. | ||
179 | ROLE_WHITESPACE | AT_APIs, Accessibility, Reference, Référence |
Represents blank space between other objects. | ||
180 | ROLE_WINDOW | AT_APIs, Accessibility, Reference, Référence |
Represents the window frame, which contains child objects such as a title bar, client, and other objects contained in a window. | ||
181 | Gecko States | AT_APIs, Accessibility |
Below you will find a list of supported states by Gecko. State constants are defined in nsIAccessibleStates . |
||
182 | Gecko Text Attributes | AT_APIs, Accessibility |
Text attributes are implemented in Firefox 3.5 (Gecko 1.9.1). You can obtain text attributes by nsIAccessibleText.getTextAttributes() method and nsIAccessibleText.defaultTextAttributes property. |
||
183 | Gecko events | AT_APIs, Accessibility, NeedsMarkupWork, Reference, Référence |
This page offers a list of Accessibility-related events supported by Gecko. Event constants are defined in nsIAccessibleEvent interface. |
||
184 | Gecko object attributes | AT_APIs, Accessibility, Gecko, NeedsMarkupWork |
You can obtain object attributes by nsIAccessible.getAttributes() method. Object attributes are relevant for the entire subtree of the object they are on, unless they are overridden by a descendent with the same object attribute. This is in contrast to text attributes, which apply only to substrings in a text object. |
||
185 | Interfaces | AT_APIs, Accessibility |
Generic interface is implemened by accessibles objects. Provides base functionality to obtain accessible object properties, navigate through accessible tree and perform actions on the accessible object. | ||
186 | Gecko Roles | AT_APIs, Accessibility, NeedsMarkupWork |
No summary! | ||
187 | IA2 | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
188 | IA2 Interfaces | AT_APIs, Accessibility |
No summary! | ||
189 | IA2 Object Attributes | AT_APIs, Accessibility |
No summary! | ||
190 | IA2 Roles | AT_APIs, Accessibility |
Below you will find how IAccessible2 roles are mapped to Gecko roles. Since IAccessible2 is a superset of MSAA, the IAccessible2 roles are used in conjunction with the MSAA roles. | ||
191 | IA2 States | AT_APIs, Accessibility |
No summary! | ||
192 | IA2 Text Attributes | AT_APIs, Accessibility |
No summary! | ||
193 | MSAA Events | AT_APIs, Accessibility |
No summary! | ||
194 | MSAA Relations | AT_APIs, Accessibility |
Mapping for IA2 Relations to Gecko Relations. | ||
195 | Implementation Details | AT_APIs, Accessibility |
This article is a reference how Gecko implements AT APIs. | ||
196 | ImplementationFeatures | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
197 | MSAA Implementation Features | AT_APIs, Accessibility |
No summary! | ||
198 | MSAA | AT_APIs, Accessibility |
The page is designed to provide information how MSAA is implemented in Gecko-based applications and how IAccessible interface is mapped into Gecko accessibility API as well. | ||
199 | Find the Window and Load the Document | AT_APIs, Accessibility |
No summary! | ||
200 | MSAA Events | AT_APIs, Accessibility |
No summary! | ||
201 | MSAA Object Attributes | AT_APIs, Accessibility |
No summary! | ||
202 | MSAA Relations | AT_APIs, Accessibility |
No summary! | ||
203 | MSAA Roles | AT_APIs, Accessibility |
The table below shows how MSAA roles are mapped to Gecko roles. There are MSAA roles mapped to several Gecko roles due to MSAA restrictions. You should use IAccessible2 to avoid this (see IAccessible2 roles). | ||
204 | MSAA States | AT_APIs, Accessibility |
shows how MSAA states are mapped to Gecko roles | ||
205 | Supported MSAA Interfaces | AT_APIs, Accessibility |
Traverses to another user interface (UI) element within a container and retrieves the object (see MSDN: IAccessible::accNavigate). | ||
206 | NotSupportedFeatures | Accessibility |
This page was auto-generated because a user created a sub-page to this page. | ||
207 | IA2 Features We Do Not Support | AT_APIs, Accessibility |
No summary! | ||
208 | MSAA Features We Do Not Support | AT_APIs, Accessibility |
No summary! | ||
209 | Web Specifications | AT_APIs, Accessibility |
Gecko is the rendering engine for Firefox, Thunderbird, Nvu, Mozilla Seamonkey and other applications. Gecko is the internal engine that Mozilla uses to render any kind of web content. It supports HTML, XHTML, Cascading Style Sheets (CSS), the Document Object Model (DOM) and many more. The content of markup languages supported by Gecko is exposed to assistive technologies (AT). This page is designated to provide information how Gecko maps these languages to AT. | ||
210 | AT Development | AT_APIs, Accessibility |
The accessibility of computer software has seen drastic improvements over the past two decades. This article (from 2007) reviews the progress and technology as it has developed. | ||
211 | Accessibility FAQ | Accessibility, FAQ |
Mozilla Accessibility Project | ||
212 | Accessibility Information for Web Authors | Accessibility, Authoring |
DHTML Accessibility Roadmap: a peek into how DHTML will be made accessible in the future. This document gives a plan which is being developed by IBM, Mozilla and WAI Protocols and Formats Working Group (PFWG) to address the issue of Accessible DHTML. | ||
213 | Accessibility documentation index | Accessibility, Index |
This document provides a list of links to all accessibility articles on the Mozilla Developer Network. | ||
214 | Accessible dynamic content | Accessibility |
This content has been moved to An overview of accessible web applications and widgets. | ||
215 | An overview of accessible web applications and widgets | ARIA, Accessibility, Guide, Web apps, Widget |
The web is changing. Static, page-based sites are increasingly being replaced by dynamic, desktop-style web applications that make heavy use of JavaScript and AJAX. Designers are creating amazing new widgets and controls entirely with a combination of JavaScript, HTML, and CSS. This shift has the potential to dramatically improve the responsiveness and usability of the web, but many users are at risk of being excluded due to accessibility gaps. JavaScript has traditionally had a reputation for being inaccessible to users of assistive technologies such as screen readers, but there are now ways to create dynamic web user interfaces that are accessible to a wide variety of users. | ||
216 | Architecture | Accessibility, Developing Mozilla |
The implementation of text and embedded objects in Mozilla is clever but confusing. Here is a bit of history and an explanation. | ||
217 | Community | Accessibility |
This document provides links to mailing lists, newsgroups, forums, and other communities related to Accessbility. | ||
218 | HTML To MSAA | Accessibility |
The table below shows how Gecko maps HTML elements to MSAA. This table reflects mapping rules for specific elements only, it doesn't reflect any general rules applicable to all elements. For example, if name column has n/a value then it means specific elements doesn't provide own rules to calculate name but name can be computed from ARIA markup or @title attribute. | ||
219 | Implementing a Microsoft Active Accessibility (MSAA) Server | Accessibility, MSAA, Microsoft, Server |
This document is for developers working to support MSAA in an application in order to make it accessible with 3rd party assistive technologies, as well as for hackers wishing to be involved in Mozilla's MSAA support specifically. | ||
220 | JAWS Issues with Firefox | Accessibility, Obsolete |
This article is no longer relevant. Please see screen readers FAQ on the Mozilla support site. | ||
221 | Keyboard-navigable JavaScript widgets | Accessibility, DOM, NeedsUpdate |
Keyboard-navigable JavaScript widgets | ||
222 | Mobile accessibility checklist | Accessibility, Firefox OS, Guidelines, Mobile, checklist |
This document provides a concise checklist of accessibility requirements for mobile app developers. It is intended to continuously evolve as more patterns arise. | ||
223 | Web Development | ARIA, Accessibility, DHTML, Web Development, XUL |
This document provides further information for developers about web accessibility and XUL accessibility. | ||
224 | XForms Accessibility | Accessibility, Obsolete, XForms |
This article provides a quick guide to how accessibility is handled in Gecko for XForms. | ||
225 | Button Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
The button invokes certain action when user activates it. This representation is used for XForms trigger element (see the doc) and for XForms submit element (see the doc). |
||
226 | Calendar Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Calendar container is used to show/change date data. This is subsidiary representation of XForms input element (see the doc) or output element (see the doc) that are bound to instance node of xsd:date type. |
||
227 | Checkbox Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Checkbox representation is used to show/change boolean data. It is used for XForms input element (see the docs). |
||
228 | Checkgroup Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Allows the user to choose a single value from a list of pre-defined values. This representation is used for full appearance select (see the doc). |
||
229 | Combobox Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Allows the user to choose a single value from a list of pre-defined values. This representation is used for minimal appearance select1 (see the doc). |
||
230 | Datepicker Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
A datepicker is similar to a combobox . It consists of a text field for direct user input next to a button that when activated displays a calendar widget that the user can also interact with. The datepicker control is used to display or edit a calendar date in the XForms input element (see the datepicker section of the input documentation). |
||
231 | DaysList Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Days list container is used to show/change day data. This is representation of XForms input element (see the doc) that is bound to instance node of xsd:gDay type. |
||
232 | Listbox Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Listbox container is used to show/change data that represents a list. This is representation of XForms select element (see the doc) or select1 element (see the doc). Listbox container uses appropriate widget from host document for represntation. If host document is XUL document then xul:listbox is used. If host document is XHTML document then xhtml:select is used. |
||
233 | MonthsList Reperesentation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Months list container is used to show/change day data. This is representation of XForms input element (see the doc) that is bound to instance node of xsd:gMonth type. |
||
234 | Password Field Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Password field is used for inputting passwords. Each character typed by the user is represented by an asterisk on the screen. It is used for XForms secret element (see the doc). |
||
235 | Radiogroup Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Allows the user to choose a single value from a list of pre-defined values. This representation is used for full appearance select1 (see the doc). |
||
236 | Slider Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Allows the user to choose a value from within a specific range of values. Slider presentation is used for XForms range element that is bound to numeric data types (see the doc). |
||
237 | Text Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Text is used to show string data in readonly manner. This is the main representation of XForms output element (see the docs). |
||
238 | TextField Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Text field is used to show/change string data. This is the main representation of XForms input element (see the docs). Also this representation is used for XForms textarea element (see the docs). |
||
239 | Upload Representation | Accessibility, Accessibility_XForms, Obsolete, XForms |
Provides a means for the user to select a file. This presentation is used for upload element (see the doc). The upload representation is combined from textfield to show uploaded file URL, upload button and clear button. | ||
240 | XUL Accessibility | Accessibility |
This article shows how XUL control elements are mapped to accessibility API. It is much in progress. | ||