Re: More UAAG use cases from mobile

there was a bug filed on chrome
https://code.google.com/p/chromium/issues/detail?can=2&q=476992&colspec=ID%20Pri%20M%20Week%20ReleaseBlock%20Cr%20Status%20Owner%20Summary%20OS%20Modified&id=476992

the default contrast of <option> in hover or focus state in <select> does
not meet WCAG, and is not styleable by the author.


On Thu, Apr 30, 2015 at 10:51 AM, Jeanne Spellman <jeanne@w3.org> wrote:

> Two examples of where browsers don't meet user needs were identified in
> the Mobile Accessibility Task Force meeting today. The group was not
> looking for examples, it came up in discussion of other topics. I'm cc
>
> 1) The ability to display captions is very inconsistent in media players
> on mobile browsers. Most mobile browsers do not respect OS settings to
> display captions and don't provide their own control to turn it on.
>
>
> 2) VW font attribute in CSS is inconsistently implemented in browsers
> (especially mobile) and some browsers prevent text size from increasing on
> zoom when the CSS attribute is set.
>
>


-- 
[image: http://www.tsbvi.edu] <http://www.tsbvi.edu>Jim Allan,
Accessibility Coordinator & Webmaster
Texas School for the Blind and Visually Impaired
1100 W. 45th St., Austin, Texas 78756
voice 512.206.9315    fax: 512.206.9264  http://www.tsbvi.edu/
"We shape our tools and thereafter our tools shape us." McLuhan, 1964