For instance, when the clock changes from '17:33' to '17:34', assistive technologies will only announce '34', which won't be very useful to users. On subsequent calls, only the parts of the content that changed compared to the previous content will be announced. The first time the function executes, the entirety of the string that is added will be announced. Basic example: Dropdown box updates useful onscreen informationĬonst PLANETS_INFO = /* first run */ updateClock ( ) /* update every minute */ setInterval (updateClock, 60000 ) As such, it can be extremely annoying and disruptive and should only be used sparingly.Īs aria-live='off' is the assumed default for elements, it should not be necessary to set this explicitly, unless you're trying to suppress the announcement of elements which have an implicit live region role (such as role='alert'). Generally, a change to an assertive live region will interrupt any announcement a screen reader is currently making. The screen reader will speak changes whenever the user is idle.Īria-live='assertive' should only be used for time-sensitive/critical notifications that absolutely require the user's immediate attention. Any region which receives updates that are important for the user to receive, but not so rapid as to be annoying, should receive this attribute.

Normally, only aria-live='polite' is used. This attribute is by far the most important. A live region is explicitly denoted using the aria-live attribute.Īria-live: The aria-live=POLITENESS_SETTING is used to set the priority with which screen reader should treat updates to live regions - the possible settings are: off, polite or assertive. Simple content changes which are not interactive should be marked as live regions. Using ARIA: Roles, states, and propertiesĭynamic content which updates without a page reload is generally either a region or a widget.

Nvda screen reader disable