ma.gnolia

Sign In | Learn More

Skip to main content


12380_32 Recent Bookmarks in Accessible Web Developers Tagged With "elements"

  1. 12517_32

    Visit Views From a Screen Reader User - Beast-Blog.com Views From a Screen Reader User - Beast-Blog.com

    Based on one screen reader user, a lot of form elements and other abuses can be easily tolerated and survived, but a lot depends on user settings.

  2. 12517_32

    Visit Are Lists Becoming the New Tables? - Beast-Blog.com Are Lists Becoming the New Tables? - Beast-Blog.com

    Misusing specific elements in a way not intended, especially for presentational purposes, while creative and admirable on many levels, simply isn't right. It happened to tables, and now it seems to be happening to lists

  3. 12517_32

    Visit Inaccessible Label-Wrapped Form Inputs - Beast-Blog.com Inaccessible Label-Wrapped Form Inputs - Beast-Blog.com

    Wrapping a form input with its label can have serious consequences affecting Windows Eyes and Mac Safari users. It's best for use a for/id attribute association

  4. 12517_32

    Visit The New Accessigooglability - Beast-Blog.com The New Accessigooglability - Beast-Blog.com

    Accessibility and Googlability combine to form Accessigooglability or Search Engine Accessibility (SEA). Is it a negative thing? It's not perfect, but is it generally good or bad?

  5. 12517_32

    Visit Tips for Keeping Forms Accessible - Beast-Blog.com Tips for Keeping Forms Accessible - Beast-Blog.com

    Forms are accessible if built right. Let's keep them that way. Here are tips for keeping them accessible and progressively enhancing them to accommodate many users

  6. 12517_32

    Visit Accessites.org: Big Red Angry Text (BRAT) Accessites.org: Big Red Angry Text (BRAT)

    Want to keep your web clients from using deprecated elements on your designs? Here's one way that might help keep them on the straight and narrow path.

Didn't find what you were looking for? Try searching Google.