referred to as u201c functionality maps u201d a functionality map can be specific to a single type of screen reader listing the specific functions for that screen reader type a functionality map can be identified by one or more identifying characteristics e g screen reader name and version number in one implementation client code identifies the screen reader in use on the client system and selects a functionality map that corresponds to the screen reader in use optionally a lookup table or list is provided that lists each available functionality map so that the appropriate functionality map can be used at run time in an alternative implementation client code scans the client system for screen readers and selects one of them the selected screen reader is then activated the selection can be based on the presence of a functionality map for the screen reader and or on the extent of the functions in the functionality maps when multiple maps are present in which case a screen reader with more available functions can be selected as shown in fig2 if there is a functionality map u201c functionality map u201d branch from decision step 208 and the target element is found in the functionality map u201c yes u201d branch from step 250 the native element i e an html element associated with the page element by the functionality map is used to represent the page element to the screen reader step 260 this representative is processed by the native functionality of the screen reader step 270 on the next navigation command of the user the process resumes at step 204 if the page element.