This is how it has been for as long as I can remember. For example, you might need to present a text-style setting that turns all styles on or off, but also lets people choose a subset of individual style settings like bold, italic, or . Regarding the focus issue, generally it is not a good idea to allow visible disabled elements to gain focus - focus implies the possibility of interaction. Single checkboxes or basic radio buttons that make sense from their labels alone do not require fieldset and legend. A sighted keyboard user must be provided with a visual indicator of the element that currently has keyboard focus. In this case it is an uninstall dialog (the first program I could find to try it on). Navigation order should be logical and intuitive. You could certainly use an SVG icon in this case tooIll leave that as homework for you! There are some types of user interface components that, when represented in a platform accessibility API, can only contain text. WebAIM: Creating Accessible Forms - Accessible Form Controls To do so, we would place theSVG inside the label: In most cases SVG is just decorative, soaria-hidden="true"hides it from AT devices. Additionally, since the elements become immutable, most other attributes, such as pattern, have no effect, until the control is enabled. For most pages this means header first, then main navigation, then page navigation (if present), and finally the footer. One common use of a tri-state checkbox can be found in software installers where a single tri-state checkbox is used to represent and control the state of an entire group of install options. When a supporting element has the disabled attribute applied, the :disabled pseudo-class also applies to it. and Layout Design. How about saving the world? The first thing I want to do is make sure that I create a pseudo-element that can act in place of my checkbox. From the question title, I had expected a concrete benefit for accessibility (possibly even for the kind of accessibility for disabled people, such as screenreaders that provide information on the focused element). Step 4: Adding the focus styles to make the checkbox accessible. Firefox will, unlike other browsers, persist the dynamic disabled state of a