Skip to main content

Home/ Web Accessibility/ Group items tagged structure

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Vernon Fowler

WebAIM: Semantic Structure - 0 views

webaim.org/...semanticstructure

semantic structure headings lists webdesign content usability accessibility markup

shared by Vernon Fowler on 18 Feb 14 - No Cached
  • Their sole purpose is to designate a hierarchy of headline importance, so that both human readers and automated search engines can look at a document and easily determine its information structure.
Vernon Fowler

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

www.nngroup.com/...breadcrumbs

navigation mobile

shared by Vernon Fowler on 18 Jul 19 - No Cached
  • 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
      Vernon Fowler on 18 Jul 19
       
      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
      Vernon Fowler on 18 Jul 19
       
      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

WebAIM: Creating Accessible Tables - Data Tables - 0 views

webaim.org/...data

tables data accessibility webdesign

shared by Vernon Fowler on 14 Jan 14 - No Cached
  • The summary attribute of the <table> tag may be used to provide a summary of a data table structure (not content). Support for summary varies, but in general, it is screen reader specific (it's not accessible to anyone else) and is not well supported. Additionally, the summary attribute is not part of the HTML5 specification. In general, if a table is so complex that it needs an explanation of how it is structured, it probably is not very accessible and should probably be simplified. For these reasons, we do not recommend the use of summary. If it is used, it must never be used for layout tables.
Vernon Fowler

Complex Data Table Markup Toolbar - 0 views

www.visionaustralia.org/digital-access-tabletoolbar

complex data table markup toolbar

shared by Vernon Fowler on 15 Jan 14 - No Cached
  • Please note that simple data tables are more accessible than complex data tables and that badly structured or marked up complex tables are not accessible.
  • Simple tables rather than complex tables should be implemented whenever possible, and when complex tables are used, please ensure that structure and mark-up is sound.
Sandra Earl

WebAIM: Accessibility of Rich Internet Applications - 0 views

webaim.org/aria

accessibility ARIA WebAIM

shared by Sandra Earl on 12 Oct 10 - Cached
  • WAI-ARIA (Accessible Rich Internet Applications or ARIA) is a W3C protocol for enhancing and supporting accessibility of scripted and dynamic content.
  • ARIA provides accessible interactive controls (such as tree menus, drag and drop, sliders, sort controls, etc.), content roles for identifying page structure (navigation, search, main content, etc.), areas that can be dynamically updated (called "live regions" in ARIA), better support for keyboard accessibility and interactivity, and much more.
  • WAI-ARIA provides the ability for developers to specify roles for document areas (and many other things).
  • ...2 more annotations...
  • accessibility issues with rich internet applications can be characterized as: Providing the semantic structure of page areas and functionality (e.g., navigation, main content, search, etc.) Maintaining accessibility of content that is dynamic and may change within the page (e.g., AJAX content updates) Allowing certain non-focusable page elements to receive keyboard focus (e.g., setting focus to an error message within the page) Providing keyboard and screen reader accessibility with complex widgets and navigation elements (e.g., sliders, menu trees, etc.)
  • ARIA is being implemented into many scripting libraries (such as jQuery, Dojo, YUI, and GWT). While developers can certainly implement ARIA into their advanced widgets and applications, using ARIA-supported libraries greatly simplifies the process of providing this level of accessibility.
Vernon Fowler

WebAIM: Keyboard Accessibility - 0 views

webaim.org/keyboard

accessibility testing keyboard

shared by Vernon Fowler on 02 Jun 17 - No Cached
  • Long lists of links or other navigable items may pose a burden for keyboard-only users.
  • The following best practices can facilitate efficient keyboard navigation: Provide a "skip to main content" link on the page. Use a proper heading structure. Provide ARIA landmarks or HTML5 structural elements (<main>, <nav>, etc.)
  • Vernon Fowler on 02 Jun 17
     
    "when testing with a keyboard, you are not just trying to interact with the page successfully, you also want to ensure all interactions are predictable. This requires an understanding of common keyboard interactions."
Vernon Fowler

WebAIM: Semantic Structure - 0 views

webaim.org/...semanticstructure

semantic structure headings html markup lists accessibility

shared by Vernon Fowler on 05 Feb 14 - No Cached
  • Technically, lower degree headings should be contained within headings of the next highest degree (i.e., one should not skip heading levels, such as from an <h2> to an <h4>, going down the document).
  • one should not skip heading levels
Vernon Fowler

HTML5 Accessibility Chops: When to use an ARIA role | The Paciello Group Blog - 0 views

www.paciellogroup.com/...chops-when-to-use-an-aria-role

accessibility html5 browser

shared by Vernon Fowler on 24 Nov 12 - No Cached
  • The situation for new HTML5 elements is different and likely to remain so for some time. It will be years before New HTML5 elements get robust accessibility support implemented across browsers and platforms. This is particularly so for non interactive elements such as the new HTML5 structural elements because  accessibility APIs in general do not have defined roles for many non interactive elements. In this case it is recommended to add the appropriate ARIA roles to elements that are meant to convey meaning but are effectively meaningless due to lack of implemented accessibility support. For example, adding role=navigation to a nav element fills the gaps in support for HTML5 semantics as ARIA  is more robustly  supported by most modern browsers and assistive technology:
  • <nav role=”navigation”>
  • Authors/developers can safely assume that any element that has been around since HTML 4.0 is already accessibility supported in browsers that support accessibility. So they do not need a default implicit role added.
Vernon Fowler

HTML5 Accessibility Chops: section elements | The Paciello Group Blog - 0 views

www.paciellogroup.com/...ibility-chops-section-elements

accessibility html5

shared by Vernon Fowler on 24 Nov 12 - No Cached
  • The following table illustrates support and interaction features for a number of structural HTML elements. The information is based on support for these elements by the JAWS screen reader.
  • Recommended ARIA role mappings for HTML5 section elements
  • <header role=”banner”>
  • ...1 more annotation...
  • <nav role=”navigation”>
  • Vernon Fowler on 24 Nov 12
     
    "banner"
Vernon Fowler

WAVE Help - 0 views

wave.webaim.org/help

wave tools accessibility testing bookmarklet toolbar headings structure forms

shared by Vernon Fowler on 04 Mar 14 - No Cached
  • Vernon Fowler on 04 Mar 14
     
    "WAVE is tool to help web developers make their web content more accessible. WAVE cannot tell you if your web content is accessible. Only a human can determine true accessibility. But, WAVE can help you evaluate the accessibility of your web content."
Sandra Earl

The Dutch accessibility law is awesome | 456 Berea Street - 0 views

www.456bereastreet.com/...h_accessibility_law_is_awesome

accessibility laws standards

shared by Sandra Earl on 12 Oct 10 - Cached
  • New Dutch accessibility law.
  • A few highlights of what is required: separate structure from presentation do not use deprecated markup when creating a new website, use a Strict doctype use progressive enhancement create semantic class and id values use the W3C DOM when scripting script-only links must be generated by JavaScript do not use the alt attribute to create tooltips
Sandra Earl

Captivate Accessibility Hints | SSB BART Group - 0 views

www.ssbbartgroup.com/...captivate-accessibility-hints

accessibility tips and tricks captivate elearning general content creation

shared by Sandra Earl on 12 Oct 10 - No Cached
  • Captivate has a number of accessibility features in version 3 and 4 although there are some issues that Adobe is working on.
  • Ensure that the “enable accessibility” checkbox is checked under the File > Publish settings in order for accessibility to be exposed to assistive technologies.
  • Slide Accessibility Text Each slide can contain accessibility text. This can be added by going to the slide properties, activating the Accessibility button and entering text in the text field.
  • ...6 more annotations...
  • Closed Captioning Closed captioning can be added to all audio files. From the record audio dialog, closed caption text can be added under the Caption tab. The playback bar contains a CC button which allows the closed captioning to be displayed or hidden.
  • Button Accessibility Text buttons can be made accessible. The text that appears on-screen becomes the button’s accessible name. To make the buttons keyboard accessible, the “Set Keystroke: Select Keys” button should be used and the keystroke of “enter” should be set in the object’s properties dialog. Other shortcuts can be assigned but enter/space will then not work to activate the button after tabbing to it. The keystroke of “enter” can be assigned to multiple buttons and the button with focus will be activated when Enter is pressed.
  • Audio recordings can be associated with click boxes and thus authors can associate descriptive text to be announced when a shortcut keystroke is pressed to assist users with visual impairments.
  • Text from PowerPoint Much of the text from PowerPoint will come through as text in Microsoft Active Accessibility (MSAA) and will be exposed to users of screen readers. Currently there isn’t a method to change the order or edit this text.
  • Quiz Questions There is some accessibility support for quiz questions. Simple types of questions such as true and false and multiple choice provide accessible names for the radio buttons and the text of the question appears as text in the accessible MSAA structure and is exposed to screen readers.
  • Accessibility Differences Between Captivate 3 and 4 The text in the “text caption” object does not show up as accessible text in Captivate 3 but does in Captivate 4. In addition, it is not possible to set accessible text for specific images in Captivate 3 but it is possible in Captivate 4.
1 - 14 of 14
Showing 20▼ items per page