AriaDescriber
+
Utility that creates visually hidden elements with a message content. Useful for elements that want to use aria-describedby to further describe themselves without adding additional visual content.
@@ -245,9 +245,9 @@InputModalityDetector
+
Service that detects the user's input modality.
This service does not update the input modality when a user navigates with a screen reader (e.g. linear navigation with VoiceOver, object navigation / browse mode with NVDA, virtual PC @@ -317,9 +317,9 @@
HighContrastModeDetector
+
Service to determine whether the browser is currently in a high-contrast-mode environment.
Microsoft Windows supports an accessibility feature called "High Contrast Mode". This mode changes the appearance of all applications, including web applications, to dramatically increase @@ -373,9 +373,9 @@
ConfigurableFocusTrapFactory
+
Factory that allows easy instantiation of configurable focus traps.
@@ -461,9 +461,9 @@FocusTrapFactory
+
Factory that allows easy instantiation of focus traps.
@@ -550,9 +550,9 @@InteractivityChecker
+
Utility for checking the interactivity of an element, such as whether it is focusable or tabbable.
@@ -809,9 +809,9 @@LiveAnnouncer
+
FocusMonitor
+
Monitors mouse and keyboard events to determine the cause of focus events.
@@ -1486,16 +1486,16 @@CdkTrapFocus
+
Directive for trapping focus within a region.
Selector: @@ -1565,9 +1565,9 @@
CdkAriaLive
+
A directive that works similarly to aria-live, but uses the LiveAnnouncer to ensure compatibility with a wider range of browsers and screen readers.
@@ -1624,9 +1624,9 @@
CdkMonitorFocus
+
Directive that determines how a particular element was focused (via keyboard, mouse, touch, or programmatically) and adds corresponding classes to the element.
There are two variants of this directive:
@@ -1683,14 +1683,13 @@ActiveDescendantKeyManager
@@ -1700,6 +1699,7 @@
+ |
+ Whether to count an element as focusable even if it is inert or inside an inert subtree. + |
+
+
+
+
+
+
||
-
Interfaces
+
RegisteredMessage
+
|
- |
- Whether the dialog should close when the user navigates backwards or forwards through browser
-history. This does not apply to navigation via anchor element unless using URL-hash based
-routing ( | Whether the dialog should be disposed of when the user navigates. |