YouTube Annotations, round 2
Made a few changes to the annotations script.
For now, I've scrapped the overlayed annotations since it was just too buggy and unstable. It didn't work reliably in enough browsers for it to be worthwhile and it was pretty meaningless anyway.
The script now adds a hidden form field which is updated with the current annotation text every time an annotation is added or removed. This should help screen readers know that something changed, I've been told. However, I'm not sure how to handle multiple overlapping annotations, since you wouldn't want the same text read again just because a second annotation is shown. As it is now, all "active" annotations are put in the same form field. Maybe it needs a whole bunch of hidden fields?
For now, I've scrapped the overlayed annotations since it was just too buggy and unstable. It didn't work reliably in enough browsers for it to be worthwhile and it was pretty meaningless anyway.
The script now adds a hidden form field which is updated with the current annotation text every time an annotation is added or removed. This should help screen readers know that something changed, I've been told. However, I'm not sure how to handle multiple overlapping annotations, since you wouldn't want the same text read again just because a second annotation is shown. As it is now, all "active" annotations are put in the same form field. Maybe it needs a whole bunch of hidden fields?
Wouldn't it be better to just use an assertive ARIA live region?
June 7, 2008 at 12:34 PM Jacob SeidelinMaybe it would. I don't know much about ARIA, but I'll check it out.
June 7, 2008 at 2:30 PM