You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to propose migrating from SweetAlert to SweetAlert2 - the supported fork of SweetAlert. The original reason for creating SweetAlert2 is the inactivity of SweetAlert: https://stackoverflow.com/a/27842854/1331425
Accessibility (WAI-ARIA) - SweetAlert2 is fully WAI-ARIA compatible and supports all popular screen-readers. Accessibility is a must in 2019, there are a lot of explanatory and tech articles, but this one is truly inspirable: Software development 450 words per minute
Better buttons contrast is a huge advantage for all users especially for users with vision disabilities.
I would like to propose migrating from SweetAlert to SweetAlert2 - the supported fork of SweetAlert. The original reason for creating SweetAlert2 is the inactivity of SweetAlert: https://stackoverflow.com/a/27842854/1331425
Reasons to switch:
More great features like toasts which were requested in Toast SweetAlert2 #119
Accessibility (WAI-ARIA) - SweetAlert2 is fully WAI-ARIA compatible and supports all popular screen-readers. Accessibility is a must in 2019, there are a lot of explanatory and tech articles, but this one is truly inspirable: Software development 450 words per minute
Better buttons contrast is a huge advantage for all users especially for users with vision disabilities.
Better support, average time to resolve an issue:
SweetAlert2 is twice more popular that SweetAlert: https://www.npmtrends.com/sweetalert-vs-sweetalert2
I can contribute with a PR if needed. After migrating, I can add the link to this project to https://github.com/sweetalert2/sweetalert2#related-community-projects so users can discover it
The text was updated successfully, but these errors were encountered: