Skip to main content

Home/ Web Accessibility/ Group items tagged WAI

Rss Feed Group items tagged

cecilia marie

My Computer Problem Was Solved in a Few Minutes - 1 views

I had a good internet connection for the past few weeks. Then I began to observe that it was not working the way it should be compared to the past few weeks. I tried to troubleshoot it myself but, ...

computer problem online help fix

started by cecilia marie on 13 Oct 11 no follow-up yet
Vernon Fowler

HTML5 Accessibility: aria-hidden and role="presentation" | Unrepentant - 0 views

  • any user accessing the Accessibility API
  • aria-hidden=”true” + role=”presentation”
    • Vernon Fowler
       
      Use both attributes for cases where browser/OS/screen-reader combinations don't support WAI-ARIA.
Vernon Fowler

Understanding Success Criterion 2.4.7: Focus Visible - 0 views

  •  
    "Success Criterion 2.4.7 Focus Visible (Level AA): Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible."
Vernon Fowler

Breadcrumbs: 11 Design Guidelines for Desktop and Mobile - 0 views

  • the breadcrumb corresponding to the current page should not be a link. You should never have a link that does nothing. The last breadcrumb (denoting the current page) should not be a link.
    • Vernon Fowler
       
      The breadcrumb denoting the current page SHOULD be a link and differentiated from others via mechanisms such as aria-current="page" See https://scottaohara.github.io/a11y_breadcrumbs/ for this pattern.
    • Vernon Fowler
       
      The breadcrumb denoting the current page SHOULD be a link and differentiated from others via mechanisms such as aria-current="page" See https://scottaohara.github.io/a11y_breadcrumbs/ for this pattern.
  • Include the current page as the last item in the breadcrumb trail.
  • Breadcrumb trails should start with a link to the homepage.
  • ...14 more annotations...
  • Breadcrumbs aren’t necessary (or useful) for sites with flat hierarchies that are only 1 or 2 levels deep, or sites that are linear in structure.
  • Unfortunately, on mobile, the cost of using breadcrumbs can quickly overwhelm the benefits. Don’t use breadcrumbs that wrap to multiple lines.
  • Don’t use breadcrumbs that are too small or too crowded together.
  • Consider shortening the breadcrumb trail to include only the last level(s).
  • The Oregon state government website includes a breadcrumb trail, but omits a link to the homepage. However, in this case this is acceptable, as the site also includes a Home link in the global navigation
  • duplicating the Home link in both the global navigation and the breadcrumb trail is not recommended — one or the other is fine
  • This site’s structure is nonhierarchical, and so there is no need (or value) in including a breadcrumb trail.
  • MIT’s main website has a flat hierarchy, with only 1 page in each section. While it features a breadcrumb at the top of the page, this breadcrumb isn’t necessary. In the main navigation, the location of the page is highlighted.
  • Breadcrumbs should include only site pages, not logical categories in your IA.
  • The link to the parent page is a dropdown menu, with the current page’s siblings (bottom image). A better design would  have a separate UI for the local navigation, to enable users to travel to lateral pages in the current section of the site.
  • Breadcrumbs should not replace the global navigation bar or the local navigation within a section.
  • Breadcrumbs augment but do not replace those main forms of navigation.
  • when they skip some of these levels (for example, because they arrived to the site by clicking on an external link such as a search-engine result), breadcrumbs orient them and help them find their way to other, possibly more relevant, pages.
  • In this example, the home page and current page are omitted from the breadcrumb trail, which is not recommended.
Vernon Fowler

Introduction to Understanding WCAG 2.0 | Understanding WCAG 2.0 - 0 views

  • Perceivable - Information and user interface components must be presentable to users in ways they can perceive.This means that users must be able to perceive the information being presented (it can't be invisible to all of their senses)Operable - User interface components and navigation must be operable.This means that users must be able to operate the interface (the interface cannot require interaction that a user cannot perform)
  • users must be able to understand the information as well as the operation of the user interface
  • robust enough that it can be interpreted reliably by a wide variety of user agents, including assistive technologies
  •  
    "The guidelines and Success Criteria are organized around the following four principles, which lay the foundation necessary for anyone to access and use Web content."
« First ‹ Previous 41 - 49 of 49
Showing 20 items per page