- From: Wayne Dick <wayneedick@gmail.com>
- Date: Mon, 24 Oct 2016 06:59:48 -0700
- To: Laura Carlson <laura.lee.carlson@gmail.com>
- Cc: Erich Manser <emanser@us.ibm.com>, public-low-vision-a11y-tf <public-low-vision-a11y-tf@w3.org>
Titles are a problem. Since the user with low vision may not be using a screen reader, the title may the only information describing a active item. How can this be solved if there is not title element? Wayne On Wed, Oct 19, 2016 at 5:03 AM, Laura Carlson <laura.lee.carlson@gmail.com> wrote: > Hi Wayne, Erich, and all, > > I think that authors can control whether or not they put important > information in title attributes that are unreadable when cursors are > enlarged. I have described the known issue [1]. Joanna Briggs from > Simply Accessible wrote an article [2] regarding it. > > She states, "When hovering over a link that has a title attribute, the > large mouse pointer covers the start of the title attribute. Longer > title attributes may not fit inside the viewport with higher levels of > magnification...In usability testing, we've even observed a user who > was looking for a link on the screen. She didn’t know that she > stopped her mouse over a link with a title attribute. That title > attribute hid the link she was trying to hunt down. How do you avoid > these problems? Just avoid using title attributes." > > The HTML5 Recommendation warns [3] against use of the title attribute. > So WCAG 2.1 wouldn't be alone in calling out another title attribute > issue. > > Alastair had suggested [4] that we could have a separate SC that > stated: "Metadata in a webpage that is shown on mouse-over does not > include information necessary to understanding the content or > functionality." That may work, *if* we can figure out a way define > "metadata". > > Or we could simply call out the issue by incorporating some more text > and images regarding the problem into resize content (size of all > elements) description [5]. > > Kindest Regards, > Laura > > [1] https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Mar/0032.html > [2] http://simplyaccessible.com/article/title-attributes/ > [3] https://www.w3.org/TR/html/dom.html#the-title-attribute > [4] https://lists.w3.org/Archives/Public/public-low-vision-a11y-tf/2016Oct/0041.html > [5] https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements#Description > > > On 10/18/16, Wayne Dick <wayneedick@gmail.com> wrote: >> I considered cursor resize carefully and really decided it was a user >> agent issue. The mouse pointer can be changed with content, but the >> serious problem is the carrot (insertion point) and that is out of >> the author's hands. The rest of the issues. >> >> That was my thinking. What do you think? >> >> Wayne >> >> On Tue, Oct 18, 2016 at 1:55 PM, Laura Carlson >> <laura.lee.carlson@gmail.com> wrote: >>> Hi Wayne and all, >>> >>> Do you think resize content (size of all elements) covers the "Cursor >>> Overlapping Tooltip Text on Hover" issue? >>> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Seeing_All_Interface_Elements#Cursor_Overlapping_Tooltip_Text_on_Hover_Examples >>> >>> If not, should that be a separate SC or would more text be needed to >>> cover that problem in the resize content (size of all elements) SC? If >>> it would help we could add the images from the "Seeing all Elements" >>> [1] page to the "Resize content" page [2]: >>> >>> Thanks. >>> >>> Kindest Regards, >>> Laura >>> >>> [1] >>> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Seeing_All_Interface_Elements >>> [2] >>> https://www.w3.org/WAI/GL/low-vision-a11y-tf/wiki/Size_of_all_elements >>> >>> On 10/18/16, Wayne Dick <wayneedick@gmail.com> wrote: >>>> If the resize content (size of all elements) is adopted, Resize Text >>>> and Resize all interface elements are unnecessary. I still have some >>>> worries. >>>> >>>> (1) Preformatted text: This SC should not allow Preformatted Text to >>>> have two dimensional scrolling. >>>> >>>> The reason is this. Preformatted text is not necessary. Complicated >>>> formats can be obtained with CSS. >>>> >>>> Maybe the exceptions that allow two dimensional scrolling need to be >>>> delineated explicitly. >>>> >>>> Wayne >>>> >>>> >>> >>> >>> -- >>> Laura L. Carlson >> > > > -- > Laura L. Carlson
Received on Monday, 24 October 2016 14:01:02 UTC