Error messages can be problematic to convey consistently to all users across browsers and assistive technology (AT). Using simple HTML, with a little ARIA polyfil magic if you want to get fancy, you can robustly associate error messages with controls and ensure that users get the message every time.
A recent question prompted me to ask whether the SVG <text> element would pass WCAG 2.0 1.4.5 (images of text).
Recent articles by people of TPG:
Jaws (screen reader) uses different keyboard commands for desktops and laptops. This is a short note to explain the difference and how to switch keyboard layout.
The WCAG 2.0 Parsing Criterion is a Pain In The Ass (PITA) because the checking of it throws up lots of potential errors that if required to fix, may result in a lot of extra work (in some cases busy work) for developers. This is largely due to the lack of robust tools for producing […]