Description
For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies.
*This success criterion is primarily for Web authors who develop or script their own user interface components. For example, standard HTML controls already meet this success criterion when used according to specification.
Questions & Answers
How do I know if my websites structure is laid out correctly?
My page looks good visually, but I am not sure if its structure is laid out properly or if I used the right elements. How am I supposed to know if I've done things the "right" way?
- best practices
- building content
- html
- page structure
Does my site need to be usable if the CSS and javascript doesn’t load?
I've always wondered this but never really known for sure. Let's say none of my CSS or javascript loads. Does the site still need to be usable? I know a lot of really big sites are useless without CSS and javascript so I'm betting the...
- best practices
- CSS
- html
- javascript
- page structure
Is there a form element meant to provide instruction?
I know how to add labels to form inputs to 'label' what they are. I am wondering if there is something similar for describing what a field is in more details? I want to there to be little text under a text field but don't...
- best practices
- form
- html