@Rick, I didn't specifically look at doctype, but Steve Faulkner did in his original article (see the link at the top of this post). He found that 101 of the 130 pages containing role="main" (78%) used the HTML5 doctype, which of course leaves 22% that didn't. I do recommend using ARIA even if using an earlier doctype. Validation is important, but if validation and accessibility conflict, I think most would agree accessibility should trump validation. Assistive technologies that support ARIA landmarks do so regardless of doctype, and otherwise the presence of these role attributes has no ill effects in any user agent.
I’ve been able to fix the problem by changing the default-calendar-grid.php file to change the contents of the buttons that they noted above. I ended up replacing the chevron icons in the file with stylized “<” and “>” characters, respectively. This allows a screen reader to see that there is actually content within the button, and furthermore within the table header, and as a result fixes the errors it has with the calendar.
This plug-in has been around for some time. Recently they were even advising users to uninstall the old version and install a new one. The new version comes with Skip menus, a button to reset font size, a Skip link inside the accessibility sidebar, and a DOM scanner that automatically checks pages and published posts for accessibility errors such as issues in image ALT, titles, and links. Contrast adjustment, color filters, lights off mode, and link highlighting are the other standout features.
The Americans with Disabilities Act (ADA) was first passed in 1990. Twenty years later, the US Department of Justice released an update called the 2010 ADA Standards for Accessible Design. These standards cover the design of physical spaces and have been interpreted to include web locations as well, so it can be difficult for the would-be accessible website designer to use them.
Video remote interpreting (VRI) is a fee-based service that uses video conferencing technology to access an off-site interpreter to provide real-time sign language or oral interpreting services for conversations between hearing people and people who are deaf or have hearing loss. The new regulations give covered entities the choice of using VRI or on-site interpreters in situations where either would be effective. VRI can be especially useful in rural areas where on-site interpreters may be difficult to obtain. Additionally, there may be some cost advantages in using VRI in certain circumstances. However, VRI will not be effective in all circumstances. For example, it will not be effective if the person who needs the interpreter has difficulty seeing the screen (either because of vision loss or because he or she cannot be properly positioned to see the screen, because of an injury or other condition). In these circumstances, an on-site interpreter may be required.
The ADA requires that title II entities (State and local governments) and title III entities (businesses and nonprofit organizations that serve the public) communicate effectively with people who have communication disabilities. The goal is to ensure that communication with people with these disabilities is equally effective as communication with people without disabilities.