You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One example I have found is that the "Menu" button for the boston.gov site is not labelled as a button or a link by ANDI in the lANDI module. It is a label element connected to an input element by its for attribute. The input element contains a type of checkbox. I think that it should be labelled as a button.
A list of things that were said to be able to be buttons are:
details tag: specifies additional details that the user can open and close
on demand
An input element whose type attribute is in one of the Submit Button,
Reset Button, Image Button, Button, Radio Button, or Checkbox states
defines a command.
NOTE: This is described in the example above.
An option element with an ancestor select element and either no value
attribute or a value attribute that is not the empty string defines a command.
A label element that has an assigned access key and a labeled control and whose
labeled control defines a command, itself defines a command.
A legend element that has an assigned access key and is a child of a fieldset
element that has a descendant that is not a descendant of the legend element
and is neither a label element nor a legend element but that defines a command,
itself defines a command.
An element that has an assigned access key defines a command.
IANDI.js defines a button as an element that passes this if statement: "if($(this).isSemantically(["button"],"button,:button,:submit,:reset,:image"))"
The w3c site has these links that also define ways to get interactive elements on the site:
The text was updated successfully, but these errors were encountered: