aboutsummaryrefslogtreecommitdiff
path: root/docs/4.0/components/forms.md
diff options
context:
space:
mode:
authorMark Otto <[email protected]>2017-12-24 20:06:33 -0800
committerMark Otto <[email protected]>2017-12-26 13:18:19 -0800
commit2435afe4e6f329ca567759f7d00890f6d523b35e (patch)
treeecf1c2df66b3f09cf929aac63a889d87c36a271d /docs/4.0/components/forms.md
parent2416801c7ea6e67d728096e0ed74568f6c742fc7 (diff)
downloadbootstrap-2435afe4e6f329ca567759f7d00890f6d523b35e.tar.xz
bootstrap-2435afe4e6f329ca567759f7d00890f6d523b35e.zip
Move from h4s and misc to h5s so headings from example snippets don't show in our table of contents
Diffstat (limited to 'docs/4.0/components/forms.md')
-rw-r--r--docs/4.0/components/forms.md4
1 files changed, 2 insertions, 2 deletions
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 `<fieldset>` to disable all the controls withi
{% endexample %}
{% callout warning %}
-#### Caveat with anchors
+##### Caveat with anchors
By default, browsers will treat all native form controls (`<input>`, `<select>` and `<button>` elements) inside a `<fieldset disabled>` as disabled, preventing both keyboard and mouse interactions on them. However, if your form also includes `<a ... class="btn btn-*">` elements, these will only be given a style of `pointer-events: none`. As noted in the section about [disabled state for buttons]({{ site.baseurl }}/docs/{{ site.docs_version }}/components/buttons/#disabled-state) (and specifically in the sub-section for anchor elements), this CSS property is not yet standardized and isn't fully supported in Opera 18 and below, or in Internet Explorer 10, and won't prevent keyboard users from being able to focus or activate these links. So to be safe, use custom JavaScript to disable such links.
{% endcallout %}