From 2435afe4e6f329ca567759f7d00890f6d523b35e Mon Sep 17 00:00:00 2001 From: Mark Otto Date: Sun, 24 Dec 2017 20:06:33 -0800 Subject: Move from h4s and misc to h5s so headings from example snippets don't show in our table of contents --- docs/4.0/components/forms.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'docs/4.0/components/forms.md') diff --git a/docs/4.0/components/forms.md b/docs/4.0/components/forms.md index 6ed98c3b7..23350415a 100644 --- a/docs/4.0/components/forms.md +++ b/docs/4.0/components/forms.md @@ -611,7 +611,7 @@ Custom form controls and selects are also supported. {% endexample %} {% callout warning %} -#### Alternatives to hidden labels +##### Alternatives to hidden labels Assistive technologies such as screen readers will have trouble with your forms if you don't include a label for every input. For these inline forms, you can hide the labels using the `.sr-only` class. There are further alternative methods of providing a label for assistive technologies, such as the `aria-label`, `aria-labelledby` or `title` attribute. If none of these are present, assistive technologies may resort to using the `placeholder` attribute, if present, but note that use of `placeholder` as a replacement for other labelling methods is not advised. {% endcallout %} @@ -684,7 +684,7 @@ Add the `disabled` attribute to a `
` to disable all the controls withi {% endexample %} {% callout warning %} -#### Caveat with anchors +##### Caveat with anchors By default, browsers will treat all native form controls (``, `