moving to mobile-l You mean title attributes?
Yeh they should have labels or title attributes for accessibility reasons. This has been somewhat neglected since tooltips don't even appear on mobile devices.
I think Pine raised a similar issue on list yesterday. On 9 Jul 2014 02:32, "Dario Taraborelli" dtaraborelli@wikimedia.org wrote:
Hi all – am I missing something or the Edit and Watchlist links (under li#ca-edit and li#ca-watch) should have HTML titles? I noticed this while browsing the mobile version on a desktop browser, I was expecting descriptive titles when hovering with the mouse over those elements.
Dario
Indeed - Pine filed a bug yesterday: https://bugzilla.wikimedia.org/show_bug.cgi?id=67726
Is this the same issue you're describing Dario?
On Wed, Jul 9, 2014 at 9:55 AM, Jon Robson jrobson@wikimedia.org wrote:
moving to mobile-l You mean title attributes?
Yeh they should have labels or title attributes for accessibility reasons. This has been somewhat neglected since tooltips don't even appear on mobile devices.
I think Pine raised a similar issue on list yesterday. On 9 Jul 2014 02:32, "Dario Taraborelli" dtaraborelli@wikimedia.org wrote:
Hi all – am I missing something or the Edit and Watchlist links (under li#ca-edit and li#ca-watch) should have HTML titles? I noticed this while browsing the mobile version on a desktop browser, I was expecting descriptive titles when hovering with the mouse over those elements.
Dario
it is, I just hadn’t thought of the issue with text browsers, but either way it’s a very much needed fix for accessibility reasons.
Thanks, guys.
D
On Jul 9, 2014, at 6:58 PM, Arthur Richards arichards@wikimedia.org wrote:
Indeed - Pine filed a bug yesterday: https://bugzilla.wikimedia.org/show_bug.cgi?id=67726
Is this the same issue you're describing Dario?
On Wed, Jul 9, 2014 at 9:55 AM, Jon Robson jrobson@wikimedia.org wrote: moving to mobile-l You mean title attributes?
Yeh they should have labels or title attributes for accessibility reasons. This has been somewhat neglected since tooltips don't even appear on mobile devices.
I think Pine raised a similar issue on list yesterday.
On 9 Jul 2014 02:32, "Dario Taraborelli" dtaraborelli@wikimedia.org wrote: Hi all – am I missing something or the Edit and Watchlist links (under li#ca-edit and li#ca-watch) should have HTML titles? I noticed this while browsing the mobile version on a desktop browser, I was expecting descriptive titles when hovering with the mouse over those elements.
Dario
-- Arthur Richards Team Practices Lead [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687
Yes, we definitely need someone to test mobile web & the new apps on iOS's 'VoiceOver' screen reader mode and Android's 'TalkBack' at some point and let us know what works/doesn't work for visually-impaired users.
Do we have someone working on accessibility issues in general that we can have help with this or will we need to take testing on ourselves when time permits?
-- brion
On Wed, Jul 9, 2014 at 10:37 AM, Dario Taraborelli < dtaraborelli@wikimedia.org> wrote:
it is, I just hadn’t thought of the issue with text browsers, but either way it’s a very much needed fix for accessibility reasons.
Thanks, guys.
D
On Jul 9, 2014, at 6:58 PM, Arthur Richards arichards@wikimedia.org wrote:
Indeed - Pine filed a bug yesterday: https://bugzilla.wikimedia.org/show_bug.cgi?id=67726
Is this the same issue you're describing Dario?
On Wed, Jul 9, 2014 at 9:55 AM, Jon Robson jrobson@wikimedia.org wrote:
moving to mobile-l You mean title attributes?
Yeh they should have labels or title attributes for accessibility reasons. This has been somewhat neglected since tooltips don't even appear on mobile devices.
I think Pine raised a similar issue on list yesterday. On 9 Jul 2014 02:32, "Dario Taraborelli" dtaraborelli@wikimedia.org wrote:
Hi all – am I missing something or the Edit and Watchlist links (under li#ca-edit and li#ca-watch) should have HTML titles? I noticed this while browsing the mobile version on a desktop browser, I was expecting descriptive titles when hovering with the mouse over those elements.
Dario
-- Arthur Richards Team Practices Lead [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687
+1
I also wanted to add that tooltips using attribute titles/labels are important for usability, particularly when an icon can be ambiguously interpreted in a given locale/culture.
On Jul 9, 2014, at 7:41 PM, Brion Vibber bvibber@wikimedia.org wrote:
Yes, we definitely need someone to test mobile web & the new apps on iOS's 'VoiceOver' screen reader mode and Android's 'TalkBack' at some point and let us know what works/doesn't work for visually-impaired users.
Do we have someone working on accessibility issues in general that we can have help with this or will we need to take testing on ourselves when time permits?
-- brion
On Wed, Jul 9, 2014 at 10:37 AM, Dario Taraborelli dtaraborelli@wikimedia.org wrote: it is, I just hadn’t thought of the issue with text browsers, but either way it’s a very much needed fix for accessibility reasons.
Thanks, guys.
D
On Jul 9, 2014, at 6:58 PM, Arthur Richards arichards@wikimedia.org wrote:
Indeed - Pine filed a bug yesterday: https://bugzilla.wikimedia.org/show_bug.cgi?id=67726
Is this the same issue you're describing Dario?
On Wed, Jul 9, 2014 at 9:55 AM, Jon Robson jrobson@wikimedia.org wrote: moving to mobile-l You mean title attributes?
Yeh they should have labels or title attributes for accessibility reasons. This has been somewhat neglected since tooltips don't even appear on mobile devices.
I think Pine raised a similar issue on list yesterday.
On 9 Jul 2014 02:32, "Dario Taraborelli" dtaraborelli@wikimedia.org wrote: Hi all – am I missing something or the Edit and Watchlist links (under li#ca-edit and li#ca-watch) should have HTML titles? I noticed this while browsing the mobile version on a desktop browser, I was expecting descriptive titles when hovering with the mouse over those elements.
Dario
-- Arthur Richards Team Practices Lead [[User:Awjrichards]] IRC: awjr +1-415-839-6885 x6687
On Wed, Jul 9, 2014 at 10:41 AM, Brion Vibber bvibber@wikimedia.org wrote:
Do we have someone working on accessibility issues in general that we can have help with this or will we need to take testing on ourselves when time permits?
Its up to us to prioritize this kind of work in all of our backlogs. One person would be swamped pretty quickly if they were responsible for it organization wide.
--tomasz
Sure, but is there anyone with domain knowledge of accessibility issues who can help us learn things like how users interact with screen readers and what their expectations are? I've fiddled with iOS's VoiceOver occasionally, but I have *no idea* how my rough attempts to use it actually apply to real-world user requirements.
We have a whole Language Engineering team to aid the rest of the teams with i18n issues for instance, but I don't know if we have *any* accessibility resources to go to...
-- brion
On Wed, Jul 9, 2014 at 1:40 PM, Tomasz Finc tfinc@wikimedia.org wrote:
On Wed, Jul 9, 2014 at 10:41 AM, Brion Vibber bvibber@wikimedia.org wrote:
Do we have someone working on accessibility issues in general that we can have help with this or will we need to take testing on ourselves when
time
permits?
Its up to us to prioritize this kind of work in all of our backlogs. One person would be swamped pretty quickly if they were responsible for it organization wide.
--tomasz
CC'ing Erik to see if anyone has this as their skill set.
--tomasz
On Wed, Jul 9, 2014 at 1:47 PM, Brion Vibber bvibber@wikimedia.org wrote:
Sure, but is there anyone with domain knowledge of accessibility issues who can help us learn things like how users interact with screen readers and what their expectations are? I've fiddled with iOS's VoiceOver occasionally, but I have *no idea* how my rough attempts to use it actually apply to real-world user requirements.
We have a whole Language Engineering team to aid the rest of the teams with i18n issues for instance, but I don't know if we have *any* accessibility resources to go to...
-- brion
On Wed, Jul 9, 2014 at 1:40 PM, Tomasz Finc tfinc@wikimedia.org wrote:
On Wed, Jul 9, 2014 at 10:41 AM, Brion Vibber bvibber@wikimedia.org wrote:
Do we have someone working on accessibility issues in general that we can have help with this or will we need to take testing on ourselves when time permits?
Its up to us to prioritize this kind of work in all of our backlogs. One person would be swamped pretty quickly if they were responsible for it organization wide.
--tomasz