Query on Accessibility Insights Potentially Flagging Issues From Other Pages

[daphneyyt]

Hi, we would like to make a few queries on WCAG potentially flagging issues on other pages of the mobile app, when the elements in question are not present on those pages.

In this post, I am asking 3 overarching questions (labelled as 'Examples', as I am sharing the context before asking the follow-up sub-questions). Hence this post might be a little long. Please bear with us :)

Thank you in advance and please feel free to reach out if further information is required. However, we won't be able to share the app details as the app requires login details that are confidential.

Example 1

When scanning Mobile App A for WCAG 1.3.1, WCAG 3.3.2, the elements raised in the following screens are shown in step 1 of the form submission.

We believe these are the elements flagged by AIFA as issues:

However, on the confirmation screen on step 2, these elements are not present. Yet they are flagged by Accessibility Insights as issues

This is how the screen looks like without the visual helper

Questions For Example 1

1. May we know what is causing Accessibility Insights to flag these WCAG issues on Step 2 of the mobile app when the flagged elements are not present?
2. Do these ‘flagged’ issues raise any potential accessibility issues? Or can these be ignored?
3. App owner claims that assistive technologies are already in place for Step 2 pages. Is there any way we could validate this? What does Microsoft recommend?

Example 2

The following are errors flagged when we scan the following pages for WCAG. For context, this is a page where the mobile app is supposed to calculate wages contribution for the user after the user keys in the required information.

These are the issues flagged in Step 1 of 2

The same issues are flagged in Step 2 of 2. However, the elements are not present on this page

Questions For Example 2

1. May we know what is causing Accessibility Insights to flag these WCAG issues on Step 2 of the mobile app when the elements are not present?
2. Do these ‘flagged’ issues raise any potential accessibility issues? Or can these be ignored?
3. App owner claims that assistive technologies are already in place for Step 2 pages. Is there any way we could validate this? What does Microsoft recommend?

Example 3

This is a page with 2 tabs: Citizen and Permanent Resident, meaning, they share the same page on the mobile app.

These are the errors flagged when we scanned the Citizen page:

These are the errors flagged when we scan the Permanent Resident page. As you can see, the errors on the Permanent Resident tab is the same as the Citizen’s tab

if the entries are filled on the Citizen’s tab, the information will be ported over when we select the Permanent Resident’s tab

Questions For Example 3

1. In such instances, could it be possible that the elements flagged by Accessibility Insights are the same between the 2 tabs – and if the app owner rectifies the source issue, the accessibility issue should be resolved on both tabs of the mobile app? Or;
2. Should we advise the app owner to treat each tab’s finding as separate entities and rectify the codes accordingly?

[lisli1]

Hello @daphneyyt, thank you for using Accessibility Insights.

Given the information that I can gather from the screenshots, my guess is that the elements are being hidden but are still present/active on the screen, which would show up to assistive technologies and thus cause the components to be flagged as issues, even if they are not visible. Currently, I can give you the following answers:

Examples 1 & 2:

1. It depends on how the elements are displayed and switched out of view; can't tell from screenshots.
2. Again, I can't give a definitive answer on whether the issues can be ignored, based solely on the screenshots.
3. I'm not sure what you mean by this question, particularly "assistive technologies are already in place." Can you clarify?

Example 3:

1. It is possible that the elements are the same, but it's hard to tell from the screenshots. You can try to fix the issue on one tab and see if the issues are still being flagged for the other tab when you re-run.
2. Accessibility Insights for Android will flag all failure instances, so it is best to fix the app so that the issues are no longer flagged. The actual fix will depend on how the components in the app are programmed.

Ultimately, based on the information shown in the screenshots, it's a bit difficult to determine what the exact issues are; I can only speculate what might be the issue, but the only way to actually diagnose the problem is if we can get a working repro of the issues.

Is there any way you can provide us with a minimal version of the app with just the components in question?

[ghost]

The team requires additional author feedback; please review their replies and update this issue accordingly. Thank you for contributing to Accessibility Insights!

[ghost]

This issue has been automatically marked as stale because it is marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. Thank you for contributing to Accessibility Insights!