Fixed edge case where if screenreader boolean is true then we would d…

…isplay null which would break the keyboard access logic. To combat this while still preserving the intent of the original code I opted to make a TextView with a zero-width space character so the TextView is still treated like an actionable item and still allows navigation of the page with keyboard access. Also, fixed formatting. Making this change allows keyboard navigation to work regardless if user has screenreader enabled or not.

VAMobile/src/components/Templates/FeatureLandingAndChildTemplate.tsx

@@ -144,7 +144,7 @@ export const ChildTemplate: FC<ChildTemplateProps> = ({
         }}
         {...scrollViewProps}>
         <View accessible accessibilityLabel={titleA11y} onLayout={getTransitionHeaderHeight}>
-          {!screenReaderEnabled ? <TextView {...subtitleProps}>{title}</TextView> : null}
+          {!screenReaderEnabled ? <TextView {...subtitleProps}>{title}</TextView> : <TextView>{'\u200B'}</TextView>}
         </View>
         <WaygateWrapper>{children}</WaygateWrapper>
       </VAScrollView>