W3C home > Mailing lists > Public > w3c-wai-ua@w3.org > April to June 2015

Re: Fwd: UAAG Examples why browsers need UAAG

From: Greg Lowney <gcl-0039@access-research.org>
Date: Thu, 30 Apr 2015 23:25:58 -0800
Message-ID: <55432A86.3040509@access-research.org>
To: Jim Allan <jimallan@tsbvi.edu>
CC: WAI-ua <w3c-wai-ua@w3.org>
Here are a few more examples:

In additional, many web pages are designed to require a mouse. The browser could provide alternative access for keyboard users, such as the ability to tab to elements that have recognized scripted reactions to mouse input; without this support the pages remain inaccessible to them. (As just one example, this prevents keyboard users from paying their property taxes online in at least one county.)

In at least one browser, the security status button next to the address can be reached using the keyboard only by navigating BACKWARDS through the tab order, which is not easily discoverable.

In at least one browser, toolbar buttons are not accessible from the keyboard (both those built-in and those added by extensions).

In at least one browser, you cannot customize the selection and order of toolbar buttons using the keyboard.

Most or all browsers interpret the HTML specification as telling them to ignore styles that generate content for elements lacking content (e.g. IMG elements). This prevents the user of style sheets to show alt text and other properties.

Generated content may not be exposed to assistive technology through platform API or the DOM, even though it appears to users indistinguishable from other content and may be required to use the page.

As we discussed on last week's call, some users find that check boxes and other controls in content do not scale up with font size, leaving them difficult for some users to see or recognize.

At least one browser running on Windows for the desktop does not assign shortcut keys to the controls in its dialog boxes, failing to comply with platform UI guidelines or accessibility guidelines, and vastly increasing the number of navigation and keystrokes required to perform tasks.

-------- Original Message --------
Subject: Fwd: UAAG Examples why browsers need UAAG
From: Jim Allan <jimallan@tsbvi.edu>
To: WAI-ua <w3c-wai-ua@w3.org>
Date: 4/21/2015 7:59 AM
> This is a document that Jeanne and I wrote to give a few powerful examples as to why UAAG is necessary.
>
> ---------- Forwarded message ----------
> From: *Jeanne Spellman* <jeanne@w3.org <mailto:jeanne@w3.org>>
> Date: Fri, Apr 17, 2015 at 5:39 PM
> Subject: UAAG Examples why browsers need UAAG
>
> ​​
> Examples of why browsers need UAAG to help them with accessibility.
>
> A blind employee who needs to search a specific entries in a photo gallery or repository of charts can't, because most browsers do not search the alternative text.
>
> Employees using a keyboard cannot read all the content contained in a  <div> with overflow, because in most browsers, they cannot use the keyboard to enter the box and cannot move the scrollbars. Even cursor browsing won't enter that overflow box.
>
> People with low vision can't customize the text so they can read it when browsers eliminate user stylesheets.  Zoom is inadequate for people who need to reduce space and heading sizes so the maximum amount of text appears in their field of vision.
>
> In most browsers, people with low vision can't print out a web page at the size or customization they need.  These employees can't work without their computer which limits their ability to do sales calls, or field service.
>
> An employee reading a long document can't resize the text or resize the window without losing their place, because browsers don't keep the point of regard.
>
> Users who want to read a tooltip from the keyboard can't in major browsers, because the browsers don't provide tooltips on keyboard focus.  Elements that can't get focus cannot display tooltips.  This requires authors to go through a lot of work to meet WCAG requirements for keyboard access.
>
> Placeholder text and disabled elements by default do not meet WCAG color contrast requirements, so authors have to compensate to meet WCAG.
>
>
>
>
>
>
>
>
>
>
>
>
> -- 
> 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 <tel:512.206.9315> fax: 512.206.9264 <tel:512.206.9264> http://www.tsbvi.edu/
> "We shape our tools and thereafter our tools shape us." McLuhan, 1964
Received on Friday, 1 May 2015 06:27:03 UTC

This archive was generated by hypermail 2.3.1 : Friday, 1 May 2015 06:27:04 UTC