Tests to determine how form controls and their associated labels/legends are announced. In some cases, the form element does not require or should not have a label.
Tests to determine how help text and error messages can be associated with form controls.
Tests to determine how nested fieldsets are announced.
Tests to determine how "required", "aria-required" and other related options are announced.
The purpose these tests is to show the cascade order of how accessible names are applied in the accessibility tree for buttons and inputs. These examples should not be considered proper practice.
Tests to determine how the "aria-invalid" attribute is announced.
Tests to determine how "max", "aria-valuemax", "min", "aria-valuemin", "maxlength", "minlength", "multiple" and "pattern" attributes are announced.
Tests to determine how the boolean "disabled" attribute is announced. Disabled attributes cannot receive focus, so the only way to test how these attributes are announced is via:
OSX Catalina - 10.15.7
Windows 10 Enterprise: