W3C home > Mailing lists > Public > public-low-vision-a11y-tf@w3.org > October 2016

Re: See all SC and title attributes

From: Laura Carlson <laura.lee.carlson@gmail.com>
Date: Fri, 7 Oct 2016 08:16:54 -0500
Message-ID: <CAOavpvcEtBijNiTVfL2=dJkNEg_ytvZrkivBfy7g3E0GK8KCXA@mail.gmail.com>
To: Alastair Campbell <acampbell@nomensa.com>
Cc: public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Hi Alastair and All,

Using real on-screen text instead of a title attribute for important
information is exactly the guidance that we provided the vendor after
our 2015 testing [1] results with students with low vision revealed
the cursor hover issue. So, yes I would be in favor of making it an
individual SC. Any ideas on how best we could phrase it?

The HTML5 Rec also warns [2] against use of the title attribute. So
WCAG 2.1 wouldn't be alone in calling out another title attribute

If we can address the Cursor Overlapping Tooltip Text on Hover Issue
separately, we may want to consider if we need the Seeing All
Interface Elements SC. Shawn or Wayne or others may have a different
perspective, but for me the latest sizing SCs seem to cover the other
“without loss of content or functionality” aspect.

Thank you!

Kindest Regards,

[1] https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Mar/0032.html
[2] https://www.w3.org/TR/html/dom.html#the-title-attribute

On 10/7/16, Alastair Campbell <acampbell@nomensa.com> wrote:
> Hi everyone,
> I have two questions on the ‘See all’ SC:
> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Seeing_All_Interface_Elements
> It references tooltips (pop-ups from mouse-over) that come from the title
> attribute, but I wasn’t clear what authors were supposed do about those?
> The browser controls the tooltip in terms of size and timing. If a user has
> enlarged their cursor or is using magnifier, the author has no way of
> knowing that.
> It seems the best guidance would be: don’t use title attributes to convey
> important information
> Or even: don’t use title attributes!
> Would it be best to separate that out?
> Secondly, if the sizing SCs include language around “without loss of content
> or functionality”, do we need the “seeing all interface elements” SC? What
> use-cases does that cover that are not content / functionality?
> Cheers,
> -Alastair
> --
> Alastair Campbell
> www.nomensa.com
> tel: +44 (0)117 929 7333 / 07970 879 653
> follow us: @we_are_nomensa or me: @alastc
> Nomensa Ltd. King William House, 13 Queen Square, Bristol BS1 4NT
> Company number: 4214477 | UK VAT registration: GB 771727411

Laura L. Carlson
Received on Friday, 7 October 2016 13:17:31 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 27 April 2017 14:44:31 UTC