Skip to main content

Home/ Web Accessibility/ Group items tagged using

Rss Feed Group items tagged

Sandra Earl

Introducing WysiHat: An eventually better open source WYSIWYG editor - (37signals) - 0 views

  • WysiHat is a WYSIWYG JavaScript framework that provides an extensible foundation to design your own rich text editor. WysiHat stays out of your way and leaves the UI design to you. Although WysiHat lets you get up and running with a few lines of code, the focus is on letting you customize it. We are giving developers early access to the project while we continue to work out the remaining issues. Note: It’s extremely early. Contributors are welcome so please check out the project on GitHub and send us your feedback.
Sandra Earl

Web Axe - Practical Web Design Accessibility Tips - Podcast and Blog: Paul Boag wears r... - 0 views

  • In Boagworld podcast episode 130, I discovered that in order to help test web accessibility, Paul Boag wears glasses (that he doesn't need) and gloves and attempts to navigate through a site. Excellent idea!In order to better understand [the elderly's] experience I have bought a pair to ski gloves and some reading glasses (I don't need reading glasses). Every now and again, I surf the site I am designing wearing both the glasses and gloves. The glasses make the screen hard to read while the gloves hamper my use of the mouse and the keyboard. There is nothing more frustrating than trying to select something from a drop down menu wearing ski gloves!
Sandra Earl

E-Access Blog » Blog Archive » Global Online Accessibility Resource Set For 2... - 0 views

  • An online resource of open source, royalty-free assistive technology tools, accessible and usable at any time and across the world, is to be launched next year by a consortium of more than 30 US and European IT and disability organisations and leaders, the European Commission e-Inclusion conference heard this month.
Sandra Earl

Captivate Accessibility Hints | SSB BART Group - 0 views

  • 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.
Sandra Earl

Web 2.0: Understanding Web Accessibility - 0 views

  • As stated by renowned accessibility expert Shawn Lawton Hewitt, Web Accessibility simply means that people with disabilities can use the Web.  More specifically, Web Accessibility means that people with disabilities can perceive, understand, navigate and interact with the Web.
  • It is important to understand one aspect that most experts agree on – an individual web site can never be perfectly accessible to everybody. This has to do with the sheer diversity of disabilities as well as the potential overlap of multiple disabilities. But a systematic approach like implementing the WCAG guidelines can go long way in accommodating a very large number of people.
Sandra Earl

Index Braille - WinBraille 5 - Braille editor - 0 views

  • WinBraille 5 Free WinBraille 5 Free includes the most commonly used braille editing functions. It handles most document types like office, pdf, and e-mails. Vista and XP support Office 2003 and 2007 support Supports import of Duxbury files
seth kutcher

Certified Expert Remote PC Tech Support Provider! - 1 views

I used to have a slow computer. It would take 10 minutes to boot up and then another 10 minutes to load. It was really a big headache. Good thing I called Remote PC Repair Now . Their remote PC...

remote PC repair

started by seth kutcher on 02 Nov 11 no follow-up yet
Vernon Fowler

Guidelines for Visualizing Links - 0 views

  • Don't underline any text that's not a link
  • The color for unvisited links should be more vivid, bright, and saturated than the color for visited links, which should look "used" (dull and washed out).
  • The two colors should be variants or shades of the same color, so that they're clearly related.
  • ...1 more annotation...
  • Don't place links so close together that users with reduced motor skills will have difficulty selecting them.
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

Screenreaders · Bootstrap - 0 views

  • Hide an element to all devices except screen readers with .sr-only.
  • Combine .sr-only with .sr-only-focusable to show the element again when it’s focused (e.g. by a keyboard-only user).
Vernon Fowler

The Same, But Different: Breaking Down Accessibility, Universality, and Inclusion in De... - 0 views

  • One way to put a name to this activity is to say that we are going up the mountain — in other words, moving upward is our goal. Another is to refer to reaching the summit — the destination to which we aspire. The former says, in effect, “We are gradually making our way up the hill.” The latter says, “We’re not done until we get to the top.”
  • Inclusive design is the practice of going up the mountain — we can always look for ways to include more people and situations to our designs, even if the result only gets us a few steps up the trail at a time.
  • I would go so far as to say that it’s the scope of that task — the seemingly infinite nature of including everyone — that is too big of a challenge. We aren’t all born to be mountain climbers. But together we can get a little farther up the hill, if we try.
  •  
    My post on the @adobe blog is up. It's about how I distinguish inclusive design from accessibility, and why you still need to go back and learn about universal design. https://t.co/OsjUp57F29 #a11y #inclusivedesign Great article on the nuances between A11y, Inclusive Design and Universal Design. Thanks @mattmay The Same, But Different: Breaking Down Accessibility, Universality, and Inclusion in Design https://t.co/QJIXT7y96T via @adobe
Vernon Fowler

WebAIM: Keyboard Accessibility - 0 views

  • 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.)
  •  
    "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: Using NVDA to Evaluate Web Accessibility - 0 views

  •  
    "This article is designed to help users who are new to NonVisual Desktop Access (NVDA) learn the basic controls for testing web content, and to serve as a reference for the occasional NVDA user. "
Vernon Fowler

Contrast ratio in devtools - 0 views

  • To enable it (as of August 2017), you need the following steps: Use Chrome CanaryEnable experiments: chrome://flags/#enable-devtools-experiments
  • From devtools, open settings (F1)Open the experiments panelHit shift seven times (no, I'm not kidding)Check the "Color contrast ratio line in color picker"
Vernon Fowler

WebAIM: To ARIA! The Cause of, and Solution to, All Our Accessibility Problems - 0 views

  • this role is often used extraneously (<button role="button">)
  • aria-label can also override other important information such as link text
  • aria-expanded This can tell screen reader users that activating a button or link will cause content to expand and collapse below (e.g., an accordion), and also whether it is currently collapsed or expanded.
Vernon Fowler

Understanding screen reader interaction modes - Tink - 0 views

  • the screen reader intercepts most keypresses before they reach the browser, triggering an interaction with the virtual document instead
  • up/down keys move focus to the previous/next line instead of scrolling the page
  • space key to select a checkbox
  • ...3 more annotations...
  • enter key is used to activate a link
  • Not all keypresses are captured by the screen reader however. When the tab key is pressed it is automatically passed through to the browser where it causes keyboard focus to move to the next piece of interactive content
  • Although this mode switching may seem unintuitive to someone unused to Windows screen readers, it works well in practice and most screen reader users are unaware of what’s happening “under the hood”.
« First ‹ Previous 101 - 120 of 121 Next ›
Showing 20 items per page