E-mail List Archives
Re: Testing SC 1.4.12 in multiple browsers
From: Jonathan Avila
Date: Sep 24, 2021 6:09AM
- Next message: wolfgang.berndorfer@zweiterblick.at: "Re: Testing SC 1.4.12 in multiple browsers"
- Previous message: Duff Johnson: "Re: [EXT] does every one else ind tables are problimatic with your clients"
- Next message in Thread: wolfgang.berndorfer@zweiterblick.at: "Re: Testing SC 1.4.12 in multiple browsers"
- Previous message in Thread: glen walker: "Re: Testing SC 1.4.12 in multiple browsers"
- View all messages in this Thread
WCAG does require that criteria be met using accessibility supported methods. The support level depends on the technologies used to claim conformance. While there are many things that can be tested automatically - many incorrect implementations of custom controls and other misuse of ARIA are quickly and clearly shown by use of assistive technology such as screen readers. Not only can these breakages be quickly spotted compared to reading through the DOM but the demonstration of the issue quickly communicates the impact to actual users. Assistive technology cannot be relied upon solely for spotting issues but I find they are often quicker at detecting issues related to custom controls. For example, ability to use combo boxes, menus, etc. with incorrect implementations that work correctly with the keyboard/mouse visually but do not work with screen readers. Links that work with the keyboard and mouse but don't support programmatic activation, etc.
Jonathan
- Next message: wolfgang.berndorfer@zweiterblick.at: "Re: Testing SC 1.4.12 in multiple browsers"
- Previous message: Duff Johnson: "Re: [EXT] does every one else ind tables are problimatic with your clients"
- Next message in Thread: wolfgang.berndorfer@zweiterblick.at: "Re: Testing SC 1.4.12 in multiple browsers"
- Previous message in Thread: glen walker: "Re: Testing SC 1.4.12 in multiple browsers"
- View all messages in this Thread