Accessibility Part 4
Presented by
Content must be robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies.
Copyright By PowCoder代写 加微信 powcoder
Parseable HTML
The HTML must be parseable. A lot of this comes for free as part of modern JS frameworks so I won’t spend too long on this one.
Opening and closing tags and attributes must not be malformed.
Open tags must have an equivalent
Open tags must have an equivalent
close tag
Parseable HTML
Checks that won’t be caught by modern JS frameworks:
A doctype is defined
No duplicate IDs
Referenced IDs in aria-labelledby or htmlFor exist
Only relevant attributes are added to tags
Elements with Roles
Interactive elements must either have a role or use a special tag that implies a role. As long as you’re using buttons, inputs, and links, this should not be a problem. If you define your own custom interactive elements (e.g. anything with an onMouseDown, onMouseUp, onClick), you must add a role.
Any roles that you do add must be appropriate for the UX.
And that’s the end of content!
Use accessibility tools
Apple’s accessibility tools come out of the box, both for macOS and iOS. Please have a go at using VoiceOver:
Guide for VoiceOver on Mac Guide for VoiceOver on iPhone
For all computers including Windows and Linux, you can use the Chrome Screen Reader.
TalkBack is the Android screen reader.
Additional topics
Reduced motion
MDN article on prefers-reduced-motion
Dark mode can also improve accessibility
Audio descriptions
Example of engaging audio descriptions
All the best!
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com