6 replies to this topic

[tam]

The videos in the article are worth a watch if you've ever wondered about how accessible code actually works for users: http://onemansblog.c...nd-wheelchairs/

[DCrx]

Here's to user testing for determining accessibility compliance.

 

A new day has dawned.

[cre8pc]

Here's to user testing for determining accessibility compliance.

 

I long for the day when every client accepts my recommendation for this.  The all say no, so I slip in a few things into every report anyway.  I've offered accessibility compliance testing for a dozen years and despite explaining why it's needed, site owners don't think they can justify the cost.

[TheAlex]

Thanks, I'll give this a read/watch.

[terriwells]

I'll definitely have to check this out. I've written about usability issues before, but never delved into them very deeply.

[cre8pc]

A usability person!  Yay! Welcome to the forums 

[cre8pc]

There is an update on the use of long descriptions (click on the link to learn more).  The reason for the change is because screen reader software is changing.

 

 

What is the current recommendation for providing long descriptions for complex graphics?

 

In HTML (Hypertext Markup Language), the "longdesc" attribute was specifically designed to allow for long descriptions of complex images. This contrasts with the "alt" attribute, which describes relatively simple images using a minimal amount of text. The "longdesc" attribute allows authors to link to a separate page (for example, longdesc="img1description.html") in which the image is described in detail. This is particularly useful for complex images such as graphs and charts.