Viewing 3 reply threads
  • Author
    Posts
    • #15429
      Miguel Ferraz
      Participant

        Hi

        Recently a colleague has started using Otobo at our University. Still, it has some issues with using the dropdown that is recognized as a search field (that filters the available entries).

        He referred to replying to a ticket; it’s impossible to read the options on the ticket state using the screen reader.

        Is there some configuration that we can do, or another theme that is more screen reader friendly?

      • #15430
        Stefan Abel
        Participant

          Hi Miguel,

          We hope you are well.
          Is he accessing the system via the agent frontend (/otobo/index.pl) or via the customer frontend (/otobo/customer.pl?)
          Do you also have some more information for us? Which screen reader setup is he using? And could you show us an example configuration of the dynamic field?
          And what exactly doesn’t work? Is the voice not telling all the values that are possible to select from? Does it happen only if you typed something or also if you just click to open it?

          Maybe you could help us out with some clarification.

          Cheers
          Stefan

        • #15431
          Miguel Ferraz
          Participant

            Hi

            Thank you for your reply, is via the agent frontend; we’ve tried the MacOS screen reader the voice doesn’t tell the values from this kind of fields:

            Thank you in advance.

          • #15648
            Miguel Ferraz
            Participant

              Hi.

              Is there any update on this topic? Because it something that will be demanding by the EU new approved law by The Digital Services Act.

               

          Viewing 3 reply threads
          • You must be logged in to reply to this topic.