Screen Readers (NVDA, JAWS) do not recognize main landmark in the 'Users' page when navigating using landmark shortcut key - Known Error

Screen Readers (NVDA, JAWS) do not recognize main landmark in the 'Users' page when navigating using landmark shortcut key Description Main landmark is not provided and not announced by screen readers NVDA / JAWS (Accessibility - WCAG 1.3.1, 2.4.1) when unified navigation is turned on.

Steps to Reproduce

1 : Enable Screen Reader 2 : Incident-All-> Incidents page-> New button (in navigation landmark)-> Incident New record page-> 3 : Lookup using list (Search icon) present beside the 'Caller' edit field-> Users Azure Managed Experience page-> Show/hide filter button-> ADD button-> OR button-> Add Sort button 4 : Navigate to the page using landmark shortcut keys 'D'

Main landmark is not recognized and not announced by the screen reader.

Workaround This problem has been fixed in San Diego Patch 1 and Tokyo as part of PRB1545442/KB1156663 "Next Experience lists generate an error - Bypass block is not provided to navigate to main content" .

Login San Diego pre-patch 1 as admin Go to the user preference table and create a record On the new user preference form, set the following: Name: glide.ui.polaris.use Type: true | false Value: false User: Here, you will select the user that requires the use of a screen reader Save the form NOTE : In San Diego patch 1 this added preference can be removed so the user can take full advantage of the unified navigation experience.