Please Add Support For Accessibility Features #7743
pythonpoole
started this conversation in
Ideas
Replies: 0 comments
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.
Many jurisdictions now require websites and apps to be accessible to persons with disabilities. For legal and regulatory compliance reasons (and also other reasons), it's important that websites and apps be screen reader accessible (so that they can be used by people who are blind or by people who otherwise require assistive technologies).
This often involves applying special platform-specific tags or labels to UI / DOM elements to indicate their function or purpose (or to explain what they are displaying).
As an example, the
altattribute for image tags in HTML documents allows web developers to provide text descriptions for images which screen readers can then speak aloud to blind users.Each platform has different ways to handle these types of accessibility tags / labels.
For example, on the web you have
altattributes,arialabels & roles, semantic markup, etc.And on iOS, for example, you have
accessibilityLabel,accessibilityHint,accessibilityValue,accessibilityFrame,accessibilityTraits, etc.And on Android, for example, you have
android:contentDescription,android:hint,android:labelFor,android:accessibilityPaneTitle, etc.I could be mistaken, but right now I don't think there is any way to set these accessibility labels in Perry (or a way to configure Perry to use appropriate semantic roles / markup).
All reactions