Skip to content

Accessibility issues  #681

@Gabrielaparada

Description

@Gabrielaparada

Has anyone successfully used this package with a screen reader?. The toastrs have the correct aria attributes but the screen reader still does not pick up the messages when they happen.
If I had to guess it's due to the fact that the toastr div is not injected into the HTML until there is a message, to my understanding the div (with the attributes) has to be present on load so when the error/success/warning message is added dynamically the screen reader can then pick up that there was a change and announce it.

I found myself having to write inline hidden fallback messages for all my toastrs, by implementing what I mentioned above however it's quite time-consuming. I'd like to know if there is a way to get the screen reader to pick up these messages successfully? am I doing something wrong?

Thanks

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions