question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Accessibility issues

See original GitHub issue

Platform

iOS

Author or host

Host

Version of SDK

1.2

Issue

Voiceover and screen reader is not working correctly on adaptive cards. We are sending correct json object but voiceover is not navigating in a serial order. Also, plenty of UI elements are not accessible.

In sample json given below, voiceover navigates to first container inside body, then moves to actions and then comes back to factsets in the body

{
  "body": [
    {
      "items": [
        {
          "size": "large",
          "weight": "bolder",
          "type": "TextBlock",
          "text": "Would you like to book this shuttle?"
        }
      ],
      "type": "Container"
    },
    {
      "items": [
        {
          "facts": [
            {
              "title": "Pick-up location:",
              "value": "Building 11"
            },
            {
              "title": "Drop-off location:",
              "value": "Building 33"
            },
            {
              "title": "Passenger count:",
              "value": "1"
            },
            {
              "title": "Accessibility options:",
              "value": "(none)"
            }
          ],
          "id": "BookingFactSet",
          "type": "FactSet"
        }
      ],
      "type": "Container"
    }
  ],
  "type": "AdaptiveCard",
  "actions": [
    {
      "title": "Book now",
      "data": {
        "CardType": "ShuttleBookingCard",
        "Command": "BookShuttle"
      },
      "type": "Action.Submit"
    },
    {
      "title": "Pick-up",
      "card": {
        "type": "AdaptiveCard",
        "actions": [
          {
            "title": "Save",
            "data": {
              "CardType": "ShuttleBookingCard",
              "Command": "ChangeFromLocation"
            },
            "type": "Action.Submit"
          }
        ],
        "version": "1.0"
      },
      "type": "Action.ShowCard"
    },
    {
      "title": "Drop-off",
      "card": {
        "type": "AdaptiveCard",
        "actions": [
          {
            "title": "Save",
            "data": {
              "CardType": "ShuttleBookingCard",
              "Command": "ChangeToLocation"
            },
            "type": "Action.Submit"
          }
        ],
        "version": "1.0"
      },
      "type": "Action.ShowCard"
    },
    {
      "title": "Options",
      "card": {
        "type": "AdaptiveCard",
        "actions": [
          {
            "title": "Save",
            "data": {
              "CardType": "ShuttleBookingCard",
              "Command": "ChangeOptions"
            },
            "type": "Action.Submit"
          }
        ],
        "version": "1.0"
      },
      "type": "Action.ShowCard"
    }
  ],
  "version": "1.0"
}

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:17 (10 by maintainers)

github_iconTop GitHub Comments

1reaction
shalinijoshi19commented, Aug 19, 2019

@arpitgupta19, just to be clear you are from the Teams team correct? Meanwhile, understood and @nesalang is already looking into this one but just setting your expectations on this that we are aware of a few major Accessibility related issues in the platform and a whole bunch that we aren’t even aware exist. The next few months for us a team, will be dedicated to discovering, triaging, fixing these issues across the board across all platforms. If there’s low hanging fruit we’ll certainly try our best to get these fixed and work with you to backport for consumption in 1.2 and others just roll out all up as part of our vNext release (1.3). Am also following up offline around this. Thanks again

1reaction
arpitgupta19commented, Aug 7, 2019

@shalinijoshi19 There is a strong push on accessibility fixes on our end and the adpative cards issues have become high priority items. We have been asked to get these issues fixed asap.

Read more comments on GitHub >

github_iconTop Results From Across the Web

10 Most Common Web Accessibility Issues to Solve for
10 Most Common Accessibility Issues to Solve for · 1. Inappropriate Alternative Text on Images · 2. Poor Contrast Text · 3. Heading...
Read more >
Top Ten Most Common Web Accessibility Issues
Top 10 Most Common Website Accessibility Issues: 1. Image alt text errors, 2. Current focus, 3. Failure to use proper labels.
Read more >
Top 8 Most Common Accessibility Issues to Avoid and Solve
1. Low Contrast on Text. In WebAIM's programmatic analysis of the top 1,000,000 homepages, low color contrast on text was the most common ......
Read more >
12 Common Web Accessibility Issues for the Visually ...
12 Common Accessibility Issues for Users with Visual Impairment · Accessibility issue #1: HTML layout · Accessibility issue #2: Text contrast.
Read more >
Why Is Accessibility Still A Problem? What Can We Do ...
1. The ADA's approach to accessibility is complex and uneven. · 2. Enforcement is inconsistent, and advocacy is stigmatized. · 3. Businesses with ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found