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
It would be wonderful to target at least A- 508 compliance for our Beta release.
TOR has known issues with supporting ARIA (and other AT) tags, so working towards a goal of being inclusive with differently abled journalists with this new Workstation setup, from the get-go, would be fabulous.
A keyboard-controllable interface (no mouse required—lots of tab and return use), font size readability, color contrast, a variety of visual affordance things, alt tags, and assistive devices support, are the core components involved in meeting that bar. All of those points less assistive device support, keyboard navigation support, and alt tags, are within my control via design choices—so those three things need implementation research by others, should this be a shared desire to prioritize among the team. Should the keyboard navigation and alt tags items be supportable, I can make UX reccos for those things. Supportive tech (eg: JAWS, etc) however, is totally out of my control.
Initial questions:
• How does QT support assistive technologies?
• What does Qubes' support for assistive tech look like (wincing, as I write this?). Would be good to add this to whatever list there may be of things to connect with the Qubes team, on.
The text was updated successfully, but these errors were encountered:
It would be wonderful to target at least A- 508 compliance for our Beta release.
TOR has known issues with supporting ARIA (and other AT) tags, so working towards a goal of being inclusive with differently abled journalists with this new Workstation setup, from the get-go, would be fabulous.
A keyboard-controllable interface (no mouse required—lots of tab and return use), font size readability, color contrast, a variety of visual affordance things, alt tags, and assistive devices support, are the core components involved in meeting that bar. All of those points less assistive device support, keyboard navigation support, and alt tags, are within my control via design choices—so those three things need implementation research by others, should this be a shared desire to prioritize among the team. Should the keyboard navigation and alt tags items be supportable, I can make UX reccos for those things. Supportive tech (eg: JAWS, etc) however, is totally out of my control.
Initial questions:
• How does QT support assistive technologies?
• What does Qubes' support for assistive tech look like (wincing, as I write this?). Would be good to add this to whatever list there may be of things to connect with the Qubes team, on.
The text was updated successfully, but these errors were encountered: