The document discusses common mistakes and misconceptions around web accessibility, including providing unnecessary or redundant alt text, overly long alt text descriptions, using images when text would suffice, improperly using tabindex and accesskeys, and prioritizing compliance over usability for those with cognitive disabilities. It also provides tips for proper use of headings, form labels, abbreviations and acronyms, and skip links to improve accessibility.
08448380779 Call Girls In Greater Kailash - I Women Seeking Men
Web Accessibility Gone Wild - 40+ Silly Aspects of Modern Web Accessibility
1. We b A c c e s s i bi l i t y
G o n e W i ld
N o w eve n w i lde r !
Jared Smith & Jon Whiting
http://webaim.org
2. Gone wild?
Mistakes, misconceptions, over-
indulgences, minutia, and generally
silly aspects of modern web
accessibility
... or “How to FAIL at web accessibility”
3. Disclaimers
• There will be controversy and you
may disagree.
• We’ll attempt to be equal
opportunity offenders
• There’s little logic to the sequencing
of topics
4. Survey of screen reader
user preferences
http://webaim.org/projects/screenreadersurvey/
14. alt=”Our business promises the best
service you will find on the
planet. Our team is professionally
trained to offer excellent customer
service throughout the contract
negotiation process. Customer
satisfaction is our top priority
and is guaranteed.”
15. “Describing” images - particularly
decorative images used to
convey mood or feeling.
16. Apple iPhone
alt=”iPhone web site”
Images that have a function MUST have alt text
17. Images that have a function MUST have alt text
alt=”iPhone web site”
36. Text-only alternatives
• Not an excuse for a site that could
otherwise be made accessible
• Only benefits a small number of users
• Native accessibility = text alternative
• Rarely used
41. Tabindex
• tabindex=”1+”
Specifies exact tab order. Ensure tabindex
is complete, logical, and intuitive.
• tabindex=”0”
Place item in the default tab order
• tabindex=”-1”
Do not place in tab order, but allow the
element to programmatically receive
focus
42. Visually hiding content
• display:none AND
visibility:hidden hides from
everyone
• Position off-screen left with CSS for
screen readers
• Use judiciously
43. Skip to content
• Think beyond “screen reader access”
• One link is typically sufficient
• Are headings “a mechanism”?
• Use ARIA landmark roles
51. You don’t need to provide...
• default text in form fields
• printable character between links
• redundant text links for client-side
image maps
52. Acronym and Abbreviation
• Expand in text at first instance OR use
<acronym> or <abbr>.
• It’s not necessary to expand all instances.
• It’s not necessary to expand commonly
known acronyms and abbreviations (for our
web site - HTML, CSS, etc.)
55. Title attribute
• Advisory information only
• Ignored by screen readers, except...
• form elements missing labels
• <frame title=”navigation”>
• <acronym>/<abbr>...usually.
63. Other
• Accessibility statements. Who cares?
• Site maps aren’t typically used
• Design for optimal line length (Jello layouts)
• Provide accurate, descriptive page titles
• You don’t HAVE to check in screen readers
• Don’t provide summary for layout tables
• Use fieldset for grouped radio buttons and
checkboxes
• Layout tables don’t (typically) affect accessibility