Difference between revisions of "Feature:Accessibility"
Jump to navigation
Jump to search
m |
|||
| Line 1: | Line 1: | ||
| − | Quick note: Apparently Slack and most other systems are next to impossible to use with screenreaders, because they never tested their apps with those. Screenreaders often read back the entire page upon DOM updates, when not doing it right. With proper usage of accessibility standards (e.g. [https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions ARIA Live Regions], it shouldn't be very difficult to take that aspect into account for client development. | + | Quick note: Apparently Slack and most other systems are next to impossible to use with screenreaders, because they never tested their apps with those. Screenreaders often read back the entire page upon DOM updates, when not doing it right. With proper usage of accessibility standards (e.g. [https://developer.mozilla.org/en-US/docs/Web/Accessibility/ARIA/ARIA_Live_Regions ARIA Live Regions]), it shouldn't be very difficult to take that aspect into account for client development. |
Latest revision as of 10:07, 5 May 2017
Quick note: Apparently Slack and most other systems are next to impossible to use with screenreaders, because they never tested their apps with those. Screenreaders often read back the entire page upon DOM updates, when not doing it right. With proper usage of accessibility standards (e.g. ARIA Live Regions), it shouldn't be very difficult to take that aspect into account for client development.
