Read This First
The code in this example is not intended for production environments. Before using it for any purpose, read this to understand why.
This is an illustrative example of one way of using ARIA that conforms with the ARIA specification.
- There may be support gaps in some browser and assistive technology combinations, especially for mobile/touch devices. Testing code based on this example with assistive technologies is essential before considering use in production systems.
- The ARIA and Assistive Technologies Project is developing measurements of assistive technology support for APG examples.
- Robust accessibility can be further optimized by choosing implementation patterns that maximize use of semantic HTML and heeding the warning that No ARIA is better than Bad ARIA.
About This Example
To use this example:
Activate the "discard" button to trigger a confirmation dialog that has the
- Activating the "yes" button in the confirmation dialog removes the contents of both the "Notes" text area and local storage of the notes.
- Activating the "no" button or pressing escape closes the dialog.
- The "discard" button is disabled if the notes text area does not contain any text.
Activate the "save" button to trigger an alert when the contents of the "Notes" text area is saved to
- A successful save triggers a short alert to notify the user that the notes have been saved.
- The "save" button is disabled if the user's local storage value is the same as the "Notes" field.
- Modify the "notes" text area as needed to enable and disable the discard and save functions.
Similar examples include:
Are you sure you want to discard all of your notes?
- The accessible name of the alert dialog is set to its heading ("Confirmation").
- The dialog's prompt ("Are you sure...?") is referenced via
aria-describedbyto ensure that the user is immediately aware of the prompt.
Focus is automatically set to the first focusable element inside the dialog, which is the "No"
button. This is the least destructive action, so focusing "No" helps prevent users from accidentally confirming the destructive "Discard" action, which cannot be undone.
When the buttons are disabled,
aria-disabledis used instead of the HTML
disabledattribute so the buttons will remain in the page Tab sequence. This makes it easier for screen reader users to discover the buttons and discern how the interface works.
|Shift + Tab||
|Escape||Closes the dialog.|
|Command + S||(Mac only) Save the contents of the notes
|Control + S||(Windows only) Save the contents of the notes
Role, Property, State, and Tabindex Attributes
||Identifies the element that serves as the alert dialog container.|
||Gives the alert dialog an accessible name by referring to the element that provides the alert dialog title.|
||Gives the alert dialog an accessible description by referring to the alert dialog content that describes the primary message or purpose of the alert dialog.|
||Tells assistive technologies that the windows underneath the current alert dialog are not available for interaction (inert).|
||Identifies the element that serves as the alert notification.|
||Tells assistive technology users the button cannot be activated.|
aria-modalproperty was introduced in ARIA 1.1. As a relatively new property, screen reader users may experience varying degrees of support for it.
- Applying the
aria-modalproperty to the
dialogelement replaces the technique of using
aria-hiddenon the background for informing assistive technologies that content outside a dialog is inert.
In legacy dialog implementations where
aria-hiddenis used to make content outside a dialog inert for assistive technology users, it is important that:
aria-hiddenis set to
trueon each element containing a portion of the inert layer.
- The dialog element is not a descendant of any element that has