When dealing with NAF elements (Not Accessibility Friendly), all it means is that an interactive element (clickable or focusable) has no accessibility data attached to the element/node. Accessibility info includes content description or text. See this question for a good explanation: http://stackoverflow.com/questions/25435878/uiautomatorviewer-what-does-naf-stand-for
NAF doesn’t stop you from automating them by using locators. You can still use XPATHs to query the child element from a unique parent/ancestor element, although it might be a longer XPATH expression than simply pointing straight to a node that is correctly labelled with an ID.
The way to solve this problem is to either:
- Ask the developers of the app to add accessibility information to those NAF nodes that unique identify the interactive element.
- Work around the lack of unique accessibility information by using locators like Xpaths which can select elements relative to other elements.