[CHANGE] existing native mobile applications must also be accessible. #245
Replies: 1 comment
-
|
Same goes with "2.3.6.1 Features that improve accessibility on all new hardware must be made available to users by default unless an exception has been granted." When will old hardware need to meet EN 301 549? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
2.3.5.1 All new native mobile applications must conform with the latest version of EN 301 549 and include an accessibility statement
https://a11y.canada.ca/en/standards/standard/#2.3.3.1
Governments should be challenged to verify that a mobile application is actually required. Often a responsive website is sufficient. Progressive web application can often provide native-like functionality. These can also improve experiences for everyone. Nobody is excited about downloading a government application.
Existing native mobile applications should have a timeline on when they will be retired or made accessible. You can't just say "All new native mobile applications must conform" while allowing the giant loophole for existing native mobile applications.
Maybe it is a longer timeline, but legacy barriers need to be identified, and eliminated over time. Most legacy applications can probably be re-implemented as accessible, Progressive web apps.
Beta Was this translation helpful? Give feedback.
All reactions