Accessibility documentation index

This document provides a list of links to all accessibility articles on the Mozilla Developer Network.

Found 269 pages:

# Page Tags and summary
1 Accessibility Accessibility, Landing
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, HTML
Accessible Rich Internet Applications (ARIA) is a set of attributes that define ways to make Web content and Web applications (especially those developed with JavaScript) more accessible to people with disabilities. It supplements HTML so that interactions and widgets commonly used in applications can be passed to Assistive Technologies
3 ARIA Live Regions ARIA, Accessibility, ariaLive
Using JavaScript, it is possible to dynamically change parts of a page without requiring the entire page to reload — for instance, to update a list of search results on the fly, or to display a discreet alert or notification which does not require user interaction. While these changes are usually visually apparent to users who can see the page, they may not be obvious to users of assistive technologies. ARIA live regions fill this gap and provide a way to programmatically expose dynamic content changes in a way that can be announced by assistive technologies.
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 Alerts ARIA, Accessibility, Forms, Web
You have a form — a contact form, for example — that you want to put some accessible error checking into. Examples of common problems include e-mail addresses which are not valid, or a name field which does not contain at least a first name or a surname.
9 Basic form hints ARIA, Accessibility, Forms
When implementing forms using traditional HTML form-related elements, it is important to provide labels for controls, and explicitly associate a label with its control.
10 Multipart labels: Using ARIA for labels with embedded fields inside them ARIA, Accessibility, Ben Millard, Firefox, Guide, HELP, HTML, HTML 4, JAWS, NeedsContent, aria-labelledby, label, solution, trouble shoot, troubleshoot
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.
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: Roles, States, and Properties ARIA, Accessibility, Overview, Reference
No summary!
13 ARIA Technique Template Accessibility
No summary!
14 Using the alert role ARIA, Accessibility, Advanced, CSS, Example, HTML, NeedsContent, alert, alert role, alertrole, alerts, assitive technology, 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(2), 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, Document Object Model, NeedsContent, Property, Widget, aria-activedescendant
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(2), 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(2), 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, 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 horizontally 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 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 used to define the maximum value allowed for a range widget such as a slider, spinbutton or progressbar.
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 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.
30 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.
31 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.
32 Using the presentation role ARIA, NeedsContent, Section 508, WAI-ARIA, WCAG
This technique demonstrates how to use the presentation role and describes the effect it has on browsers and assistive technology.
33 Using the progressbar role ARIA, Accessibility, NeedsContent, NeedsExample
This technique demonstrates how to use the progressbar role and describes the effect it has on browsers and assistive technology.
34 Using the radio role NeedsContent
This technique demonstrates how to use the radio role and describes the effect it has on browsers and assistive technology.
35 Using the slider role ARIA, Accessibility, NeedsContent
This technique demonstrates how to use the slider role and describes the effect it has on browsers and assistive technology.
36 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.
37 Using the toolbar role NeedsContent
This technique demonstrates how to use the toolbar role and describes the effect it has on browsers and assistive technology.
38 x-ms-aria-flowfrom
The x-ms-aria-flowfrom property specifies the id of the previous element in an alternative reading order, allowing assistive technology to override the general default of reading in document source order. The property serves to define element relationships utilizing ARIA relationship attributes and the aria-flowto property.
39 WAI-ARIA Roles ARIA, ARIA Roles, Accessibility, Reference, Rôles
This page lists reference pages covering all the WAI-ARIA roles discussed on MDN. For a full list of roles, see Using ARIA: Roles, States, and Properties
40 ARIA: Complementary role ARIA, ARIA Role, Reference, role-complementary
The complementary landmark role is used to designate a supporting section that relates to the main content, yet can stand alone when separated. These sections are frequently presented as sidebars or call-out boxes. If possible, use the HTML <aside> element instead.
41 ARIA: List role ARIA, ARIA Role, ARIA list, Accessibility, Reference, Rôle, list
The ARIA list role can be used to identify a list of items. It is normally used in conjunction with the listitem role, which is used to identify a list item contained inside the list.
42 ARIA: Listitem role ARIA, ARIA Role, ARIA listitem, Accessibility, Reference, Rôle, listitem
The ARIA listitem role can be used to identify an item inside a list of items. It is normally used in conjunction with the list role, which is used to identify a list container.
43 ARIA: Main role ARIA, ARIA Role, Reference, role-main
The main landmark role is used to indicate the primary content of a document. The main content area consists of content that is directly related to or expands upon the central topic of a document, or the central functionality of an application.
44 ARIA: Navigation Role ARIA, ARIA Role, Reference, role-navigation
The navigation landmark role is used to identify major groups of links used for navigating through a website or page content.
45 ARIA: Region role ARIA, ARIA Role, Accessibility, Reference, landmark role, role-region
The region landmark role is used to identify an area in the document that the author has identified as significant. It is used to provide a generic landmark for people to be able to navigate to easily when none of the other landmark roles are appropriate.
46 ARIA: Search role ARIA, ARIA Role, Reference, role-search
The search landmark role is used to identify a section of the page used to search the page, site, or collection of sites.
47 ARIA: Tab Role ARIA, ARIA Role, ARIA Tab, ARIA widget, Reference
The ARIA tab role indicates an interactive element that, when activated, displays its associated tab panel.
48 ARIA: alert role ARIA, ARIA Role, ARIA alert, ARIA widget, Reference
The alert role can be used to tell the user an element has been dynamically updated. Screen readers will instantly start reading out the updated content when the role is added. If the user is expected to close the alert, then the alertdialog role should be used instead.
49 ARIA: application role ARIA, ARIA Role, ARIA widget, Reference, Role application
The application role indicates to assistive technologies that an element and all of its children should be treated similar to a desktop application, and no traditional HTML interpretation techniques should be used. This role should only be used to define very dynamic and desktop-like web applications.
50 ARIA: article role ARIA, ARIA Role, ARIA article role, Article, Article role, Reference
The article role indicates a section of a page that could easily stand on its own on a page, in a document, or on a web site. It is usually set on related content items such as comments, forum posts, news paper articles or other items grouped together on one page.
51 ARIA: banner role ARIA, Accessibility, NeedsContent
A banner role represents general and informative content frequently placed at the beginning of the page. This usually includes a logo, company name, search icon, photo related to the page, or slogan.
52 ARIA: button role ARIA, ARIA Role, ARIA button, Accessibility, Button Role, Reference
The button role should be used for clickable elements that trigger a response when activated by the user. Adding role="button" will make an element appear as a button control to a screen reader. This role can be used in combination with the aria-pressed attribute to create toggle buttons.
53 ARIA: cell role
The cell value of the ARIA role attribute identifies an element as being a cell in a tabular container that does not contain column or row header information. To be supported, the cell must nested in an element with the role of row.
54 ARIA: checkbox role ARIA, Accessibility, NeedsContent, Role(2), Rôle
The checkbox role is used for checkable interactive controls. Elements containing role="checkbox" must also include the aria-checked attribute to expose the checkbox's state to assistive technology.
55 ARIA: contentinfo role ARIA, ARIA Role, Reference, role-contentinfo
The contentinfo landmark role is used to identify information repeated at the end of every page of a website, including copyright information, navigation links, and privacy statements. This section is commonly called a footer.
56 ARIA: dialog role ARIA, Accessibility, NeedsContent, Web Development
The dialog role is used to mark up an HTML based application dialog or window that separates content or UI from the rest of the web application or page. 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).
57 ARIA: document role ARIA, ARIA Role, Document, Reference
Generally used in complex composite widgets or applications, the document role can inform assistive technologies to switch context to a reading mode: the document role tells assistive technologies with reading or browse modes to use the document mode to read the content contained within this element.
58 ARIA: feed role ARIA, ARIA Role, Reference, feed
A feed is a dynamic scrollable list of articles in which articles are added to or removed from either end of the list as the user scrolls. A feed enables screen readers to use the browse mode reading cursor to both read and scroll through a stream of rich content that may continue scrolling infinitely by loading more content as the user reads.
59 ARIA: figure role ARIA, ARIA Role, ARIA figure, Accessibility, Reference, Rôle, figure
The ARIA figure role can be used to identify a figure inside page content where appropriate semantics do not already exist. A figure is generally considered to be one or more images, code snippets, or other content that puts across information in a different way to a regular flow of text.
60 ARIA: form role ARIA, ARIA Role, ARIA figure, Accessibility, Reference, Rôle, form
The form landmark role can be used to identify a group of elements on a page that provide equivalent functionality to an HTML form.
61 ARIA: grid role
The grid role is for a widget that contains one or more rows of cells. The position of each cell is significant and can be focused using keyboard input.
62 ARIA: heading role ARIA, ARIA Role, ARIA heading, Reference
The heading role defines this element as a heading to a page or section. To give the page more structure, a level should also be provided to indicate relationships between sections.
63 ARIA: img role ARIA, ARIA Img, ARIA Role, Accessibility, Reference, Rôle, figure
The ARIA img role can be used to identify multiple elements inside page content that should be considered as a single image. These elements could be images, code snippets, text, emojis, or other content that can be combined to deliver information in a visual manner.
64 ARIA: listbox role ARIA, Accessibility, NeedsContent
The listbox role is used for lists from which a user may select one or more items which are static and, unlike HTML <select> elements, may contain images.
65 ARIA: row role ARIA, ARIA Role, ARIA Row, ARIA Row Role, Accessibility, Reference, Row Role
An element with role="row" is a row of cells within a tabular structure. A row contains one or more cells,  grid cells, or column headers, and possibly a row header, within a grid, table or treegrid, and optionally within a rowgroup.
66 ARIA: rowgroup role
An element with role="rowgroup" is a group of rows within a tabular structure. A rowgroup contains one or more rows of cellsgrid cells, column headers, or row headers within a grid, table or treegrid.
67 ARIA: switch role ARIA, ARIA Role, Accessibility, On/Off, Reference, Switch, a11y, toggle
The ARIA switch role is functionally identical to the role, except that instead of representing "checked" and "unchecked" states, which are fairly generic in meaning, the switch role represents the states "on" and "off."
68 ARIA: table role ARIA, ARIA Role, ARIA Table, ARIA Table Role, Accessibility, Reference, Table Role
The table value of the ARIA role attribute identifies the element containing the role as having a non-interactive table structure containing data arranged in rows and columns, similar to the native <table> HTML element.
69 ARIA: textbox role ARIA, Accessibility, NeedsContent
The textbox role is used to identify an element that allows the input of free-form text.
70 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.
71 widgets Accessibility
This page was auto-generated because a user created a sub-page to this page.
72 overview Accessibility, JavaScript, Landing, NeedsUpdate
Here's a look at working examples and best practices in building accessible JavaScript widgets.
73 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.
74 AT-SPI Accessibility
This page was auto-generated because a user created a sub-page to this page.
75 AT-SPI Document Attributes AT_APIs, Accessibility
You can obtain document attributes by Document::getAttributes method.
76 AT-SPI Events AT_APIs, Accessibility
Proposed mapping AT-SPI Events to Gecko Events.
77 AT-SPI Object Attributes AT_APIs, Accessibility
AT-SPI exposes object attributes by Accessible::getAttributes method.
78 AT-SPI Roles AT_APIs, Accessibility
Below you will find the table of AT-SPI roles and how they are mapped to Gecko roles.
79 AT-SPI States AT_APIs, Accessibility
The table below shows how AT-SPI states are mapped to Gecko states.
80 AT-SPI Text Attributes AT_APIs, Accessibility
AT-SPI has Text::getAttributes() method to get text attributes.
81 Find the Window and Load the Document AT_APIs, Accessibility
No summary!
82 MSAA Relations AT_APIs, Accessibility
Mapping for ATK/AT-SPI relations to Gecko Relations.
83 Supported AT SPI Interfaces AT_APIs, Accessibility
No summary!
84 Differences Accessibility
This page was auto-generated because a user created a sub-page to this page.
85 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.
86 Gecko Accessibility
This page was auto-generated because a user created a sub-page to this page.
87 Gecko Relations AT_APIs, Accessibility, Gecko
Below you will find a list of supported relations by Gecko. Relation constants are defined in nsIAccessibleRelations interface.
88 Gecko Roles AT_APIs, Accessibility, Reference, Référence(2)
This page offers a list of accessible roles used in Gecko. Role constants are defined in the nsIAccessibleRole interface.
89 ROLE AUTOCOMPLETE AT_APIs, Accessibility
No summary!
90 ROLE CAPTION AT_APIs, Accessibility
No summary!
91 ROLE DOCUMENT FRAME AT_APIs, Accessibility
No summary!
92 ROLE EDITBAR AT_APIs, Accessibility
No summary!
93 ROLE ENTRY AT_APIs, Accessibility
No summary!
94 ROLE FOOTER AT_APIs, Accessibility
No summary!
95 ROLE FORM AT_APIs, Accessibility
No summary!
96 ROLE GLASS PANE AT_APIs, Accessibility
No summary!
97 ROLE HEADER AT_APIs, Accessibility
No summary!
98 ROLE HEADING AT_APIs, Accessibility
No summary!
99 ROLE HTML CONTAINER AT_APIs, Accessibility
No summary!
100 ROLE ICON AT_APIs, Accessibility
No summary!
101 ROLE LABEL AT_APIs, Accessibility
No summary!
102 ROLE LAYERED PANE AT_APIs, Accessibility
No summary!
103 ROLE LISTBOX AT_APIs, Accessibility
No summary!
104 ROLE OPTION PANE AT_APIs, Accessibility
No summary!
105 ROLE PAGE AT_APIs, Accessibility
No summary!
106 ROLE PARAGRAPH AT_APIs, Accessibility
No summary!
107 ROLE PASSWORD TEXT AT_APIs, Accessibility
No summary!
108 ROLE REDUNDANT OBJECT AT_APIs, Accessibility
No summary!
109 ROLE RICH OPTION AT_APIs, Accessibility
No summary!
110 ROLE RULER AT_APIs, Accessibility
No summary!
111 ROLE SECTION AT_APIs, Accessibility
No summary!
112 ROLE TOGGLE BUTTON AT_APIs, Accessibility
No summary!
113 ROLE TREE TABLE AT_APIs, Accessibility
No summary!
114 ROLE VIEWPORT AT_APIs, Accessibility
No summary!
115 ROLE_ACCEL_LABEL AT_APIs, Accessibility, Reference, Référence(2)
Represents a label control that has an accelerator.
116 ROLE_ALERT AT_APIs, Accessibility, Reference, Référence(2)
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.
117 ROLE_ANIMATION AT_APIs, Accessibility, Reference, Référence(2)
Represents an animation control, which contains content that changes over time, such as a control that displays a series of bitmap frames.
118 ROLE_APPLICATION AT_APIs, Accessibility
Represents a main window for an application. Also refer to ROLE_APP_ROOT.
119 ROLE_APP_ROOT AT_APIs, Accessibility, Reference, Référence(2)
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.
120 ROLE_ARROW AT_APIs, Accessibility, Reference, Référence(2)
Represents an arrow in one of the four cardinal directions.
121 ROLE_BORDER AT_APIs, Accessibility, Reference, Référence(2)
Represents a window border.
122 ROLE_BUTTONDROPDOWN AT_APIs, Accessibility
Represents a button that drops down a list of items.
123 ROLE_BUTTONDROPDOWNGRID AT_APIs, Accessibility, Reference, Référence(2)
Represents a button that drops down a grid.
124 ROLE_BUTTONMENU AT_APIs, Accessibility, Reference, Référence(2)
Represents a button that drops down a menu.
125 ROLE_CALENDAR AT_APIs, Accessibility, Calendar, Gecko Roles, NeedsContent, Reference, Référence(2)
A calendar that lets the user select a date.
126 ROLE_CANVAS AT_APIs, Accessibility, Reference, Référence(2)
Represents a control that can be drawn into and is used to trap events.
127 ROLE_CARET AT_APIs, Accessibility, Reference, Référence(2)
Represents the system caret. The role is supported for caret.
128 ROLE_CELL AT_APIs, Accessibility, Reference, Référence(2)
Represents a cell within a table. Also, see ROLE_TABLE.
129 ROLE_CHARACTER AT_APIs, Accessibility, Reference, Référence(2)
Represents a cartoon-like graphic object, such as Microsoft Office Assistant, which is displayed to provide help to users of an application.
130 ROLE_CHART AT_APIs, Accessibility
Represents a graphical image used to represent data.
131 ROLE_CHECKBUTTON AT_APIs, Accessibility, Reference, Référence(2)
Represents a check box control.
132 ROLE_CHECK_MENU_ITEM AT_APIs, Accessibility, Reference, Référence(2)
Represents a menu item with a check box.
133 ROLE_CHROME_WINDOW AT_APIs, Accessibility, Reference, Référence(2)
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.
134 ROLE_CLOCK AT_APIs, Accessibility, Reference, Référence(2)
Represents a control that displays time.
135 ROLE_COLOR_CHOOSER AT_APIs, Accessibility, Reference, Référence(2)
Represents a specialized dialog that lets the user choose a color.
136 ROLE_COLUMNHEADER AT_APIs, Accessibility, Reference, Référence(2)
Represents a column header, providing a visual label for a column in a table. Also refer to ROLE_TABLE.
137 ROLE_COMBOBOX AT_APIs, Accessibility, Reference, Référence(2)
Represents a combo box; an edit control with an associated list box that provides a set of predefined choices.
138 ROLE_COMBOBOX_LIST AT_APIs, Accessibility, Reference, Référence(2)
A list of items that is presented using a combobox.
139 ROLE_COMBOBOX_OPTION AT_APIs, Accessibility, Reference, Référence(2)
A item of list that is shown by combobox.
140 ROLE_CURSOR AT_APIs, Accessibility, Reference, Référence(2)
Represents the system mouse pointer.
141 ROLE_DATE_EDITOR AT_APIs, Accessibility, Reference, Référence(2)
Represents control whose purpose is to allow a user to edit a date.
142 ROLE_DESKTOP_FRAME AT_APIs, Accessibility, Reference, Référence(2)
A desktop pane. A pane that supports internal frames and iconified versions of those internal frames.
143 ROLE_DESKTOP_ICON AT_APIs, Accessibility, Reference, Référence(2)
An iconified internal frame in an ROLE_DESKTOP_PANE. Also refer to ROLE_INTERNAL_FRAME.
144 ROLE_DIAGRAM AT_APIs, Accessibility, Reference, Référence(2)
Represents a graphical image used to diagram data.
145 ROLE_DIAL AT_APIs, Accessibility, Reference, Référence(2)
Represents a dial or knob whose purpose is to allow a user to set a value.
146 ROLE_DIALOG AT_APIs, Accessibility, Reference, Référence(2)
Represents a dialog box or message box.
147 ROLE_DIRECTORY_PANE AT_APIs, Accessibility, Reference, Référence(2)
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.
148 ROLE_DOCUMENT AT_APIs, Accessibility, Reference, Référence(2)
Represents a document window. A document window is always contained within an application window.
149 ROLE_DROPLIST AT_APIs, Accessibility
Represents the calendar control.
150 ROLE_EQUATION AT_APIs, Accessibility, Reference, Référence(2)
Represents a mathematical equation.
151 ROLE_FILE_CHOOSER AT_APIs, Accessibility, Reference, Référence(2)
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.
152 ROLE_FONT_CHOOSER AT_APIs, Accessibility, Reference, Référence(2)
A font chooser. A font chooser is a component that lets the user pick various attributes for fonts.
153 ROLE_GRAPHIC AT_APIs, Accessibility, Gecko, Reference, Référence(2)
Represents a picture.
154 ROLE_GRIP AT_APIs, Accessibility, Reference, Référence(2)
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.
155 ROLE_GROUPING AT_APIs, Accessibility, Reference, Référence(2)
Logically groups other objects. There is not always a parent-child relationship between the grouping object and the objects it contains.
156 ROLE_HELPBALLOON AT_APIs, Accessibility, NeedsContent, Reference, Référence(2)
Displays a Help topic in the form of a tooltip or help balloon.
157 ROLE_HOTKEYFIELD AT_APIs, Accessibility, Reference, Référence(2)
Represents a hot-key field that allows the user to enter a combination or sequence of keystrokes
158 ROLE_IMAGE_MAP AT_APIs, Accessibility, NeedsContent, Reference
An image map, which has child links representing the areas.
159 ROLE_IME AT_APIs, Accessibility, Reference, Référence(2)
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.
160 ROLE_INDICATOR AT_APIs, Accessibility, Reference, Référence(2)
Represents an indicator, such as a pointer graphic, that points to the current item.
161 ROLE_INTERNAL_FRAME AT_APIs, Accessibility, Reference, Référence(2)
A sub-document.
162 ROLE_IPADDRESS AT_APIs, Accessibility, Reference, Référence(2)
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.
163 ROLE_LINK AT_APIs, Accessibility, Reference, Référence(2)
Represents a link to something else. This object might look like text or a graphic, but it acts like a button.
164 ROLE_LIST AT_APIs, Accessibility, Reference, Référence(2)
Represents either:
165 ROLE_LISTITEM AT_APIs, Accessibility, Reference, Référence(2)
Represents an item in a list. See also ROLE_LIST.
166 ROLE_MENUBAR AT_APIs, Accessibility, Reference, Référence(2)
Represents the menu bar (positioned beneath the title bar of a window) from which menus are selected by the user.
167 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.
168 ROLE_MENUPOPUP AT_APIs, Accessibility, Reference, Référence(2)
Represents a menu, which presents a list of options from which the user can make a selection to perform an action.
169 ROLE_NOTHING AT_APIs, Accessibility, Reference, Référence(2)
Used when the accessible doesn't have a strongly defined role.
170 ROLE_OPTION AT_APIs, Accessibility, Reference, Référence(2)
An option in a listbox.
171 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.
172 ROLE_OUTLINEITEM AT_APIs, Accessibility, NeedsContent, Reference, Référence(2)
Represents an item in an outline or tree structure.
173 ROLE_PAGETAB AT_APIs, Accessibility, Reference, Référence(2)
Represents a page tab, it is a child of a page tab list. Also refer to ROLE_PAGETABLIST.
174 ROLE_PAGETABLIST AT_APIs, Accessibility, Reference, Référence(2)
Represents a container of page tab controls. Also refer to ROLE_PAGETAB
175 ROLE_PANE AT_APIs, Accessibility, Reference, Référence(2)
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.
176 ROLE_PARENT_MENUITEM AT_APIs, Accessibility, Reference, Référence(2)
Represents a menu item, which is an entry in a menu that a user can choose to display another menu.
177 ROLE_POPUP_MENU AT_APIs, Accessibility, Reference, Référence(2)
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
178 ROLE_PROGRESSBAR AT_APIs, Accessibility, Reference, Référence(2)
Represents a progress bar, dynamically showing the user the percent complete of an operation in progress.
179 ROLE_PROPERTYPAGE AT_APIs, Accessibility, Reference, Référence(2)
Represents a property sheet.
180 ROLE_PUSHBUTTON AT_APIs, Accessibility, Reference, Référence(2)
Represents a push button control.
181 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.
182 ROLE_RADIO_MENU_ITEM AT_APIs, Accessibility, Reference, Référence(2)
Represents a radio button that is a menu item.
183 ROLE_ROOT_PANE AT_APIs, Accessibility, Reference, Référence(2)
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.
184 ROLE_ROW AT_APIs, Accessibility, Reference, Référence(2)
Represents a row of cells within a table. Also, see ROLE_TABLE.
185 ROLE_SCROLLBAR AT_APIs, Accessibility, Reference, Référence(2)
Represents a vertical or horizontal scroll bar, which is part of the client area or used in a control.
186 ROLE_SCROLL_PANE AT_APIs, Accessibility, Reference, Référence(2)
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.
187 ROLE_SEPARATOR AT_APIs, Accessibility, Reference, Référence(2)
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.
188 ROLE_SLIDER AT_APIs, Accessibility, Reference, Référence(2)
Represents a slider, which allows the user to adjust a setting in given increments between minimum and maximum values.
189 ROLE_SOUND AT_APIs, Accessibility, Reference, Référence(2)
Represents a system sound, which is associated with various system events.
190 ROLE_SPINBUTTON AT_APIs, Accessibility, Reference, Référence(2)
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.
191 ROLE_SPLITBUTTON AT_APIs, Accessibility, Reference, Référence(2)
Represents a toolbar button that has a drop-down list icon directly adjacent to the button.
192 ROLE_SPLIT_PANE AT_APIs, Accessibility, Reference, Référence(2)
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.
193 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.
194 ROLE_STATUSBAR AT_APIs, Accessibility, NeedsUpdate, Reference, Référence(2)
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.
195 ROLE_TABLE AT_APIs, Accessibility, Reference, Référence(2)
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.
196 ROLE_TABLE_COLUMN_HEADER AT_APIs, Accessibility, Reference, Référence(2)
The header for a column of a table. It looks this role is dupe of ROLE_COLUMNHEADER.
197 ROLE_TABLE_ROW_HEADER AT_APIs, Accessibility, Reference, Référence(2)
The header for a row of a table. It looks this role is dupe of ROLE_ROWHEADER.
198 ROLE_TEAR_OFF_MENU_ITEM AT_APIs, Accessibility, Reference, Référence(2)
A menu item used to tear off and reattach its menu.
199 ROLE_TERMINAL AT_APIs, Accessibility, Reference, Référence(2)
Represents an accessible terminal.
200 ROLE_TEXT_LEAF AT_APIs, Accessibility, Reference, Référence(2)
Represents selectable text that allows edits or is designated read-only.
201 ROLE_TITLEBAR AT_APIs, Accessibility, Reference, Référence(2)
Represents a title or caption bar for a window.
202 ROLE_TOOLBAR AT_APIs, Accessibility, Reference, Référence(2)
Represents a toolbar, which is a grouping of controls (push buttons or toggle buttons) that provides easy access to frequently-used features.
203 ROLE_TOOLTIP AT_APIs, Accessibility
Represents a tooltip that provides helpful hints.
204 ROLE_WHITESPACE AT_APIs, Accessibility, Reference, Référence(2)
Represents blank space between other objects.
205 ROLE_WINDOW AT_APIs, Accessibility, Reference, Référence(2)
Represents the window frame, which contains child objects such as a title bar, client, and other objects contained in a window.
206 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.
207 Gecko events AT_APIs, Accessibility, NeedsMarkupWork, Reference, Référence(2)
This page offers a list of Accessibility-related events supported by Gecko. Event constants are defined in nsIAccessibleEvent interface.
208 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.
209 Gecko states AT_APIs, Accessibility
Below you will find a list of supported states by Gecko. State constants are defined in nsIAccessibleStates.
210 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.
211 Gecko Roles AT_APIs, Accessibility, NeedsMarkupWork
No summary!
212 IA2 Accessibility
This page was auto-generated because a user created a sub-page to this page.
213 IA2 Interfaces AT_APIs, Accessibility
No summary!
214 IA2 Object Attributes AT_APIs, Accessibility
No summary!
215 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.
216 IA2 States AT_APIs, Accessibility
No summary!
217 IA2 Text Attributes AT_APIs, Accessibility
No summary!
218 MSAA Events AT_APIs, Accessibility
No summary!
219 MSAA Relations AT_APIs, Accessibility
Mapping for IA2 Relations to Gecko Relations.
220 Implementation Details AT_APIs, Accessibility
This article is a reference how Gecko implements AT APIs.
221 ImplementationFeatures Accessibility
This page was auto-generated because a user created a sub-page to this page.
222 MSAA Implementation Features AT_APIs, Accessibility
No summary!
223 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.
224 Find the Window and Load the Document AT_APIs, Accessibility
No summary!
225 MSAA Events AT_APIs, Accessibility
No summary!
226 MSAA Object Attributes AT_APIs, Accessibility
No summary!
227 MSAA Relations AT_APIs, Accessibility
Mapping for MSAA Relations and additional relations to Gecko relations. Use IAccessible::accNavigate method to get relations.
228 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).
229 MSAA States AT_APIs, Accessibility
shows how MSAA states are mapped to Gecko roles
230 Supported MSAA Interfaces AT_APIs, Accessibility
Traverses to another user interface (UI) element within a container and retrieves the object (see MSDN: IAccessible::accNavigate).
231 NotSupportedFeatures Accessibility
This page was auto-generated because a user created a sub-page to this page.
232 IA2 Features We Do Not Support AT_APIs, Accessibility
No summary!
233 MSAA Features We Do Not Support AT_APIs, Accessibility
No summary!
234 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.
235 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.
236 Accessibility FAQ Accessibility, FAQ
Mozilla Accessibility Project
237 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.
238 Accessibility documentation index Accessibility, Index
This document provides a list of links to all accessibility articles on the Mozilla Developer Network.
239 Accessible dynamic content Accessibility
This content has been moved to An overview of accessible web applications and widgets.
240 An overview of accessible web applications and widgets ARIA, Accessibility, Guide, Web apps, Widget
Most JavaScript libraries offer a library of client-side widgets that mimic the behavior of familiar desktop interfaces. Sliders, menu bars, file list views, and more can be built with a combination of JavaScript, CSS, and HTML. Since the HTML4 specification doesn't provide built-in tags that semantically describe these kinds of widgets, developers typically resort to using generic elements such as
and . While this results in a widget that looks like its desktop counterpart, there usually isn't enough semantic information in the markup to be usable by an assistive technology.
241 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.
242 Community Accessibility
This document provides links to mailing lists, newsgroups, forums, and other communities related to Accessbility.
243 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.
244 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.
245 JAWS Issues with Firefox Accessibility, Obsolete
This article is no longer relevant. Please see screen readers FAQ on the Mozilla support site.
246 Keyboard-navigable JavaScript widgets Accessibility, DOM, NeedsUpdate
Web applications often use JavaScript to mimic desktop widgets such as menus, tree views, rich text fields, and tab panels. These widgets are typically composed of <div> and <span> elements that do not, by nature, offer the same keyboard functionality that their desktop counterparts do. This document describes techniques to make JavaScript widgets accessible with the keyboard.
247 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.
248 Understanding the Web Content Accessibility Guidelines WCAG, Web Content Accessibility Guidelines
This set of articles provides quick explanations to help you understand the steps that need to be taken to conform to the recommendations outlined in the W3C Web Content Accessibility Guidelines 2.0 or 2.1 (or just WCAG, for the purposes of this writing).
249 Operable Accessibility, Focus, Navigation, Principle 2, Timing, WCAG, Web Content Accessibility Guidelines, headings, keyboard, keyboard trap, labels, operable, seizures
This article provides practical advice on how to write your web content so that it conforms to the success criteria outlined in the Operable principle of the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. Operable states that user interface components and navigation must be operable.
250 Perceivable Accessibility, Principle 1, WCAG, Web Content Accessibility Guidelines, contrast, different presentation, text alternatives, time-based media
This article provides practical advice on how to write your web content so that it conforms to the success criteria outlined in the Perceivable principle of the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. Perceivable states that users must be able to perceive it in some way, using one or more of their senses.
251 Robust Accessibility, HTML, Parsing, Principle 4, Robust, Role(2), Validation, WAI-ARIA, WCAG, Web Content Accessibility Guidelines, value
This article provides practical advice on how to write your web content so that it conforms to the success criteria outlined in the Robust principle of the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. Robust states that content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies. This can generally be achieved by following web standards and testing rigorously.
252 Understandable Accessibility, HELP, Language, Navigation, Principle 3, Text, Understandable, WCAG, Web Content Accessibility Guidelines, abbreviations, consistency, error messages, form validation, labels, slang
This article provides practical advice on how to write your web content so that it conforms to the success criteria outlined in the Understandable principle of the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. Understandable states that information and the operation of user interface must be understandable.
253 XForms Accessibility Accessibility, Obsolete, XForms
This article provides a quick guide to how accessibility is handled in Gecko for XForms.
254 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).
255 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.
256 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).
257 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).
258 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).
259 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).
260 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.
261 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.
262 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.
263 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).
264 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).
265 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).
266 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).
267 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).
268 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.
269 XUL Accessibility Accessibility
This article shows how XUL control elements are mapped to accessibility API. It is much in progress.

Document Tags and Contributors

Contributors to this page: rralian, Fredchat, fscholz
Last updated by: rralian,