Skip to main content

Home/ Web Accessibility/ Group items tagged Web

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
Sandra Earl

Forget WYSIWYG editors - use WYSIWYM instead | 456 Berea Street - 0 views

www.456bereastreet.com/...yg_editors_use_wysiwym_instead

accessibility WYSIWYG

shared by Sandra Earl on 12 Oct 10 - Cached
  • A huge problem with almost every CMS in existence is the extremely poor quality of the code produced by their WYSIWYG editors.
  • Since visual gadgetry like WYSIWYG editors sells, every CMS has to have one.
  • That, in turn, makes it necessary for Web professionals who want to reduce the risk of clients unknowingly ruining the website’s semantics and accessibility to disable features and implement more or less advanced code cleaning procedures. It is a mess.
  • ...4 more annotations...
  • Because of the problems caused by WYSIWYG editors I have toyed with the idea of providing a much simpler interface for content editors. Markdown, BBCode, and Textile are a few possible solutions that ensure valid markup and increase the likelihood of it being semantic. The problem would be making clients accept working that way, directly editing pseudo markup. Most clients wouldn’t, so that option is ruled out.
  • But there is another kind of editor that is better suited than WYSIWYG for content-driven, client-edited sites - the WYSIWYM (What You See Is What You Mean) editor. In Visually Editing Semantics - What You See Is What You Mean, Peter Krantz mentions one such editor: WYMeditor.
  • From the WYMeditor site: Our goal is to create a XHTML strict web-based editor which will be usable on many platforms, whith the help of the Open Source Community.
  • There are a few limitations, of course. This is an early version, after all. Besides the issues Peter notes in his post about WYMeditor, here are a few more things I noticed: Table accessibility. There is no way to add elements and attributes (th, caption, scope, etc) needed for accessibility to data tables. Table resizing. It is possible to size tables by dragging handles. Doing so is reflected in the markup. That needs to be filtered out at some stage before saving the page to the database. Incorrect nesting of lists. When you create nested lists, the current list element is closed before the next level ul or ol is inserted.
Sandra Earl

Introduction to screen readers and screen magnifiers | 456 Berea Street - 0 views

www.456bereastreet.com/..._readers_and_screen_magnifiers

accessibility screen reader general resources FUSION09

shared by Sandra Earl on 12 Oct 10 - Cached
  • And that leads me to three great videos posted on the Yahoo! User Interface Blog: In Introduction to Screen Readers, Yahoo! engineer Victor Tsaran talks about who will be likely to use a screen reader, how screen readers work, and how they can be used to interact with the computer desktop and to browse web sites. In Introduction to Screen Magnifiers, Karo Caran shows how the screen magnifier ZoomText is used to make the computer desktop and web sites readable to people with reduced vision. And finally, in From the Mouth of a Screenreader, Doug Geoffray from GW Micro (Window-Eyes vendor) talks about the history of screen reading software and how they analyse what is displayed on the screen in order to speak it to the user.
Vernon Fowler

WebAIM: Web Accessibility Gone Wild - Now even wilder! - 0 views

webaim.org/gonewild

accessibility web

shared by Vernon Fowler on 07 Jan 14 - No Cached
  • The title attribute, by definition, can be used to provide advisory information. It should: NOT provide vital information or information necessary for accessibility. NOT provide the same information as is available in text or alternative text. NOT present the obvious. If the advisory title does not provide additional, useful information, it can be removed.
Vernon Fowler

Customise radio buttons without compromising accessibility - 0 views

www.chenhuijing.com/...out-compromising-accessibility

accessibility webdesign input buttons inclusivedesign

shared by Vernon Fowler on 16 Sep 18 - No Cached
  • go with option 3, a good ole’ opacity: 0 coupled with a position: absolute. Hidden but still focusable, well-supported across browsers. Just what we’re looking for.
  • opacity: 0
  • the label has to come after the input element in the source order
  • ...1 more annotation...
  • sad state of affairs when it comes to browser support for clip-path.
  • Vernon Fowler on 16 Sep 18
     
    "Customised radio buttons and checkboxes are a common design pattern found on the web, and it doesn't take too much to ensure that your beautifully designed toggles are still navigable via keyboard."
Vernon Fowler

Tanaguru Contrast-Finder - 0 views

contrast-finder.tanaguru.com

accessibility contrast color colors tools WCAG wcag2 colour tool testing design

shared by Vernon Fowler on 04 Aug 17 - No Cached
  • Vernon Fowler on 04 Aug 17
     
    "Find me the good constrasts, for web accessibility, between these two colors"
Sandra Earl

50+ Readability Resources Related To Cognitive Web Accessibility « Clear Helper - 2 views

clearhelper.wordpress.com/...to-cognitive-web-accessibility

cognitive readability resources reading accessibility

shared by Sandra Earl on 12 Oct 10 - Cached
  • shereekrause on 12 Mar 22
     
    Thanks for sharing these! Great resource!
Vernon Fowler

In Search Of The Perfect CAPTCHA | Smashing Coding - 0 views

coding.smashingmagazine.com/...-search-of-the-perfect-captcha

captcha development accessibility web webdesign usability

shared by Vernon Fowler on 28 Apr 13 - No Cached
  • Try the honeypot method or another that is invisible to users. Some could potentially be bypassed, but their presence is often enough to thwart automated efforts.
« First ‹ Previous 61 - 80 of 154 Next › Last »
Showing 20▼ items per page