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 should make accessibility enhancements to make the Cupcake more usable for the visually impaired and people who use accessibility devices.
I could make this happen with ARIA markup. The most commonly used screen readers offer support for ARIA and some automatically select a speech/aural stylesheet if one is offered. (aural was offered for CSS2, speech is the variety used in CSS3. Backwards compatibility is in play, but given that Cupcake only exists for modern browsers, I'm just going for CSS3).
Cupcake is small enough that this would dictate the accessibility tree in a pretty straightforward way. Instead of listing current and possible statuses (as it does now), Cupcake will just list the current status and ways to resolve it, if necessary. This will be partly implemented as part of the UX overhaul.
I should make accessibility enhancements to make the Cupcake more usable for the visually impaired and people who use accessibility devices.
I could make this happen with ARIA markup. The most commonly used screen readers offer support for ARIA and some automatically select a speech/aural stylesheet if one is offered. (
aural
was offered for CSS2,speech
is the variety used in CSS3. Backwards compatibility is in play, but given that Cupcake only exists for modern browsers, I'm just going for CSS3).Cupcake is small enough that this would dictate the accessibility tree in a pretty straightforward way. Instead of listing current and possible statuses (as it does now), Cupcake will just list the current status and ways to resolve it, if necessary. This will be partly implemented as part of the UX overhaul.
References:
(note to self: JAWS 8 is the IE6 of screen readers)
The text was updated successfully, but these errors were encountered: