Bridgit is a blind mother to a five-year-old girl and an 11-year-old boy:
"There are some things that are just tricky, and then there are things that do not work at all. One thing that often does not work is those drop-downs where you have to search for something. You know, where you type in text and then a list of suggestions pops up, and you have to choose from that list instead of just typing what you want. This happens a lot when I am booking flights. The field where I have to choose which airport I am flying from and to. Sometimes I can type in the text, and the screen reader will tell me there are, say, 3 or 10 results on the list. But I cannot see or select anything from that list. I just get stuck and cannot move forward."
A checkbox is coded using a <div> element, with the role and state of the checkbox added through ARIA attributes. Unfortunately, the attribute that is intended to indicate the state of the checkbox is not a valid ARIA attribute because aria-not-checked is not part of the WAI-ARIA standard.
<div role="checkbox" aria-not-checked="false">Accept terms and conditions.</div>aria-not-checked.A checkbox is coded with a <div> element, with the role and state of the checkbox added through ARIA attributes.
<div role="checkbox" aria-checked="true">Accept terms and conditions.</div>This section provides information on how to identify and fix the issue.
The Acquia Web Governance platform flags instances of attributes that start with aria- but are not defined in the ARIA standard.
You must correct these attributes so that your code only uses valid ARIA attributes as defined in the WAI-ARIA standard
The ACT rules section below includes a link to a complete technical explanation of this check.
Related accessibility conformance testing rules:
If this content did not answer your questions, try searching or contacting our support team for further assistance.
If this content did not answer your questions, try searching or contacting our support team for further assistance.